Co-sell acceleration

The 90-Day Co-Sell Motion: From Co-Sell Ready to IP Co-Sell Eligible

A specific milestone sequence for partners who need Azure IP Co-Sell Eligible status before the next board meeting, not another program overview.

The eligibility target

Two converging tracks

The Marketplace dependency

The early-access signal

What derails the 90 days

The 90-day checklist

Most partners treat Co-Sell Ready as the finish line. It is the starting line. Co-Sell Ready puts a partner's solution in front of Microsoft field sellers. It does not give any seller a financial reason to act on it. Azure IP Co-Sell Eligible is where the seller incentive activates: quota credit on the deal, Microsoft Azure Consumption Commitment (MACC) eligibility for the offer, enhanced Marketplace Rewards. That is the actual target for any partner whose leadership wants to see Microsoft field engagement, not just program enrollment.

This brief is not a program overview. It is the milestone sequence: what has to be true in the first 30, 60, and 90 days, which parts of that sequence depend on Microsoft's own review timelines rather than partner effort, and where the honest edge of a 90-day claim actually sits.

The eligibility target

What Azure IP Co-Sell Eligible actually requires

Azure IP Co-Sell Eligible has four requirements, and they still read the same: a transactable Marketplace offer, USD100,000 in trailing 12-month Azure Consumed Revenue (ACR) or Marketplace Billed Sales (MBS) (co-sell requirements page, updated August 18, 2026), Azure-platform technical validation, and a reference architecture diagram where the offer type requires one. What changed in July is the accepted evidence. In FY27 Microsoft made co-sell Marketplace-first: partner-reported ACR (PRACR) no longer operates as a broad co-sell mechanism, and co-sell credit for Marketplace transactions continues to be recognized through MBS. Azure credits and Azure Consumption Offers (ACOs) are explicitly excluded from the $100K count. A partner burning through Azure credits at scale may be further from the threshold than the Partner Center dashboard suggests.

One precision note before anything else: "Azure IP Co-Sell Eligible" and "IP Co-Sell Eligible" are the same status. Microsoft's own documentation uses both forms interchangeably. Do not let a program deck or a PDM's shorthand make it sound like these are two different tiers. They are not.

Requirement 1

Transactable Marketplace offer. Mandatory since July 2023. Not optional, not a "recommended" step. No offer, no eligibility, regardless of revenue.

Requirement 2

$100,000 trailing 12-month ACR or MBS. Rolling window, not a fixed fiscal period. Azure credits and Azure Consumption Offers are excluded. Consumption counts only if it transacts through Marketplace or Microsoft already attributes it to your organization. See Section 2.

Requirement 3

Azure-platform technical validation. A Microsoft-side review, not a self-attestation. Schedule this in parallel with Marketplace offer review, not after it clears. See Section 3.

Requirement 4

Reference architecture diagram. Required for SaaS and Dragon Copilot offers; optional for Azure Application, Container, and Virtual Machine offers. A documentation task, not a revenue task. Completable well inside 90 days by any partner who starts it early.

$100K

Trailing 12-month ACR or Marketplace Billed Sales, net of Azure credits and Azure Consumption Offers. The typical timeline from first Marketplace listing to IP Co-Sell Eligible runs 6 to 12 months industry-wide. This brief is about the partners for whom that timeline can realistically compress to 90 days, and clear about the ones for whom it cannot.

Two converging tracks

Why 90 days is real for some partners and false for others

The 90-day framing lands differently depending on which track a partner is starting from, and naming that difference is what separates a credible plan from a sales promise. Track one is mechanical: publish a transactable Marketplace offer, complete Azure-platform technical validation, file the reference architecture, and assemble Co-Sell Ready collateral. None of these four steps require revenue. All four are realistically completable within 90 days by any partner who starts on day one, because the constraint is process, not money.

Track two is revenue. The $100K ACR or MBS threshold is measured on a trailing 12-month rolling window, not a fixed fiscal period. That detail matters more than it looks. A partner with a deal already generating Azure consumption that transacts through Marketplace, or that Microsoft already attributes to the partner's organization, sees it accrue in the trailing window month by month. If the deal is large enough and recent enough, crossing $100K within 90 days is a provable outcome. A partner starting both tracks from zero, with no offer, no technical validation, and no revenue in flight, cannot compress trailing-12-month math by working harder.

The claim is a converging pair, not a universal promise. The mechanical track is 90-day-completable for anyone who starts today. The revenue track is 90-day-completable for partners who already have consumption moving. Selling "90 days for everyone" regardless of starting point is not a credible claim, and it is not the one this brief makes.

Rolling
window

The $100K threshold is trailing 12 months, recalculated every month

A partner with attributable consumption already in flight sees it accrue in the trailing window every month. This is what makes a real 90-day crossing possible for some partners and not others.

Partners starting from zero revenue should treat 90 days as the target for the mechanical checklist, not as a revenue guarantee.

The Marketplace dependency

The one variable in the sequence you cannot compress by working harder

Marketplace offer review is the one dependency in this sequence controlled entirely by Microsoft's own queue, not partner effort. Industry sources, Clazar, Tackle, and other Marketplace practitioner guides, not an official Microsoft-published SLA, put typical review timelines at four to six weeks. Treat that figure as informed consensus, not a guarantee. The practical implication: submit the offer on day one of the 90-day sequence, not after the mechanical checklist and revenue tracking feel further along. Waiting to submit is the single most common way partners lose weeks they cannot get back.

Two Marketplace mechanics are worth knowing once the offer is live. First, mid-term amendments: a newer Marketplace capability, described at the Partner Insights event in August 2026, that lets a partner modify an existing private offer, pricing, terms, or duration, without rebuilding it from scratch. Second, Resale Enabled Offers (REO), Multiparty Private Offers (MPO), and CSP private offers are three separate channel routes, not interchangeable labels. They are set up after the offer is live; they are not offer types that go through certification, so they add nothing to the review clock. Decide which route fits your channel motion while the offer is in review, and confirm it with your Microsoft contact.

One easy-to-miss lever, regardless of tier: the "Request a private offer" button on a Marketplace listing is off by default, even on offers that are already transactable. Turning it on costs nothing but a toggle and a republish, and it is worth checking on day one alongside the initial offer submission. For IP co-sell questions, Microsoft's documented contact is IPCosellDesk@microsoft.com (July 10, 2026 announcement).

4–6 wks

Typical Marketplace offer review timeline, per independent practitioner sources. This is not an official Microsoft SLA. Submit the offer on day one of the sequence, not once the rest of the checklist feels ready. This is the single dependency in the entire 90-day plan that Microsoft controls, not the partner.

The early-access signal

Two early paths for partners below $100K

Path one is documented: Azure IP Co-Sell Acceleration, a Microsoft for Startups benefit published on Microsoft Learn (updated May 7, 2026). Criteria: an active Microsoft for Startups member; at least $8,000 a month of Azure consumption for three consecutive months (credits count); a live transactable SaaS offer that has passed SaaS technical validation; three customers in the past 12 months; a completed Co-sell Solutions page; and either $1M+ in submitted co-sell referrals or one $500K+ Marketplace-billed opportunity. The designation then carries a 120-day window to reach $100,000 in Marketplace Billed Sales or paid Azure consumption over the trailing 12 months. The benefit can be used once. Mira Ayad, Microsoft's General Manager for Marketplace, described it at the Partner Insights event in August 2026.

Path two is not yet defined. 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. How it works inside Frontier Accelerate for Marketplace, which opened on September 28, 2026, is not yet published.

At the same August event, a Microsoft speaker cited a 200% increase in Marketplace investment and a 3.5X figure for channel-led sales growth. Only third-party outlets reported them, and IMS hasn't found either on a Microsoft-owned page, so treat both as unconfirmed. The practical takeaway for a partner below $100K: startups should check the Acceleration criteria now and time activation to deals that are close to closing, because the 120-day window is fixed. Everyone else should track MACC customer traction and pipeline now; the pilot weighs current activity.

Two paths,
one documented

Azure IP Co-Sell Acceleration is published policy for startups. The nomination pilot's mechanics are not yet published.

Acceleration: Microsoft for Startups members only. 120 days to reach $100K MBS or paid Azure consumption. Usable once. Source: Microsoft Learn, updated May 7, 2026.

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.

What derails the 90 days

The friction points Microsoft does not put in a deck

Company validation during onboarding is the most underestimated delay in the sequence. Julia Chow, a Microsoft Senior PDM for AI Incubate and Launch, said directly at the Partner Insights event that company validation can take weeks. That is a Microsoft-side review dependency, the same category as Marketplace offer review, and it belongs on the calendar from day one rather than being treated as a formality.

Vendor claims of faster timelines deserve skepticism proportional to their source. A Marketplace automation vendor pitching a "two-to-three month accelerator" at a sponsored industry event is describing its own product, not a Microsoft benchmark. Treat vendor-sponsored acceleration claims as color, not as a planning input.

Beyond onboarding, the Marketplace review clock is the recurring casualty. Partners routinely start it late because the mechanical checklist feels secondary to the revenue track, which is backward: the revenue track cannot be rushed, so the mechanical track is the one place urgency actually helps. Referral data fields left incomplete cause a quieter version of the same problem. The "Marketplace Intent" field is required for API-based submissions from January 5, 2026, and a CRM integration built before then may not populate it. Confirm referrals actually arrive in Partner Center. Technical validation scheduled too close to the 90-day mark, instead of running in parallel with offer review from day one, is the third way partners lose weeks they did not need to lose.

The 90-day checklist

The milestone sequence, broken into three 30-day windows

Each milestone below is sequenced against the two dependencies Microsoft controls, not the partner: Marketplace offer review and company validation. Both should start on day one, not after the rest of the checklist feels ready.

Days 1–10

Submit the Marketplace offer for review, on day one. Decide which channel route (REO, MPO, or CSP private offer) you will set up once the offer is live. Turn on "Request a private offer" if not already active. Begin the technical validation request in parallel; do not wait for offer approval to start it. Initiate company validation now if it has not already started.

Days 1–30

Assemble Co-Sell Ready collateral. One-pager, pitch deck, and a draft reference architecture. Confirm the CRM integration correctly populates the "Marketplace Intent" and "Estimated Azure Consumed Revenue" referral fields. If company validation has not progressed by day 30, escalate through the PDM or Microsoft contact now, not at day 60.

Days 30–60

Marketplace offer review typically clears in this window (4 to 6 weeks from submission, per industry sources). Finalize the reference architecture diagram for filing. Confirm technical validation status; this is the second most common stall point in the sequence, after Marketplace review itself.

Days 60–90

File the completed reference architecture. Confirm trailing 12-month ACR/MBS tracking against the $100K threshold, counting only Marketplace-transacted or Microsoft-attributed consumption and excluding Azure credits and ACOs. Document MACC customer traction and pipeline now, in case Microsoft publishes how the nomination pilot works inside Frontier Accelerate for Marketplace.

Day 90+

Azure IP Co-Sell Eligible status is achieved once all four requirements are met and the revenue threshold is crossed. If revenue has not yet crossed $100K, the mechanical checklist is complete, and the partner is positioned to cross the threshold as soon as trailing consumption catches up, not starting from zero on a second 90-day clock.

Find out whether your 90-day sequence is realistic, or whether you are still missing a step Microsoft won't flag for you.

The IMS CRI takes 10 minutes and places your current status against this exact milestone sequence, before any scope is set.

Measure your readiness

90 days is a real, provable claim for the mechanical checklist, and for partners with revenue already moving through the trailing window. It is not a guarantee for partners starting both tracks from zero. The difference between those two outcomes comes down to whether someone started the Marketplace review clock, the technical validation request, and the company validation process on day one, or waited until the sequence felt more urgent.