- Transactable is not optional. A free or contact-me listing gets you no MACC drawdown eligibility and no co-sell pipeline. The revenue gap between transactable and non-transactable ISVs is structural, not marginal.
- Azure Marketplace and AppSource serve different buyers. Choose the wrong one for your product category and your listing traffic will be thin regardless of how good your copy is.
- Azure Co-Sell has three tiers. Only Azure IP Co-Sell unlocks the incentives that make Microsoft sellers actively bring you deals — and it requires meeting specific criteria before your listing can qualify.
- The $460B in global MACC committed spend (Tackle, 2025) is the biggest untapped revenue lever for most Azure ISVs. A transactable listing is the only way to access it.
92% of Azure customers use at least one ISV solution from Azure Marketplace (Azure Market Share Report). That tells you the distribution channel is real. What it does not tell you is why most ISVs who list on Azure Marketplace generate far less revenue than the opportunity suggests — and why a small percentage generates most of it. The difference almost always comes down to three decisions: whether you got transactable, whether you pursued Co-Sell status, and whether your listing is structured to capture MACC committed spend. This guide walks every step of the Azure Marketplace seller journey — from choosing the right storefront to managing your listing post-launch.
Azure Marketplace vs AppSource: Which Should You List On?
Microsoft operates two storefronts under the commercial marketplace umbrella, and choosing the wrong one is a quiet mistake that costs ISVs months of listing traffic. They are not interchangeable.
Azure Marketplace is for technical solutions that deploy on or integrate with Azure infrastructure. Think virtual machines, containers, managed applications, and SaaS products built on Azure. Buyers here are technical buyers and procurement teams looking for solutions they can provision directly to their Azure subscription. Transactable offers on Azure Marketplace draw from Azure MACC committed spend — the single biggest purchasing incentive in the Microsoft ecosystem.
AppSource is for business applications that extend Microsoft products — Dynamics 365, Power Platform, Microsoft 365, and Teams. The buyer persona is a business user or line-of-business buyer, not a cloud infrastructure team. Most AppSource listings are contact-me or free-trial; transactable offers exist but are less common.
- Technical solutions deploying on Azure (VMs, containers, SaaS)
- Buyers: cloud architects, technical procurement, IT
- MACC drawdown eligible (transactable offers)
- Azure billing integration for transact
- Best for infrastructure, data, developer tools, security, AI
- Business apps extending Dynamics 365, M365, Power Platform
- Buyers: business users, ops teams, department heads
- Mostly contact-me / free-trial (no MACC drawdown)
- Microsoft Teams and M365 distribution
- Best for CRM plugins, finance apps, HR tools, workflow automation
The practical rule: if your product runs on Azure compute or storage, list on Azure Marketplace. If your product is a business application built on top of Microsoft productivity tools, list on AppSource. Many ISVs ultimately list on both — their SaaS core on Azure Marketplace for transact, a Teams app or M365 integration on AppSource for breadth. The two are not mutually exclusive, but each has a separate listing and a separate review process.
If accessing Azure committed spend (MACC) is a priority for your go-to-market motion, you must be on Azure Marketplace with a transactable offer. AppSource listings do not qualify for MACC drawdown. This single fact drives most ISVs with enterprise ambitions toward Azure Marketplace as their primary commercial marketplace listing.
Azure Marketplace Listing Requirements for ISVs
Before you build the listing, four things have to be in place. Missing any one of them blocks either the listing itself or the transactable capability — the part that actually generates revenue.
You need a Partner Center account with the Commercial Marketplace program enrolled. This is separate from a Microsoft account or an Azure subscription. The account requires a legitimate business entity, a valid tax profile, and a payout account for transactable revenue. Expect 1–3 business days for verification to complete.
The Microsoft Publisher Agreement governs your relationship with Microsoft as a commercial marketplace publisher. It covers revenue share (3% for most transactable offers, 1.5% for qualified renewals), payment terms (roughly 45 days after month end), and your obligations around customer data and support. Accept it before creating your first offer.
A transactable SaaS offer requires Azure AD integration for identity. Microsoft uses this to authenticate the buyer at subscription setup and to surface your SaaS offer in the buyer’s Azure portal. A SaaS listing without Azure AD integration can only be listed as contact-me or free-trial — it cannot transact. This is the most common technical gap that prevents ISVs from going transactable.
Every transactable SaaS offer needs a landing page URL that Microsoft redirects buyers to after purchase, and a webhook endpoint that receives subscription lifecycle events (activate, suspend, unsubscribe, reinstate). These are not optional for transact — without them your subscriptions cannot be provisioned or managed.
Tax profile and payout account verification are the slowest part of Partner Center setup. Microsoft verifies your business entity, and some countries require additional documentation. Submit the tax profile on day one — not after you have finished building the listing. A listing ready to go live with a payout profile still “in review” is a common and entirely avoidable delay.
How to Create Your Azure Marketplace Listing (Step-by-Step)
Once Partner Center is set up, creating the listing is a seven-step process. The steps are sequential — Partner Center will not let you publish until each section is marked complete. The most common mistake is treating the listing as a copywriting exercise and skipping ahead to the description before the technical configuration is thought through. The pricing model and technical setup in steps 4 and 5 are the decisions that last.
Create a new offer in Partner Center
Go to Partner Center → Commercial Marketplace → Overview → New offer. Choose your offer type: SaaS (most common for cloud-native ISVs), Virtual Machine, Azure Container, Managed Application, or Consulting Service. The offer type is permanent after creation — you cannot change it later without creating a new offer.
Configure offer setup
Set the offer alias (internal name, not customer-facing), choose whether you want to sell through Microsoft (transact) or list only (contact-me, free trial). Choose “Sell through Microsoft” to get MACC eligibility. Select your customer leads destination — connect your CRM (HubSpot, Salesforce, Marketo) to capture every trial signup and purchase inquiry.
Set offer properties
Select categories (up to 2 primary + 2 secondary), industries, and Azure Active Directory and Microsoft 365 integration capabilities. Categories determine where your listing appears in marketplace search and browsing. Choose them based on how buyers describe their problem, not how you describe your product.
Create plans and set pricing
Each plan is a distinct pricing and availability configuration. For a SaaS transact offer: choose flat rate (per-term billing), per-user (seat-based), or metered billing (custom meters billed via the Marketplace Metering Service API). You can create up to 100 plans per offer — use private plans for custom enterprise pricing without separate private offers. See the section on Azure MACC drawdown mechanics for how plan pricing affects MACC eligibility.
Technical configuration
Enter your landing page URL and webhook URL. The landing page receives the purchase token after a buyer completes checkout — your application must call the SaaS Fulfillment API to resolve the token and activate the subscription. The webhook receives subscription events throughout the lifecycle. Test both endpoints before submission. A webhook that fails silently will leave subscriptions in a broken state that neither you nor the customer can diagnose easily.
Marketplace listing (the copy)
Name, description, search keywords, screenshots (up to 5, 1280×720 minimum), and videos. The description is searchable within Azure Marketplace. Use concrete use-case language your buyers type, not marketing language your product team writes. Include a PDF offer document for enterprise buyers who need vendor summaries for procurement.
Preview, validate, and publish
Add your preview audience (Azure subscription IDs that can see the listing before it goes public). Click Publish — Partner Center runs automated validation first, then Microsoft review (typically 2–5 business days). Fix any validation errors before the reviewer sees the listing; a listing with open errors will be rejected and restart the review clock.
The pricing model you choose in step 4 constrains every downstream commercial motion. An ISV that ships a flat-rate plan to get live quickly and later wants metered billing must create a new plan — existing subscribers stay on the old structure.
Transactable vs Free Listings: Choosing the Right Model
The word “free listing” is slightly misleading. A free listing costs nothing in marketplace fees — but it also generates no marketplace revenue, no MACC drawdown eligibility, and no co-sell pipeline. The commercial calculus is straightforward: the listing fee saved by staying on contact-me is smaller than the co-sell revenue not generated.
The fee difference is modest. Azure Marketplace charges 3% on transactable revenue for most offers, dropping to 1.5% for qualified renewals (Microsoft, Publisher Agreement 2026). Compare that to the 15–25% rev share of traditional resellers (Suger), and marketplace fees look inexpensive. The more important number is $460B in global MACC committed spend (Tackle, 2025) — none of which is accessible to a contact-me listing.
MACC (Microsoft Azure Consumption Commitment) is the mechanism that makes Azure Marketplace uniquely powerful for enterprise ISVs. Buyers with MACC commitments — typically large enterprises with multi-year Azure contracts — can draw down their committed spend on transactable marketplace purchases. This means your software spend comes out of budget the customer has already allocated, not from a net-new procurement line. The mechanics of Azure MACC drawdown are covered in detail in a dedicated guide, but the practical implication is simple: if your product is not transactable, enterprise buyers with MACC cannot spend their committed budget on you.
Contact-me and free-trial listings have a legitimate role in early-stage market testing. If your pricing is not finalized, or if you are validating Azure Marketplace as a channel before investing in the technical integration, a non-transactable listing lets you capture leads and test messaging without building the full fulfillment stack. The goal should be to move to transactable once the channel is validated — not to remain on contact-me indefinitely.
Azure Co-Sell: How to Unlock Microsoft’s Sales Channel
Azure Co-Sell is the program through which Microsoft sellers bring your product into their deals and you get joint pipeline. It is not a single status — it is a three-tier progression, and the top tier is where the real commercial leverage lives. Understanding the distinction between the tiers is one of the most misunderstood parts of the Azure Marketplace seller journey. The full breakdown of Co-Sell Eligible vs IP Co-Sell is worth reading before you submit your co-sell solution.
Co-Sell Ready
Entry level. Requires a published transactable or contact-me offer, a one-pager, and a pitch deck. Gets your solution visible to Microsoft sellers but provides no financial incentive for them to bring you into deals.
Co-Sell Eligible
Requires Co-Sell Ready plus a two-year revenue target, a mapped reference customer, and a technical solution map. Microsoft sellers can co-sell but there is still no Microsoft incentive payment tied to your deals.
Azure IP Co-Sell
The top tier. Requires a transactable offer generating $100K+ in Azure consumed revenue TTM. Microsoft sellers receive an incentive payment for co-selling Azure IP Co-Sell solutions — which means they are financially motivated to bring you into enterprise deals. MACC drawdown is automatically available.
MACC + Co-Sell Together
When an offer is both transactable (MACC-eligible) and Azure IP Co-Sell, you have a compound buying incentive: the customer’s committed spend covers the purchase, and the Microsoft seller gets paid to bring the deal. This is the configuration that drives disproportionate enterprise pipeline.
The path to Azure IP Co-Sell runs through transactable revenue first. You cannot hit the $100K Azure consumed revenue threshold on a contact-me listing. The sequencing is: get transactable, build early revenue, pursue IP Co-Sell status, then see Microsoft sellers arrive. Teams that try to shortcut to co-sell without building the revenue base first spend time on partner alignment that produces no pipeline because the incentive structure for Microsoft sellers is not activated.
Common Azure Marketplace Listing Mistakes
The mistakes that cost Azure ISVs revenue are concentrated in a few categories. They are rarely catastrophic individually — each one quietly reduces conversion or removes revenue that should have been generated, and most are invisible until you look for them.
Not getting transactable
The single highest-cost mistake. Staying on contact-me to avoid the Azure AD integration work leaves MACC eligibility, co-sell incentives, and Microsoft-facilitated billing all on the table. The integration work is a one-time cost; the revenue gap compounds every quarter.
Missing or fragile Azure AD integration
A transactable SaaS offer that fails at the Azure AD authentication step loses the buyer at the moment of highest intent — right after they have completed purchase. Azure AD integration issues also surface as silent failures in trial activations, where the buyer receives no onboarding and churns before anyone notices.
Webhook errors that break subscription lifecycle
Microsoft sends subscription lifecycle events (suspend, reinstate, unsubscribe) to your webhook endpoint. If the webhook fails silently — returning a 200 status without actually processing the event — subscriptions get out of sync. A buyer who cancels still has access. A buyer whose payment fails is not suspended. These are the kinds of errors that only surface in billing reconciliation months later.
Wrong category selection
Category determines where your listing appears in marketplace search and browse. ISVs who choose categories based on what their product does internally rather than what buyers search for get traffic from the wrong audience. Review the category tree with a focus on how procurement teams describe the problem your product solves.
Not connecting a CRM to capture leads
Contact-me and free-trial listings generate leads that Partner Center can forward to your CRM. ISVs who skip this step receive no notification of trial signups and contact requests. The leads exist in Partner Center and age without follow-up — a pipeline problem that looks like a conversion problem.
Skipping private plans for enterprise deals
Enterprise buyers expect custom pricing. ISVs who only publish public plans and then handle enterprise pricing outside the marketplace lose MACC eligibility on those deals. Private plans in Partner Center let you offer a custom price and term to a specific Azure tenant without building a full private offer.
Managing Your Azure Marketplace Listing Post-Launch
A published Azure Marketplace listing is not a set-and-forget asset. The ISVs who build real marketplace revenue treat the listing as an active commercial channel with its own analytics, co-sell pipeline, and update cadence.
Partner Center analytics
Partner Center provides two dashboards that matter for post-launch management. Marketplace Insights shows listing traffic, conversion from page view to trial/purchase, and the referral sources driving visitors to your offer. Revenue Summary shows transactable revenue, payout status, and the breakdown across plans and geographies. These two reports tell you whether your listing is a traffic problem (low impressions, needs category/keyword work) or a conversion problem (impressions present, purchases low, needs landing page or offer structure work).
Private offer management
Private offers — custom-priced, custom-term offers sent directly to a specific buyer’s Azure tenant — are where most enterprise revenue closes on Azure Marketplace. Managing the pipeline of private offers (which are pending, which have been accepted, which have expired) is a distinct motion from managing the public listing. See the guide on Azure Multiparty Private Offers (MPO) for how the channel-partner dimension adds complexity here.
Co-sell pipeline management
Once Co-Sell Ready or higher, you register deals through Partner Center’s Co-Sell Opportunities section. Microsoft sellers can refer opportunities to you and vice versa. Referral response time matters — Microsoft monitors partner responsiveness and deprioritizes slow-responding ISVs in seller recommendations. Respond to inbound referrals within 24–48 hours during business days.
Offer updates and version management
Plan updates (price changes, new dimensions, availability changes) go through a review cycle before they take effect for new subscribers. Existing subscribers stay on their current plan structure until renewal or until they explicitly accept an upgrade. Price increases require advance notice to existing subscribers. Build the review lead time into your update planning — a plan update submitted the day before a sales event will not be live in time.
Fee structures vary by offer type, TCV range, and renewal status. For deals where the exact fee impacts your margin targets or custom pricing, use the marketplace fee calculator to model the net revenue before you sign. Azure’s 3% standard fee and 1.5% renewal fee are straightforward, but the total picture includes payment timing and payout processing that affects cash flow differently than direct sales.
Azure Marketplace is a revenue channel, not a listing exercise.
Automatum handles the operational layer of an Azure Marketplace launch — listing setup, Azure AD integration, private offer management, co-sell pipeline, and billing reconciliation — so the path from Partner Center account to active pipeline does not hinge on one person knowing every step. See how it works on the Azure Marketplace overview.
See Automatum in Action →Frequently Asked Questions
Common questions about selling on Azure Marketplace as an ISV.
What is the difference between Azure Marketplace and AppSource?
Azure Marketplace is for technical solutions that deploy on or integrate with Azure infrastructure — think SaaS, VMs, containers, and managed applications. AppSource is for business applications that extend Microsoft productivity products like Dynamics 365, Power Platform, and Microsoft 365. The key commercial difference is that transactable offers on Azure Marketplace qualify for MACC committed spend drawdown; AppSource listings generally do not. ISVs with cloud-native products should default to Azure Marketplace for their primary transactable listing.
How do I make my Azure Marketplace listing transactable?
In Partner Center, when creating or editing your offer, choose “Sell through Microsoft” on the Offer Setup page. This enables transact. For a SaaS offer, you must also provide a valid landing page URL that integrates with the SaaS Fulfillment API, a webhook endpoint that receives subscription lifecycle events, and Azure AD authentication on your landing page. Without the technical integration, Partner Center will not allow you to publish a transactable offer.
What are the fees for selling on Azure Marketplace?
The standard Azure Marketplace fee is 3% of the transactable price for most offer types. Qualified renewals (subscriptions renewing at the same or lower price) attract a reduced fee of 1.5%. These fees apply to net revenue after refunds. Microsoft handles billing and collection, then remits payment to your payout account approximately 45 days after the end of each calendar month. There are no fees for free, contact-me, or BYOL listings. For custom fee calculations across deal scenarios, the marketplace fee calculator can model your net revenue before you commit to a price.
What is Azure Co-Sell and how do I qualify?
Azure Co-Sell is a program where Microsoft field sellers bring your product into their customer deals. There are three tiers: Co-Sell Ready (requires a published offer, a one-pager, and a pitch deck), Co-Sell Eligible (adds a reference customer and revenue target), and Azure IP Co-Sell (the top tier, requires a transactable offer with $100K+ Azure consumed revenue TTM). Only Azure IP Co-Sell gives Microsoft sellers a financial incentive to actively recommend your product in enterprise deals. The path runs through transactable revenue first — you cannot reach the IP Co-Sell revenue threshold on a contact-me listing.
How long does the Azure Marketplace listing review take?
Microsoft’s review typically takes 2–5 business days for a new offer or a significant update. Automated validation runs first and catches configuration errors (missing fields, invalid URLs, webhook failures) before the human review begins. Listings with validation errors are returned without completing the review, which resets the clock. For time-sensitive launches, resolve all validation errors before submission and allow a full week of buffer between submission and any planned go-live date.
Go deeper on Azure Marketplace
Guides on MACC, co-sell, private offers, and the full commercial marketplace.
