Microsoft Marketplace Private Offers: What ISVs Need to Know in 2026

• Private offers on azure marketplace let ISVs structure negotiated enterprise deals with custom pricing and terms while keeping the transaction within Microsoft Marketplace.
• ISVs can sell directly to customers, through multiparty private offers (MPOs), or via CSP partners, depending on how the deal is being sold.
• For eligible solutions, purchases through direct and multiparty private offers can count toward a customer’s Microsoft Azure Consumption Commitment (MACC), making marketplace procurement more attractive for enterprise buyers.
• The mechanics matter: billing accounts, permissions, pricing structure, acceptance and purchase are separate steps, and mistakes at any stage can delay an otherwise closed deal.
• As private-offer activity grows, ISVs need tighter coordination between CRM, marketplace operations and finance to track offers through purchase, revenue and renewal.

A Microsoft Azure Marketplace private offer is a custom, time-bound transaction that lets an ISV sell to a specific customer or partner at negotiated pricing and terms through Microsoft Marketplace (previously Azure Marketplace), scoped to a named Azure billing account.

Public listings handle self-service purchases. They can’t handle volume pricing, contract-length variations, or procurement-negotiated terms. Private offers do that within the marketplace. A private offer gives you:

• Organization-level targeting. The offer attaches to the customer’s Azure billing account, not a subscription or tenant.
• Time-bound pricing. Start and end date, with duration depending on the pricing path used.
• Custom terms. Attach your own PDF, subject to Microsoft Publisher Agreement rules.
• Bundling. Up to 10 eligible products or plans in one offer.
• Fast availability. Most submitted offers become visible to the customer within about 15 minutes.

Private offers work for transactable SaaS, professional services, Azure virtual machines, Azure containers, and Azure applications. Discounts apply to the ISV’s software charges, not the customer’s Azure infrastructure consumption.

When ISVs want to sell privately through Microsoft Marketplace, there are two main options: private plans and private offers. They can both support customer-specific transactions, but they solve different problems.

A private plan is essentially a version of a marketplace plan that is visible only to selected customers. It works well when you want to offer a specific configuration, pricing structure, or set of terms to a restricted audience.

A private offer, on the other hand, is built around a specific negotiated deal. It lets you take an existing marketplace product or plan and structure customer-specific pricing, terms, dates, and other commercial details against the customer’s billing account.

The simplest way to think about it is:

• Use a private plan when you need a restricted or customized version of a product plan.
• Use a private offer when you are closing a negotiated commercial deal with a specific customer.

For most negotiated enterprise transactions, private offers are now the more natural route because they are designed around the deal rather than the underlying product configuration.

Private plans still have an important role. They are useful when an ISV needs to create a restricted-access or specialized version of a SaaS, VM, or Azure Application plan for selected customers. But when the underlying product is already available and the requirement is simply to negotiate pricing, terms, or deal structure with a specific buyer, a private offer is usually the better fit.

ISV-to-customer private offers

The direct sales model. You create the offer against the customer’s Azure billing account, share it with them, and they accept and purchase through Azure Marketplace. This works cleanest when there’s no partner between you and the buyer.

Multiparty private offers (MPOs)

MPOs bring a channel partner into the transaction. The partner earns margin on the deal, not a referral fee. The flow:

• You configure the offer and set commercial terms with the partner
• The partner sets the customer-facing price and sends the offer through to the end customer
• The customer purchases through Microsoft Azure Marketplace, and Microsoft handles both the transaction and the payouts

MPOs work for transactable SaaS, Azure VMs, Azure applications, and Azure containers. They don’t cover professional services sold to customers. If professional services are part of the deal:

• Run it through an ISV-to-customer private offer
• Note that professional services on the marketplace are currently limited to the US, UK, and Canada

Eligible MPO purchases count toward a customer’s MACC when the underlying solution is MACC-eligible.

CSP private offers

CSP private offers exist for the Microsoft Cloud Solution Provider ecosystem. You create an offer that provides a margin to the CSP partner.

The customer flow is different. The end customer doesn’t accept a separate private offer in the Azure portal. The purchase runs through the CSP partner’s standard commerce motion. CSP private offers follow the CSP program’s own commercial and billing rules. MACC eligibility on CSP transactions varies. Check with Microsoft on each deal.

MACC and committed cloud spend

MACC (Microsoft Azure Consumption Commitment) is the pool of committed Azure spend an enterprise has agreed to consume over a contract period. For years, only Microsoft’s own first-party consumption drew it down. However, now, 100% of eligible purchases of MACC-eligible ISV solutions through ISV-to-customer or multiparty private offers count towards MACC too.

For customers, that can make marketplace procurement more attractive. Instead of securing a completely new budget for your software, they may be able to use cloud spend they have already committed to Microsoft.

But MACC should not be assumed on every marketplace deal. For it to be relevant, three things need to be true:

1. The customer must have an active MACC. Not every enterprise Azure customer does.
2. Your solution must be MACC-eligible. Being transactable on Microsoft Marketplace does not automatically make a solution eligible.
3. The customer must have commitment remaining. There needs to be enough available MACC balance for the purchase to draw against.

That is why MACC eligibility is worth validating early in the sales process. If all three conditions are met, it can become a meaningful part of the commercial conversation.

Channel margin

MPOs and CSP private offers give channel partners real commercial margin. Public listings only offer a referral fee. That’s usually the difference between a partner selling with you and a partner sending customers to your URL.

For a channel-led motion on Microsoft, MPOs are the way partner economics work.

Private offers and Microsoft’s co-sell programs get conflated a lot. Private offers structure the transaction. Co-sell governs the joint go-to-market motion and its incentive programs. They come up together in enterprise conversations but do different things.

Once you decide to use a private offer, the next question is how much of the deal you can actually customize. The answer depends on whether you are adjusting an existing marketplace plan or creating a new customized plan within the private offer.

Option 1: Customize pricing and terms on an existing public plan

This is the more straightforward route. You use an existing marketplace plan as the base and customize the commercial terms for a specific customer.

You can change:

• Price or discount off the base plan
• Start and end dates
• Accept-by date
• Bundle composition, with up to 10 products or plans
• Custom terms attached as a PDF
• Pricing approach, using either a discount or absolute pricing where supported

However, the underlying structure of the public plan remains unchanged. That includes:

• Pricing model and billing dimensions
• Contract duration structure
• Trial availability
• Offer type

This distinction matters during negotiation. If a customer asks for a change that sits within the underlying plan structure rather than the private offer itself, you may need to create or republish a plan before the deal can proceed.

Option 2: Absolute pricing as a new customized plan inside the private offer

For some offer types, Microsoft also allows ISVs to create a new customized plan directly within an ISV-to-customer private offer.

This provides greater flexibility than simply adjusting an existing plan. For supported SaaS and professional services offers, ISVs can customize elements such as:

• Absolute price
• Charge schedule
• Metering quantities
• User limits
• Contract duration, including non-standard terms from 1 to 120 months

Absolute pricing works for SaaS, professional services, Azure applications, and Azure containers, plus VM software reservations. It doesn’t work for Azure VM offers or plans with a trial enabled. Currency alignment matters since the customer’s market currency and billing account currency have to match.

The practical takeaway is simple: a private offer does not automatically make every part of a marketplace deal negotiable. The flexibility available depends on the underlying offer type and the pricing path you choose.

Once the commercial structure of the deal is agreed, the next step is getting everything in place to create the private offer in the Partner Center. First, you need a transactable offer live on Microsoft Marketplace. You’ll also need:

• The appropriate Marketplace developer, manager, or account-owner role in Partner Center
• The customer’s Azure billing account ID
• Agreed pricing and offer dates, including the start date, end date, and accept-by date
• Any commercial terms that need to be included with the offer
• For an MPO, the channel partner’s Marketplace seller ID and confirmation that the partner is eligible for MPO transactions

Billing account IDs commonly cause delays. ISVs can’t pull them. The customer has to fetch it from Azure Cost Management and Billing, or run Microsoft’s private-offer eligibility report. That report also flags permissions and policy issues. Ask for the billing account ID during the pricing conversation so marketplace ops runs in parallel with legal review.

With the prerequisites in place, the Partner Center flow is direct:

1. Sign in to Partner Center and open the Marketplace offers workspace.
2. Select Private offers, then the Customers tab.
3. Select New private offer and give it a descriptive name.
4. Choose the pricing approach.
5. Add the customer’s Azure billing account ID.
6. Configure the private pricing.
7. Set the pricing start date, end date, and accept-by date.
8. Attach custom terms and conditions as a PDF where needed.
9. Add notification contacts and the “prepared by” contact.
10. Review, submit, and share the private-offer link with the customer.

Publication usually completes inside 15 minutes.

Creating and publishing the private offer does not mean the deal is complete. In a marketplace transaction, there is often a gap between the customer agreeing to buy and the purchase actually going through.

That creates two distinct milestones to track:

The commercial close happens when the customer agrees to the deal, pricing and terms are finalized, and procurement signs off.

The marketplace close happens when the transaction is completed through Microsoft Marketplace. The offer is published, the customer accepts it, the Purchase option becomes available in Azure, and the subscription goes active.

The gap between these two milestones can be significant:

• Publication: typically up to 15 minutes after submission
• Acceptance: depends on when the customer acts
• Purchase option enabled: typically 15 to 60 minutes after acceptance
• Purchase: depends on when the customer or finance team completes the transaction

This is why an offer marked “accepted” should not automatically be treated as closed revenue. Until the customer completes the purchase, the transaction is still pending.

For teams managing marketplace deals at scale, both milestones need to be visible in the pipeline. Sales may track the commercial close, but marketplace operations and forecasting should also account for whether the purchase has actually been completed.

Renewals

Microsoft Marketplace private offers don’t auto-renew. Each offer has a defined end date, and continuing the customer at the negotiated price requires a new private offer created and accepted before the current one expires.

Microsoft applies a 50% discount to the standard marketplace transaction fee on qualifying renewals. To get the reduced fee, self-attest to the renewal status during private offer creation in Partner Center. Renewals include:

• Renewal of a current private offer
• Renewal of a paid offer being migrated to the marketplace
• Upsell to an existing paid customer

The discount applies for the entire term of the renewal offer, not just the first year. Offers created before October 1, 2024 aren’t eligible.

Subscription renewal is a separate setting. For SaaS, publishers choose how the underlying subscription renews when the current contract term ends:

• Renew into private offer: While the private offer is active, the subscription continues at private offer terms
• Renew into public offer: The subscription renews to the selected public plan at the end of the current term

A public offer renewal term must be selected either way, as the fallback if the private offer is no longer active. Auto-renew is off by default; the customer chooses whether to enable it at purchase.

At scale, renewals become their own operational problem. Every customer needs a new offer created before their existing one expires, tracked in Partner Center or wherever else the ISV holds subscription data. Miss the window and the subscription either lapses or falls back to public pricing.

Most delays fall into a handful of patterns:

• Billing account mismatches. The billing account on the offer has to match the account the customer plans to purchase through.
• Insufficient customer permissions. The people accepting and purchasing need the right billing and Azure subscription roles.
• Marketplace purchasing policies. The customer’s internal policies can block the transaction even when the offer is configured correctly.
• Overlapping offers. Microsoft blocks conflicting offers against the same customer, base plan, and pricing period.
• Accepted but not purchased. The acceptance-to-purchase gap turns accepted offers into deals at risk.

Microsoft’s private-offer eligibility report checks billing account, subscriptions, roles, permissions, and marketplace policies before purchase. Run it before the deal, not after something breaks.

For a small number of private offers, managing through the Partner Center is usually enough. The challenge starts when marketplace deals become a meaningful part of the sales motion and multiple offers are in motion.

The issue is less about creating the offer and more about keeping the entire deal lifecycle connected.

In a typical workflow:

• The deal starts in the CRM, where the seller manages the opportunity, pricing, and commercial terms.
• The seller then moves to Partner Center to recreate the offer and enter much of the same information again.
• Acceptance, purchase, and subscription status remain in Partner Center rather than flowing back into the CRM.
• Finance then has to reconcile marketplace transactions with CRM opportunities, often through exports and manual matching.

At low volumes, these handoffs are manageable. At scale, they create duplicate work and make it harder to see where a deal actually stands. An offer may be commercially closed but still waiting for acceptance or purchase, while the CRM continues to show it as complete.

This is where connecting marketplace execution with the CRM becomes important. Instead of running Partner Center as a separate operational workflow, teams can create and track marketplace deals from the systems where sales already works.

That is the problem SaaSify is designed to solve.

SaaSify supports the Microsoft Marketplace journey from getting an offer transactable to creating and managing private offers through the CRM.

Get transactable on Azure Marketplace

SaaSify provides pre-built marketplace integrations and SaaS fulfillment capabilities, reducing the engineering effort required to launch and operate a transactable offer. This can also help ISVs move from a Contact Me listing to a transactable marketplace motion.

Create private offers from your CRM

SaaSify supports CRM platforms including Salesforce, HubSpot, and Zoho, allowing teams to create Microsoft Marketplace private offers from the sales systems they already use.

Teams can:

• Create and publish ISV-to-customer and multiparty private offers
• Use existing customer, pricing, and opportunity data to build the offer
• Reduce manual re-entry between the CRM and Partner Center

For Salesforce teams, for example, an opportunity, quote, or order can become the starting point for a Microsoft Marketplace private offer.

Manage private offers and the ongoing lifecycle

SaaSify brings marketplace activity back into the CRM, giving teams visibility into the transaction after the offer is published.

Teams can track offer status through acceptance, purchase, and subscription activation, while also managing:

• Subscriptions, renewals, and co-terming
• Payouts, collections, tax, and marketplace fees
• Reporting and reconciliation across sales, finance, and marketplace teams

This helps teams manage both the marketplace close and what happens after the customer purchases. SaaSify also tracks renewal timing as part of subscription lifecycle management. Upcoming renewals surface inside Salesforce alongside the rest of the pipeline, offers can be generated from the CRM before the current pricing period ends.

The SaaSify MCP Connector

The SaaSify MCP Connector connects marketplace and CRM data to MCP-compatible AI applications. Your teams can query marketplace status, revenue, subscriptions, and pipeline in plain English:

• What’s the status of the ‘Company name’ Microsoft Marketplace private offer?
• How much marketplace revenue did we close last quarter?
• Which subscriptions renew in the next 30 days?
• What’s the pipeline running through MPOs right now?

Answers come back live, pulled from data across SaaSify, the CRM, and the cloud providers. For teams running many concurrent offers, this changes how quickly they can find and act on marketplace data.

Microsoft Azure Marketplace private offers can unlock more flexible enterprise deals, stronger partner participation, and access to committed cloud spend. But the advantage only compounds when the operational side keeps pace with the sales motion. SaaSify helps ISVs get transactable, create and manage private offers from the CRM, and keep sales, marketplace operations, and finance aligned as volume grows.

Ready to make Microsoft Marketplace a repeatable revenue channel, not another manual workflow? Book a demo with SaaSify and see how your team can run private offers at scale.

Does Microsoft charge a transaction fee on Microsoft Azure Marketplace private offers?

Yes, a 3% standard store service fee on customer purchases through the marketplace, and 1.5% on qualifying renewals (a 50% discount that applies for the full term of the renewal offer, provided the renewal status is self-attested during offer creation). There’s no cost to publish offers themselves.

Who does the customer pay when they purchase through a Microsoft Marketplace private offer?

The customer pays Microsoft. Microsoft is the merchant of record, collects the payment and any taxes, and remits the ISV’s share. For MPOs, it also handles the channel partner’s share.

Can a Microsoft Azure Marketplace private offer auto-renew?

No. Microsoft Marketplace private offers are time-bound with a defined end date. Renewals require a new private offer created and accepted before the current pricing period ends.

Can I move an existing customer from a public plan onto a Microsoft Marketplace private offer?

Yes, but there’s no in-place migration. The customer cancels the existing subscription and accepts the new private offer. Timing against renewal dates takes the most coordination.

Can I create a Microsoft Marketplace private offer in a currency other than USD?

Yes. Marketplace transactions can be completed in 17 currencies, including USD, EUR, GBP, JPY, AUD, CAD, INR, BRL, CHF, DKK, NOK, SEK, NZD, TWD, HKD, RUB, and KRW. Pricing is entered in USD by default and converts to the customer’s local currency based on their billing address. Absolute pricing requires the customer’s market currency and billing account currency to match. Discounted pricing off a public plan is more flexible.

Can SaaSify automate Microsoft Marketplace private offers?

Yes. SaaSify handles ISV-to-customer and multiparty Microsoft Marketplace private offer creation and lifecycle, integrates with Salesforce and other CRMs, provides transactable marketplace capabilities, and covers subscriptions, payouts, and reporting.