How to Sell on Microsoft Azure Marketplace: The Complete 2026 Playbook

If you're a B2B SaaS company that wants to sell on Microsoft Azure Marketplace, the right path depends on one decision: build the Partner Center integration yourself, or use a platform that abstracts it. This playbook walks through both paths, the realistic timelines, and the gotchas that bite first-time sellers.

TL;DR

• Listing on Azure Marketplace requires a Microsoft Partner Center account, a configured offer (SaaS, Azure Application, or Container), and a working integration with the Marketplace Fulfillment API.
• Transactable status unlocks MACC eligibility, private offers, and co-sell. This is the actual goal, not just being listed.
• DIY timeline: 3-6 months for first transactable offer if your engineering team has bandwidth.
• Platform timeline: Days to weeks using a purpose-built solution like WeTransact.
• Once live, the highest-leverage workflows are private offers (custom-price deals) and co-sell (Microsoft field sellers pushing your solution).

Step 1: Decide What You're Actually Trying to Do

There are three distinct levels of presence on Azure Marketplace, and they have very different effort profiles.

Free listing (consult / contact-me offer). No transaction happens through the marketplace. Customers see your listing and contact you. This is the easiest to set up (no Fulfillment API needed) but provides almost no marketplace value. Skip this unless you literally just want a listing for SEO.

Transactable SaaS offer with public pricing. Customers can buy your product directly through the marketplace at your published price. Requires Fulfillment API integration. Counts toward MACC consumption. This is the minimum viable transactable state.

Transactable SaaS offer with private offers + co-sell. Same as above, plus you can issue custom-price offers to specific customers (private offers) and Microsoft sellers can find and pitch your solution to their accounts (co-sell). This is what actually moves the needle on enterprise revenue.

Most vendors should aim directly for level 3. The incremental work over level 2 is small.

Step 2: Set Up Microsoft Partner Center

Partner Center is the back office where you manage everything. Before you can publish offers, you need:

1. A Partner Center account. Sign up at partner.microsoft.com with a work email that owns your domain.
2. Microsoft Partner Network (MPN) ID enrollment. Free to enroll. Required for transactable offers.
3. Tax and payout profile. Bank account, tax forms (W-8/W-9 equivalents), and a verified business address. This is where most companies hit a 2-3 week delay if they don't start it early.
4. Verification of company identity. Microsoft verifies your business via documentation. Plan a week of latency.

This is the unglamorous part. If you delegate it to a platform like WeTransact, they walk you through it in parallel with the technical setup so the bureaucratic latency doesn't bottleneck go-live.

Step 3: Configure Your Offer

Once Partner Center is enabled, you create an offer. The high-impact decisions:

Offer type: For B2B SaaS, choose "SaaS offer." For dev tools or infrastructure that runs on Azure, "Azure Application" or "Container offer" may be better.

Plans: A plan is a tier of your offer (Starter, Pro, Enterprise). Each plan has its own pricing model.

Pricing models (per plan):

• Flat rate (monthly or annual)
• Per user (per-seat billing)
• Per unit (transactions, devices, custom units)
• Metered (true usage-based billing)
• Custom (private offer template)

For most SaaS vendors, the right combo is: a public Pro plan at flat-rate monthly, a public Enterprise plan at higher flat-rate, and a private plan template for custom enterprise deals.

Trials: Microsoft supports free trials. Set this if your motion includes trial-to-paid conversion.

Geographic availability: Choose which countries can transact your offer. Default to "all" unless you have a real reason to exclude regions.

Categories and tags: Used by buyers to discover your offer. Pick the categories that match your actual product, not the most popular ones. Misalignment hurts conversion.

Step 4: Build the Fulfillment API Integration

This is where most DIY projects stall. The Fulfillment API is what tells your product "a new customer just bought you through the marketplace, provision them an account." Specifically you need to handle:

• Subscription lifecycle webhooks (created, updated, suspended, canceled, reinstated). Each needs an idempotent handler that updates your own user/subscription database.
• Token-based landing page authentication. When a buyer clicks "Configure account now" after purchase, they hit your app with a marketplace-issued token. Your app exchanges the token for subscription details via the Fulfillment API, then provisions the account.
• Resolve API and Activate API calls to confirm the subscription is active.
• Metering API if you're using usage-based pricing. Submit usage events at the dimension you defined in your plan.

Common gotchas:

• Webhook signing. Microsoft signs webhooks with a JWT. Validate it. Most first-time integrations skip this and Microsoft fails certification.
• Idempotency. Webhooks retry on failure. If you process a "subscription created" event twice, you must not provision the account twice. Use the event ID as a dedup key.
• Token expiration. The marketplace token expires fast (5 minutes). Resolve it immediately when the user lands.
• Sandbox testing. Microsoft has a sandbox environment for testing. Use it religiously before going to certification.

This entire step is what platforms like WeTransact handle for you. They run a hosted Fulfillment integration that signs you up with a webhook URL on their side, processes the events, and pushes provisioning calls to your product via a simpler API or via direct CRM sync. The build-vs-buy math here is about a month of senior engineering time vs platform pricing.

Step 5: Submit for Certification

Microsoft reviews every offer before it goes live. Certification checks:

• Technical integration works end to end (Fulfillment, Resolve, Activate, webhooks).
• Listing content is accurate and matches the actual product.
• Pricing and terms are clear.
• Legal documents (privacy policy, terms of service) are present and valid.
• The product is functional (they will test purchase it in their sandbox).

First-time certification takes 2-4 weeks if your integration is clean. If there are issues, expect a back-and-forth that adds weeks per round. Common rejection reasons:

• Webhook signature validation missing or broken.
• Landing page doesn't handle the marketplace token correctly.
• Offer description doesn't match what the product actually does.
• Required legal documents missing.

Tip: ask your Microsoft account team or partner manager to do a pre-review. They will surface issues before formal submission, saving you a cycle.

Step 6: Configure Private Offers

Once live, your single highest-leverage workflow is private offers. These let you issue a custom-priced version of your offer to a specific customer's tenant ID. The customer sees the private offer in their Azure portal and can purchase it directly.

Why private offers matter for enterprise:

• MACC consumption. A private offer with a large one-time fee can drain a customer's remaining MACC in a single transaction.
• Negotiated pricing. You can match the discount you negotiated in their MSA without publishing it.
• Speed. A private offer that's accepted closes the deal in days, not the months of new-vendor approval.

Set up private offer templates for each major customer profile (e.g., "Mid-market 50-200 seats," "Enterprise 200+ seats"). Train your AEs to issue them from the template rather than configuring from scratch.

In Partner Center, private offers are clunky. In WeTransact, salespeople issue them from inside Salesforce or HubSpot.

Step 7: Activate Co-Sell

Microsoft's co-sell program is where Microsoft field sellers find your solution and recommend it to their accounts. To be co-sell ready:

1. Mark your offer as "co-sell ready" in Partner Center.
2. Complete the co-sell metadata (solution overview, customer case studies, technical fit description).
3. Enroll in the Microsoft Solutions Partner program for the relevant designation (Modern Work, Business Applications, Data and AI, Infrastructure, Digital and App Innovation, Security).
4. Engage your Microsoft Partner Development Manager (PDM) to introduce your solution to relevant field sellers.

Co-sell isn't automatic. It works when there's real partnership investment. Microsoft sellers respond to vendors who help them close deals, not vendors who just listed.

Step 8: Drive Marketplace Traffic

A listing without sales motion behind it collects dust. Once live:

• Train your sales team to identify MACC-committed accounts and lead with the marketplace option.
• Update your website CTAs to include "Buy on Azure Marketplace" alongside "Contact Sales."
• Run paid search ads on relevant terms: "your product + Azure Marketplace" gets the bottom-funnel buyer.
• Co-marketing with Microsoft. Once you're in the Solutions Partner program, you can apply for co-marketing funds and joint campaigns.

This is where the marketplace becomes a primary channel rather than a passive listing.

What the Timeline Actually Looks Like

DIY path (engineering team handles everything):

• Weeks 1-2: Partner Center enrollment, tax/payout setup, MPN registration
• Weeks 3-6: Engineering builds Fulfillment API integration, tests in sandbox
• Weeks 7-9: Offer configuration, listing content, legal docs
• Weeks 10-14: Submit for certification, iterate on rejections
• Weeks 15-16: Go live, start configuring private offers
• Weeks 17-24: Co-sell setup, sales enablement, marketing motion

Total: ~6 months to fully operational, assuming engineering availability.

Platform path (using WeTransact or similar):

• Day 1-3: Partner Center work delegated, offer configuration in platform UI
• Day 4-7: Certification submitted with pre-validated integration
• Day 8-14: Certification passes, listing goes live, private offer templates configured
• Day 15-21: Co-sell metadata, Microsoft PDM introduction
• Day 22-30: Sales enablement, first private offers issued

Total: ~30 days to fully operational.

The gap is real. The cost of the platform vs the cost of three additional months of engineering time and lost enterprise pipeline is almost always favorable to the platform.

FAQ

Do I need to be a US company to sell on Azure Marketplace?
No. Vendors from most countries can publish. Some payout regions have additional verification steps but the platform is global.

What's Microsoft's cut?
3% transaction fee. Far below the 20% it used to be and below most affiliate programs.

Can I have multiple offers?
Yes. Vendors typically have one offer per product line. Some vendors have a public "self-serve" offer plus separate private offer templates for enterprise.

What if my customer is on AWS or GCP, not Azure?
Multi-cloud platforms like Suger and Tackle.io support all three. WeTransact focuses on Azure depth specifically.

Can I list a product that's currently in beta?
Yes, with the "preview" offer state. Useful for getting feedback from marketplace buyers before full GA pricing.

Is there a minimum revenue threshold to be on the marketplace?
No. Microsoft has no minimum revenue requirement for vendors. They want as much marketplace SKU breadth as possible.

The Bottom Line

Listing on Azure Marketplace is technical work, not strategic work. The strategic decision is whether to be on the marketplace at all (yes, if you sell B2B to Azure customers). The execution is well-understood and either takes 6 months DIY or 30 days with a platform.

For most SaaS vendors, WeTransact is the fastest path. Free 30-day trial. By the end of the trial period, you can be live on the marketplace.

Related reading:

• Microsoft Azure Marketplace Complete Guide for SaaS Vendors — the strategic case for being on the marketplace
• MACC Explained — the buyer-side incentive that makes marketplace deals close
• Best Marketplace Transactability Platforms 2026 — head-to-head review of the available platforms