Intelligent Modern Solutions
Intelligent Modern Solutions
Fractional Alliance & GTM Advisory  |  intelligentmodernsolutions.com
Practitioner Brief
Program posture

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

ISV Success tiers, 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 tiers
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 now has three distinct tiers, and not every enrolled partner is in the right one. Frontier Accelerate for Marketplace is introducing a co-sell access pathway that changes who qualifies for field engagement and on what basis. The MCEM framework distinguishes Solutions co-sell from Services co-sell in ways that directly affect how referrals route and how Microsoft field teams allocate attention. Certifications that supported your designation evidence may be retiring before your anniversary. 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 Q1 FY27 closes.

1
ISV Success tiers
Three tiers. Most enrolled partners do not know which one they are in or why it matters.

Microsoft restructured ISV Success into three distinct tiers: Core, Expanded, and Advanced. The tiers differ in annual investment, Microsoft benefit access, eligibility criteria, and the level of support and co-sell resourcing available to the partner. This is not cosmetic renaming. The structure determines which program benefits are available to you and under what conditions.

Core is the base tier. It provides foundational marketplace and co-sell onboarding support, standard benefit access, and annual fee billing. Most partners who enrolled in ISV Success before the restructure landed here.

Expanded is invitation-only. Microsoft selects partners for this tier based on Marketplace performance signals, pipeline traction, and transact intent. Benefits are materially enhanced relative to Core. Partners in this tier typically have an active PDM relationship and are producing referral pipeline.

Advanced requires the Certified Software Designation (CSD), a new Microsoft program designation that gates the highest benefit tier in the program. CSD eligibility criteria are managed by Microsoft and have not been publicly detailed in full. Partners who achieve CSD access the highest available ISV Success benefits, including Microsoft-funded cash incentives and Azure credit allocations that are not available at Core or Expanded.

If you are enrolled in ISV Success and have not confirmed your current tier, this is the starting point. The tier you are in is not necessarily the tier you are eligible for, and CSD eligibility is a separate assessment from everything you did to enroll. CSD eligibility is assessed through a Microsoft-managed application; contact your ISV Success manager in Partner Center or your PDM to initiate the review.

ISV Success
Three Tiers
Core → Expanded → Advanced

Core: Base enrollment, standard benefits, annual fee. The default landing tier for most partners who enrolled through ISV Success previously.

Expanded: Invitation-only. Enhanced benefits and support. Microsoft selects based on Marketplace performance signals, pipeline traction, and transact intent.

Advanced: Requires CSD. Highest benefit tier. Cash incentives and Azure credits gated here. Not accessible without the Certified Software Designation.

2
Frontier Accelerate for Marketplace
The $100K threshold is no longer the only path to early co-sell access.

Frontier Accelerate for Marketplace is Microsoft's confirmed consolidation of ISV Success, Marketplace Rewards, Azure IP co-sell, and certified software designations into a single unified program entry point, confirmed by name and launch date at the FY27 GTM Kickoff (July 28, 2026) and directly in Microsoft's own June and July 2026 Partner Center announcements. Earlier partner briefings referred to this consolidation under the unconfirmed working name "App Accelerate"; that name never appeared in Microsoft's own FY27 GTM Kickoff materials and should be treated as superseded. The structural change is significant. The most operationally relevant element for partners below the Azure IP Co-Sell Eligible threshold is the nomination pathway described below, which remains unconfirmed in its specific mechanics as of this update.

Partner briefings ahead of GA described a possible nomination pathway: partners below the $100K ACR threshold could be nominated for early co-sell access based on MACC customer traction and pipeline strength, rather than trailing revenue alone, a departure from the current binary of reach $100K or stay at Co-Sell Ready. Microsoft's FY27 GTM Kickoff materials confirmed the program's name, structure, and launch timing, but did not confirm or publish specific nomination criteria for this pathway. Treat it as a plausible but not yet confirmed mechanic.

The practical implication either way: MACC customer traction is worth tracking now, whether or not the specific nomination pathway above is confirmed as described. Partners who are tracking MACC traction data and can articulate their pipeline strength will be better positioned 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 before Frontier Accelerate for Marketplace reaches general availability. Your PDM is the fastest path to identifying which active opportunities involve MACC customers.

Frontier Accelerate for Marketplace launches September 2026, confirmed at the FY27 GTM Kickoff. Do not restructure your current ISV Success or Marketplace Rewards engagement until the transition framework is published. The specific nomination criteria and how current ISV Success contracts interact with the new program have not been fully disclosed.

Update, Aug 2026: The FY27 GTM Kickoff confirmed this consolidation's real name (Frontier Accelerate for Marketplace, not "App Accelerate") and a September 2026 launch date. Microsoft's own June and July 2026 Partner Center announcements, and Mira Ayad (GM, Microsoft Marketplace) speaking publicly in August 2026, confirm the consolidation folds together four programs — ISV Success, Marketplace Rewards, Azure IP co-sell, and certified software designations — not just the first two, as earlier language on this page stated. Nomination criteria for the early co-sell access pathway described above remain unpublished. See the MCAPS FY27 recap brief for the full FY27 GTM Kickoff recap.
Frontier Accelerate
for Marketplace
Unified program entry: ISV Success, Marketplace Rewards, Azure IP co-sell, and certified software designations

A possible nomination pathway: partners below $100K ACR could be nominated for early co-sell access based on MACC customer traction and pipeline signals, not trailing revenue. Not yet confirmed in its specific mechanics.

Launches September 2026, confirmed at the FY27 GTM Kickoff (July 28, 2026). Formerly referred to under the unconfirmed name "App Accelerate."

3
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. Marketplace Rewards expand to enhanced tiers. 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. Azure credits and Azure Consumption Offers are explicitly excluded from the ACR count.

Add to this the MCEM distinction. Microsoft's commercial engagement model formally distinguishes Solutions co-sell, for software and ISV partners, from Services co-sell, for systems integrators, GSIs, and managed service providers. If your PDM is tracking your engagement under the Services co-sell motion because your organization delivers implementation services alongside your software, you may be missing quota credit structures and referral routing that are specific to the Solutions track. Partners with a platform-plus-services business model need to confirm which MCEM motion they are registered under, and whether the motion matches how Microsoft field teams are actually positioning them in deals.

$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 Basic tier only Enhanced; grows with ACR
Frontier Accelerate for Marketplace nomination pathway eligibility Possible if MACC traction qualifies Full program access
MCEM Solutions co-sell routing Limited visibility in routing Active in Solutions co-sell referral routing

4
Certification posture
Two deadlines have already passed. One more is active now.

The FY27 certification overhaul has three components that directly affect designation evidence. Partners with Solution 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
Audit required by July 31, 2026. The June-July 2026 certification overhaul is retiring traditional role-based credentials and replacing them with agentic AI-focused certifications. Key retirements include Azure AI Engineer Associate and Azure Data Scientist Associate. Key replacements include Azure AI Apps and Agents Developer Associate and Agentic AI Business Solutions Architect (AB-100). If a team member's certification supports your current Solution Partner designation evidence, and that certification is on the retirement list, you need a replacement credential in place before your next designation anniversary. Microsoft allows one year of validity for certifications earned before their retirement date.
Security Audit
Third-party audit model effective July 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 June 30, 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. Enrollment and audit scheduling roll out in Partner Center through 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.


5
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.

01
Which ISV Success tier are you in? Core, Expanded, or Advanced. If you do not know, log into Partner Center and verify your enrollment status under ISV Success. This is the foundation. Everything else in the program's benefit structure depends on tier placement.
02
Have you assessed CSD eligibility for the Advanced ISV Success tier? The Certified Software Designation is a separate track from ISV Success enrollment and from Solution Partner designations. If your product meets Microsoft's technical and commercial standards, CSD eligibility is not automatic but it may be within reach. Not assessing it is not a neutral decision: it is leaving the highest ISV Success benefit tier off the table without knowing whether it was accessible.
03
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.
04
Do your API-based co-sell referral submissions populate the Marketplace Intent field? The field became mandatory in January 2026. CRM integrations that do not populate it are silently failing at the data layer, submitting referrals that never complete intake. If you have a CRM integration, verify it against the current Partner Center API schema. If you are not sure, check your referral acceptance rate in Partner Center for any drop after January 2026.
05
Have you audited team certifications against the July 2026 retirement list? Any certification supporting your Solution Partner designation evidence that is on the retirement schedule needs a replacement credential in place before your next anniversary date. Partners have until July 31 to identify the gaps. After that, the exam availability and scheduling windows become the constraint.
06
Are you tracking MACC customer traction for the Frontier Accelerate for Marketplace nomination pathway? 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 are in a materially better position to make the case for nomination than those who are not tracking it, if the nomination pathway is confirmed as described. This is data you should have visibility into now, before Frontier Accelerate for Marketplace reaches general availability in September 2026, because the pipeline signal Microsoft would use for nomination evaluation is being built from current activity. Your PDM can help identify which active opportunities involve customers with MACC balances.
07
Do you know which Microsoft MCEM motion you are registered under? Solutions co-sell for software and ISV partners routes and scores differently than Services co-sell for implementation partners. Partners who deliver services alongside their platform sometimes find their PDM is tracking them under the Services motion, which does not carry the same quota credit structures for Microsoft sellers and does not route the same way in deal-level referrals. Confirm with your PDM which motion your organization is under and whether 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 the entry requirements again.
The IMS CRI maps your position across all six co-sell dimensions in ten minutes. Tier, status, referral mechanics, designation posture. One clear output before any scope is set.
Measure your readiness

The FY27 updates have not made the co-sell motion simpler. They have added more tiers, 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.