Microsoft launched a reimagined Microsoft Marketplace on September 25, bringing the previously separate Azure Marketplace and AppSource storefronts into one catalogue for cloud software, AI applications and agents. It is live in the United States and rolling out to other markets.
If you already sell on AWS Marketplace, the commercial logic will feel familiar and most of the implementation will not. Here is what differs.
What the merge actually changed
For buyers, a single place to look instead of two. For publishers, less than you might expect in the short term — publishing still runs through Partner Center, and your existing offers carried over.
The change is not purely cosmetic though. Microsoft updated its Publisher Agreement to version 8.0, with Section 12(m) redefining “Microsoft Marketplace” to cover Microsoft-owned storefronts and any Microsoft endpoints pointing at them. The updated terms took effect automatically at the end of September with no signature required from partners. Worth having your legal team read the definition rather than assuming it matches the old scope.
The practical effect of a single catalogue is on discovery. The old split meant an infrastructure product and a business application were found by different audiences in different places. Now they compete for attention in the same catalogue, which puts more weight on listing content.
Publishing differs from AWS
Partner Center, not a marketplace-specific portal. If you are used to the AWS Marketplace Management Portal, Partner Center covers considerably more ground — it is also where CSP, co-sell and payout profiles live. Expect to spend time working out which section governs what.
Offer types matter more than on AWS. Which offer type your product belongs in affects how it can be transacted and how it is found. Getting this wrong is recoverable but tedious.
Transactable versus list-only. This is the distinction with real consequences. A list-only offer is a brochure; a transactable offer puts Microsoft in the billing path. Only transactable offers produce the commercial effects you want — committed spend drawdown and co-sell credit. An ISV who publishes list-only and expects marketplace revenue has built a directory entry.
Fulfillment: the activation step AWS does not have
On AWS, you resolve a registration token and provision. Microsoft adds a second call.
The flow is: buyer lands on a landing page you host with a token, you resolve the token to get the subscription details, and then you must explicitly activate the subscription by calling back to Microsoft.
Resolution and activation are separate operations. Forgetting the activation call leaves subscriptions sitting in a pending state — the customer has paid, your system may have provisioned them, and Microsoft does not consider the subscription started. This is the single most common integration bug on the Microsoft side and it does not announce itself.
Everything else in the three-cloud comparison still applies: separate seller registration, separate metering API, separate reporting.
Channel is structurally different, and your finance team will notice
If you sell through resellers, this is the biggest divergence from AWS.
With a multiparty private offer, Microsoft collects payment from the customer and pays the channel partner directly. The channel partner then pays you outside the marketplace, under your agreement with them.
Compare AWS, where the channel partner creates the offer and holds the customer contract, and your money arrives as a marketplace disbursement.
So the same commercial arrangement produces a different accounting artifact: a marketplace disbursement on AWS, a partner receivable on Microsoft. If you run channel on both clouds you maintain two reconciliation paths for what your sales team considers one motion. We went through the mechanics in CPPO explained.
There is also a separate CSP private offer route for selling through a customer’s Cloud Solution Provider, which is worth understanding if your customers buy their Microsoft estate through a partner — many mid-market ones do.
Fees and incentives
Microsoft has been actively using fee levers to shape behaviour. The notable one: the agency fee on renewals sold as private offers was halved effective October 1, 2024, applied when you claim either an existing marketplace agreement or an off-marketplace sale as a renewal in Partner Center.
That last clause is easy to miss and is money. An off-marketplace renewal you bring onto the marketplace can qualify. If you have a book of business renewing outside the marketplace, there is a reason to look at moving it.
Professional services can also be sold through private offers, which opened up for partners in Canada, the UK and the US last year — relevant if you bundle implementation with software.
Committed spend works the same way
The core argument for being on a marketplace does not change by cloud. Enterprise Microsoft customers hold spend commitments, purchases through the marketplace draw down against them, and that turns a budget conversation into a procurement conversation. The same committed spend and quota credit mechanics that make AWS Marketplace worth doing apply here.
If you are adding Microsoft to an existing AWS listing
A realistic sequence:
- Confirm the offer type and commit to transactable
- Build the landing page, token resolution and activation
- Implement metering against Microsoft’s API — do not assume your AWS metering code ports
- Decide your channel model deliberately, knowing the money arrives differently
- Plan reconciliation for two disbursement shapes before revenue starts arriving
Launch covers going live on a new marketplace end to end, and the Microsoft cloud page sets out what CloudX handles.
The summary
One storefront for buyers, Partner Center unchanged for publishers, a new Publisher Agreement definition worth reading, an activation call that AWS does not require, and a channel model that pays you through the partner instead of through the marketplace. Budget for a real second integration rather than a port.