Partner One ID, MPN ID, location ID, seller ID. They are not the same thing, and using the wrong one is the quietest way to lose attribution, incentives and designation progress.
Microsoft renamed the MPN ID to the Partner One ID when the Microsoft Partner Network became the Microsoft AI Cloud Partner Program. The number itself did not change. What did change is the labelling, which is now inconsistent: Partner Center calls it the Partner One ID, while several Azure portal screens and older documentation still say MPN ID. If a form asks for either, it wants the same value.
The real trap is the difference between the global ID and location IDs. Large partners have one global Partner One ID and many location IDs, and the two are used in different places.
The top-level identifier for your partner organisation, formerly known as the MPN ID or partner global ID. This is the one used for PAL, designations and most incentive reporting.
A separate ID for each registered business location under your global account. Used for CSP transactions, some incentive payout setups and certain marketplace and co-sell records.
Not a partner ID at all, but often confused with one. It identifies your Microsoft Entra tenant, not your standing in the partner program.
Used for Microsoft Marketplace publishing and co-sell records. Linked to your partner account but distinct from the Partner One ID.
One number, a lot of places. Getting it consistent across all of them is usually the first fix we make on a Partner Center Health Check.
A Microsoft Partner ID is the numeric identifier Microsoft uses to recognise your partner organisation across its programs. The top-level one is now called the Partner One ID, and it was previously known as the MPN ID.
Yes, for practical purposes. Microsoft renamed the MPN ID to the Partner One ID as part of the move to the Microsoft AI Cloud Partner Program. The value itself did not change, and plenty of Azure portal screens and documentation still use the older label.
In Partner Center, under your account settings and legal or identity information. The global ID sits at the top of the account; location IDs are listed separately against each registered business location.
For PAL and attribution, use the global Partner One ID unless Microsoft explicitly asks for a location ID. Mixing the two is one of the most common reasons partner reporting looks fragmented across entities.
The activity still happens, it just gets attributed somewhere you are not looking, or to a different legal entity. Fixing it is straightforward, but the attribution is not backdated once corrected.
We'll check how your Partner One ID and location IDs are used across PAL, incentives, marketplace and co-sell, and untangle anything that's attributing to the wrong place.