Frontier Partner Specialisation: what it takes and what the audit wants to see 

What Frontier is (and what it isn't) 

Frontier went live in Partner Center on 30 September, so it is still very new. It is also unusual. Most specialisations sit under a single solution area, but Frontier runs across all of them, something only the Digital Sovereignty specialisation does today. That tells you Microsoft sees it as a statement about your whole partner business rather than one practice. 

What it tests is whether your team can take an agent through its entire life cycle: design, build, deploy, secure, govern, keep it running and make sure customers actually adopt it. Microsoft's line is that an agent that works is no longer enough. It has to be secure and governed, with controls that map back to the Secure Future Initiative and the Microsoft cloud security benchmark. Security is baked in from the start rather than bolted on at the end. 

The audit is written around capabilities rather than product names. Given Microsoft's fondness for a rename, that is a small mercy: your work should survive the next rebrand. 

Two things worth slowing down on: 

• The Frontier partner badge is a different thing entirely. It retires at the end of June 2027 and holding it gets you no closer to the specialisation. We have already seen partners caught out by this. 
• The audit stands for two years, but you still need to meet the prerequisites every year at your anniversary. 

What you get 

The confirmed benefits are the customer-facing Frontier label and a prioritised profile in Microsoft Marketplace and the partner directories. One detail people miss: the label belongs to your partner global account (PGA). If you are part of a group, a subsidiary or have been acquiring businesses, check where your PGA sits before your marketing team gets excited. 

Further benefits have been reported in the trade press following Microsoft's announcements, including front-of-the-line co-sell with the field, agent pre-purchase plan credits and licence benefits. They may well land as described. We would wait for the detail in Partner Center before building a business case on them. 

Start with the foundations 

At the base are two solutions partner designations: Security, plus either Data & AI (Azure) or Digital & App Innovation (Azure). Nothing above that stands up without them. 

Frontier does not name designations outright, but its prerequisite specialisations do. Copilot can sit on Modern Work, Business Applications or Security. Data Security and Identity and Access Management both need Security. The Azure specialisation needs Data & AI or Digital & App Innovation. Because Security also satisfies Copilot, you don't actually need Modern Work at all. 

This is where many partners find their first gap. A Modern Work designation and a healthy Copilot practice can feel like a head start, when in reality they tick one box of four. If that sounds familiar, Security is the first place to look. 

The four prerequisite specialisations 

On top of the foundations sit four advanced specialisations, each with its own audit: 

1. Microsoft 365 Copilot 
2. Data Security 
3. Identity and Access Management 
4. Either AI Apps on Azure or AI Platform on Azure 

Add Frontier itself and you are looking at five audits in total. 

The first three measure growth in monthly active usage (MAU) rather than seat count, over a trailing 12 months on a rolling 28-day basis. That means growth on Microsoft 365 Copilot, Microsoft Purview and Microsoft Entra ID (P1 or P2) respectively. A big licence deal that nobody on the customer side uses will not get you very far. 

A few recent changes to keep on your radar: 

• Copilot skilling changed in July. MS-102 no longer counts, and AB-100 and AB-620 replaced the Copilot Studio Applied Skills. 
• Customer references were replaced by third-party audits in July, including for Data Security and Identity and Access Management. You pay for these yourself, typically a couple of thousand dollars each, and they are revalidated every two years. 
• Existing holders of Data Security or Identity and Access Management were given a six-month extension to prepare for the audit. Check your renewal date now, because that one is easy to lose track of. 

Choosing your Azure route 

The AI requirement is identical on both routes: the same AI ACR, the same workloads and three unique customers. After that, they part ways. 

• AI Apps on Azure adds $15K of app platform ACR, $15K of data platform ACR and five or more people across a broad set of certifications. If you have a strong app and data practice, you may already be a good chunk of the way there. 
• AI Platform on Azure relies purely on AI consumption and needs only three people, but with more specific certifications. If your Azure business is mostly AI work, this is probably the shorter route. 

Either way, it needs its own audit. 

Partner Center hygiene 



Not the most glamorous subject, but this is where a surprising number of partners fall down before they get anywhere near the audit. 

There are two association models and both need to be in good shape. MAU for Copilot, Data Security and Identity and Access Management is attributed through CPOR. Azure ACR needs DPOR, PAL or a CSP transaction. Most partners we work with have one of these in decent order and the other less so. 

Timing matters too. MAU is measured on what changed over the last 12 months, not what you have built up over the years. Azure ACR counts the last three months, which is a tight window when you are lining up everything else a specialisation this complex needs. 

Start by checking which customers are and are not counting towards your designations and specialisations. A gap usually points to a missing CPOR, DPOR or PAL, and from there to the internal process that let it slip. 

The audit itself 

The audit is the roof on the house: four sections, eight controls and one eight-hour independent audit. It is the part everyone wants to talk about because it unlocks the label, but most of the effort and elapsed time sits in the layers underneath. 

The first two sections ask whether you can deliver agentic solutions for customers. The last two ask whether you can do it securely, and that is where most of the weight sits. There are no partial passes. The advanced items do not count yet, though we wouldn't bet on that lasting. The good news is that evidence overlaps: the same identity matrix and threat model get reused across sections, so build them once and build them properly. 

How it runs 

• Apply once every prerequisite shows as met in Partner Center. An account admin or global admin has to submit the application. 
• You then have 30 days to complete the audit. Gather your evidence before you apply rather than starting the clock and scrambling. 
• The checklist planning figure is $4,000, including the gap review. Final pricing and tax are confirmed when you schedule, and the fee is paid in full to the audit company upfront. 
• It is a single eight-hour remote session. Microsoft recommends a subject matter expert per section, plus one person who knows the whole audit end to end. Evidence can be redacted or sanitised, so you don't need to show production systems or customer data. 
• Anything left open triggers a gap report within five business days. You have two business days to acknowledge it and the gap review follows within 15 calendar days. That is your one chance to close everything off before you would need to reapply. 
• Pass and you hold the specialisation for a year. The audit itself stands for two. 
• Your PDM can join the optional consulting sessions with the auditor, but not the audit. 

Know which checklist you will be audited against 

Version 1 of the checklist is in Partner Center now and is live until 31 December. Unless you are auditing in the next few weeks, you will be assessed against the version released on 1 January. You are audited against whichever version is live on your audit date, not the one you prepared against, and Microsoft plans to update it every six months. Expect the next one in July 2027. 

Is the juice worth the squeeze? 

Five audits, a heavy skilling load and customer projects that need months in production. It is a significant investment. 

Lindsay's view: it absolutely can be worth it, but only when it sits inside a deliberate AI practice strategy. As a badge hunt, much less so. 

Sequencing 

Work backwards from a target audit date: 

1. Foundations: the Security designation and your Azure designation 
2. The four prerequisite specialisations 
3. Skilling and customer projects, running in parallel 
4. Evidence 
5. Application for the audit 

Customer evidence will almost certainly set the pace. Projects need three months live and must have completed within the last 12. If your best candidate is still in pilot, your earliest audit date is at least three months after it goes into production. Skilling runs alongside everything else and there is a lot of it, so get it started early. 

The industry perspective 

Eric Boussier, Microsoft 

Eric's team is new for FY27: a small global team working with strategic partners such as Arrow to accelerate Frontier transformation in the market, reaching the resellers and MSPs that distributors serve. For all the big language around Frontier, he was clear the work is very down to earth. 

Asked what makes a Frontier partner beyond the requirements, he gave three attributes that reflect Microsoft's thinking: 

• Customer zero. Use AI and agents to transform your own business first. It is very hard to have credible AI conversations with customers if you aren't doing it yourself. 
• End-to-end technical capability. Not deploying products in isolation, but bringing Copilot, data, security and build together into solutions that are secure, governed and ready to run at scale. 
• A focus on business outcomes. The most advanced partners have moved from product features to outcomes, and customers want to measure the impact. AI is not a cheap technology. 

On what Frontier says that existing designations don't, Eric stressed those designations and specialisations are not going anywhere. Customers aren't thinking about products in isolation, though. They are thinking about how AI transforms business processes and how agents work across the organisation. Frontier recognises partners who have assembled that jigsaw, rather than being very good at one thing. 

On co-sell, he framed it around two questions Microsoft sellers ask constantly. Can this partner deliver what my customer needs? And is this the right partner for this opportunity? Frontier helps answer the first. With SME&C leadership doubling down on partner-led motions, sellers have to find the right partner for complex AI work, but Eric was clear that Frontier matters most for the bigger, more transformative opportunities rather than every deal. 

Kate Balgowan, Arrow 

Kate sees progress across Arrow's partners as very mixed. Many aren't talking about Frontier at all because they are still working towards a first designation or specialisation. Others already live the Frontier attributes in how they run their business without necessarily chasing the specialisation. That can be perfectly fine, particularly for smaller partners who simply don't have six people for some of the certifications. A smaller group has decided they need it to accelerate co-sell this year and is putting the strategy in place to get there. 

Her advice for anyone unsure: if Frontier isn't the right route yet, find the specialisation that fits your go-to-market and proves your capability. One attendee suggested the audits might make partners think twice about cost and benefit. Kate's answer was that this is fine. If you are hitting your goals without it, that is a legitimate choice. But if you want to work closely with Microsoft, this year it will be looking at where you are qualified, audited and proven. 

She also made a point worth remembering. Frontier is meant to be a step above the norm. If every partner could get it, it would no longer be Frontier. 

Size matters less than you might think 

A question in the chat asked how Microsoft would avoid favouring the biggest resellers if smaller partners invest in this. Lucy's view is that some of the responsibility sits with partners themselves: make sure the right people at Microsoft know what you can deliver, share your win wires, identify key stakeholders and resist trying to be all things to all people. Getting the programmatics right is one part. Understanding what sellers need to see to back you is the other. 

Kate added that this is where distribution is your friend. Arrow regularly surfaces strong customer use cases from smaller partners back into Microsoft, and she has seen partners three years old with ten people securing QBRs with Microsoft solution area directors. Customer outcomes are what get you noticed, not headcount.

Get in touch