Azure Marketplace Private Offers: Complete 2026 Guide

If you have ever closed a six-figure enterprise SaaS deal, you know the public list price is rarely what gets signed. Custom terms, multi-year discounts, negotiated SLAs — that is where actual enterprise revenue lives. Azure Marketplace handles this through private offers, and they are how most real money on the platform actually transacts.

This guide explains what private offers are, when to use them, the technical mechanics, the MACC drawdown story (the reason your CFO buyer cares), and the mistakes that delay deals.

If you are an ISV selling enterprise software and skipping Marketplace because "we customize every deal," this is the article that should change your mind.

What a private offer is, in one sentence

A private offer is a custom price quote you create for one or more specific Azure customers, with terms different from your public Marketplace listing, that the customer accepts through their Azure portal.

That is it. It is functionally the same as a regular sales quote with one important difference: when the customer accepts, Microsoft handles the billing and the deal counts against the customer's Microsoft commit.

The public offer / private offer split

Your Azure Marketplace listing has two transaction modes:

Public listing. Anyone with an Azure subscription can purchase at the published price, with the standard plans you defined. Self-serve, transparent, fast.

Private offer. You create a quote in Partner Center scoped to a specific customer (identified by their Microsoft account billing email or Azure subscription ID). The quote has custom pricing, custom terms, and is invisible to anyone else. The customer reviews and accepts inside Azure portal.

Public listings are for discovery and small deals. Private offers are for enterprise revenue.

Most ISVs in Marketplace see something like 80% of revenue close through private offers, with public listings driving inbound and net-new SMB deals.

When to use a private offer

Five clear cases:

Custom pricing different from public list. Your sales team negotiated a multi-year commitment or volume discount that does not fit your public plans.

Strategic enterprise account. Bespoke contract terms, custom SLA, security addendums, indemnification language. You and the buyer's legal team negotiated something that does not appear on the public catalog page.

Multi-product bundles. The customer is buying several of your SKUs in one transaction with a custom blended rate.

Channel partner / reseller deal. A Microsoft partner is brokering the deal and you are quoting them, not the end customer.

MACC drawdown timing. The customer has remaining commit they need to spend before fiscal year-end and you are creating a quote tailored to that timing.

If none of these apply and the customer is happy with public list pricing, skip the private offer machinery and let them self-serve.

How private offers count toward MACC

This is the critical commercial driver and the reason private offers matter for procurement.

A Microsoft Azure Consumption Commitment (MACC) is a multi-year spend commitment large enterprises make to Microsoft. Typical commitments range from $1M to $100M+ per year. Microsoft pre-allocates the budget; the customer commits to consuming it.

If the customer does not consume the commitment, they lose it. End of fiscal year, unused commit evaporates.

Microsoft created the rule that eligible third-party SaaS purchased through Marketplace counts against the customer's MACC commitment. That includes private offers. Suddenly, "$3M of unspent Azure commit" becomes "$3M of budget for any qualifying SaaS, paid through Marketplace."

For an enterprise buyer, that flips your sales conversation:

• Without Marketplace: "I'd love to buy your $200K/year tool but I need to find net-new budget"
• With Marketplace + private offer: "I have unspent Azure commit. Quote me a private offer and we can transact this fiscal quarter"

This is why enterprise customers actively push their vendors to publish on Marketplace. It unlocks budget that already exists.

For your sales team, the practical playbook:

1. Qualify whether the prospect has MACC or EA commitment
2. Confirm your offer is MACC-eligible (Microsoft maintains this flag)
3. Create the private offer tailored to the deal terms
4. Buyer accepts in Azure portal
5. Microsoft invoices the buyer, pays you, draws down their commit

The mechanics: how to create a private offer

The flow in Partner Center, step by step:

Step 1Verify you have a transactable offer

Private offers only work on offers that are already transactable through Marketplace. If your public listing is "Contact us" only (not transactable), you cannot create private offers. Build the transactable foundation first.

Step 2Identify the customer's Azure billing account

You need the customer's billing account ID or the email of their Azure billing administrator. Sales team typically gathers this during the deal close.

The customer has to grant you visibility into their billing account (a one-click approval). Without this, you cannot scope the offer correctly.

Step 3Build the private offer in Partner Center

Inside the Commercial Marketplace area:

• Select the existing public offer your private offer extends
• Define the plan (existing plan with override pricing, or new private-only plan)
• Set the price (flat-rate, per-user, or metered — same models as public offers)
• Set the term length (1-month, 1-year, 3-year, custom)
• Add the customer billing account(s) to scope visibility
• Optionally add payment schedule overrides (e.g., upfront annual payment, quarterly billing)

Microsoft supports several private offer types:

• Customer private offer. Direct from ISV to customer.
• Reseller private offer. Channel partner resells to end customer.
• Multi-party offer. ISV + System Integrator + end customer in one deal.
• Marketplace migration offer. Move an existing non-Marketplace contract onto Marketplace mid-cycle.

For most direct enterprise deals, the customer private offer is what you want.

Step 4Publish and notify

Submit the private offer. Microsoft validates it (usually within 1 business day). The customer's Azure billing admin gets a notification in their Azure portal.

You also typically email the buyer with the direct link. Buyers do not always check their Azure portal notifications.

Step 5Customer accepts

The buyer reviews the offer in Azure portal, accepts, and the subscription activates. Microsoft handles billing and the commit drawdown.

You receive an event through your subscription webhook, just like a public offer purchase. Your fulfillment system activates the customer.

Step 6Manage the subscription

Once active, the private offer subscription behaves like any other Marketplace subscription. Quantity changes, plan upgrades, and renewals flow through Partner Center.

Pricing models on private offers

Private offers support the full range of Marketplace pricing models:

• Flat-rate. Custom annual or monthly price.
• Per-user. Custom per-seat rate with commitment levels.
• Metered. Custom unit pricing with overage rules.
• Custom-meter. Base + usage-based overages with negotiated terms.

In practice, most enterprise private offers use flat-rate annual because that fits enterprise procurement budgets cleanly. Per-user and metered are common for usage-driven products where the unit economics matter more than predictability.

Multi-year private offers

A private offer can lock in multi-year terms with built-in escalators. The structure:

• Year 1 pricing
• Year 2 pricing (typically +3-7% escalator)
• Year 3 pricing
• Total commitment value

Multi-year private offers are powerful because they:

1. Lock in revenue for the ISV
2. Lock in pricing for the buyer
3. Count toward MACC commit across multiple fiscal years
4. Reduce renewal friction (auto-renews into the next year)

The downside is reduced flexibility. If your product roadmap changes significantly, you cannot easily restructure a signed multi-year private offer.

Channel and reseller private offers

For deals that flow through partners (systems integrators, resellers, Microsoft CSPs), the multi-party private offer structure handles the channel mechanics:

• ISV publishes the offer
• Reseller / channel partner takes margin
• End customer purchases and gets the product
• Microsoft handles all the splits

This unlocks Microsoft's channel as a real distribution path. ISVs who set up multi-party private offers correctly can scale through Microsoft partners in ways direct sales never reaches.

Common channel structures:

• Resellers (CSPs). They package and bill the customer.
• Systems integrators. They wrap the offer with services.
• Co-sell partners. Microsoft field sellers refer the deal and earn incentives.

Each structure has different commission economics. Plan the partner motion before you set up the private offer flow, not after.

What you actually save (or earn) versus a direct deal

The economics of private offers versus direct contracts:

For the ISV:

• Microsoft takes 3% transaction fee (versus 0% on direct)
• Faster deal cycle (procurement friction reduced)
• Multi-year escalators are easier to enforce
• Co-sell incentive eligibility (if applicable)

Net: 3% fee, often offset by faster close and higher renewal rates.

For the customer:

• One consolidated Microsoft invoice (versus per-vendor PO)
• Procurement approval often pre-approved through the Azure relationship
• MACC commit drawdown (if eligible)
• Simpler tax handling

Net: substantial procurement savings, especially in large vendor portfolios.

The 3% fee is often the cheapest enterprise procurement workflow change you can make.

Common mistakes that delay private offers

After watching dozens of deals go through (and stall), four mistakes consistently delay close:

Not having a transactable public offer first. Private offers require a transactable foundation. ISVs who try to skip straight to private offers without the public infrastructure end up rebuilding everything.

Wrong billing account ID. Customers have multiple Azure billing accounts (subsidiaries, regional). Scoping the private offer to the wrong one makes it invisible to the actual buyer.

Skipping MACC eligibility check. Buyers assume your offer is MACC-eligible. Confirm the flag in Partner Center before promising commit drawdown.

Manual deal terms outside Marketplace. ISVs sign side letters with custom terms not reflected in the Marketplace contract. This creates conflict between what Microsoft enforces and what the side letter says. Put everything in the Marketplace contract.

No co-sell motion. Private offers close fastest when Microsoft sellers refer the deal. ISVs who skip co-sell setup never get the field-team referral pipeline.

How a managed service partner handles all this

The technical and operational work to run private offers well is substantial:

• Maintaining the transactable infrastructure
• Building the sales process to scope offers correctly
• Tracking MACC eligibility status
• Coordinating with Microsoft on co-sell
• Handling channel and reseller motions
• Operating the renewal cycle

For ISVs without an internal Microsoft commerce expert, services like WeTransact run the entire Marketplace operation as a managed service. They handle the technical infrastructure, the private offer mechanics, the partner relationship, and the deal-flow operations. Your team focuses on the sales conversation; they handle the Marketplace plumbing.

This is the path most growth-stage B2B SaaS companies pick once they have 2-3 enterprise deals that need Marketplace transaction. The alternative is hiring a Microsoft commerce expert (rare, expensive) or burning engineering time on Microsoft APIs.

Frequently asked questions

Final word

Private offers are how enterprise software actually sells on Azure Marketplace in 2026. Public listings drive discovery and small deals. Private offers close enterprise revenue.

If you are an ISV with enterprise pipeline and you are not on Marketplace, you are losing deals to vendors who can transact through their customers' Azure commits.

Two paths from here:

1. Build it in-house. Plan for 3-6 months of engineering to make your public offer transactable, then 2-4 weeks to set up the private offer playbook and train sales.
2. Use a managed service. WeTransact operates the entire Marketplace infrastructure including private offer mechanics. Most growth-stage B2B SaaS companies end up here because the alternative is paying senior engineering time for half a year.

For a broader overview of Marketplace and what gets you to a working transactable offer in the first place, see How to Sell Software on Azure Marketplace.

The opportunity is real. Most ISVs are still on the fence. The time to be there first is now.

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.