Program mechanics

The Microsoft Partner Program Has Not Stopped Changing. Here Is Where It Actually Stands.

Six structural changes since FY25. What moved, what stayed the same, and what your co-sell motion depends on getting right.

The changing program

Co-sell status mechanics

The referral reset

Designations and certifications

What actually matters

Most partners who have been working the Microsoft partner ecosystem for more than 18 months are operating on a mental model of the program that is at least partially wrong. Not because they stopped paying attention. Because the Microsoft AI Cloud Partner Program (MAICPP) has changed more in the last three years than in the prior decade, and most of the changes have not been announced with enough visibility for the average partner to track.

The program that exists at the start of FY27 is meaningfully different from the one that existed 18 months ago. Six structural changes have rolled out since late 2024. Some affect how co-sell referrals flow. Some affect how designations are maintained. Several affect which certifications count toward program standing. One changed how security specializations are validated, effective July 30, 2026. None of these changes are optional for partners who want the Microsoft channel to produce. This brief covers each one, and what stays constant underneath all of them.

The changing program

Six structural changes since FY25

The 2022 transition from Gold and Silver competencies to Solutions Partner designations was the last major disruption most partners built their mental model around. It was significant enough that many organizations are still adjusting. The program has not stood still since then.

Since September 2024, six structural changes have reshaped how the program operates at the level that matters for co-sell: how referrals flow, how designations are earned and maintained, and how Microsoft validates that partners are delivering what they claim. Taken together, they constitute a materially different operating environment from the one described in any partner playbook written before 2025.

Sep 2025

Marketplace unified. Azure Marketplace and AppSource merged into a single Microsoft Marketplace. Unified Partner Center interface, new category definitions, and a dedicated AI Apps & Agents category growing faster than the rest of the marketplace. Partners who have not audited their category selections since the unification may be poorly positioned in search and discovery.

Jan 2026

Referral data requirements tightened. The "Marketplace Intent" field became mandatory for all API-based co-sell referral submissions. API submissions without it are not accepted. Partners using CRM integrations should confirm the field is populated and that the integration surfaces any rejection.

Mar 2026

QRP retired. The Qualified Referral Program retired at the end of Q3 FY26. All co-sell intake now runs through the standard Partner Center co-sell referral experience. Partners who built internal workflows around QRP need to update their process. The replacement experience includes new referral fields and AI-enhanced partner matching. See Section 3.

Jun 15, 2026

Partner University closed permanently. No new user linkings are accepted after June 15, 2026. Partners who did not complete assessment-to-profile linkings before this date have lost those skilling pathways. Existing linked assessments remain valid until June 2027, then retire entirely. New skilling requirements using formal certifications replace the assessment-based model. See Section 4.

Jun–Aug 2026

Largest certification overhaul in recent partner history. Dozens of traditional role-based certifications retired in waves from June 30 through August 31, 2026, replaced with AI and agentic AI-focused credentials. "Agentic AI Business Solutions Architect" now appears as a required or replacement certification across several specializations. Three specialization tracks merged into consolidated categories on July 31, 2026. Partners maintaining designations or specializations should audit their certification mix now. See Section 4.

Jul 2026

Security specializations moved to audit model. On July 30, 2026, all four Microsoft Security specializations (Cloud Security, Data Security, Identity and Access Management, Threat Protection) replaced customer reference validation with third-party audits. Partner-funded. Conducted every two years. This is a significant raise in the bar for what it means to hold a security specialization. See Section 4.

Co-sell status mechanics

The $100,000 gate has not moved

Through every structural change listed above, one mechanic has not changed: the difference between Co-Sell Ready and Azure IP Co-Sell Eligible determines whether Microsoft field sellers have a financial reason to bring a partner into a deal. This is the most consequential distinction in the partner program, and the most widely misunderstood.

At Co-Sell Ready, a Microsoft field seller can see a partner's solution in internal catalogs. There is no quota credit for the seller. No Microsoft Azure Consumption Commitment (MACC) eligibility for the customer. Co-Sell Ready is visibility. Not field engagement.

Azure IP Co-Sell Eligible is where the seller incentive exists. Sellers earn quota credit. Enterprise customers can apply purchases toward committed Azure spend balances, which significantly reduces procurement friction. The referral pipeline opens fully. (Marketplace Rewards tiers are separate: they scale with trailing-12-month Marketplace Billed Sales, independent of co-sell status.)

The four requirements for Azure IP Co-Sell Eligible status are unchanged, regardless of program rebranding:

Feature	Co-Sell Ready	Azure IP Co-Sell Eligible
Visibility in Microsoft seller catalogs	✓ Yes	✓ Yes
Microsoft seller quota credit	✗ No	✓ Yes, sellers earn quota credit on co-sold deals
Customer MACC eligibility	✗ No	✓ Purchases decrement committed Azure spend
Marketplace Rewards tier	Scales with trailing-12-month MBS	Same; set by MBS, not co-sell status or ACR
Transactable offer required	No (recommended)	✓ Yes, mandatory since July 2023
Revenue threshold	None	$100K ACR or Marketplace Billed Sales, trailing 12 months
Technical validation	Not required	Required: Azure-platform validation
Reference architecture diagram	Not required	Required for SaaS and Dragon Copilot offers; optional for Azure Application, Container, and Virtual Machine offers

$100K

Azure Consumed Revenue (ACR) or Marketplace Billed Sales, trailing 12 months, required for IP Co-Sell Eligible status. Two categories explicitly excluded from this count: Azure credits and Azure Consumption Offers (ACOs). Partners burning Azure credits at scale may be further from this threshold than their dashboard indicates. The typical timeline from first Marketplace listing to IP Co-Sell Eligible is 6 to 12 months, depending on ACR velocity. Planning from month one is not optional.

The referral reset

QRP is gone. This is what the co-sell referral experience looks like now.

Here is what replaced QRP and what you need to do now. The Qualified Referral Program was retired at the end of March 2026. All co-sell intake now runs through the standard Partner Center co-sell experience. For partners who built internal workflows, CRM integrations, or reporting structures around QRP, this is an operational change that requires attention, not just awareness.

Two new data fields now shape how referrals move through the system. "Marketplace Intent" has been required for API referral submissions since January 5, 2026, and API submissions without it are not accepted. Confirm your CRM integration surfaces that rejection. "Estimated Azure Consumed Revenue" is now a standard referral field, and Microsoft field teams use it to prioritize which partner opportunities get seller attention.

Microsoft has also added AI-enhanced partner matching to the referral routing process, using real-time data on partner capabilities and ACR signals to route leads. IP Co-Sell Eligible partners with active referral engagement see higher-quality inbound lead routing as a direct result of this change.

Frontier Accelerate for Marketplace combines ISV Success, Marketplace Rewards, Azure IP co-sell, and certified software designations into a single entry point. Microsoft announced it at MCAPS Start for Partners, and the program opened on September 28, 2026. Existing ISV Success, Marketplace Rewards, and Azure IP co-sell participants transition automatically at renewal. Microsoft previewed this consolidation at Ignite 2025 as App Accelerate and renamed it Frontier Accelerate for Marketplace at MCAPS Start for Partners. The same Ignite 2025 announcement describes a nomination-based pilot, Early access to co-sell benefits, for partners below the $100K MBS or ACR milestone, weighing MACC, customer traction, and pipeline strength. How it works inside Frontier Accelerate for Marketplace is not yet published.

Frontier Accelerate
for Marketplace

Microsoft's consolidation of ISV Success, Marketplace Rewards, Azure IP co-sell, and certified software designations into one program entry point

Early access to co-sell benefits, a nomination-based pilot published at Ignite 2025, is the element to watch for partners below the $100K MBS or ACR milestone. It weighs MACC, customer traction, and pipeline strength. How it works inside Frontier Accelerate for Marketplace is not yet published.

Opened September 28, 2026. Existing participants transition automatically at renewal. Do not restructure your ISV Success or Marketplace Rewards engagement until the transition details are published.

Designations and certifications

The bar for program standing is going up. Participation is no longer enough.

Every structural change in the June and July 2026 program update points in the same direction: Microsoft is replacing lightweight validations and self-attested credentials with formal certifications and, in the case of security specializations, third-party audits. The pattern is consistent. Partners who have been meeting program requirements through assessments and customer references are now being asked to prove delivery capability with more rigor.

For alliance leaders, four areas require immediate attention.

Partner University

Closed June 15. No pathway back. Partners who did not link their team's Partner University assessments to Learn profiles before June 15 have lost those skilling points permanently. Linked assessments remain valid until June 2027. After that, the requirement shifts entirely to formal certifications. Partners relying on Partner University credits for Solutions Partner designation should audit their skilling score now to identify gaps before renewal cycles hit.

Certifications

Agentic AI credentials replaced traditional role-based certifications in waves, June 30 through August 31, 2026. Key retirements include: Azure AI Engineer Associate, Azure Data Scientist Associate, Power Platform Solution Architect Expert, and Dynamics 365 Supply Chain Management Functional Consultant Expert. Key replacements include: Azure AI Apps and Agents Developer Associate, Machine Learning Operations Engineer Associate, and Agentic AI Business Solutions Architect (AB-100), which now spans several specializations including Supply Chain, Finance, and Agentic Business Solutions (the merged Low Code and Intelligent Automation track). Skilling earned before a retirement counts for one year, so audit which team certifications retired and schedule replacement exams before that credit lapses.

Microsoft 365 Copilot Specialization

Requirements overhauled July 2026, no confirmed enforcement date. Renamed from Copilot Specialization, the performance bar shifts to account-only paid monthly active usage growth. Customer references are replaced by a third-party capabilities audit that requires real customer examples and is valid for two years. Skilling drops MS-102 and the retired APL-4002 and APL-7008 applied skills, and adds AB-100, AB-620, and SC-401. Earning it still requires an active Solutions Partner designation in AI Business Solutions or Security. Microsoft has not published a hard deadline tying this specialization to Frontier Accelerate Copilot track eligibility; treat the audit requirement as the real bar. See the MCAPS FY27 recap brief for the full context.

Designation Badge Rename

Badges renamed August 5, 2026. No transition required. In August 2026 Microsoft renamed the customer-facing Solutions Partner badges to Cloud & AI Platforms, AI Business Solutions, and Security. Azure-aligned designations sit under Cloud & AI Platforms; Modern Work and Business Applications sit under AI Business Solutions. Solution paths, scoring, and benefits are unchanged; update customer-facing materials. This is the three-pillar taxonomy (Cloud & AI Platforms, AI Business Solutions, Security) now used across Microsoft's own partner materials. See the MCAPS FY27 recap brief for the full context.

Frontier Partner Specialization

New audited credential replacing the current Frontier Partner badge; badge retires at the end of June 2027. The existing badge (three Solutions Partner designations plus three specializations) does not auto-convert. The replacement requires four specializations held simultaneously on the same Partner Global Account (Microsoft Copilot with audit, AI Apps or AI Platform on Azure, Data Security, and Identity and Access Management), plus a skilling bar (five individuals on the Frontier Transformation Engineer learning path, three with Fabric Analytics Engineer Associate) and a third-party audit renewed every two years. Microsoft says it opens for enrollment later in FY27. Concierge engagements began August 2026, per FY27 GTM Kickoff session materials (July 28, 2026); Microsoft has not published these details publicly. Partners holding the current badge should treat this as the real target, not a rebrand.

Specialization Mergers

Three specialization tracks consolidated into new categories, effective July 31, 2026. Analytics on Azure now includes Data Warehouse Migration to Microsoft Azure and Business Intelligence. Agentic Business Solutions replaces Low Code Application Development and Intelligent Automation. App Modernization on Microsoft Azure merges Kubernetes on Microsoft Azure and Migrate Enterprise Applications. Partners who held a predecessor specialization should confirm in Partner Center how their standing and anniversary date carried over. The naming shift toward "Agentic" is deliberate: Microsoft is repositioning these workloads around AI delivery capability, not traditional deployment motions.

Security Audit

All four security specializations moved to third-party audit model, effective July 30, 2026. Cloud Security, Data Security, Identity and Access Management, and Threat Protection now require third-party validation of actual delivery capability, replacing the customer reference model. Audits are partner-funded, conducted by independent third-party auditors, and recur every two years. Partners have a six-month extension on their anniversary date to allow audit preparation. Security specializations are no longer achievable through documentation and references alone. Partners that hold these specializations as marketing credentials should begin assessing their actual audit readiness now.

What actually matters

The production gap is operational. It has not changed.

Every change described in this brief operates at the administrative or programmatic layer: new referral fields, retired certifications, consolidated specializations, an audit model for security, a unified marketplace. None of these change the fundamental reason most partners with Co-Sell Ready status see no meaningful field engagement.

The reason is the same one it was before 2022, before the Solutions Partner designation, and before the MAICPP rebranding. Microsoft field sellers engage partners when there is a financial incentive, when the co-sell motion is operationally easy to execute, and when the right relationship exists to surface the opportunity. Those three conditions are operational. They do not appear because a partner achieves a program status. They appear because someone is managing the alliance function: maintaining the PDM relationship, submitting and responding to referrals on cadence, keeping co-sell assets current, and tracking the ACR trajectory against the IP Co-Sell Eligible threshold.

What has changed is the administrative urgency. Partner University skilling pathways have closed. Certification paths are shifting under active designation strategies. Co-sell referral workflows now have mandatory data fields, and API submissions that omit them are not accepted. Frontier Accelerate for Marketplace, open since September 28, 2026, brings ISV Success, Marketplace Rewards, Azure IP co-sell, and certified software designations into one entry structure; existing participants transition automatically at renewal. Partners without someone tracking these changes are falling behind on the prerequisites for a program they may already be underutilizing.

The IMS Co-Sell Readiness Index (IMS CRI) places a partner on the map. It identifies the specific gaps between current program status and the next meaningful milestone, including where program changes have created new gaps since the last assessment. Ten minutes of input. A clear output on where you actually stand.

Still
operational

The co-sell production gap is a motion problem, not a program mechanic

Program changes affect the administrative layer: certifications, referral fields, specialization names, validation models. The underlying production gap, why partners at Co-Sell Ready see no field engagement, is not fixed by any of them.

At Co-Sell Ready, Microsoft sellers have no quota credit incentive to engage. That mechanic has not changed through six structural program updates. It will not change regardless of what the program is called next year.

Program posture audit

Nine things to verify before your next partner review.

Each item below corresponds to a structural change in the program since September 2024. If you have not confirmed the item in the last 90 days, treat it as an open gap.

Status checked September 28, 2026: This checklist reflects MCAPS Start for Partners (July 22), the FY27 GTM Kickoff (July 28), and Microsoft's partner announcements through September 2026. Item 09 will change most now that Frontier Accelerate for Marketplace is open.

Co-sell referral workflow updated for QRP retirement. The Qualified Referral Program retired March 2026. If your internal process or CRM workflow referenced QRP intake, it needs to be rebuilt against the standard Partner Center co-sell referral experience.

"Marketplace Intent" field populated in all API referral submissions. This field became mandatory on January 5, 2026, and API submissions without it are not accepted. Confirm your CRM integration populates it and surfaces any rejection, and verify it against the current Partner Center API schema.

Team certification audit completed against the 2026 retirement list. Traditional role-based certifications retired in waves from June 30 through August 31, 2026, and skilling earned before a retirement counts for one year. Any team member holding a retired certification that supports a current Solutions Partner designation needs its replacement credential before that credit lapses.

Partner University assessment-to-profile linkings confirmed or abandoned. The window closed June 15, 2026. If your team completed linkings before the deadline, verify they are reflected in your Partner Center profile. If not, those skilling records are gone and your designation evidence needs to be rebuilt through formal certifications.

Marketplace listing category reviewed under the unified framework. The September 2025 consolidation introduced new category definitions and a dedicated AI Apps & Agents category. An offer that was correctly categorized under the old structure may be misfiled under the new one, reducing discoverability in search and browse.

Solutions Partner designation performance thresholds verified against current requirements. Thresholds for Customer Success and Skilling have shifted since the initial rollout of the designation framework. Confirm your current evidence score against the thresholds that apply at your next anniversary date, not the ones that applied when you first achieved designation.

IP Co-Sell Eligible status confirmed and co-sell assets current in Partner Center. One-pager and pitch deck should be reviewed against the current field standards Microsoft uses to evaluate co-sell material quality. Assets that were approved under older standards may still appear valid but may not pass the informal review sellers perform when deciding whether to bring a partner into a deal.

Security specialization audit readiness assessed (if applicable). If your organization holds Cloud Security, Data Security, Identity and Access Management, or Threat Protection specializations, the third-party audit model is now the path to renewal. Begin assessing your actual delivery capability against the audit criteria now. Six-month extension windows close before most partners are ready.

Frontier Accelerate for Marketplace entry requirements reviewed for ISV Success, Marketplace Rewards, Azure IP co-sell, and certified software designation eligibility. Frontier Accelerate for Marketplace, which opened September 28, 2026, combines all four into a single entry structure (launch brief). Existing ISV Success, Marketplace Rewards, and Azure IP co-sell participants transition automatically at renewal. Microsoft previewed this consolidation at Ignite 2025 as App Accelerate. Review current program requirements now and track the transition before your next renewal or application window.

Find out where your Microsoft co-sell motion stands before the next round of changes lands.

The IMS CRI takes 10 minutes. You will know exactly what the current state of the program means for your specific position, before any scope is set.

Measure your readiness

Every structural change Microsoft has made to the partner program since 2022 has raised the bar for verified delivery capability and reduced the value of participation without proof of results. That direction is consistent. Partners already at IP Co-Sell Eligible with a functioning GTM motion will move forward as the program continues to evolve. Partners still at Co-Sell Ready, waiting for field engagement the program does not incentivize at that status, will keep waiting. The program will keep changing. That part of it will not.