A marketplace EULA is the end user license agreement that governs how a buyer may use your product once they transact. Every marketplace offers a standard one, every marketplace lets you supply your own, and the choice you make sets your legal review time for years. This is not legal advice — it is the mechanics your counsel will need before they can give you any.
The first private offer is where most teams discover they have a contract problem. Procurement asks which terms apply. Someone forwards the master services agreement from the website. The buyer’s counsel points out that the marketplace transaction is not covered by it. Two weeks disappear.
None of that is a legal disagreement. It is an unmade decision about which paper governs a marketplace deal, made under time pressure by whoever is nearest.
What is a marketplace EULA?
A marketplace EULA is the agreement between you and the buyer that governs use of your product, referenced by the listing and accepted at purchase. The marketplace facilitates the transaction; it is not a party to that agreement. AWS states the position bluntly in its own documentation: “The EULA is between you and the buyer.”
That single sentence explains most of the mechanics that follow. Because the cloud is not a party, it cannot negotiate on your behalf, cannot waive your terms, and cannot resolve a dispute about them. What it can do is offer a template that most buyers have already accepted — which is where standard contracts come from.
Every seller therefore picks one of three paths:
| Path | What it is | Best when |
|---|---|---|
| Standard contract | The marketplace’s own template, pre-vetted by many buyers | Self-service and mid-market deals where speed matters more than bespoke terms |
| Standard contract + amendments | The template, plus your changes layered on | You need a handful of specific carve-outs, not a rewrite |
| Your own EULA | Your paper, hosted by you | Regulated products, unusual liability profiles, or terms you cannot express as an amendment |
How each cloud implements it
AWS
AWS gives sellers three named options: your own EULA, the Standard Contract for AWS Marketplace (SCMP), or the Reseller Contract for AWS Marketplace (RCMP) for channel deals. Two mechanics set it apart from the other clouds. Its standard contract is amendable on private offers, so a negotiated deal starts from the template rather than from a blank page. And the choice is reversible: you can leave the SCMP program at any time by replacing the template with your own EULA. The addendums, what opting in commits you to, and a deal-by-deal routing table are in the AWS standard contract, or your own paper?
Microsoft
Microsoft offers a Standard Contract for Microsoft Marketplace that “customers only need to vet and accept one time,” and supports it across Azure Applications, Azure Containers, Container Apps, Virtual Machines, SaaS and the AI Apps and Agents category.
Its amendment model is the most structured of the three, and the most useful to understand:
- Universal amendments apply to every customer of the offer and appear in every purchase flow.
- Custom amendments are targeted at specific customers by Azure tenant ID. Only customers in that tenant see them.
- The two stack: a targeted customer gets the universal amendment as well as their own.
Two hard limits: amendments are capped at 4,000 characters including spaces, and you can add universal terms plus up to 10 custom amendments.
And one rule that is genuinely irreversible: “Once you publish an offer using the Standard Contract for Microsoft Marketplace, you won’t be able to use your own custom terms and conditions. You either offer your solution under the Standard Contract or your own terms and conditions.” There is no migrating later.
Google Cloud
Google Cloud Marketplace follows the same shape — a standard set of terms for self-service purchases, with negotiated terms attaching to private offers. Confirm the current requirements in Google’s own producer documentation before you commit a listing to either path, because the terms structure is the part of a marketplace that changes least loudly.
What custom terms actually cost you
Not the drafting. The drafting is a week of counsel’s time and then it is done. The recurring costs are the ones that show up in the pipeline:
Every buyer reviews from scratch. A standard contract has already passed through the legal team of many of your prospects. Your paper has not. That is a review cycle per deal, and the review sits between the verbal yes and the revenue.
Self-service stops working. A buyer who has to route your EULA through counsel is not clicking subscribe. If any part of your motion is meant to be self-service, custom terms remove it.
Amendments outlive the people who wrote them. Three years in, nobody remembers why clause 7 was struck for one customer, and the renewal has to reconstruct it. This is an argument for expressing changes as amendments to a known base rather than as a bespoke document per deal — the diff stays visible.
The channel multiplies it. Reseller deals mean your terms have to flow through a partner to an end customer, which adds a second contract between you and the partner on top of the one the buyer accepts.
A workable default
For most ISVs, the shape that holds up is:
- Standard contract on the public listing. Self-service stays self-service.
- Standard contract plus amendments for mid-market private offers. Small, named deltas rather than a different document.
- Your own paper only where a real obligation requires it — a regulated data commitment, an unusual indemnity, a term the amendment mechanism genuinely cannot express.
- A decision rule written down, so a deal desk owner knows which path a deal takes without escalating to counsel. That rule is what turns a two-week question into a two-minute one.
Signature mechanics are a separate question from which paper governs — when you need a signature on legal documents in cloud marketplace deals covers what marketplace acceptance does and does not replace.
Frequently asked questions
What is a EULA on a cloud marketplace? The end user license agreement between you and the buyer, referenced by your listing and accepted at purchase. The marketplace facilitates the transaction but is not a party to the agreement.
Can I use my own terms instead of the marketplace standard contract? Yes, on every major marketplace. On Microsoft the choice is one-way: once an offer is published under the Standard Contract, you can’t switch to your own terms and conditions.
How many amendments can I add to Microsoft’s standard contract? Universal amendment terms plus up to 10 custom amendments targeted by Azure tenant ID. Each amendment is limited to 4,000 characters including spaces.
Can standard contract terms be changed for one customer? Yes. On AWS, the SCMP can be amended on a private offer as agreed by the parties. On Microsoft, a custom amendment targeted by Azure tenant ID applies only to that customer.
What is the difference between universal and custom amendments on Microsoft? Universal amendments apply to every customer of the offer. Custom amendments apply only to the Azure tenants you target, and a targeted customer gets the universal amendment as well as their own.
Takeaways
- The EULA is between you and the buyer. The marketplace facilitates the transaction and is not a party to the agreement.
- Three paths exist everywhere: the standard contract, the standard contract with amendments, or your own paper.
- AWS’s standard contract is amendable on private offers and, unlike Microsoft’s, reversible: you can replace it with your own EULA later.
- Microsoft’s amendments are structured — universal for everyone, custom by tenant ID, stacking, capped at 4,000 characters, up to 10 custom.
- Microsoft’s choice is one-way. Publish under the Standard Contract and you cannot later use your own terms for that offer.
- The cost of custom terms is not drafting. It is a legal review per deal, and the loss of any self-service motion.
Terms are only half the problem; keeping track of which version a given customer accepted is the other half. See how Fours’ agreement management holds the offer, the accepted terms and the resulting contract as one record across every marketplace you sell on.
Sources
Primary sources for the platform rules cited above. Last verified August 12, 2026. Cloud providers change fees, eligibility, and program terms without notice — check the source before relying on a figure.
- AWS Marketplace Seller Guide: Using standardized contracts in AWS Marketplace — The three EULA options, the amendment path on private offers, and withdrawal from the SCMP program
- Microsoft Learn: Standard Contract for Microsoft Marketplace — Universal vs custom amendments, the 4,000-character limit, the eligible offer types, and the one-way rule after publishing
- Microsoft Learn: Plan a SaaS offer for Microsoft Marketplace — The limit of up to 10 custom amendments and the either/or framing of standard contract vs own terms
Keep reading
Stay Updated
New posts, product updates and marketplace strategy are shared on LinkedIn as they publish.
Follow Fours on LinkedIn