Not able to add MPN ID to App registration

Karsten Borsch 16 Reputation points
2022-03-08T07:55:22.107+00:00

Hi all,

when i am trying to add our MPN ID to an App that we have created ("Azure Active Directory" > "App registrations" > app > Branding -> "Add MPN ID to verify publisher")

I get the following error message:

A verified publisher cannot be added to this application. Please contact your administrator for assistance.

No further information available.

Even after waiting for 5 days I still get the message.

I have checked all preconditions mentionedn in https://learn.microsoft.com/de-de/azure/active-directory/develop/mark-app-as-publisher-verified

I also have tried most of the advices which i have found like logging of in all browser sessions, wait a few days, and so on ... but nothing helped.

The Problem also occurs if i add a new app via azure and try to connect it to our MPN ID.

Do you have any further advices for me to resolve the issue?

Please let me know how I can add the MPD ID to the App registration?

Thanks in advance,

Karsten

Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
19,619 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Karsten Borsch 16 Reputation points
    2022-03-16T06:13:58.17+00:00

    Dear James,

    thank you for your reply and my apologies for the delayed reply. I was out of the office for some days.

    I have checked (and listed) all of the points from the link you provided:

    • An MPN ID for a valid Microsoft Partner Network account that has completed the verification process. This MPN account must be the Partner global account (PGA) for your organization.
      -> I have checked the MPN ID. For the App registration i have tried the global and also a local MPN ID. Both didn´t work. Using the global ID results in the error from my original post
    • An app registered in an Azure AD tenant, with a Publisher Domain configured.
      -> The APP is registred in a teanent with a registred public domain
    • The domain of the email address used during MPN account verification must either match the publisher domain configured on the app or a DNS-verified custom domain added to the Azure AD tenant.
      -> The domain of the email address matches the one from the MPN account verification
    • The user performing verification must be authorized to make changes to both the app registration in Azure AD and the MPN account in Partner Center.
      -> The user (me) is global admin in the Azure AD and has also the rights in the MPN to make changes to the Partner Centre
    • In Azure AD this user must be a member of one of the following roles: Application Admin, Cloud Application Admin, or Global Admin.
      -> The user (me) is global admin in the Azure AD
    • In Partner Center this user must have of the following roles: MPN Admin, Accounts Admin, or a Global Admin (this is a shared role mastered in Azure AD).
      -> The user (me) is global admin in the Partner Centre. I Also added the other Admin Rights which didn´t help so far.
    • The user performing verification must sign in using multifactor authentication.
      -> The user (me) is set to mfa
    • The publisher agrees to the Microsoft identity platform for developers Terms of Use.
      -> The Cehckbox is checked during the process of registering the app (if this is meant by this point)

    The App registration still does not work (checked a minute ago). Do you have any further advices / assistance for me since we need to register / sign the APP for multi teanant use and can not provide it to our customer / assosiated.

    I´m realy hoping that you can help me with this, since it seems, that we can not solve the issue on our own.

    If you need any further information, please let me know.

    With kind regards,
    Karsten

    1 person found this answer helpful.

  2. JamesTran-MSFT 36,376 Reputation points Microsoft Employee
    2022-03-16T21:12:30.6+00:00

    @Karsten Borsch
    Thank you for the detailed follow up on this!

    Based off your error and since you confirmed all the pre-requisites have been met, can you try adding your verified publisher using another user (either existing or newly created user) with similar permissions, to see if that helps resolve your issue.

    Similar Issues:
    https://learn.microsoft.com/en-us/answers/questions/446540/index.html
    https://github.com/MicrosoftDocs/azure-docs/issues/62877

    If this doesn't work and you're still having issues, please let me know.
    Thank you for your time and patience throughout this issue.

    1 person found this answer helpful.