Marketplace channel motions

REO vs. MPO vs. CSP Private Offers: The Three Marketplace Motions Microsoft's Own Documentation Can't Keep Straight

Microsoft's Marketplace overview page and its own FAQ page currently list different sets of eligible countries for the same program. Here is what each motion actually does, where partners get stuck, and how to pick the right one anyway.

The documentation gap

Three motions, one confusion

Where partners get stuck

Why now, precisely

Which one fits your deal

Before you configure one

Ask a Microsoft partner to explain the difference between Resale Enabled Offers, Multiparty Private Offers, and CSP Private Offers, and most will get two of the three right. That is not a knowledge gap on the partner's side. Microsoft's own Marketplace overview page and its own CSP FAQ page currently state two different lists of eligible countries for the same program, one dated three months after the other, and neither has been reconciled with the other yet.

This brief is not a documentation fix. It is a working explanation of what each of the three channel-led Marketplace motions actually does, where the real friction sits once a partner tries to use one, and which motion fits which kind of deal, built from Microsoft's current published mechanics and the actual questions partners are asking in Microsoft's own forums.

The documentation gap

Even Microsoft's own pages don't agree

Microsoft's "Multiparty private offers overview" page (learn.microsoft.com/en-us/partner-center/marketplace-offers/multiparty-private-offers-overview, last updated July 22, 2026) lists 36 supported countries and regions: the US, the UK, Japan, Australia, South Africa, Canada for customers only, and 30 EU and EEA countries. Microsoft's own "CSP private offers FAQ" page (learn.microsoft.com/en-us/partner-center/marketplace-offers/isv-csp-faq, last updated April 2, 2026) still states, in its own side-by-side comparison table, that multiparty private offers are "Available in US, UK, and Canada," and links directly to the page above that now contradicts it.

Neither page is wrong exactly. One is stale. But there is no banner, no version note, and no flag telling a partner which one to trust, and a partner who plans a deal around the older figure will misjudge which customers even qualify for the offer type they are about to configure.

The practical lesson holds regardless of which page happens to be current on a given day. Treat any single Microsoft Learn page as a starting point, not a final answer, and confirm current country eligibility directly in Partner Center before committing to a deal structure with a customer.

Countries Microsoft's current MPO overview page lists as supported

Its own CSP private offers FAQ, published three months earlier and still live, says "US, UK, and Canada" in its own comparison table. Both pages rechecked September 23, 2026.

Three motions, one confusion

REO, MPO, and CSP private offers are not interchangeable

The three channel-led motions solve different problems. Microsoft's own "Multiparty private offers FAQ" page (learn.microsoft.com/en-us/partner-center/marketplace-offers/multiparty-private-offers-faq, updated August 18, 2026) compares customer private offers, MPO, and CSP private offers side by side. REO is not in that table. The REO rows below come from the REO overview and REO FAQ pages, and the rest from the MPO and CSP private offers FAQs, all rechecked September 23, 2026.

Three motions, side by side, deliberately not ranked

Motion	Best For	Eligible Seller	Geography
Resale Enabled Offers (REO)	Ongoing resale across many customers without renegotiating each deal (SaaS, VM software reservation, and Dragon Copilot offers only)	Any partner the software company authorizes; each authorization covers one offer, one channel partner, and the markets selected	All Marketplace-supported countries except Belarus, Brazil, China, India, Mexico, Russia, Singapore, and South Korea (REO overview, updated May 27, 2026)
Multiparty Private Offers (MPO)	A single negotiated enterprise deal that should count toward Azure IP Co-Sell eligibility	A channel partner collaborating directly with the software company	36 countries per the MPO overview page (updated July 22, 2026); the CSP FAQ (updated April 2, 2026) still lists only US, UK, and Canada in its own comparison table, see Section 1
CSP Private Offers	Selling to SMB customers already buying through a CSP program	CSP Direct Bill Partner or Indirect Provider only, not Indirect Reseller	Wherever the CSP program itself operates

What actually trips people up is who is allowed to be the seller, not geography. Microsoft's own CSP private offers FAQ states plainly that a software company can extend a private offer to CSP Direct Bill or Indirect Provider partners only. Its own words: "Indirect Resellers need to work with their Indirect Providers." A software company cannot pass a margin to an Indirect Reseller directly under any circumstance. The Indirect Provider is the required intermediary, not an optional one.

Where partners get stuck

The mechanics nobody warns you about until you hit them

Real friction shows up in predictable places once a partner is actually inside a deal, and each one is a limitation discovered mid-configuration rather than planned around in advance.

Inside an MPO, software companies and channel partners can attach up to five customer-facing terms and conditions documents, but those are for the customer to accept, not for exchanging terms privately between the two partners. Microsoft's own MPO FAQ states this directly: "Multiparty private offers currently do not support the ability for software companies and channel partners to exchange partner-only terms for acceptance that don't get passed to the customer" (learn.microsoft.com/en-us/partner-center/marketplace-offers/multiparty-private-offers-faq, updated August 18, 2026). Partners discussing this in Microsoft's own Marketplace community forum have been pointed toward handling that exchange offline, outside the platform entirely, since there is no in-product path for it.

CSP private offers introduce a separate reporting blind spot. Software companies can filter CSP transactions in Marketplace Insights using Sales Channel = CSP, per Microsoft's own documentation. That filter is easy to miss if a partner is checking the default Marketplace reporting view out of habit. More than one partner has reported not being able to find a first CSP private-offer transaction as a result.

Resale Enabled Offers add a third kind of friction. Microsoft's own REO FAQ (learn.microsoft.com/en-us/partner-center/marketplace-offers/resale-enabled-offers-faq, updated May 26, 2026) answers two related questions with a flat no: the offer owner is not notified when a resale partner creates a private offer against their authorization, and cannot set wholesale pricing directly in Partner Center. An offer owner can still find completed transactions afterward in Marketplace Insights by using the Resale partner filter on the Revenue, Orders, and Usage dashboards. Pricing on those private offers stays hidden from the offer owner, and the sales are absent from the Earnings workspace, since Microsoft pays the resale partner directly rather than the offer owner.

Offline

Microsoft's own fix for exchanging MPO partner-only terms

Confirmed directly in Microsoft's own Multiparty Private Offers FAQ: the platform does not currently support exchanging terms between the two partners that stay private from the customer. The workaround is procedural, not a setting to enable.

Build that exchange into the deal timeline now, not after a customer is already waiting on it.

Why now, precisely

Marketplace investment is real. Be precise about which parts are confirmed.

Microsoft is not quiet about wanting more Marketplace volume. Mira Ayad, General Manager of Global Marketplace, wrote directly in "Built to grow together: The FY27 Microsoft Marketplace opportunity" on Microsoft's own Tech Community Partner Blog, published July 28, 2026. Marketplace sales, she wrote, have been "doubling year-over-year, for the third consecutive year." That is a Microsoft-published figure, not a partner estimate, and it is the clearest evidence that channel-led motions like REO and MPO are getting more Microsoft attention going into FY27, not less.

consecutive years of year-over-year Marketplace sales doubling, stated directly by Mira Ayad, Microsoft's General Manager of Global Marketplace, Tech Community Partner Blog, published July 28, 2026.

A separate figure, a 200% increase in Microsoft's own investment to power Marketplace sales, has circulated since a Microsoft speaker cited it at an August 2026 industry event. The only outlets IMS has found reporting it, Dutch IT Channel and MSP Business, share the same parent publisher (DutchIT.com), which is one source network, not independent corroboration. IMS has not found that figure published on any Microsoft-owned page. Treat it as reported, not confirmed, until Microsoft publishes it directly, and do not repeat it as a sourced Microsoft statistic in a board deck.

One more claim is worth naming specifically because it is the kind of thing that spreads fast: Mason McCoy, Director of Marketplace Strategy at Microsoft, was reported at that same event saying Resale Enabled Offers recently generated more global revenue than Multiparty Private Offers for the first time, roughly six months after REO's own launch. That claim traces to the same two same-publisher articles as the 200% figure above. Naming a real Microsoft speaker is better sourcing than an anonymous claim, but it is still a third-party paraphrase, not a Microsoft-published statement. It may well be true. It is not yet something a partner should cite as an established Microsoft fact.

Which one fits your deal

A practical way to choose, not a coin flip

REO fits when

You want repeatable channel expansion across markets without renegotiating each deal, your offer is SaaS, VM software reservation, or Dragon Copilot, and you are comfortable authorizing partners offer by offer and market by market.
Signal: "We need a channel motion that scales."

MPO fits when

You have one specific enterprise deal, a channel partner already in the room, and the deal needs to count cleanly toward Azure IP Co-Sell eligibility and the customer's Microsoft Azure Consumption Commitment (MACC).
Signal: "This deal needs to hit Azure IP Co-Sell mechanics cleanly."

CSP fits when

The customer is SMB-sized, already buying through a CSP Indirect Provider or Direct Bill partner, and the deal does not need to touch Azure IP Co-Sell mechanics at all.
Signal: "This is an SMB CSP customer, stay inside the CSP program."

Most partners eventually use more than one. That reflects the three motions mapping to different deal shapes, a structural fact about the deals themselves that holds at every stage of program maturity. Choosing the wrong one for a specific deal usually means rework, because the eligibility and reporting mechanics only reveal themselves once a partner is already inside the configuration flow.

Before you configure one

Six things to confirm before your first offer goes live

Lock in the offer type

Once you select an offer type (SaaS, Azure Application, Azure Virtual Machine, Azure Container, Managed Service, and the rest), it locks at creation, per Microsoft's publishing guide by offer type. Switching types means creating a new offer. Get this decision right before configuration starts.

Confirm geography

Check current country eligibility directly in Partner Center before quoting a customer, not from a cached Learn page. Section 1 of this brief is itself proof that Microsoft's own pages can disagree for months at a time.

Plan the exchange

If the deal needs partner-only terms inside an MPO, plan for an offline exchange between the two partner companies now. The platform does not support exchanging those terms in-product, and Microsoft's own FAQ confirms that limitation directly.

Check the seller type

Confirm whether your channel partner is a CSP Direct Bill Partner, Indirect Provider, or Indirect Reseller before assuming CSP private offers apply. Indirect Resellers are excluded outright; the margin has to route through the Indirect Provider.

Verify MACC impact

REO and MPO count toward a customer's Microsoft Azure Consumption Commitment (MACC) when the offer is Azure IP Co-Sell Eligible; CSP does not. In FY27, co-sell credit for Marketplace transactions is recognized through Marketplace Billed Sales (MBS), which measures activity, not eligibility itself.

Watch your reporting

CSP private-offer transactions live in Marketplace Insights under the Sales Channel = CSP filter, not the default reporting view most partners check out of habit. Confirm you know where to look before assuming a completed deal failed to report.

Not sure which Marketplace motion your current posture even supports?

The IMS CRI scores Marketplace Transactability as one of six co-sell readiness dimensions in about ten minutes, no email required to see your score.

Measure your readiness

Microsoft will eventually reconcile its own Marketplace pages. Partners who need the answer before that happens are better served reading the current documentation closely than waiting for a banner that says which version to trust.

Published FY27 (August 2026), current as of September 2026. REO, MPO, and CSP mechanics are cited directly to Microsoft Learn pages rechecked September 23, 2026 (see Section 1) and are subject to change; Microsoft's own pages currently disagree on MPO country eligibility. FY27 investment figures are sourced to Microsoft's own July 28, 2026 Tech Community post where directly stated; figures not attributed to a Microsoft-owned source are marked accordingly. This brief cites public Microsoft Learn documentation, not an authenticated Partner Center session. Verify current mechanics in your own Partner Center account before making deal-structure decisions.