Partner Admin Link is the cheapest Azure growth lever a Microsoft partner has, and the one most often half-implemented. This guide covers what to tag, who does it, and how to check it is actually working.
PAL tagging links your Partner One ID to the identities your team uses inside a customer's Azure tenant. Once the link exists, Microsoft attributes the Azure consumption those identities can see back to your organisation. That attributed consumption is what drives your Azure performance metrics in Partner Center, your Solutions Partner designation scores and your eligibility for several incentive programs.
It costs nothing, it changes nothing for the customer, and it takes a couple of minutes per identity. The reason partners still lose money on it is that tagging is treated as a one-off task rather than something built into how consultants are onboarded onto customer accounts.

Every tag points at a single Partner One ID (the identifier previously called the MPN ID). Take it from the account settings area of Partner Center and make sure everyone tagging uses the same one, not a location-level ID from a different legal entity.
PAL tags the identity your team uses inside the customer's Azure tenant, not the subscription itself. Any user account, guest account or service principal your consultants and managed services team use to administer customer Azure resources should carry the tag.
Sign in as the customer-facing identity and link the Partner One ID from the Azure portal, Azure CLI (az managementpartner create) or PowerShell (New-AzManagementPartner). The tag is applied per identity per tenant, so repeat it for every account that holds access.
PAL only attributes consumption the tagged identity has permission over. Reader on the subscription or resource group is the minimum. If the access is removed, the attribution stops from that day forward.
Attributed consumption shows up in the Partner Center insights reporting within a few days. If a customer never appears, the usual cause is an untagged identity, the wrong Partner One ID or access that was granted and then revoked.
Almost every PAL gap we find in a Partner Center Health Check comes down to one of these six things.
PAL tagging is the act of linking your Partner One ID to an identity that has access to a customer's Azure environment, so Microsoft can attribute that customer's Azure consumption and influence to your partner organisation. PAL stands for Partner Admin Link.
No. PAL does not change the customer's billing, their agreement or their access. It is a reporting and attribution mechanism only, and it does not give you any additional permissions in their tenant.
All of them. Every user, guest and service principal your business uses to administer a customer's Azure resources should carry the tag. Attribution is calculated from the access those identities hold, so a partially tagged team reports partial consumption.
No. Consumption is attributed from the point the tag exists alongside valid access. This is why partners who tag late almost always understate their real Azure influence for that fiscal year.
In Partner Center insights, and from there it feeds the performance component of your Solutions Partner designation scores and several Microsoft Commerce Incentives programs.
We'll review which customers you're attributing today, find the tenants and identities you're missing, and give you a plan to close the gap before the end of the fiscal year.