Cannot connect MPN ID to App Registration, HELP!

The error in the screenshot indicates that the Partner One ID (MPN ID) either does not exist or the signed‑in user does not have access to it. This maps to the MPNAccountNotFoundOrNoAccess / MPNAccountInvalid family of errors in publisher verification.

Follow these steps end‑to‑end to fix the issue and then retry connecting the MPN ID to the app registration:

1. Verify the exact Partner One ID (MPN ID)
   1. Go to the partner profile Identifiers blade: Partner profile → Identifiers → Microsoft Cloud Partners Program tab.
   2. Confirm that the ID being entered in Entra is the PartnerGlobal Partner One ID, not a Partner Location Account (PLA) or any other ID.
   3. If the ID being used is not of type PartnerGlobal, switch to the PartnerGlobal ID and use that value when connecting the MPN ID.
2. Confirm the account is vetted and active
   1. In the same partner profile page, check that there are no errors or pending actions.
   2. Ensure the Legal business profile and Partner info both show authorized or success.
   3. If vetting is incomplete, follow the pending action items and the guidance under verification responses, then retry.
3. Confirm tenant association
   1. Open the CPP tenant management page.
   2. Verify that the Microsoft Entra tenant where the app is registered is listed as an associated tenant.
   3. If it is missing, add the tenant according to the multi‑tenant‑account instructions, then retry the verification.
4. Confirm the user’s role and access
   1. On the CPP User Management page, locate the user account being used to perform publisher verification.
   2. Ensure this user is assigned one of the required roles: Global Administrator, MPN Admin, or Accounts Admin.
   3. If necessary, have an existing admin assign the appropriate role and then retry.
5. Retry publisher verification
   1. After confirming the correct PartnerGlobal ID, successful vetting, tenant association, and user role, go back to the app registration’s publisher verification flow.
   2. Enter the same PartnerGlobal ID exactly as shown in the Identifiers blade and submit again.

If the error persists after these checks, the guidance is to open a support ticket with Partner Center and reference that the correct PartnerGlobal ID, vetted account, associated tenant, and eligible role are already in place.

References:

• Troubleshoot publisher verification