Unable to add MPN. I have tried as the GA and as the Partner Center GA neither work.

Marcus Thompson 20 Reputation points
2025-03-10T16:16:44.87+00:00

Unable to add MPN. I have tried as the GA and as the Partner Center GA neither work.

When I try to add my ID in app registration I get a message that it does not exist or I don't have access.

As a result I added the Partner Center Admin to my Azure Tenant and gave it global access, since I could not create a partner ID with my Azure GA for some reason. The Legal info in the Partner Center all looks good except for the Developer tab which is a separate issue that I can't seem to resolve either.

Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
23,621 questions
0 comments No comments
{count} votes

Accepted answer
  1. Sakshi Devkante 1,485 Reputation points Microsoft External Staff
    2025-03-12T13:00:19.4633333+00:00

    Hello Marcus,

    Issue: Unable to add MPN.

    Error: The MPN ID you provided does not exist, or you do not have access to it. Please provide a valid MPN ID and try again

    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. See requirements for a list of eligible roles and common issues.

    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.

    Confirm that your MPN associated with Entra ID 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.

    I hope this clarifies things.

    Please remember to "Accept Answer", so that others in the community facing similar issues can easily find the answers.


0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.