This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(249.60000000000002, 98%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETM%3C/text%3E%3C/svg%3E)
I am attempting to register an application for use by multiple clients who are hosting their own AD in Azure. These customers follow a SAML2 workflow utilizing their own IDp to authorize/identify a user prior to being sent over to our application. as a result documentation says we must associate an MPN ID to be a verified publisher.
"Starting November 9th, 2020 end users will no longer be able to grant consent to newly registered multitenant apps without verified publishers."
As I understand it, this terminology is wrong, and its no longer called MPN ID, its a Global Partner ID. I created a profile and paid the $99 registration fee and have an active status within the Microsoft Partner Network, but every time I try to validate the MPN ID an error message is displayed saying: "The MPN ID you provided (xxxxxxxx) does not exist, or you do not have access to it."