Azure IP Co-Sell Eligible status tells Microsoft sellers your solution is ready to co-sell. To qualify, you need a GA, transactable Azure Marketplace listing, the required technical and sales readiness assets, and $100K in Marketplace Billed Sales (MBS) or Azure Consumed Revenue (ACR) over a rolling 12-month period.
Labra helps you publish, transact quickly, prepare validation evidence, and work with Microsoft to complete the process.
Why this matters
Earning Azure IP Co-Sell Eligible status signals to Microsoft field sellers that your solution is ready to co-sell. It helps unlock internal seller incentives, increases field visibility, and—when your SaaS listing is MACC-enabled—allows customers to draw down Azure commitments on purchases transacted via the commercial marketplace.
What IP Co-Sell Eligible criteria includes
To qualify, Microsoft requires:
A transactable, GA commercial marketplace listing (SaaS or relevant offer type)
Validated technical architecture and security posture, including:
Reference architecture
Support and compliance details
Sales readiness signals, such as:
Co-sell contacts
Value proposition and customer outcomes
At the organization level, at least $100,000 USD in Azure Consumed Revenue (ACR) or Marketplace Billed Sales (MBS) over a trailing 12-month period
Microsoft measures eligibility using completed marketplace transactions reported in Partner Center.
Plain English: Microsoft is the seller of record. You do not invoice customers for marketplace deals—Microsoft bills the customer and disburses funds to you. Eligibility is validated using Microsoft’s own marketplace revenue data.
How Microsoft measures eligibility (at a glance)
Source of truth
Partner Center → Commercial Marketplace (Marketplace Insights / Revenue reports)
What counts
$100K in completed marketplace transactions
Reported as Marketplace Billed Sales (gross revenue) or ACR
Evidence you’ll provide
Revenue export showing Revenue column totals
Private Offer IDs tied to accepted transactions
Listing and solution artifacts (reference architecture, better-together content, co-sell contacts)
Your role vs. Labra vs. Microsoft
You (the ISV / SDC)
Finalize listing artifacts (reference architecture diagram, security and support details, value story)
Identify a set of deals (they can be small) to reach the MBS threshold
Nominate co-sell contacts and align your sales motion
Labra (your enabler & guide)
Support the Azure Marketplace listing process and readiness assets
Advise on private-offer structure and the fastest path to MBS
Help prepare validation evidence (revenue exports, offer IDs)
Support escalation with Microsoft when backend data and UI states don’t match
Microsoft
Bills customers and disburses funds (seller of record)
Validates eligibility and tags your solution as IP Co-Sell Eligible (and MACC-enabled, when applicable)
Surfaces your offer to field sellers and aligns co-sell programs
Typical path to eligibility
Readiness & listing (assets completed, GA marketplace listing live)
Transact initial private offers to reach the MBS threshold (a mix of smaller deals is fine)
Submit validation with revenue evidence and offer IDs
Microsoft review & tagging (IP Co-Sell Eligible; MACC if enabled)
Tip: Annual-upfront billings can accelerate reaching the $100K bar. Make sure transaction booking dates fall within Microsoft’s measurement window.
How Labra gets you there
Velocity plan: Shortlist 3–5 transactable opportunities to reach MBS quickly
Offer design: Private-offer structures aligned to your pricing and buying routes
Evidence package: Revenue exports (Revenue column), offer IDs, architecture, contacts
Escalation runway: Direct coordination with Microsoft to resolve validation gaps