Program posture

The Program Changed. Here Is What That Means for Your Co-Sell Motion.

ISV Success packages, Frontier Accelerate for Marketplace, co-sell status mechanics, and the FY27 certification shift: a structured audit of where your program posture actually stands.

ISV Success packages

Frontier Accelerate for Marketplace

Co-sell status

Certification posture

Posture audit

The companion brief, The Microsoft Partner Program Has Not Stopped Changing. Here Is Where It Actually Stands, covered what changed in the Microsoft AI Cloud Partner Program since FY25: six structural updates across certifications, referral mechanics, marketplace unification, and designation requirements. This brief starts where that one ends. Knowing what changed is not the same as knowing where you stand in the structure that now exists.

The FY27 updates have not reshuffled all partners equally. ISV Success, whose Core, Expanded, and Advanced packages date to November 2024, is folding into Frontier Accelerate for Marketplace, and existing participants transition automatically at renewal. A nomination-based pilot for partners below the $100K milestone could change who reaches co-sell benefits early. Whether a solution co-sells as IP or as services is set by its solution type in Partner Center, not by MCEM. Certifications that supported your designation evidence may have retired in the June to August 2026 waves. None of these are information problems. They are posture problems. This brief maps the questions a partner with a co-sell motion needs to answer before its next renewal.

ISV Success packages

Three packages, now folding into two paths. Know which one you hold before your renewal does it for you.

ISV Success has offered three packages, Core, Expanded, and Advanced, since November 2024. They are not a new FY27 restructure. What changes in FY27 is where they lead. ISV Success is folding into Frontier Accelerate for Marketplace, announced at MCAPS Start for Partners and opened on September 28, 2026. Existing ISV Success, Marketplace Rewards, and Azure IP co-sell participants transition automatically at renewal.

Microsoft's program page shows Frontier Accelerate for Marketplace as two paths. A no-cost path carries partner incentives, go-to-market resources, Azure sponsorship, and co-sell eligibility. A paid Premium path adds $30,000 in Azure credits, technical presales and deployment consultations, and closer Microsoft engagement.

The audit question is not which path sounds better. It is which package you hold today, when it renews, and which path your current benefits map to once you transition. Your package and renewal date decide when the change reaches you and what you carry into it. A partner that lets renewal arrive unexamined has made the choice by default.

If you are enrolled in ISV Success and have not confirmed your current package and renewal date, this is the starting point. Check your enrollment in Partner Center, then ask your ISV Success contact or PDM how your benefits map to the no-cost and Premium paths. The certified software designation, one of the four elements Frontier Accelerate for Marketplace brings together, is a separate assessment worth confirming at the same time.

ISV Success
Two Paths Ahead

Core, Expanded, Advanced → no-cost or Premium

Today: Core, Expanded, and Advanced packages, in place since November 2024. Confirm which one you hold and when it renews.

No-cost path: Partner incentives, go-to-market resources, Azure sponsorship, and co-sell eligibility.

Premium path: Paid. Adds $30,000 in Azure credits, technical consultations, and closer Microsoft engagement.

Frontier Accelerate for Marketplace

The $100K threshold is no longer the only path to early co-sell access.

Frontier Accelerate for Marketplace combines ISV Success, Marketplace Rewards, Azure IP co-sell, and certified software designations into a single program entry point. Microsoft announced it at MCAPS Start for Partners, and the program opened on September 28, 2026 (what launched and what to check before renewal: Frontier Accelerate Is Live). 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 most operationally relevant element for partners below the Azure IP Co-Sell Eligible threshold is the nomination pilot described below.

Microsoft's 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 rather than trailing revenue alone. That is a departure from the old binary of reach $100K or stay at Co-Sell Ready. How it works inside Frontier Accelerate for Marketplace is not yet published.

The practical implication either way: MACC customer traction is worth tracking now, whatever form the pilot takes inside the new program. Partners who track MACC traction data and can articulate their pipeline strength have a stronger case to make regardless of the final mechanics. If you do not currently have a view into which of your customers are Microsoft Azure Consumption Commitment customers, that is a gap worth closing as partners move into Frontier Accelerate for Marketplace. Your PDM is the fastest path to identifying which active opportunities involve MACC customers.

Do not restructure your current ISV Success or Marketplace Rewards engagement until the transition details are published. How the pilot's criteria and current ISV Success contracts carry into the new program has not been fully disclosed.

Status checked September 28, 2026: Frontier Accelerate for Marketplace opened on September 28, 2026, and existing participants transition automatically at renewal. How the Early access to co-sell benefits pilot works inside it is not yet published. See the MCAPS FY27 recap brief for the MCAPS Start for Partners and FY27 GTM Kickoff context.

Frontier Accelerate
for Marketplace

Unified program entry: ISV Success, Marketplace Rewards, Azure IP co-sell, and certified software designations

Early access to co-sell benefits: a nomination-based pilot from Ignite 2025 for partners below the $100K MBS or ACR milestone, weighing MACC, customer traction, and pipeline strength. How it works inside the new program is not yet published.

Announced at MCAPS Start for Partners and opened September 28, 2026; previewed at Ignite 2025 as App Accelerate. Existing participants transition automatically at renewal.

Co-sell status

Co-Sell Ready is visibility. Azure IP Co-Sell Eligible is engagement. Most partners conflate them.

Through all FY27 program changes, one mechanic has not moved: the distinction between Co-Sell Ready and Azure IP Co-Sell Eligible determines whether Microsoft sellers have a financial reason to include your solution in a deal. This distinction is the most consequential in the entire program and, consistently, the most misread.

At Co-Sell Ready, a Microsoft field seller can see your solution in internal catalogs. There is no quota credit for the seller. No MACC eligibility for the customer. No deal-level financial incentive for Microsoft to bring you in. Co-Sell Ready is a prerequisite. Not an outcome.

At Azure IP Co-Sell Eligible, the seller earns quota credit on co-sold deals. Enterprise customers can apply your Marketplace purchases toward committed Azure spend. Referral volume from Microsoft field teams increases. The four requirements for this status are unchanged under the current program structure: a transactable Marketplace offer, $100K trailing ACR or Marketplace Billed Sales, Azure-platform technical validation, and a filed reference architecture. As of the Sept 28, 2026 launch of Frontier Accelerate for Marketplace, Microsoft's published $100K requirement is unchanged. Azure credits and Azure Consumption Offers are explicitly excluded from the ACR count.

Add to this the solution type distinction. Whether a solution co-sells as IP or as services is set by the solution type chosen in Partner Center, and for Azure IP co-sell that solution type must be "IP." If your organization delivers implementation services alongside its software and a listing is set up as a services solution, that listing cannot qualify for Azure IP co-sell benefits, however strong the product is. Partners with a platform-plus-services business model need to confirm which solution type each listing uses, and whether it matches how Microsoft field teams are actually positioning them in deals. (Marketplace Rewards tiers are a separate matter: they scale with trailing-12-month Marketplace Billed Sales, independent of co-sell status.)

$100K

Azure Consumed Revenue or Marketplace Billed Sales, trailing 12 months, is the threshold for Azure IP Co-Sell Eligible. Azure credits and Azure Consumption Offers are excluded from this count. Partners burning Azure credits at scale may be further from this threshold than their dashboard suggests. The typical path from first Marketplace listing to IP Co-Sell Eligible is 6 to 12 months, depending on ACR velocity and how quickly the transactable offer and technical validation are in place.

What it means in practice	Co-Sell Ready	Azure IP Co-Sell Eligible
Microsoft seller has a financial reason to engage	✗ No quota credit	✓ Seller earns quota credit
Customer MACC eligibility	✗ Not available	✓ Purchases decrement committed Azure spend
Marketplace Rewards tier	Scales with trailing-12-month MBS	Same; set by MBS, not co-sell status or ACR
Early access to co-sell benefits (nomination pilot)	Possible below the $100K milestone	Not needed; benefits already apply
Solution type in Partner Center	Must be "IP" to progress to IP co-sell	✓ Set to "IP"

Certification posture

The deadlines have passed. The one-year credit window has not.

The FY27 certification overhaul has three components that directly affect designation evidence. Partners with Solutions Partner designations need to know where their team stands on each.

Partner University

Window closed June 15, 2026. Partners who did not complete assessment-to-Learn profile linkings before June 15 cannot retroactively restore those records through Partner University. If your designation evidence relied on Partner University assessments, audit your current skilling score in Partner Center now. Existing linked assessments remain valid through the period noted in your Partner Center skills profile. After that window closes, the requirement shifts entirely to formal certifications.

Cert Retirements

Retirements ran June 30 through August 31, 2026. The 2026 certification overhaul retired traditional role-based credentials in waves (for example MB-240 on June 30; AZ-204 and MB-280 on July 31; AZ-500 and PL-200 on August 31) and replaced them with agentic AI-focused certifications. Key replacements include Azure AI Apps and Agents Developer Associate and Agentic AI Business Solutions Architect (AB-100). Skilling earned before a retirement counts for one year. If a retired certification supports your current Solutions Partner designation evidence, you need a replacement credential in place before that credit lapses.

Security Audit

Third-party audit model effective July 30, 2026. All four Microsoft Security specializations (Cloud Security, Data Security, Identity and Access Management, Threat Protection) have moved from customer reference validation to independent third-party audits conducted every two years. Partners holding these specializations as marketing credentials, without the operational depth to support an audit, face a renewal path that is significantly more demanding than the one they used to earn the specialization initially. Six-month anniversary extensions are available for audit preparation but close before most partners are ready.

Frontier Partner Specialization

Current Frontier Partner badge retires at the end of June 2027; the replacement does not auto-convert. Where the badge required three Solutions Partner designations plus three specializations, the new Frontier Partner Specialization 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 and a third-party audit renewed every two years. If your designation-evidence audit is treating the legacy badge as the durable target, it is auditing against a credential with an expiration date. Microsoft says the specialization opens for enrollment later in FY27.

For the full change-by-change breakdown of FY27 certification and designation updates, see the companion brief: The Microsoft Partner Program Has Not Stopped Changing. Here Is Where It Actually Stands. Specific certification names and replacement exam codes should be verified against the Microsoft certification catalog before acting on them; retirement lists are updated on a rolling basis.

Posture audit

Seven questions. Not knowing the answer to any of them is itself a program gap.

These are not administrative tasks. They are diagnostic questions about your current position in the FY27 program structure. Each one corresponds to a specific element covered in this brief. If you cannot answer it, that is the gap.

Which ISV Success package are you in, and when does it renew? Core, Expanded, or Advanced. If you do not know, log into Partner Center and verify your enrollment under ISV Success. Existing participants move to Frontier Accelerate for Marketplace automatically at renewal, so your renewal date sets your timeline.

Have you assessed certified software designation eligibility? The certified software designation is a separate track from ISV Success enrollment and from Solutions Partner designations, and it is one of the four elements Frontier Accelerate for Marketplace brings together. If your product meets Microsoft's technical and commercial standards, eligibility is not automatic but it may be within reach. Not assessing it is not a neutral decision: it leaves a benefit off the table without knowing whether it was accessible.

What is your trailing-12-month ACR, net of Azure credits and Azure Consumption Offers? The $100K threshold for Azure IP Co-Sell Eligible is calculated on Azure Consumed Revenue and Marketplace Billed Sales. Azure credits and ACOs are excluded. Your Partner Center dashboard may show a higher ACR figure than what Microsoft uses for IP Co-Sell Eligible evaluation. Know the net number.

Do your API-based co-sell referral submissions populate the Marketplace Intent field? The field has been required for API referral submissions since January 5, 2026, and API submissions without it are not accepted. If you have a CRM integration, confirm it populates the field and surfaces any rejection to your team, and verify it against the current Partner Center API schema. Check your referral acceptance rate for any drop after January 2026.

Have you audited team certifications against the 2026 retirement list? Certifications retired in waves from June 30 through August 31, 2026. Skilling earned before a retirement counts for one year, so any retired certification supporting your designation evidence needs a replacement credential before that credit lapses. Exam availability and scheduling windows are now the constraint.

Are you tracking MACC customer traction for the Early access to co-sell benefits nomination pilot? Microsoft Azure Consumption Commitment status is customer-specific: your customer either has a MACC balance in place or they do not. Partners who understand which of their active deals involve MACC customers can make a stronger case for nomination than those who are not tracking it, whatever form the pilot takes inside Frontier Accelerate for Marketplace. This is data you should have visibility into now, while partners move into the new program, because the pipeline signal Microsoft would use for nomination is being built from current activity. Your PDM can help identify which active opportunities involve customers with MACC balances.

Do you know which solution type each listing uses in Partner Center? Whether a solution co-sells as IP or as services is set by its solution type in Partner Center, and Azure IP co-sell requires that type to be "IP." Partners who deliver services alongside their platform sometimes list a solution under a services type, which cannot qualify for Azure IP co-sell benefits for Microsoft sellers or customers. Confirm the solution type on each listing, and check with your PDM that it matches how you are actually positioned in your deals.

Know your exact position in the FY27 program structure before Frontier Accelerate for Marketplace changes how your renewal works.

The IMS CRI maps your position in ten minutes across all six dimensions: Marketplace Transactability, Co-Sell Eligibility & Status, Microsoft Field Traction, Enablement & Sales Readiness, Program & Incentive Capture, and Measurement & Attribution.

Measure your readiness

The FY27 updates have not made the co-sell motion simpler. They have added more paths, more gates, more administrative precision to a program that was already difficult to navigate without someone dedicated to tracking it. The seven questions above are the starting point. Not knowing the answers does not mean the program is not affecting your position. It means it is doing so without your awareness.