How to Sell Software on Azure Marketplace: 2026 ISV Playbook

Selling on Azure Marketplace is one of those things every B2B SaaS founder hears about, files under "we should probably do this eventually," and then never gets around to. Six months later, three deals stalled because the buyer asked "can you transact through our Azure commit?" and the answer was no.

This guide walks through the actual work, in the order you have to do it, with realistic timelines and the trade-offs most playbooks skip. I have watched dozens of ISVs go through this. The pattern of where they get stuck is consistent.

By the end of this you will know:

• Whether Azure Marketplace is worth your team's time at your stage
• What the technical work to be "transactable" actually involves
• How to set up private offers and co-sell properly
• The mistakes that cost ISVs 3-6 months and how to avoid them

Is Azure Marketplace worth it for you?

Before the steps, the gut check. Azure Marketplace makes sense if any of these are true:

You sell to enterprises with Microsoft commits. Enterprises with MACC or Enterprise Agreement commitments actively look for vendors they can transact through Marketplace because the spend draws down committed budget. If a buyer told you "we'd love to but our Azure commit is the priority," Marketplace solves that.

You compete with vendors who are already listed. If Datadog, Snowflake, Databricks, MongoDB, or your direct competitors are on Marketplace, you are at a procurement disadvantage by not being there.

You sell developer or IT tools. Buyers in those personas use Azure Marketplace as a discovery channel for new tools. You miss that traffic if you are not listed.

You want access to Microsoft's co-sell motion. Co-sell-ready ISVs get distribution from Microsoft field sellers in ways direct outbound never matches.

If none of these are true (you sell to SMBs, you have no enterprise motion, your buyers are not in Microsoft-loyal accounts), Marketplace may not be a priority yet. It is real work to set up, and the ROI is in enterprise revenue.

Try WeTransact → — if you decide Marketplace is in your roadmap, this is where most growth-stage SaaS companies end up to skip the 3-6 month engineering project.

Step 1: Join the Microsoft AI Cloud Partner Program

Microsoft renamed and restructured its partner program in 2023, and the entry has gotten faster.

The free partner program entry tier is your starting point. Sign up at partner.microsoft.com. You will need:

• A business email (not Gmail)
• Company legal name and tax ID
• A primary contact who will own the relationship

After signup, you get access to Partner Center, which is the operational hub for everything else: Marketplace publishing, co-sell submission, incentive tracking, certifications.

Higher tiers (Solutions Partner, Specialization) unlock more benefits but require demonstrated capability and customer references. Do not block on these. Publish your first offer at the free tier, then upgrade as you grow.

Step 2: Set up a Commercial Marketplace account in Partner Center

Inside Partner Center, create a Commercial Marketplace account. This is the publishing surface for both Azure Marketplace and Microsoft AppSource (they share the same backend).

Required during setup:

• Banking details for receiving payouts (Microsoft pays you monthly for transacted revenue)
• Tax forms (W-8 / W-9 for US entities, equivalent forms for non-US)
• Verified legal entity matched to your incorporation documents

This takes 1-2 weeks. Most delays come from tax form verification, especially for non-US companies. Start early.

Step 3: Pick your offer type

Your offer type determines everything that follows. Five options on Azure Marketplace:

Virtual Machine offer. Your software ships as a pre-configured VM image (VHD). Customer deploys into their Azure subscription. Used for security tools, network appliances, database engines.

Container offer. Your software ships as container images. Customer deploys into Azure Kubernetes Service or Container Apps. Used for cloud-native middleware, observability tools.

SaaS offer. Your SaaS app stays on your infrastructure. Microsoft handles the billing and subscription state. Customer accesses your app through the standard browser flow with SSO. This is the most flexible and increasingly the most popular option.

Managed app. Your software runs as a managed solution inside the customer's Azure subscription. You operate the solution; the customer pays for the underlying Azure resources plus your fee. Used for managed databases, security platforms.

Consulting offer. Pre-packaged services (audits, implementations, training). Lower technical lift, used by services-led ISVs.

For most B2B SaaS, the answer is SaaS offer. It works regardless of where you run (AWS, GCP, on-prem), supports flexible pricing, and is the path Microsoft is investing in.

Step 4: Decide on your pricing model

Six pricing models supported on SaaS offers:

• Free. Lists with no charge. Use for freemium products driving signups.
• Flat-rate monthly or annual. Fixed price billed by Microsoft.
• Per-user. Seat-based billing.
• Per-unit (consumption / usage). Metered billing via Microsoft's metered service. Requires telemetry integration.
• Custom-meter. Base price plus usage-driven overages.
• Bring Your Own License (BYOL). Customer brings an existing license; Microsoft charges Azure infrastructure only.

For enterprise sales velocity, flat-rate annual wins. Procurement teams approve flat-rate annual plans faster because the budget impact is predictable.

For products with strong usage-based unit economics (data, AI, API products), per-unit unlocks the right monetization story but adds 2-3 weeks of metering integration work.

You do not have to pick once. A single SaaS offer can have multiple plans with different pricing models, presented as tiers.

Step 5: Build the technical foundation for transactable SaaS

This is where ISVs underestimate the work and where most of the 3-6 month timelines come from.

A "transactable" SaaS offer means Microsoft handles the billing and subscription state. Your SaaS has to respond to Microsoft's commerce events. The technical work:

Landing page integration

After a customer purchases your SaaS through Marketplace, Microsoft redirects them to your landing page. This page receives a token in the URL. Your landing page must:

1. Validate the token against Microsoft's Subscription API
2. Identify the subscription details (plan, quantity, customer info)
3. Provision the customer in your application
4. Activate the subscription in Microsoft's system

If any step fails, the customer cannot use the product they just paid for. The landing page is brittle to get right.

Subscription webhook

Microsoft posts webhook events to your endpoint when subscription state changes:

• New subscription
• Plan change
• Quantity change
• Cancellation
• Reinstatement

Your backend has to handle each event, update your customer's state, and acknowledge the webhook within a tight timeout window. Missed or mishandled webhooks cause subscription drift between Microsoft and your system.

Metered usage submission (if using per-unit pricing)

For per-unit plans, your system has to submit usage records to Microsoft's metered billing API. The API has rate limits and idempotency requirements. Your usage submission has to be reliable and auditable.

Single sign-on (recommended)

Customers expect to click "open" inside Microsoft's UI and land inside your app already authenticated. The standard pattern is Microsoft Entra ID (formerly Azure AD) SSO. If your app does not support Entra ID, the customer experience after purchase is rough.

End-to-end testing

Marketplace requires a working preview offer that Microsoft uses to validate the technical integration. This is where many submissions get rejected the first time.

Realistic engineering effort: 8-16 weeks for a team of two engineers with Microsoft Marketplace context. Longer if your team is new to it.

This is the work most ISVs outsource. Services like WeTransact operate the entire transactable infrastructure as a managed layer, so your engineering team does not absorb a quarter of work on Microsoft commerce APIs.

Step 6: Build the marketing assets

Microsoft's listing requirements are stricter than people expect:

• Hero image. Specific dimensions, no text overlays.
• Logo. Multiple sizes (small, medium, large), specific format.
• Screenshots. 5 minimum, showing the product in actual use.
• Description. 3,000 characters max, must avoid certain marketing language.
• Categories and search keywords. Choose carefully because they drive discoverability.
• Privacy policy and terms of use URLs. Public, hosted on your domain.
• Support URL or email. Active and monitored.
• Localization (optional but recommended). German, French, Japanese, Spanish boost relevance.

Microsoft's certification team checks every field. Common rejection reasons: marketing claims without proof, screenshots showing competitor logos, broken support URLs.

Step 7: Submit for certification and preview

You build the offer in Partner Center, fill in everything, and submit. Microsoft runs:

• Automated checks (image formats, URL validity, manifest validation)
• Manual content review (marketing copy, screenshots, claims)
• Technical validation (especially for VM, container, managed app)

If you pass, the offer goes into preview state. Only your account and named tester accounts can see it.

Preview testing is critical. Run an end-to-end test purchase using a test Azure subscription. Verify:

• Customer can complete checkout
• Token validates on your landing page
• Provisioning happens correctly
• Webhook receives subscription event
• Activation goes through
• Customer can access the product

If anything breaks here, fix it before going live. Customer-facing bugs after go-live are visible to Microsoft sellers and affect your offer's standing.

Step 8: Go live and announce

Once preview testing passes, submit for live publish. Microsoft re-reviews the offer (usually 1-3 business days) and publishes it to the public catalog.

Your live offer is now searchable on Marketplace. But "live" is not "selling." You still need:

• A go-to-market motion (announce internally, train sales, update collateral)
• A way to drive Marketplace-specific traffic (paid ads, landing pages, partner co-marketing)
• A private offer playbook (most enterprise deals close through private offers, not public listings)

Step 9: Set up private offers

Private offers are scoped quotes you create for specific buyers. They override the public listing price and terms.

When to use a private offer:

• Custom pricing different from public list
• Negotiated contract terms (longer commitment, custom SLA)
• Multi-year deal with built-in discounts
• Strategic enterprise account

How they work:

1. You create the private offer in Partner Center, scoped to the buyer's Azure account
2. The buyer receives a notification in their Azure portal
3. The buyer reviews, accepts, and the deal counts against their MACC commit
4. Microsoft handles billing and payout

Private offers are how most enterprise software actually sells on Marketplace. Public listings drive discovery; private offers close revenue.

If you want the deep mechanics, see Azure Marketplace Private Offers: Complete 2026 Guide.

Step 10: Apply for co-sell ready status

Co-sell unlocks Microsoft field sellers as a channel for your product. To get there:

1. Customer success references. Microsoft wants proof your product works in production.
2. Solutions Partner designation. Earn this in at least one partner solution area.
3. Co-sell readiness checklist. Includes deal registration support, sales collateral, named seller contacts.

Co-sell ready ISVs:

• Get listed in Microsoft's internal seller catalog
• Receive deal registration leads from Microsoft sellers
• Qualify for partner incentives
• Often see deal velocity increase 2-3x

Co-sell takes another 2-6 months of partner relationship building after you list. It is the highest-leverage Marketplace investment after the listing itself.

The mistakes most ISVs make

Treating it as a marketing checkbox. A static listing without active co-sell motion or partner engagement gets almost no traffic. Marketplace amplifies existing demand; it does not create it.

Underestimating the technical work. Plan for 8-16 weeks of engineering for transactable SaaS. Teams that try to do it on the side end up shipping in 6-9 months with bugs.

Skipping private offers. Public listings are for discovery. If your AE is not creating private offers in Partner Center, you are not closing Marketplace revenue.

Not setting up co-sell. The Microsoft sellers are the channel. ISVs who skip co-sell setup get the catalog and nothing else.

Going alone for too long. ISVs with internal Microsoft Marketplace expertise can build this. Most B2B SaaS teams do not have that and benefit from a managed service to skip the engineering project entirely.

Realistic timeline

For an ISV starting from zero, here is what to expect:

End-to-end from zero to first private offer signed: typically 6-9 months in-house, or 6-10 weeks with a managed service partner like WeTransact.

Frequently asked questions

Final word

Azure Marketplace is real revenue infrastructure for enterprise B2B SaaS in 2026, not a marketing checkbox. The work to set it up properly is significant. The ROI is in deals you would otherwise lose to buyers who say "we can only spend our Azure commit."

If you have a few hundred thousand in enterprise pipeline that could route through Marketplace, the math on investing here is straightforward.

Two paths from here:

1. Build it in-house. Plan for 3-6 months of engineering, 1 quarter of partner motion ramp, ongoing operations. You get full control and full cost.
2. Use a managed service. WeTransact and similar partners operate the transactable infrastructure, certification, private offer mechanics, and ongoing motion as a single contract. You get faster time-to-revenue and a smaller engineering burden.

Most growth-stage B2B SaaS companies end up on option 2 because the alternative is paying senior engineering time for half a year against Microsoft's commerce APIs. Pick based on your team's capacity and your urgency.

The opportunity is real. Most of your competitors are still figuring out whether to invest. The window to be there first is open.

Disclosure: This article contains affiliate links. We may earn a commission when you sign up through links on this page at no extra cost to you. Read our affiliate disclosure.