Azure Expert MSP retirement

Azure Expert MSP Is Retiring. What Replaces It Depends on What You Used It For

New enrollments ended Sept 15, 2026, and renewals end in January 2027. Microsoft's own pages send its benefits to three different places. This brief maps each one and lists what to check in Partner Center before the renewal window closes.

What's ending

Three jobs

Where each goes

Frontier Partner

Workloads that count

Before January

Microsoft built Azure Expert MSP to give "our most capable Azure MSPs full support." Holders cleared three Solutions Partner designations, a high monthly Azure consumption bar, four customer references and a third-party audit that Microsoft says can take "more than 300 hours of effort." Microsoft is retiring it: new enrollments ended Sept 15, 2026, renewals end in January 2027, and the program retires "by the end of 2027."

The banner on the program page says to "Get ahead of the change by earning the distinguished Frontier Partner specialization." The body of the same page, and the Learn page behind it, send the program's benefits, incentives and tools somewhere else. Azure Expert MSP did three jobs at once: access, tooling and differentiation. Work out which one your practice can least afford to lose, then check where each now lives before your anniversary date.

What's ending

Four dates that set the timeline

Sept 15, 2026

Enrollments closed. Microsoft "stops accepting new Azure Expert MSP applications."

January 2027

Renewals end. Learn: "If your renewal comes up before January, continue to renew if you want to maintain enrollment in Azure Expert MSP."

June 30, 2027

FY27 engagement access ends. "Partners keep eligibility for various engagement types through Azure Expert MSP enrollment within Frontier Accelerate for Azure for FY27, ending June 30, 2027."

End of 2027

The program retires. Current members "continue to receive associated benefits through their Azure Expert MSP anniversary date."

A renewal still means the full process. Learn says partners "must meet the qualification requirements, submit the application, and schedule and complete an audit" inside the renewal window.

Days in the renewal window: it opens 45 days before the anniversary date, plus a 30-calendar-day grace period

Learn calls this "the 75-day period" to meet the published requirements. An audit has to fit inside it, so start before the window opens.

Source: Microsoft Learn, Azure Expert MSP program page, last updated Aug 19, 2026.

Three jobs

What Azure Expert MSP did for a practice

The program page lists the benefits in Microsoft's own words. Differentiation: "Earn an exclusive Azure Expert MSP badge, get showcased to our customers, and gain top priority in our referral engine." Customer engagement: "Be prioritized for co-sell engagements and leads." Sales and business development: "Get support to develop new practices."

Learn adds two operational pieces: eligibility for engagement types in Microsoft's incentive programs, and access to tooling such as the direct MCA-E/EA to CSP for Azure transfer tool.

Grouped by what a practice used them for, that is three jobs. Access covers engagements, incentives and practice support. Tooling covers the transfer tool. Differentiation covers the badge, the referral priority and co-sell prioritization. One enrollment covered all three. Microsoft now sends each job to a different place, so start with the one your practice can least afford to lose.

Prerequisites a holder already cleared

Three Solutions Partner designations (Data & AI, Digital & App Innovation, Infrastructure)
A high monthly Azure consumption bar
An active Cloud Solution Provider (CSP) contract
An MSP offer listed in AppSource or Azure Marketplace, and promoted on your website
Certified staff, four customer references and Advanced or Premier Support

Where each goes

Three destinations, in Microsoft's words

Source: Azure Expert MSP program page (read Oct 30, 2026) and Microsoft Learn Azure Expert MSP page (updated Aug 19, 2026). The grouping into three jobs is IMS's.

Job	Where Microsoft sends it	Microsoft's words, and where they appear
Access	Azure specializations, with FY27 continuity through Frontier Accelerate for Azure	"Review the FY27 Incentives guide to understand the engagements qualified for through Azure Expert MSP enrollment and the corresponding Azure specializations that offer similar access." (Learn, Aug 19, 2026)
Tooling	Cloud & AI Platforms designations plus Direct Bill CSP	The transfer tool is now available "through enrollment in Cloud & AI Platforms-related Solutions Partner designations plus Direct Bill CSP authorization." (Learn, Aug 19, 2026)
Differentiation	Frontier Partner specialization	"To differentiate your business and signal validated enterprise AI capabilities, explore the Frontier Partner specialization." (Azure Expert MSP program page, undated, read Oct 30, 2026)
The rest	Designations and Azure-aligned specializations	"You can continue to access many of the benefits, incentives, and tools through Cloud & AI Platforms-related Solutions Partner designations and Azure-aligned specializations." (same page)

Two limits on what the public pages show. The engagement-to-specialization mapping lives in the FY27 Incentives guide, which sits behind a Microsoft sign-in, so the public pages don't say which Azure specialization carries which engagement. And the program name varies: the Azure Expert MSP pages say "Frontier Accelerate for Azure," while IMS's Oct 22 conflict log found Microsoft's Agent Factory FAQ using "Azure Accelerate." Use both names when you ask a Microsoft contact.

One knock-on effect. The Digital Sovereignty specialization still lists Azure Expert MSP as one of three qualifying Azure prerequisites, alongside Infra and Database Migration and Azure VMware Solution. If Azure Expert MSP is the one you hold, plan for one of the other two.

Frontier Partner

Four specializations across Azure, Microsoft 365 and Security

Microsoft's Learn page calls Frontier Partner "the recommended path forward for eligible partners." Its requirements come in three parts, and a partner must meet all three. Specializations: four active ones, Microsoft 365 Copilot; AI Apps on Microsoft Azure or AI Platform on Microsoft Azure; Data Security; and Identity and Access Management. Skilling: five people with the Frontier Transformation Engineer badge, and three with the Fabric Analytics Engineer Associate certification (DP-600). They "can be the same or different people." Audit: "Your company must pass a third-party audit," against a published checklist.

It is "not aligned to a specific Solutions Partner designation," and the listed benefits are a specialization badge, "Frontier-aligned co-sell opportunities," agent-usage credits and Microsoft 365 E7 licenses, and go-to-market resources.

What that means for an Azure-only practice. Three of the four prerequisites sit outside Azure, in Microsoft 365 and Security, and each carries its own designation, skilling and audit requirements. Data Security, for example, requires the Solutions Partner designation for Security, "a minimum of 2,500 Monthly Active Usage (MAU) growth of Microsoft Purview Information Protection" over a trailing 12 months, and a third-party remote audit. Size that work, and decide whether it fits the practice you run, before you treat Frontier Partner as the replacement. It is also a separate credential from the Frontier Partner badge, which Microsoft says "retires at the end of June 2027."

1 of 4

Frontier Partner prerequisites an Azure practice can meet with Azure specializations alone

AI Apps or AI Platform on Microsoft Azure is the only Azure prerequisite. The other three are Microsoft 365 Copilot, Data Security, and Identity and Access Management.

Source: Frontier Partner specialization page, read Oct 30, 2026.

Workloads that count

If access moves to Azure specializations, check their workloads

Five Azure specializations had their eligible Azure consumed revenue (ACR) workloads realigned to the FY27 rollover taxonomy: AI Platform, AI Apps, App Modernization, Azure Virtual Desktop and Azure VMware Solution. Microsoft's instruction is to "review the updated performance requirements to confirm your ACR workloads still count." For example, AI Platform on Microsoft Azure asks for "$15,000 of Azure Consumed Revenue (ACR) from the eligible Strategic Pillars of Azure AI platform services in the last 3 months," from at least three unique customers. Its eligible pillars are Foundry Models, Foundry Services and GPU IaaS.

Two Microsoft pages give different dates for the change. IMS doesn't pick one.

Topic	One page says	Another page says	Microsoft's pointer
When the ACR workload change took effect	Tech Community specialization blog (Oct 1, 2026): the workloads "are being updated to match the FY27 rollover taxonomy"	Learn monthly program update (Oct 22, 2026): "On August 31, 2026, the eligible Azure Consumed Revenue (ACR) workloads for five Azure specializations were updated"	"Check Partner Center to find out if you maintain the requirements under the new taxonomy."

A related change on the Security side. Since Oct 5, 2026, new Azure security ACR workloads count toward the Solutions Partner designation for Security, including Azure Firewall, Key Vault, Microsoft Defender for Cloud and Microsoft Sentinel; Network Watcher no longer counts. The Data Security specialization page lists that designation as its first requirement.

Before January

Eight checks to run now

If nothing changes

Renewals end in January 2027, so each enrollment runs out at its next anniversary after that, along with the badge and the benefits tied to it.
Engagement eligibility through Azure Expert MSP enrollment ends June 30, 2027.
A Digital Sovereignty specialization that relies on Azure Expert MSP as its Azure prerequisite loses that prerequisite when the enrollment lapses.
Neither Microsoft page says a holder is moved into any of the new destinations automatically. Each one has its own requirements.

Anniversary date

Find it. If it falls before January and you want to keep the enrollment, start the requirements and the audit before the window opens.

Rank the jobs

Rank access, tooling and differentiation by what the practice can least afford to lose, and name who in the business depends on each.

Specializations

List the Azure specializations you hold and read each one's current performance requirements on its program page.

ACR still counts

For the five realigned specializations, confirm in Partner Center that your workloads still qualify under the new taxonomy.

Transfer tool

If you use it, confirm Direct Bill CSP authorization and a Cloud & AI Platforms-related designation.

Incentives guide

Digital Sovereignty

If Azure Expert MSP is your only qualifying Azure prerequisite, plan for Infra and Database Migration or Azure VMware Solution.

Frontier gaps

Mark which of the four Frontier Partner prerequisites you hold, then the skilling and audit gaps, before deciding to pursue it.

What's still coming. Microsoft's Learn page says it "will share additional Partner Program updates for Managed Services Partners in FY27." IMS will reread these pages the week after Microsoft Ignite (Nov 17 to 20, 2026) and update this brief if anything changes.

Rebuilding your Azure credentials? Find the constraint that binds first.

The free IMS Co-Sell Readiness Index (CRI) scores six dimensions, including Program & Incentive Capture and Microsoft Field Traction, in about ten minutes with no email required.

Measure your readiness

Azure Expert MSP put three jobs under one badge, and Microsoft is splitting them up. Name the job, find where Microsoft now sends it, and check it in Partner Center while the renewal window is still open.

Published Oct 30, 2026. Public pages only, read Oct 30, 2026. Dates are each page's visible "Last updated" or post date; partner.microsoft.com program pages show none. The FY27 Incentives guide requires a sign-in and was not read. Sources: partner.microsoft.com Azure Expert MSP, Frontier Partner, Digital Sovereignty, AI Platform and Data Security pages; Microsoft Learn Azure Expert MSP page; Partner Center announcements (Aug and Oct 2026); Microsoft Tech Community. Verify against current Microsoft documentation.