MPN is verified but not accepted in App registration

Question

My MPN ID is already verified (6542504) but when registering an app it always say the follow error "The MPN ID you provided (6542504) does not exist, or you do not have access to it. Please provide a valid MPN ID and try again. Click for additional information.". we have already checked the prerequisites and followed them. Is there any way how can we check further the errors why it doesn't us allow to use that MPN ID? A step by step instruction would really be great. Thanks!

Answer 1

Hi @techmaster ,

I understand that you have verified your MPN but are having trouble getting your MPN accepted in the app registration and are receiving the error:

"The MPN ID you provided (xxxxxx) does not exist, or you do not have access to it. Please provide a valid MPN ID and try again. Click for additional information."

This error often occurs when the signed-in user not a member of the proper role for the MPN account in Partner Center. In Azure AD this user must be a member of one of the following roles: Application Admin, Cloud Application Admin, or Global Admin. In the Partner Center this user must have of the following roles: MPN Admin, Accounts Admin, or a Global Admin.

This error can also occur if the tenant the app is registered in is not added to the MPN account, or there is an invalid MPN ID. The troubleshooting steps for this scenario are covered here.

I would confirm that your MPN associated with Azure AD and the current directory are same, as you cannot associate an MPN with different directory other than one approved.

As long as you created the App Registration where the domain is primary domain (used to verify MPN ID in the Partner Center), and granted sufficient rights for the user who is trying to add MPN ID to Application (the right role and MFA enabled, if that is required), you should be able to resolve this issue.

I don't think this applies to your situation based on the error message you included, but I will also note that you can get blocked if your account has been identified as a "risky user." If the user is on the “risky users” list, you or your admin may need to perform remediation steps to eliminate user risk. Reference: Remediate risks and unblock users in Azure AD Identity Protection | Microsoft Learn. After remediating, it will take several hours to invoke dismiss process in our backend, and then you can try adding the MPN ID again.

Please let me know if you have any further questions.

-

If this answer was helpful to you, please consider "marking as answer" so that others in the community with similar issues can more easily find a solution.