Moving a verified Entra application publisher to a new legal entity

Publisher verification is tied to:

1. The verified Microsoft AI Cloud Partner Program / Microsoft Partner Network (MPN/CPP) account (the legal entity Microsoft has verified), and
2. The app registration in a specific Microsoft Entra tenant, including its verified publisher domain.

From the provided information:

• To be a verified publisher, the company identity must be verified in Partner Center and associated with the app registration.
• Publisher verification shows that Microsoft has verified the entity behind the domain and tenant as authentic, and the verified badge is based on that association.
• Guidance describes how to verify a company identity and then associate that verified PartnerID with an app registration, but it does not describe any supported process to “migrate” or “transfer” an existing verified publisher identity from one legal entity (or PartnerID) to another.

Therefore, based only on the available documentation, the supported pattern is:

• New legal entity B must have its own verified Partner account and verified publisher domain.
• Apps that should appear as published by entity B must be associated with B’s verified PartnerID and domain via the normal publisher verification process.

The documentation does not provide a mechanism to move or reassign an existing verified publisher identity from entity A to entity B; instead, entity B must complete its own verification and association for the relevant app registrations.

References:

• Publisher verification
• Integrate applications with Microsoft Entra ID and the Microsoft identity platform
• Use Microsoft Entra work and school accounts for B2B collaboration
• Use Microsoft accounts (MSA) for B2B collaboration
• Establish applications in the Microsoft Entra ID ecosystem