Seamless Marketplace private offers: creation to customer use

Private offers are a core mechanism for bringing negotiated commercial terms into Microsoft Marketplace. They allow publishers and channel partners to offer negotiated pricing, flexible billing structures, and custom terms; while enabling customers to purchase through the same Microsoft governed procurement, billing, and subscription experience they already use for Azure purchases.

As Marketplace adoption grows, private offers increasingly involve channel partners, including resellers, system integrators, and Cloud Solution Providers. While commercial relationships vary, the Marketplace lifecycle remains consistent. Understanding that lifecycle—and where responsibilities differ by selling model—is essential to executing private offers efficiently and at scale.

Join us April 15 for Marketplace Partner Office Hours, where Microsoft Marketplace experts Stephanie Brice and Christine Brown walk through how to execute private offers end to end—from creation to customer purchase and activation—across direct and partner‑led selling models. The session will include a live demonstration and Q&A, with practical guidance on flexible billing, channel scenarios, and common pitfalls.

This article walks through the private offer lifecycle to help partners establish a clear, repeatable operating model to successfully transact in Microsoft Marketplace.

Why private offers are structured the way they are

Private offers are designed to align with how enterprise customers already procure software through Microsoft. Customers purchase through governed billing accounts, defined Azure role-based access control (RBAC) enforced roles, and Azure subscriptions that support cost management and compliance.

Rather than bypassing these controls, private offers integrate negotiated deals directly into Microsoft Marketplace. This allows customers to:

• Apply purchases to existing Microsoft agreements (Microsoft Customer Agreement (MCA) or Enterprise Agreement (EA))
• Preserve internal approval workflows
• Manage Marketplace subscriptions alongside other Azure resources

Private offers also support flexible billing schedules. This is especially important for enterprise customers managing budget cycles, approvals, and cash flow. Flexible billing allows partners to align charges to agreed timelines—such as billing on a specific day of the month or spreading payments across defined milestones—while still transacting through Microsoft Marketplace. Customers can align Marketplace charges with internal finance processes without requiring separate contracts or off‑platform invoicing.

For publishers and partners, this design creates a predictable lifecycle that scales across direct and channel‑led motions. Each stage exists for a specific reason and understanding that intent helps reduce delays and rework.

Learn more:
Private offers overview

One lifecycle, multiple selling models

All private offers—regardless of selling model—follow the same three stages:

1. Creation of a private offer based on a publicly transactable Marketplace offer
2. Acceptance, purchase, and configuration of the private offer
3. Activation or deployment, based on how the solution is delivered

What varies by model is who creates the offer, who sets margin, and who owns the customer relationship—not how Microsoft Marketplace processes the transaction.

1. Creation: Starting with a transactable public offer

Every private offer begins with a publicly transactable Marketplace offer enabled for Sell through Microsoft. Private offers inherit the structure, pricing model, and delivery architecture of that public offer and its associated plan.

If a public offer is listed as Contact me or otherwise non‑transactable, it must be updated before any private offers—direct to customer or channel‑led—can be created.

Creation flows by selling model:

Customer private offers (CPO)
The publisher creates a private offer in Partner Center for a specific customer, based on the Azure subscription (Customer Azure Billing ID) provided by the customer. The publisher defines negotiated pricing, duration, billing terms (including any flexible billing schedule), and custom conditions.

Multiparty private offers (MPO)
The publisher creates a private offer in Partner Center and extends it to a specific channel partner. The partner adds margin and completes the offer before sending it to the customer.

Resale enabled offers (REO)
The publisher authorizes a channel partner in Partner Center to resell a publicly transactable Marketplace offer. Once authorized, the channel partner can independently create private offers for customers without publisher involvement in each deal.

Cloud Solution Provider (CSP) private offers
A CSP hosts the customer’s Azure environment (typically for SMB customers) and acts on behalf of the customer. The publisher creates a private offer in Partner Center for a CSP partner, extending margin so the CSP can sell the solution to customers through the CSP motion.

In all cases, the private offer remains anchored to the same underlying public Marketplace offer.

2. Acceptance and purchase: What happens in Marketplace

Microsoft Marketplace provides a consistent purchasing experience while supporting different partner‑led models behind the scenes.

Customer private offer, multiparty private offer, resale enabled private offer

For these models, the customer experience is the same and includes three steps:

1. Accepting the private offer
   The customer accepts the negotiated terms (price, duration, custom terms) in Azure portal. This is the legal acceptance step under the customer’s MCA or EA.
2. Purchasing or subscribing
   The customer associates the offer to the appropriate billing account and Azure subscription. This enables billing and fulfillment.
3. Configuring the solution
   After subscription, the customer is redirected to the partner’s landing page. This step connects the Marketplace purchase to the partner’s system, enabling provisioning, subscription activation, and setup.

Learn more:
Accept the private offer 

Purchase and subscribe to the private offer

In large enterprises, acceptance and purchase are often completed by different roles, supporting governance and auditability.

CSP private offers

In the CSP model, the CSP partner—not the end customer—accepts and purchases the private offer on the customer’s behalf. Microsoft invoices the CSP partner, and the CSP bills the end customer under their existing CSP relationship.

Key distinctions:

• The end customer does not interact with the Marketplace private offer
• CSP private offers do not decrement customer Microsoft Azure Consumption Commitment (MACC) because there is no MACC in the CSP agreement
• Customer pricing and billing occur outside Marketplace

Learn more:
ISV to CSP private offers

3. Activation or deployment: Defined by delivery model, not selling motion

Activation or deployment is determined by how the solution is built, not whether the deal is direct to customer or channel‑led.

SaaS offers
The solution runs in the publisher’s environment. After subscription, activation occurs through the SaaS fulfillment process, typically involving customer onboarding or account configuration. No Azure resources are deployed into the customer’s tenant.

Deployable offer types (virtual machines, containers, Azure managed applications)
The solution runs in the customer’s Azure tenant. Deployment provisions resources into the selected Azure subscription according to the offer’s architecture.

Channel partners may support onboarding or deployment, but Marketplace activation or deployment reflects the technical delivery model—not the commercial route.

Setting expectations that scale

Successful partners set expectations early by separating commercial steps from technical activation:

1. The customer transacts under an Enterprise Agreement (EA) or Microsoft Customer Agreement (MCA)
2. The private offer includes custom pricing and any flexible billing schedule based on the publicly transactable offer
3. The customer accepts negotiated terms in Microsoft Marketplace
4. The purchase and subscribe steps associate the offer to the billing account and Azure subscription, the configure step triggers the notification to activate or deploy the solution for customer use
5. Billing starts based on SaaS fulfillment or Azure resource deployment

Choosing the right model

While the lifecycle is consistent, each model supports different strategies:

• Customer private offers allow the publisher to negotiate terms directly with the customer
• Multiparty private offers enable close channel collaboration while sharing margin
• Resale enabled offers support scale by empowering channel partners to transact independently
• CSP private offers align with customer segments led with this motion

The right choice depends on partner strategy, not on how Marketplace processes the transaction.

Learn more:

Transacting on Microsoft Marketplace

Bringing it all together

Private offers turn negotiated agreements into scalable, governed transactions inside Microsoft Marketplace. Regardless of whether a deal is direct or channel‑led, the underlying lifecycle remains the same, rooted in a transactable public offer, executed through Microsoft‑managed purchasing, and activated based on how the solution is delivered.

By understanding that lifecycle and intentionally choosing the right direct or channel model and billing structure, partners can reduce friction, set clearer expectations, and scale Marketplace transactions with confidence. When aligned correctly, private offers become more than a deal construct; they become a repeatable operating model for Marketplace growth.