An Azure Marketplace private offer is a custom, time-bound deal sent to one named customer. A private plan is a pricing plan within an offer that only the customers you target can see and buy, and an offer can be made of private plans alone. They solve different problems, and Microsoft supports them on different offer types.
Updated November 6, 2026: an earlier version of this post called the multiparty private offer the only way to bring a reseller into a Microsoft deal. Resellers in the Cloud Solution Provider program get CSP partner private offers instead, as the multiparty section now says; the private plan section and two FAQ answers now also say how targeting varies by offer type. It also no longer says a private plan must sit in a public listing: an offer can contain only private plans.
The first time a deal desk sends a custom-priced deal through Microsoft’s marketplace, somebody opens Partner Center and finds three things that all look like the answer: a private offer, a private plan, and — if a partner is involved — a multiparty private offer.
Picking the wrong one is not a formatting mistake. Each construct targets the customer differently, carries different legal terms, and is supported on a different set of offer types. Some deals simply cannot be done with the construct you reached for first.
Here is what each one is, and a decision framework for choosing between them.
What is an Azure Marketplace private offer?
An Azure Marketplace private offer is a custom deal a publisher extends to one specific buyer, with negotiated pricing, terms, and an expiry date. It is created in Partner Center, sits outside the public listing entirely, and is built to align the customer’s procurement and IT teams around one agreed transaction.
Two properties make it the default for enterprise deals. It is time-bound — the offer has a deadline, which does useful work in a negotiation. And it can carry a custom end user licence agreement attached to that specific transaction, so a customer with redlines is not forced onto your standard public terms.
Private offers are also the construct that carries the full deal-making surface: negotiated price, term, and the paperwork enterprise procurement expects. If you are new to selling through Microsoft, how to sell on Azure Marketplace covers where offers sit in the wider listing and Partner Center flow.
What is a private plan?
A private plan is a pricing plan within an offer that only targeted customers can see and buy. Beside public plans, the listing stays public and the plan does not; an offer that contains only private plans isn’t visible in Microsoft Marketplace at all. Publishers use it to give a specific customer — or a small set of them — custom pricing without building a separate deal each time.
The differences from a private offer are precise and worth memorising:
- Targeting. A private plan is scoped by tenant ID for SaaS offers; Azure Application and Managed Service plans use Azure subscription IDs, and Virtual Machine plans can use either or both. A private offer is scoped to the customer’s billing account. That distinction decides which one your customer’s procurement structure can even accept.
- Legal terms. Both constructs can carry customer-specific terms. Microsoft’s publisher documentation lists private terms and conditions as a private-plan capability that “enable publishers to tailor terms and conditions to a specific customer.” What only a private offer adds is contract upload — Microsoft lists “Custom terms and contract upload,” attaching a PDF of your contract, among the benefits of private offers, and says private plans “don’t support some important private offer capabilities.”
- Supported offers. Private plans are only available for paid products that can be purchased and installed directly from the Azure portal. Publishers cannot create private plans for consulting services, for any offer whose call to action is “Contact me,” or for any free service — regardless of whether it installs from the portal.
That last constraint is where most teams discover the difference the hard way. A services offer or a “Contact me” listing has no private-plan path at all.
And multiparty private offers
A multiparty private offer (MPO) works like a private offer, except a channel partner sells it to the customer. The customer buys each included product through Microsoft Marketplace, and Microsoft invoices and collects payment from the customer under their existing billing terms with Microsoft.
Use it when the transacting party is not you. If your motion is direct, an MPO adds a party and a margin conversation for no benefit. If your motion runs through resellers, it is the construct that puts them in a Microsoft Marketplace transaction (partners selling through the Cloud Solution Provider program get CSP partner private offers instead) — CPPO vs MPO vs reseller offers across the clouds compares it with the AWS and Google Cloud equivalents.
Which construct for which deal shape
| Deal shape | Use | Why |
|---|---|---|
| One enterprise customer, negotiated price and term | Private offer | Time-bound, billing-account scoped, full deal terms |
| Customer requires their own contract attached as a PDF | Private offer | Contract upload is listed as a private-offer capability; private plans tailor terms but take no contract file |
| A few known tenants on standing custom pricing | Private plan | No per-deal build; pricing lives in the offer |
| Consulting or professional services offer | Private offer | Private plans are not supported for consulting services |
| Offer with a “Contact me” call to action | Private offer | Private plans require a directly purchasable, installable product |
| Free offer with a custom arrangement | Neither — restructure | Private plans exclude free services |
| A reseller transacts with the customer through Microsoft Marketplace | Multiparty private offer | Puts the partner in the transaction; Microsoft bills the customer |
| Customer wants the spend to count against committed Azure spend | Private offer | Enterprise buyers are usually optimising for MACC drawdown — see below |
Read the table top to bottom and the rule of thumb emerges: private offers are for deals, private plans are for standing arrangements. If the pricing is the outcome of a negotiation, it is an offer. If the pricing is a policy you apply to a known tenant, it is a plan.
The reason the customer cares at all
Most enterprise buyers are not asking for a private offer because they like the mechanism. They are asking because purchases made through Microsoft’s marketplace can draw down their Microsoft Azure Consumption Commitment (MACC) — money they have already promised Microsoft they will spend.
That is the actual centre of gravity in an Azure deal, and it changes which internal conversation the customer has to win. What is a MACC? explains the drawdown mechanics and why it moves procurement timelines.
Which is also why the construct choice matters more than it looks. Reaching for a private plan because it seemed simpler, on an offer type that does not support one, restarts a procurement conversation that was nearly finished.
Operating all this without a Partner Center tab open
The constructs are Microsoft’s; the operational load is yours. Each private offer has an expiry to track, each private plan has a tenant list to maintain, and every accepted deal has to reconcile back to the opportunity in your CRM and the revenue in your books.
Fours creates and tracks private offers across every connected marketplace from one place — including Microsoft — so a deal desk works one queue instead of one console per cloud, and accepted offers sync back to Salesforce or HubSpot without re-keying. Private offer automation covers the offer lifecycle, and the Azure Marketplace seller solution covers the Microsoft-specific setup.
Frequently asked questions
What is the difference between an Azure private offer and a private plan? A private offer is a time-bound custom deal sent to one customer’s billing account. A private plan sits within an offer, visible only to the tenants or subscriptions you target. Both can carry customer-specific terms; only a private offer lets you upload your own contract as a PDF.
Can I create a private plan for a consulting services offer? No. Private plans are only available for paid products that can be purchased and installed directly from the Azure portal. Consulting services, “Contact me” offers, and free services are excluded.
Which one lets me attach custom legal terms? Both can. Microsoft’s publisher docs say private terms and conditions “enable publishers to tailor terms and conditions to a specific customer.” Only a private offer adds “Custom terms and contract upload” — attaching a PDF of your contract to that transaction.
How does a customer get targeted for each? A private plan uses tenant IDs for SaaS, Azure subscription IDs for Azure Application and Managed Service offers, and either or both for Virtual Machine offers. A private offer is aligned to the customer’s billing account. Confirm which identifier your customer can provide before you build the offer.
What is a multiparty private offer? A multiparty private offer works like a private offer, except a channel partner sells it to the customer. The customer buys each product through Microsoft Marketplace, and Microsoft invoices and collects payment.
Do private offers count toward a customer’s MACC? Eligible marketplace purchases are what enterprise buyers use to draw down a Microsoft Azure Consumption Commitment. It is usually the reason they asked for a marketplace transaction in the first place.
Takeaways
- Private offers are for negotiated deals; private plans are for standing custom pricing on known tenants.
- Both constructs can carry customer-specific terms, but only a private offer takes a contract upload. If the customer needs their own paper attached, the choice is already made.
- Private plans don’t exist for consulting services, “Contact me” offers, or free services — check the offer type before promising one.
- Confirm whether the customer can give you a tenant or subscription ID, or a billing account. That identifier decides the construct.
- Use a multiparty private offer when a partner transacts, not when you do.
Three constructs, one deal desk. See how private offer automation in Fours builds and tracks Microsoft offers alongside every other marketplace you sell on.
Sources
Primary sources for the platform rules cited above. Last verified November 6, 2026. Cloud providers change fees, eligibility, and program terms without notice — check the source before relying on a figure.
- ISV-to-customer private offers - Marketplace publisher — Private offers are time-bound and carry customized terms; custom terms and contract upload (a PDF) is listed among their benefits; CSP partner and multiparty private offers are separate types.
- Learn about Private plans - Marketplace customer documentation — Exact exclusion list: consulting services, Contact me, free services. Private plans lack some private offer capabilities.
- Private plans in Microsoft Marketplace - Marketplace publisher — Private plans are components of an offer, visible and purchasable only by targeted customers; an offer can contain only private plans and is then not visible in Microsoft Marketplace. Private-plan targeting by offer type: Microsoft Entra tenant IDs for SaaS, Azure subscription IDs for Azure Application and Managed Service, tenant IDs, subscription IDs or both for Virtual Machine.
- Multiparty private offers overview - Marketplace publisher — MPO flow: partner sells, Microsoft invoices and collects.
- Azure Consumption Commitment Benefit - Marketplace customer documentation — Eligible marketplace purchases count toward the customer's MACC.
Keep reading
Stay Updated
New posts, product updates and marketplace strategy are shared on LinkedIn as they publish.
Follow Fours on LinkedIn