1. Why Attribution Is the Foundation of Everything
Microsoft cannot reward what it cannot see. Every partner incentive — from Azure Consumed Revenue (ACR) credit to Solutions Partner designations to ECIF funding — requires Microsoft to know which partner did the work. That's what attribution does: it connects your partner ID to the customer environments where you deliver value.
Without proper attribution, you're building on sand. Your consultants can deliver transformational Azure projects, migrate entire data estates, and deploy enterprise security solutions — but if Microsoft doesn't know it was you, none of it counts toward your Partner Capability Score, your designation progress, or your incentive eligibility.
A partner with 10 consultants each managing $50K/year in Azure workloads — without PAL established — loses visibility on $500K in annual ACR. That's zero credit toward Solutions Partner designation, zero progress on Advanced Specialization qualification, and for CSP partners, approximately $75K in missed Partner Earned Credit annually.
Microsoft provides three attribution mechanisms, each designed for different scenarios. The mistake most partners make is using only one and assuming it covers everything. It doesn't. Here's how they differ — and when to use each.
2. The Three Attribution Methods Compared
| Dimension | PAL | DPOR | CPOR |
|---|---|---|---|
| Full Name | Partner Admin Link | Digital Partner of Record | Claiming Partner of Record |
| Who Sets It Up | Partner (self-service) | Customer (in Azure portal) | Partner (claims in Partner Center) |
| Scope | User account level | Subscription level | Workload level |
| Multiple Partners? | Yes ✓ | No — 1 per subscription | Yes ✓ |
| Agreement Types | MCA, Web Direct, EA | EA only | All agreement types |
| Best For | Azure resource work | Legacy EA subscriptions | M365, Security, Biz Apps |
| Tracking | Automatic (RBAC-based) | Manual (customer sets) | Claim-based (PoE required) |
| Customer Visibility | Cannot see or remove it | Full control to change | Receives notification |
| Transfers on Migration | Yes (stays with account) | No — lost on EA→MCA | Yes (workload-based) |
| PCS Contribution | Data & AI, Infrastructure, Digital & App Innovation, Security, Biz Apps | Same + Modern Work | Modern Work, Security, Biz Apps |
| Incentive Eligibility | Yes (ACR-based programs) | Yes (subscription-based) | Yes (workload-based + usage) |
Attribution isn't a one-time checkbox — it's an ongoing discipline. The partners who consistently earn incentives treat it like a process, not an afterthought. Every new consultant, every new customer environment, every contract renewal is an attribution event.
3. PAL — Partner Admin Link (The Azure Workhorse)
PAL is the most important attribution mechanism for partners doing Azure work. It's automatic, invisible to customers, and works across all agreement types. Once your consultant links their MPN ID to their Azure credentials, every resource they touch gets attributed to your organization — without the customer lifting a finger.
How PAL Works
PAL connects your Partner Location ID (PLA) to a user account or service principal in the customer's Azure environment. Microsoft then measures the Azure Consumed Revenue (ACR) within whatever scope that account has access to — subscription, resource group, or individual resource.
If your consultant has Contributor access at the subscription level, you get ACR credit for the entire subscription. If they only have access to a specific resource group, you only get credit for resources in that group. Negotiate the broadest access possible during onboarding.
Setting Up PAL — Step by Step
Get RBAC Access in Customer's Azure
Your customer grants your consultant a role — Owner, Contributor, or a custom role with write access. This should happen as part of standard engagement onboarding, not as a separate ask.
Sign into the Azure Portal
Your consultant signs in with the credentials that have access to the customer's environment. Navigate to Cost Management + Billing → Link to a partner ID.
Enter Your Partner Location ID
Enter your 7-digit Partner Location ID (PLA — not your PGA). This is the location-specific ID from Partner Center, found under Account Settings → Identifiers.
Click "Link a Partner ID"
That's it. PAL automatically tracks everything from this point forward. The customer cannot see this link and cannot remove it — only the partner user can modify their own PAL.
Verify in Partner Center
Within 24-72 hours, check Partner Center → Insights → Cloud Product Performance. Select "Partner Admin Link" as the attribution type. Your customer's ACR should appear.
PIE eliminates all 5 steps above. Your admin generates a magic link for each consultant in Partner Admin Link. The consultant clicks it, OAuth fires, and PAL is established — no portal navigation, no training, no missed environments. Bulk send to your entire team in one click. See it in action
PEC-Eligible RBAC Roles
For CSP partners, Partner Earned Credit (PEC) provides up to 15% back on Azure consumption. But not all roles qualify:
| Azure RBAC Role | ACR Attribution | PEC Eligible (15%) |
|---|---|---|
| Owner | Yes ✓ | Yes ✓ |
| Contributor | Yes ✓ | Yes ✓ |
| Reader | Yes ✓ | No ✗ |
| User Access Administrator | Yes ✓ | No ✗ |
| Custom (with write) | Yes ✓ | Yes ✓ |
Partner Earned Credit is specifically a CSP program benefit. It is not a universal benefit of PAL. For non-CSP partners (the majority of Microsoft's 400,000 partners), PAL's value is ACR attribution → designation scoring → Advanced Specialization qualification → incentive program eligibility. Don't position PEC as guaranteed for all partners.
4. DPOR — Digital Partner of Record (The Legacy Mechanism)
DPOR predates both PAL and CPOR. It associates one servicing partner with a customer's Microsoft cloud subscription — but the customer, not the partner, must set it up. Originally created for Enterprise Agreement (EA) contracts, DPOR is still relevant for partners with EA customers but carries significant limitations.
Key Limitations
- One partner per subscription. If your customer works with three partners on one subscription, only one gets DPOR credit. The rest are invisible.
- Customer must initiate. You can ask, but the customer has to log into the Azure portal and add your MPN ID. Many forget — or don't know they should.
- Doesn't survive EA→MCA migration. When a customer moves from Enterprise Agreement to Microsoft Customer Agreement, DPOR is lost. You must re-establish attribution, and PAL is the recommended replacement for MCA.
Setting Up DPOR
Customer Signs into Azure Portal
The customer (must be subscription admin or owner) navigates to Subscriptions → [Select Subscription] → Partner Information.
Customer Enters Your MPN ID
They enter your Partner Location ID (PLA) in the partner field and click Save. Only the subscription owner or administrator role can do this.
Verify in Partner Center
Check Partner Center → Insights with DPOR as the attribution type. Attribution appears within one billing cycle.
DPOR still counts toward Partner Capability Score for Modern Work — an area where PAL alone doesn't contribute. If your customer is on EA and you're pursuing Modern Work designation, ask them to set DPOR. For Azure-only work on MCA, PAL is the better choice.
5. CPOR — Claiming Partner of Record (The Modern Standard)
CPOR was introduced in October 2019 to solve DPOR's biggest problems: single-partner limitation and customer dependency. With CPOR, you — the partner — submit a claim in Partner Center that says "we deployed Teams for this customer" or "we drove Security adoption." Multiple partners can claim the same customer, and the claim is workload-specific rather than subscription-wide.
CPOR Advantages Over DPOR
- Partner-initiated. You don't wait for the customer to do anything. You claim the association yourself in Partner Center.
- Multiple partners supported. Three different partners can each get credit for different workloads on the same customer — reflecting how real engagements work.
- Workload-level granularity. Instead of an entire subscription, CPOR ties to specific workloads: Teams, Security, Power Platform, Dynamics 365, etc.
- Incentive-eligible. CPOR claims can earn incentives for deployment, usage, and adoption programs — with Proof of Execution (PoE) required for incentivized workloads.
CPOR Association Types
| Association Type | Purpose | Earns Incentives? | PoE Required? |
|---|---|---|---|
| Usage Recognition | Recognized for driving customer usage | Some workloads | No |
| Revenue Recognition | Recognized for customer impact | No | No |
| Deployment | Credited for implementing workloads | Yes ✓ | Yes ✓ |
Setting Up CPOR
Go to Partner Center → Incentives → Customer Associations
Sign in with your Partner Center admin credentials. Navigate to the customer associations section.
Create New Association
Enter the customer's tenant ID, select the workload (Teams, Security, etc.), and choose the association type (usage, revenue, or deployment).
Submit Proof of Execution (for Deployment)
Upload evidence of your work: project plans, deployment docs, customer sign-off. Not required for usage or revenue recognition types.
Microsoft Reviews (5-10 Business Days)
Microsoft validates your claim. The customer receives a notification and can dispute if they don't recognize the partner. Most claims are approved automatically.
Incentive Claims automatically creates CPOR tracking entries when your SOW matches eligible workloads. Every claim gets a deadline, expected value, and 6-stage pipeline — so nothing falls through the cracks. See it in action
If you are the CSP transacting partner, attribution is tracked automatically — no CPOR claim needed. CPOR is essential for non-CSP partners or partners on EA who are driving deployment or adoption but are not the transacting partner. Best practice: Some CSP partners still submit CPOR claims for cleaner records and attribution clarity.
6. The CPOR "Double Points" Advantage
Here's something most partners miss: CPOR earns points in BOTH Performance AND Customer Success categories of your Partner Capability Score. No other attribution type does this.
When you claim a CPOR association for a workload like Modern Work, Microsoft counts it toward your net customer adds (Performance) and your usage/deployment metrics (Customer Success). With the 70-point threshold for Solutions Partner designation, this double contribution can be the difference between qualifying and falling short.
7. When to Use Each — The Decision Framework
🔍 Which Attribution Method Do You Need?
Select your scenario to see the recommended approach.
VMs, databases, networking, storage, containers, AI services — any Azure consumption
Teams, Exchange, SharePoint, OneDrive, Copilot rollout, user training
Sentinel, Defender, Purview, Entra, Zero Trust implementation
Dynamics 365, Power Apps, Power Automate, Power BI, Customer Insights
Consultants placed at customer site, ongoing environment management
✅ Recommended: PAL (Primary) + DPOR (if EA)
PAL is your #1 priority for all Azure work. It's automatic once linked, covers MCA and EA, and allows multiple partners. If the customer is on EA, also ask them to set DPOR for belt-and-suspenders coverage. CPOR is not typically needed for Azure infrastructure unless you're also driving specific workload adoption.
✅ Recommended: CPOR (Primary) + DPOR (if EA)
For Modern Work, CPOR is essential — it's how you get recognized for deployment and adoption work. Submit usage or deployment claims in Partner Center. Also request DPOR from your customer for subscription-level association. PAL alone won't cover M365 workloads. CPOR earns double points (Performance + Customer Success).
✅ Recommended: All Three
Security straddles Azure (Sentinel, Defender for Cloud) and M365 (Defender for Office, Purview). Use PAL for Azure-based security resources, CPOR for workload adoption claims, and DPOR if on EA. Security Solutions Partner designation benefits from all three attribution sources. The more attribution types, the more PCS points you accumulate.
✅ Recommended: CPOR (Primary) + PAL (for Power Platform)
CPOR is the primary mechanism for Dynamics 365 and Business Applications. For Power Platform specifically, PAL can also be linked via service accounts or service principals. Submit CPOR claims for all D365 workloads (Finance, Sales, Customer Insights, etc.). Business Applications designation requires strong CPOR presence.
✅ Recommended: PAL (Critical) + CPOR (if applicable)
Staff augmentation is where the most attribution is lost. Every consultant placed at a customer site should establish PAL on day one — make it part of your onboarding checklist. If your consultants have Owner or Contributor access to Azure, you're leaving ACR on the table every day PAL isn't linked. If the engagement includes specific workload deployment, also submit CPOR.
8. The 6 Mistakes That Cost Partners Real Money
Forgetting PAL During Onboarding
Every day a consultant works without PAL is a day of invisible ACR. Make PAL establishment step one in your consultant onboarding checklist — before the first line of code.
Using PGA Instead of PLA
Your Partner Global Account (PGA) is not the same as your Partner Location Account (PLA). PAL requires the location-specific PLA ID. Using the wrong ID means zero attribution.
Not Re-establishing After EA→MCA
DPOR doesn't survive agreement migration. When a customer moves from Enterprise Agreement to Microsoft Customer Agreement, your attribution vanishes. Switch to PAL immediately.
Relying on DPOR Alone
DPOR only covers one partner per subscription and the customer must set it. PAL is partner-controlled, works across all agreements, and allows multiple partners. Don't put your attribution in someone else's hands.
Skipping CPOR for Non-Azure Work
If you're deploying Teams, rolling out Security, or building Power Apps, PAL alone won't cover it. CPOR is how you get credit for non-Azure workloads. Submit claims for every deployment.
No Verification Process
Establishing PAL once doesn't mean it stays forever. If a user account is deleted or disabled, attribution stops. Audit your PAL links quarterly — not annually.
The number one thing partners miss isn't a program or an incentive — it's attribution. Get PAL, DPOR, and CPOR right, and you unlock everything downstream: designations, specializations, ECIF funding, co-sell opportunities. Get it wrong, and you're running a marathon with no timing chip.
PAL Manager automates onboarding attribution. SOW Analyzer catches missed CPOR opportunities. Workforce Intelligence tracks which consultants have active PAL links and flags gaps before they cost you money. Book a 15-minute demo
9. Stacking All Three for Maximum Coverage
The strongest attribution posture uses all three mechanisms where applicable. Here's what full coverage looks like for a typical customer engagement:
| Engagement Activity | PAL | DPOR | CPOR |
|---|---|---|---|
| Azure VM deployment | ✓ Primary | If EA | Optional |
| SQL migration to Azure | ✓ Primary | If EA | Optional |
| Teams rollout (5,000 seats) | — | If EA | ✓ Primary |
| Sentinel + Defender deployment | ✓ Azure components | If EA | ✓ Security workloads |
| Power Apps custom development | ✓ Service principal | — | ✓ Primary |
| D365 Finance implementation | — | If EA | ✓ Primary |
| Managed services (ongoing) | ✓ All consultants | If EA | Usage recognition |
10. Verification — How to Confirm It's Working
PAL Verification
- Azure Portal: Sign in with the linked account → Cost Management → Link to a partner ID. Your PLA should display as linked.
- Partner Center: Insights → Cloud Product Performance → Filter by "Partner Admin Link" → Customer ACR should appear within 24-72 hours.
DPOR Verification
- Customer must check: Azure Portal → Subscriptions → [Subscription] → Partner Information. Your MPN ID should display.
- Partner Center: Insights → filter by DPOR → subscription-level attribution visible.
CPOR Verification
- Partner Center: Incentives → Customer Associations → check claim status (Pending, Approved, Rejected).
- Approval timeline: 5-10 business days. Customer can dispute within 7 days of notification.
Set a calendar reminder every quarter to audit your attribution. Check: (1) Every active consultant has PAL linked, (2) Every EA customer has DPOR set, (3) CPOR claims submitted for all non-Azure deployments, (4) No deleted or disabled accounts breaking existing PAL links. Most partners discover 20-30% of their attribution has silently lapsed.
Stop Guessing. Start Tracking.
PIE's Partner Admin Link module automates PAL establishment with one-click magic links. Your consultants get an email, click a button, and PAL is linked — no Azure portal navigation, no training required.
See How PIE Automates PAL →FAQ Frequently Asked Questions
What is the difference between PAL, DPOR, and CPOR?
+PAL (Partner Admin Link) automatically tracks Azure consumption by linking your MPN ID to credentials in the customer's environment. DPOR (Digital Partner of Record) associates one partner per subscription and is set by the customer. CPOR (Claiming Partner of Record) lets partners claim workload-level credit across all Microsoft products, with multiple partners able to claim the same customer. PAL is best for Azure, DPOR for legacy EA subscriptions, and CPOR for Modern Work, Security, and Business Applications.
Can I use PAL, DPOR, and CPOR at the same time?
+Yes. Microsoft recommends using all three where applicable. PAL covers Azure resource attribution, DPOR covers EA subscription-level recognition, and CPOR covers workload-level claims across Microsoft 365, Dynamics 365, and Power Platform. Using all three maximizes your Partner Capability Score and incentive eligibility.
How do I set up PAL for a customer?
+Get RBAC access in the customer's Azure environment (Owner or Contributor). Sign in to the Azure portal with those credentials. Navigate to Cost Management → Link to a partner ID. Enter your Partner Location ID (PLA). Click "Link a partner ID." PAL then automatically tracks Azure Consumed Revenue attributed to your account's permissions and scope.
Which RBAC roles are eligible for PAL attribution?
+For ACR attribution, any RBAC role works — including Reader. For PEC (Partner Earned Credit at 15%), you need a role with write access: Owner, Contributor, or a custom role with write permissions. User Access Administrator has attribution but no PEC eligibility. The scope (subscription, resource group, or resource) determines how much consumption is attributed.
Does DPOR transfer when a customer moves from EA to MCA?
+No. DPOR does not automatically transfer. When a customer migrates from Enterprise Agreement to Microsoft Customer Agreement, DPOR is lost. This is one of the most common attribution gaps. Make PAL your primary mechanism for MCA subscriptions and re-establish attribution immediately after any agreement migration.
How many partners can be associated through CPOR vs DPOR?
+DPOR allows only one partner per subscription — a major limitation. CPOR allows multiple partners at the workload level, reflecting how customers actually work with multiple partners. PAL similarly allows multiple partners in the same customer environment. This multi-partner support is why Microsoft introduced CPOR and recommends it over DPOR for most scenarios.
What counts toward Partner Capability Score?
+PAL contributes to Data & AI, Infrastructure, Digital & App Innovation, Security, and Business Applications. DPOR covers the same areas plus Modern Work. CPOR contributes to Modern Work, Security, and Business Applications. CSP partnerships count automatically. You need 70 points across Performance, Skilling, and Customer Success to earn Solutions Partner designation.
Do I need CPOR if I'm already a CSP partner?
+If you're the CSP transacting partner, attribution is automatic — no CPOR claim needed. If you're not the transacting CSP but are driving deployment or adoption, CPOR is essential to get recognized. Best practice: Even some CSP partners submit CPOR claims for cleaner records.
What happens if I forget to establish PAL?
+Without PAL, Microsoft has zero visibility into your Azure work. No ACR credit, no designation progress, no Advanced Specialization qualification, and for CSP partners, no PEC (up to 15% back). A consultant with Owner access to $75K/year in Azure who forgets PAL loses approximately $11,250 annually in PEC alone — and far more in downstream incentive eligibility.
How long does attribution take to appear?
+PAL attribution typically appears in Partner Center within 24-72 hours. Full PCS impact may take one billing cycle (~30 days). CPOR claims go through Microsoft review taking 5-10 business days. DPOR changes can take up to one billing cycle to reflect in reporting.