What is Microsoft’s Partner Capability Score & How to Master It

by Darren Lloyd

22 September 2026

Microsoft's Cloud Solution Provider incentive model has been reshaped more significantly over the past 12 months than at any point in the last decade. The direction is consistent: less margin for flat resale, more for partners who grow, upsell, and drive adoption of security and AI products.

Here's what's changed, what's still coming, and what CSPs need to be doing differently.

Summary

Outcome-first shift: Microsoft has rebuilt its scoring, specialisations, and incentive structures around usage and consumption growth, not license sales
Customer Zero requirement: partners are expected to run their own operations on Copilot and autonomous agents before selling them to customers.
Hard telemetry metrics: the Partner Capability Score (PCS) is a 100-point composite across three categories: performance, skilling, and customer success, weighted differently by solution area, and it takes 70 points in one of six solution areas to earn a designation.
Specialisation tightening: Microsoft is shifting toward proctored certifications and formal audits e.g., the newly renamed Microsoft 365 Copilot specialisation (formerly "Microsoft Copilot") added a dedicated validation audit in July 2026.

What Does Microsoft Consider an "Outcome-First" Partner?

Microsoft defines an "outcome-first" partner as one that drives active, metered technology consumption by pairing rapid deployment with strict security guardrails and continuous adoption governance.

Microsoft frames this explicitly as a shift "from transaction-first to outcome-first." Four operational traits now define a top-tier partner:

Customer Zero Maturity
Partners run their own business on the technology first. Sellers and engineers use Copilot and autonomous agents internally, so they're speaking from operational experience, not a slide deck.
Security-first Architecture
Identity, data protection and governance, increasingly built on Microsoft 365 E7 controls and the emerging Agent 365 management layer, get designed into the baseline, not bolted on as a post-deployment upsell.
Adoption as a Managed Program
Microsoft expects a structured rollout combining licensing, change management, and a recurring optimisation cadence.
Agentic Process Orchestration
Microsoft is weighting incentives toward partners who can orchestrate multi-step autonomous agent workflows across finance, supply chain, and operations.

Partners publishing transactable offers through the Microsoft Marketplace also see faster sales cycles and deal closures, which is another sign Microsoft wants packaging and consumption running through its own commercial rails.

How Does the Microsoft Partner Capability Score (PCS) Measure AI Consumption?

The Partner Capability Score (PCS) is Microsoft's 100-point composite across three categories, Performance, Skilling, and Customer Success, and a partner needs 70 points in at least one of six solution areas to earn a Solutions Partner designation.

The PCS replaced the old Gold/Silver competency model in 2022, trading a binary pass/fail for a granular, monthly-refreshed score. Each of Microsoft's six solution areas: Infrastructure, Data & AI, Security, Modern Work, Digital & App Innovation, and Business Applications, carries its own independent PCS, so a partner can hold multiple designations at once.

Category weighting varies by solution area. For Solutions Partner for Business Applications, for example, the 100 points break down as:

PCS Category	Points	What It Measures
Skilling	35 (20 intermediate + 15 advanced)	Uniquely certified individuals against intermediate and advanced-level exams
Performance	15	Net new customer adds, trailing 12 months
Customer Success	50 (30 usage growth + 20 deployments)	Usage growth and deployment quality across existing customers

Skilling is the only category a partner fully controls; there is no attribution setup required, just certified people.

There's a trap, however, that quietly stalls a lot of partners here: fundamentals-level exams (AZ-900, AI-900, DP-900, SC-900) don't count toward Skilling points. Only intermediate/associate and advanced/expert-level certifications count, and Microsoft rewards breadth over depth. Certifying five different people outscores stacking five certs on one person.

Performance and Customer Success run on a different mechanic: attribution. Microsoft can't score revenue or usage it can't see, so those points depend on registering the right partner-of-record association for each engagement:

Claiming Partner of Record (CPOR): counts toward Modern Work, Business Applications, and Security. Claimed per workload or product against a customer's usage, licensing influence, or revenue.
Digital Partner of Record (DPOR): counts toward Data & AI, Digital & App Innovation, Infrastructure, Modern Work, and Business Applications. One DPOR per subscription, tied to the partner actually designing, deploying, or managing the solution.
Partner Admin Link (PAL): ties an MPN ID to the credentials used to manage a customer's Azure or Business Applications environment. Unlike DPOR, multiple partners can claim PAL on the same engagement and still get credit.

Skip the attribution step, and Performance and Customer Success stay at zero, regardless of how much real deployment work happened underneath.

Miss 70 combined points in a solution area, and a partner is locked out of that area's co-sell referrals, higher incentive rates, Advanced Specialization eligibility, and ECIF funding.

If a score dips below 70 after a designation is already attained, Microsoft doesn't pull it immediately: a 30-day grace period follows the partner's program anniversary date, and qualification is assessed against a trailing 6-month window, so touching 70 points on even one day in that window is enough to keep the designation.

For AI-focused work specifically, Customer Success weighs consumption growth and workload health on active Azure AI and Copilot deployments. The more distinct advanced AI services a partner gets running in production, and the more that usage grows quarter over quarter, the more points land in that category.

Which AI and Agent Specialisations Matter Most?

Microsoft's 2026 specialisation catalog prioritises active usage metrics, agentic workflow, delivery, and audited security practices over seat counts.

Specialisation	Primary Telemetry / Requirement	Core Focus Area
Microsoft 365 Copilot (renamed from "Microsoft Copilot," July 2026)	Paid Monthly Active Users (MAU) growth, trailing 12 months	Active paid usage over licenses sold
Agentic Business Solutions	Live Copilot Studio or Power Platform agent deployments	Autonomous agent deployment and architecture
AI Platform on Azure	Azure AI consumption (Azure OpenAI, Azure AI Services, Azure ML)	Infrastructure and production AI model deployment
Analytics on Azure	Coverage across Fabric, Power BI, and Databricks	Data pipeline readiness for enterprise AI
Secure AI Productivity	Copilot security, automation, and governance track	Copilot security, automation, and governance

As part of the July 2026 update, the Microsoft 365 Copilot specialisation also dropped the Microsoft 365 Certified: Administrator Expert (MS-102) requirement in favor of the new Agentic AI Business Solutions Architect (AB-100) and AI Agent Builder Associate (AB-620) certifications.

Self-attestation is on its way out. Microsoft is shifting toward proctored certifications and formal validation, and specialisations like Microsoft 365 Copilot now include a dedicated audit requirement. That closes a loophole that let partners claim delivery capability they hadn't actually proven.

What Consumption Motion Does Microsoft Expect Partners to Run?

Microsoft expects partners to run a metered "30-day adoption motion" that pairs technical deployment directly with usage tracking, governance, and long-term MACC expansion.

Rather than a discrete project, Microsoft wants a repeatable loop:

Step	Action
1 - Rapid pilot	Land an initial trial or POC quickly
2 - Usage telemetry	Instrument active-user metrics from day one
3 - Governance & training	Pair the technical rollout with a change management framework
4 - MACC expansion	Convert proven pilots into long-term Azure commitments

In practice, that means:

Land and instrument: deploy 30-day pilots with user telemetry and consumption tracking active from day one.
Wrap in governance: put security and data boundary policies in place immediately, so usage doesn't stall on compliance fears.
Expand via MACC: turn proven usage numbers into a case for broader Microsoft Azure Consumption Commitments, tying multi-year expansion to real business operations.

Firms in Microsoft's AI Business Solutions Inner Circle, including KPMG, Protiviti, and Cyclotron, follow exactly this arc: pilots that become instrumented, agentic workflows driving continuous Azure and Copilot consumption.

Final Strategy for Microsoft Partners

Microsoft's partner evaluation model doesn't hide the ball: revenue from reselling licenses doesn't buy strategic alignment anymore.

Co-sell support, incentive dollars, and Inner Circle standing go to partners who treat AI adoption as a metered, operational motion: proving capability internally, locking down security from day one, and tracking active consumption metrics without exception. Do that consistently, and the PCS framework becomes navigable instead of punishing.

To find out how ChangePilot can help partners navigate the scoring, read about our partner programme.

Frequently Asked Questions

What is the minimum score required for a Microsoft Solutions Partner designation?
70 points out of 100, in at least one of Microsoft's six solution areas: Infrastructure, Data & AI, Security, Modern Work, Digital & App Innovation, and Business Applications. Each solution area carries its own independent score.MC1426371 is the Microsoft Message Center post announcing that Microsoft Entra will make passkeys the default authentication method and retire Microsoft-provided SMS and voice MFA. The Admin and User Impact is rated High.

What are the PCS categories, and how are they weighted?
Performance, Skilling, and Customer Success.

Weighting isn't a fixed 100-point split; it varies by solution area. For Business Applications, for example, it's Skilling 35 points, Performance 15 points, and Customer Success 50 points. Skilling is the only category entirely within a partner's control.

What are CPOR, DPOR, and PAL, and why do they matter for PCS?
They're the partner-of-record associations Microsoft uses to attribute revenue and usage back to a partner. Without one in place, Performance and Customer Success points stay at zero, no matter how much deployment work actually happened.

What happens if a partner's PCS drops below 70?
Not an immediate loss. Microsoft applies a 30-day grace period after the partner's program anniversary date and checks qualification against a trailing 6-month window, so hitting 70 points on even one day in that window preserves the designation. Persistently missing the threshold across that window means losing the Solutions Partner designation and everything gated behind it: co-sell access, incentive rates, and Advanced Specialization eligibility.

What is "Customer Zero" maturity?
Microsoft's requirement that partners deploy, test, and run their own internal operations on Copilot, Azure AI, and agentic workflows before packaging and selling those solutions to customers.