Priya, the procurement lead at a freight company, can buy the same contract-review agent on AWS Marketplace, Microsoft Marketplace, and Google Cloud Marketplace this quarter. Microsoft publishes the clearest rule for counting that purchase against a cloud spending commitment, 100% with no cap, and its own marketplace website also offers a checkout button that counts nothing toward the commitment.
Her brief has three lines. Legal wants a third-party contract-review agent in front of 400 employees by March. The data team wants a data-quality tool that runs inside the company's own AWS account. Finance wants both purchases to count toward a cloud spending commitment, the minimum spend a company promises a cloud provider in exchange for discounts. The company holds commitments with all three clouds and is behind on its AWS and Microsoft ones, so the counting rule decides real money. Both vendors list on all three marketplaces. A January 2026 Omdia report sponsored by Red Hat names commitment burndown first among the reasons enterprises buy through these marketplaces, and projects marketplace spend growing from $45.5 billion in 2025 to $163.1 billion by 2030.
Her trade-off: the clearest counting rule and the right front door may sit on different clouds.
Marketplaces are the buying layer of a larger map of AI and data services across the three clouds, and companion posts cover agent platforms, agent identity, and models.
Three marketplaces, side by side
Status as of November 18, 2026.
| AWS Marketplace | Microsoft Marketplace | Google Cloud Marketplace | |
|---|---|---|---|
| Published commit rule | No percentage; products deployed on AWS "typically qualify" | 100% of the pretax amount for eligible offers bought through the Azure portal | No percentage for direct purchases; channel purchases 100% up to a 25% cap |
| Private-offer fee, new deals (paid by the vendor) | 3% under $1M, 2% to $10M, 1.5% at $10M+ | 3% | 3% under $1M, 2% to $10M, 1.5% at $10M+ |
| Renewal fee | 1.5% on all renewals | Half the fee on renewal private offers | 1.5% on qualifying renewals and migrations |
| Where a bought agent lands | AgentCore Runtime or AgentCore Gateway | Microsoft 365 admin center, then Copilot | Gemini Enterprise (preview) |
| Admin catalog control | Per organization, OU, or account; doesn't block existing subscriptions | Per tenant; all Microsoft solutions added by default | Per organization; fails open |
What counts toward the commit
Think of the commitment as a cafeteria meal plan the company promised to spend down, where some outside vendors in the food court accept the plan card. Each cloud labels those vendors differently and says different things about how much of the bill the card covers. The analogy breaks at the end of the term: an unspent meal-plan balance is money already paid, while a commitment shortfall is money the company still owes.
Microsoft writes the rule out in full, exceptions included. Its commitment benefit page says that for Azure benefit-eligible offers, "100% of the pretax purchase amount also contributes toward your commitment," and the buyer page says "with no limits." The same benefit page lists what falls outside. Card purchases made directly on the Microsoft Marketplace website "do not contribute" even though the listing shows the eligibility badge, purchases paid with Azure prepayment are not eligible, and licenses deployed in a hybrid environment or on-premises don't count. Timing matters too: per the commitment FAQ, purchases made before the commitment starts or before an offer became eligible don't count retroactively, and that future installment payments don't count when the purchase falls in the term's last month. Offers bought through a cloud solution provider reseller don't decrement the commitment.
AWS publishes no percentage. Since May 2025, AWS Marketplace accepts SaaS products hosted anywhere, and a "Deployed on AWS" badge marks those running 100% on AWS infrastructure, which "may qualify for additional AWS customer benefits." The buyer FAQ says "Products deployed on AWS typically qualify. Eligibility is determined separately for each product."
Google publishes a number only for channel purchases. Its marketplace page says "Qualifying purchases of third-party Google Cloud Marketplace solutions can draw down on your Google Cloud commitments." A May 15, 2025 partner post announced that starting June 9, 2025, purchases through reseller private offers apply "the full qualifying amount of the private offer (up to an allowable 25% cap)" to the commitment.
That leaves Priya with a different question for each account team. Microsoft has already answered on a public page, exclusions and all, so she needs only two things: an offer that is eligible today and an order placed through the Azure portal. On AWS, the answer turns on whether the product is deployed on AWS and on what her own agreement says. Google's turns on whether the purchase qualifies, plus the 25% cap if a reseller sells it.
What the fee schedule tells a buyer
The vendor pays the marketplace fee, and Priya never sees it on an invoice. My read is that it still shapes the private offer she negotiates, a custom price and term the vendor extends to one buyer.
AWS's listing fees and Google's revenue share schedule use identical bands for new private offers. They part at renewal: AWS charges 1.5% on all renewals, while Google's 1.5% applies only to renewals, migrations, and replacement deals that the vendor flags and that meet the schedule's definitions. Microsoft charges a flat 3% store service fee and halves it on renewal private offers.
AWS diverges in two more places. It charges 20% on public offers for server products (machine images, containers, and ML models a buyer runs in their own account) and adds a 0.5% uplift when a channel partner resells the offer. Priya's data-quality tool ships as a container that runs in her own account, so a public listing for it carries the 20% rate. My inference: that gap gives the vendor a reason to move her to a private offer at 3% or less, and her negotiation should start there.
Where the agent lands
The anchor post argues that each cloud converts anything foreign into one of its own systems. A bought agent is foreign, so the marketplace delivers it into whatever system its cloud is anchored on.
AWS sends the bought agent to the developer platform. The AI Agents and Tools category, launched in July 2025, lets buyers deploy through Amazon Bedrock AgentCore Runtime or add tools to AgentCore Gateway, with filters for MCP and A2A support. Since October 2025, remote MCP servers can be Gateway targets. Products deployable on Runtime launch only in US East (N. Virginia). Employees reach agents through AWS Quick, which since August can use agents and MCP servers from AWS Agent Registry and runs inside Teams and Outlook through extensions. AWS documents no step that takes a Marketplace purchase straight into AWS Quick, so a developer registers the agent in between.
Microsoft's destination is the productivity suite. Its launch post says AI apps and agents are available "directly on Marketplace and in Microsoft products — from Azure AI Foundry to Microsoft 365 Copilot", provisioned through standards like MCP. The Agent 365 overview bounds that path: "At launch, a set of partner agents are available to deploy directly from the Microsoft 365 admin center," and Agent 365 "works best when using Microsoft E5 as a pre-requisite." Agent 365 needs at least one licensed user to turn on, at $15 per user per month, paid yearly. Employees find agents on the Plugins page in Microsoft Copilot, which requires "A Microsoft Copilot license assigned to your organization."
On Google, the agent goes to the employee app. An admin holding the Gemini Enterprise Admin role can add a marketplace A2A agent to Gemini Enterprise, where users reach it in the Agent Gallery. That feature is in preview, and the page warns that Gemini Enterprise's console Model Armor settings "don't automatically protect agents registered through Cloud Marketplace"; the vendor has to call Model Armor from the agent's code. Google's listing rules for "AI Agents as a Service" require an A2A Agent Card, agents that run on Google Cloud, and Model Garden models as the default configuration.
The same split runs one layer down: each cloud sells Claude and OpenAI models under a different contract shape, which the models post traces.
Priya's choice
Her 400 users work in Outlook and Teams, so what separates the three paths is the number of steps between purchase and those users. Microsoft's is shortest: a partner agent in the launch set deploys from the admin center to users who hold Copilot licenses. AWS adds a developer, who deploys the agent to AgentCore and registers it before users reach it through AWS Quick's Teams and Outlook extensions. Google's path ends in Gemini Enterprise, an app the company has not rolled out.
My recommendation, built from the documented rules:
- Put both vendors in each private marketplace first, knowing each control's limit. AWS's Private Marketplace "will not block usage from these existing subscriptions" and "does not control what can be deployed in AWS accounts." Microsoft's private Marketplace adds "All Microsoft solutions and Endorsed Linux distributions" by default. Google's Private Marketplace uses a "fail open governance model" and cannot revoke an approval once granted for a procurable Vertex AI model.
- Buy the contract-review agent through Microsoft Marketplace, in the Azure portal, if the vendor's agent is in the admin-center launch set and the offer is Azure benefit-eligible. That draws down the Microsoft commitment at 100% and puts the agent where her users work. If either condition fails, the AWS path is next, and it draws down the AWS commitment only if her agreement confirms the product counts.
- Buy the data-quality tool through AWS as a private offer, which avoids the 20% public rate, and get written confirmation that it counts toward the AWS commitment.
- Collect security-review evidence on each marketplace. AWS Vendor Insights ends after November 26, 2026, with a replacement listed as "coming soon." Google's featured partner agents carry a "Google Cloud Ready - Gemini Enterprise" designation after a four-step evaluation. Microsoft's Agent Store guide tells admins to check each agent's "publisher attestation or certification status" in the admin center.
Google stays out of this purchase because Priya's company is not behind on that commitment and has no Gemini Enterprise rollout. A company anchored on Gemini Enterprise would read the same table the other way.
Where this stops
- The commit rules here are the public ones. Each company's own agreement can override them, and those agreements are private.
- The Omdia projection is a sponsored third-party report.
- Fees are what the vendor pays; whether a given vendor passes them into price is my inference.
- Gemini Enterprise's marketplace agents are in preview, AWS has not described the Vendor Insights replacement, Microsoft Ignite is running this week, and AWS re:Invent starts November 30, so rows on all three will change.
So what
If you are buying third-party agents through a cloud marketplace, pick the marketplace by where the agent will land, then confirm the counting rule for that product before you sign. New private-offer fees differ by at most 1.5 points; the commit rule and the front door differ by much more.
The question I have not answered: what happens when the buyer is an agent? None of the three documents an agent finishing a purchase today. AWS's agent mode stops at purchase proposals and private-offer requests, and Google's AP2 announcement names marketplace procurement only as an example use. When Priya's own procurement agent can accept a private offer, I don't know whose marketplace rules will govern it, or whether the commit drawdown follows the agent or the account it buys from.
Top comments (0)