Azure-docs: Add Troubleshooting steps for UnableToAddPublisher error message

[JamesTran-MSFT]

Based off these GitHub and Q&A issues:

GitHub - https://github.com/MicrosoftDocs/azure-docs/issues/62877
Q&A - https://docs.microsoft.com/en-us/answers/questions/167247/index.html

It seems that there's a trend where customer's can't add a publisher to their App registrations following the documentation.

Error:
"code": "UnableToAddPublisher",
"message": "A verified publisher cannot be added to this application. Please contact your administrator for assistance.",

Currently there's a solution that seems to keep working, so I'd like to purpose this be added to the troubleshooting documentation.

Proposed change/resolution:
Wait 48hrs and retry operation

Any questions, please let me know.
Thank you!

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: df11cb03-70da-7df3-4941-3c2f8ea022f8
• Version Independent ID: 96cd8eec-ed94-05bf-1288-86b6ef3db105
• Content: Troubleshoot publisher verification - Microsoft identity platform
• Content Source: articles/active-directory/develop/troubleshoot-publisher-verification.md
• Service: active-directory
• Sub-service: develop
• GitHub Login: @rwike77
• Microsoft Alias: ryanwi

[JamesTran-MSFT]

@rwike77
I created this issue so we can address the MPN ID issue, please review and update as necessary!

If you have any questions, please let me know.
Thank you!

[aditrades]

Also getting:
A verified publisher cannot be added to this application. Please contact your administrator for assistance. [lB+9bPoGdscYk+9kqjzDJo]
😢

[aditrades]

@JamesTran-MSFT
Any ETA for solving this issue?

[jezell]

Waiting 48 hours does not seem to work. We have been experiencing this issue for over a week and have been unable to add a verified publisher.

[BBrukner]

Same experience as jezell. We have waited a week and have the same issue as we initially had "You are unable to add a verified publisher to this application. Please contact your administrator for assistance. [KJX/8gto677Fyq8JM7vFls]"

[JamesTran-MSFT]

Hi all,

As of right now, this problem appears to be caused by a known issue that engineering is working to resolve. We don’t have a specific ETA yet, but are hoping to have one soon.

[AquanPJCA]

Any workaround for this in the meantime?

[oliviomouraoutsystems]

Same here:
A verified publisher cannot be added to this application. Please contact your administrator for assistance. [ppUQBIBP3d6UDcZ+4pOP5y]

[aditrades]

@JamesTran-MSFT Can Microsoft at least remove the requirement for MPN for opening applications?
2020 was already a weak year in terms of sales, now it's december (The strongest sales months) and this requirement is blocking us from selling to some strategic clients.

[BBrukner]

@JamesTran-MSFT - echoing others in the chat, can the requirement for MPN be removed, at least until the feature is stable, to enable us to achieve business requirements dependent on this?
We have an open support case for over 1 week being moved to different teams, can you suggest the team to be assigned on this request to facilitate a workaround or permanent solution for this bug?
Case # 120120224003327

[Wtrapp]

+1 same issue. Support is no help. MPN support says it's an Azure problem. Azure support says it's a MPN problem.

[oliviomouraoutsystems]

Just tried again, it worked now, 48 hours after.

[BBrukner]

Just tried again, it worked now, 48 hours after.

@oliviomouraoutsystems I wish I could say the same. We've been trying for 10 days and still same error. Glad it worked out for you.

@JamesTran-MSFT Any insight on the issue or ETA for a fix or workaround?

[BBrukner]

Just tried again, it worked now, 48 hours after.

@oliviomouraoutsystems I wish I could say the same. We've been trying for 10 days and still same error. Glad it worked out for you.

@JamesTran-MSFT Any insight on the issue or ETA for a fix or workaround?

After 14 days it is now working for us, 4 days after our ticket was moved to be reviewed by the back-end team. Unfortunately we have no clarity on what caused the issue to be resolved after this time to share with others at this time.