We listed our B2B SaaS product on Azure Marketplace expecting a new sales channel. What we got first was four months of certification delays, a metering API we rebuilt twice, and a co-sell requirement that took a full year to clear before Microsoft's own sales reps could route us a single deal. Azure Marketplace works, but not the way most guides describe it. It is not a discovery channel where new customers stumble onto your listing. It is a procurement channel that only pays off once an enterprise buyer already has budget committed to Microsoft and needs somewhere to spend it besides a competitor. Here is what actually happened, in order, including the mistakes that cost us weeks and the one mechanism that eventually got a stalled deal moving again.
Why we listed on Azure Marketplace in the first place
Azure Marketplace matters because it lets an enterprise buyer pay for your SaaS product out of a cloud budget they already committed to Microsoft, instead of opening a brand-new vendor line item that finance has to approve from scratch. That single fact changes the sales conversation more than any feature comparison does.
Most mid-market and enterprise Microsoft customers sign an Azure Consumption Commitment, known as a MACC, promising to spend a fixed dollar amount on Azure over one to three years. If your offer is transactable through the marketplace, eligible purchases draw down against that commitment. The customer is not spending new money. They are reallocating money they already agreed to spend, and procurement already trusts the billing relationship because it runs through Microsoft, not through you.
The certification process took four months, not four weeks
Certification through Microsoft's Partner Center takes two to four weeks if your first submission is clean. Ours took closer to four months, and the delay was entirely self-inflicted.
We underestimated two pieces of engineering work: the Fulfillment API, which provisions a customer's account the moment they purchase, and the Metering API, which reports usage back to Microsoft for anything billed beyond a flat subscription fee. Usage events have to be reported within an hour of occurrence, and Microsoft's validation environment flags anything that looks inconsistent before you can go live.
Three mistakes cost us the most time:
- An offer description Microsoft's reviewers flagged as unclear on pricing, which reset our position in the review queue.
- A webhook handler that did not acknowledge Microsoft's activation call correctly, so test purchases silently failed provisioning.
- Building metered billing before validating a single private offer, which meant debugging two new systems at once instead of one.
None of these mistakes were exotic. They are the same three Microsoft's own documentation warns about, which we read carefully only after we had already made them.
The co-sell problem nobody warns you about
The most valuable part of Azure Marketplace, getting deals routed to you by Microsoft's own sales reps, requires $100,000 of Azure Consumed Revenue or Marketplace Billed Sales in the trailing twelve months before you even qualify. You need marketplace revenue to unlock the thing that is supposed to generate marketplace revenue.
To reach Azure IP co-sell eligible status, an ISV has to clear four requirements after first becoming co-sell ready:
- At least $100,000 in Azure Consumed Revenue or Marketplace Billed Sales over the trailing 12 months, excluding Azure credits
- A transactable offer, since free and bring-your-own-license listings stopped qualifying for this status as of July 2023
- Technical validation confirming the solution is primarily platformed on Azure
- A reference architecture diagram submitted with the co-sell documentation in Partner Center
Clear all four and Microsoft typically enrolls the offer for MACC eligibility within about a week. Getting there took us most of a year of our own outbound and existing customers migrating their purchase to the marketplace, not a single deal Microsoft sent us first. Anyone telling a seed-stage founder that a marketplace listing alone produces inbound, Microsoft-sourced pipeline is skipping this part.
What actually changed once we went live
The bigger change came from one specific deal. A prospect's budget had been approved for months, but the contract sat in procurement because we were not yet an approved vendor in their system, a process that can take a full quarter on its own. Once we had a private offer live on the marketplace, their team applied the purchase against their existing MACC instead of opening a new vendor record. That mechanism, not the marketplace's search or discovery features, moved a stalled six-figure deal to signed in about three weeks.
The 30-day move if you are starting today
Do not build the Metering API first. Start with a single private offer for one prospect who already has an approved Microsoft budget, and confirm they will actually redirect spend through it before investing engineering weeks into usage-based billing infrastructure. If no prospect in your current pipeline has a MACC to draw down, the marketplace will not create demand that was not already there. It only removes friction from demand that already exists, the same lesson that applied when we looked at whether AWS Marketplace was worth it.
Frequently asked questions
How much does Azure Marketplace charge in fees for a SaaS offer?
Microsoft charges a 3% store service fee on transactable offers, down from 20% before a 2023 change. There are no separate listing fees, and Microsoft bills the customer directly before paying out the remainder to the publisher.
How long does Azure Marketplace certification actually take?
Two to four weeks if the first submission is clean. Realistically, plan for two to six months if this is your first integration with the Fulfillment API and Metering API, since most delays come from webhook errors, missing metadata, or unclear pricing descriptions.
What is Azure IP co-sell eligible status?
It is the status that lets Microsoft's own sales teams route deals to your product. It requires $100,000 in trailing 12-month Azure revenue, a transactable offer, technical validation, and a submitted reference architecture diagram.
Does an Azure Marketplace purchase count toward a customer's MACC?
Yes, for eligible private offers and transactable listings. The purchase amount draws down against the customer's existing Azure Consumption Commitment instead of requiring new budget approval.
Is Azure Marketplace a good lead-generation channel for an early-stage B2B SaaS company?
No. It is a procurement and consumption channel, not a discovery channel. It removes friction for deals that already exist inside an account with Microsoft budget, and it rarely creates net-new pipeline on its own.
Azure Marketplace did exactly one thing well for us: it turned an already-approved budget into a signed contract three weeks faster than our normal procurement cycle. It did not generate a single net-new lead. If your pipeline already includes Microsoft-heavy enterprise accounts, the four months of setup is worth it. If it does not, the engineering time is better spent somewhere your buyers already are.