The Microsoft Partner programme in plain English
If you've ever tried to explain the difference between a designation, a specialisation and a certification to someone outside the business, you'll know how quickly it gets muddy. They're related, they're all earned, and they all show up in Microsoft's language about partners - but they measure different things.
The programme itself has been through several names. It was the Microsoft Partner Network (MPN), then the Microsoft Cloud Partner Program (MCPP) from 2022, and Microsoft now increasingly refers to it as the Microsoft AI Cloud Partner Program. Underneath the naming, the structure has held steady: one membership, six solution areas, a scored capability model, and a set of badges and benefits you unlock as you perform against it.
This page is a reference. It covers what each layer is, roughly what it takes to earn, and - the part most partners actually need help with - what to do with it once you've got it.
The six solution areas
Almost everything in the programme is organised around these. Designations, specialisations, incentives and co-sell attention all follow the same six lines.
Modern Work
Microsoft 365, Teams, Copilot adoption and the productivity estate. The busiest solution area by partner count, so differentiation matters most here.
Security
Identity, threat protection, compliance and the wider security stack. Consistently one of Microsoft's highest-priority investment areas.
Data & AI
Data platform, analytics and AI workloads. Where a lot of Microsoft's current attention and customer demand sits.
Infrastructure
Azure migration and modernisation of servers, VMware estates and databases. Strong consumption pull-through.
Digital & App Innovation
Cloud-native development, app modernisation and DevOps on Azure. Often where ISVs anchor.
Business Applications
Dynamics 365 and Power Platform across sales, service, finance and operations.
Designations: the headline badge
A Solutions Partner designation is the top-level proof that you can deliver in a solution area. You earn one per solution area, and you can hold more than one - though holding six rarely does as much for you as owning one convincingly.
Designations are earned through the Partner Capability Score, a points-based model scored out of 100 across three categories: performance (net customer adds and revenue), skilling (certified individuals and intermediate or advanced certifications) and customer success (usage growth and deployments). You need a minimum score in each category as well as a qualifying total, and the score is measured on a rolling basis - so it can lapse if activity drops off.
Two things surprise partners. The first is that skilling is a real gate, not a tick-box: you need named, certified people, and certifications expire. The second is that designations are re-evaluated continuously, so a designation earned during a strong year needs maintaining through a quiet one.
Designations, specialisations and certifications compared
| What it is | Who earns it | What it signals | |
|---|---|---|---|
| Designation | Solutions Partner status in one of the six solution areas, earned via the Partner Capability Score | The organisation | You can deliver at scale in this solution area |
| Specialisation | An advanced badge inside a solution area, validated by a third-party technical audit | The organisation | You have proven, audited depth in a specific scenario |
| Expert programme | Invitation-only tiers such as Azure Expert MSP or Inner Circle | The organisation | Elite status, usually with a managed-services or sales bar |
| Certification | An individual exam-based credential (Fundamentals, Associate, Expert) | A named person | That person is skilled - and it counts toward your designation score |
Specialisations: the badge that actually moves a conversation
Where a designation says you can deliver in Security, a specialisation says exactly what you're good at inside it. They sit on top of a designation, require the relevant certifications, customer references and - crucially - an independent third-party technical audit.
That audit is why specialisations carry more weight with Microsoft sellers and with sophisticated buyers. Anyone can describe themselves as a Copilot practice. A specialisation is somebody outside your business confirming it.
Specialisations change over time as Microsoft's priorities move. Recent additions have clustered around AI, security operations and cloud migration, and older ones get retired when the workload stops being strategic. If you're choosing where to invest, pick the one closest to the work you already sell profitably, not the one that sounds most impressive.
Certifications and skilling
Individual credentials are the fuel for everything above. They're earned by people, not by the business, and they feed straight into the skilling component of your capability score.
Fundamentals
Entry-level credentials such as AZ-900 or MS-900. Useful for breadth, and for getting non-technical staff conversant, but they carry limited weight in scoring.
Associate
Role-based credentials that do the heavy lifting in most designations - administrators, engineers, consultants and analysts.
Expert
The deepest tier, covering architecture and advanced roles. Fewer people hold them, so they're a genuine differentiator.
Renewals
Role-based certifications need renewing annually through a free online assessment. Missed renewals quietly erode your score.
Attribution
Certifications only count when the individual's account is associated with your organisation. Leavers take their points with them.
Planning
Map certifications to the designation you want rather than letting people pick freely. Ten unaligned certifications can score worse than four aligned ones.
What most partners get wrong
Five patterns that show up again and again.
- Chasing designations in every solution area instead of owning one or two.
- Treating skilling as an IT task rather than a scored business metric with an owner.
- Earning a specialisation and then never mentioning it anywhere a buyer or a Microsoft seller can see it.
- Letting certifications lapse because nobody tracks renewal dates.
- Describing status on the website without ever explaining what the customer gets because of it.
What this means for your marketing
Status is a marketing asset that most partners under-use. A designation on its own is a logo. A designation translated into a claim a buyer cares about - fewer failed migrations, faster Copilot adoption, a security posture that survives an audit - is a positioning statement.
Practically, that means three things. Put the badge where it's verifiable, including your website, your Microsoft Marketplace listing and your partner directory profile. Then write the "so what" next to it, in the customer's language. Then use it as the credibility layer under campaigns, not as the campaign itself.
It also affects who you can co-sell with. Microsoft sellers need a short, repeatable reason to bring you into an account, and a specialisation in the workload they're being measured on is one of the clearest reasons available. If your positioning doesn't make that obvious in ten seconds, the badge isn't working hard enough.
If you're weighing up where to invest next, the honest answer is usually: fewer badges, better told.