Table of Contents
The Cloud Marketplace Landscape
AWS Marketplace, Azure Marketplace, and Google Cloud Marketplace have evolved from niche developer tools catalogs into enterprise software procurement channels moving billions of dollars in annual transactions. AWS Marketplace alone listed over 12,000 products as of 2025, with enterprise software from virtually every major ISV available for direct subscription.
The appeal is real: single billing consolidation, faster procurement bypassing traditional vendor negotiations, potential EDP/MACC commitment counting, and simplified vendor management. But the speed of marketplace purchasing has outpaced enterprise procurement governance in many organizations — creating contract risk that compounds over time.
The core problem: marketplace purchases bind you to ISV terms, not your standard enterprise contract terms. The click-through EULA you accept during a marketplace subscription often contains materially worse terms than you'd obtain through direct negotiation — on pricing flexibility, SLAs, data rights, IP ownership, and termination provisions.
How Marketplace Contracts Actually Work
Understanding the contractual structure of marketplace purchases is the first step to managing the risk. There are three distinct legal relationships in any cloud marketplace transaction:
1. The Cloud Provider Agreement
Your existing cloud provider agreement (AWS Customer Agreement, Microsoft Online Services Agreement, or Google Cloud Platform Terms of Service) governs your relationship with the cloud provider — not the software you're purchasing. The cloud provider acts as a billing and distribution intermediary. Their obligations to you under a marketplace purchase are limited to infrastructure availability and payment processing.
2. The ISV EULA / Software Terms
When you subscribe to a marketplace product, you agree to the ISV's end-user license agreement and service terms. These are set unilaterally by the ISV, published on their marketplace listing, and are typically not negotiable through the marketplace channel. This is where most enterprise contract risk lives.
3. The Marketplace Listing Agreement
The marketplace listing agreement between the cloud provider and the ISV governs what the ISV is permitted to offer and how billing works. Buyers are not party to this agreement but are affected by its terms (e.g., what refund rights apply, how subscription changes work).
EULA and Terms of Service Risks
The EULA risks in cloud marketplace purchases are specific and predictable. They appear consistently across ISV categories.
Data Processing and Privacy
ISV data processing agreements (DPAs) on marketplace listings are frequently generic and may not satisfy your GDPR, CCPA, or sector-specific compliance requirements (HIPAA, FedRAMP, SOC 2). Marketplace convenience does not mean compliance coverage. Before subscribing to any product that will process personal data or regulated information, obtain and review the ISV's DPA separately from the marketplace listing — and verify it meets your compliance requirements.
IP Ownership for AI-Adjacent Products
For AI, machine learning, and analytics products, EULA terms on data rights and output ownership vary dramatically and are frequently drafted in the ISV's favour. Terms that allow the ISV to use your data to train their models, retain anonymized copies of your outputs, or claim ownership over derivative works may be embedded in marketplace EULAs without being obvious. These terms require explicit legal review and are often negotiable only through a private offer or direct agreement.
Pricing Stability
Standard marketplace subscription terms typically allow ISVs to change pricing with 30-60 days' notice — sometimes less. Unlike negotiated multi-year enterprise agreements with price lock provisions, marketplace subscriptions may expose you to unilateral price increases that your procurement process cannot efficiently respond to. For material software spend, pricing stability provisions require a private offer or direct agreement.
Termination and Minimum Commitments
Annual marketplace subscriptions typically auto-renew with limited cancellation windows. Quarterly subscriptions may have termination restrictions that effectively create de facto annual commitments. Review termination notice periods, cancellation windows, and auto-renewal terms before subscribing — particularly for products with user count or consumption-based pricing that can escalate during the term.
The Support Gap Problem
Support responsibility in cloud marketplace transactions creates what we call the "two-vendor problem" — a structural gap that appears when issues span the infrastructure layer (cloud provider) and the application layer (ISV).
| Issue Type | Cloud Provider Responsibility | ISV Responsibility |
|---|---|---|
| Infrastructure outage | Yes — availability SLA applies | No (unless affects their application) |
| Application bug | No | Yes — ISV support applies |
| Performance degradation | Partial — if infrastructure-related | Partial — if application-related |
| Data access issues | Partial — storage/network | Partial — application authentication |
| Integration failures | Rarely | Primarily |
The danger zone is the overlap: performance issues, data access problems, and integration failures that could involve both providers. When these occur, the cloud provider points to the ISV ("our infrastructure is functioning normally") and the ISV points to the cloud provider ("our application is running correctly, this is an infrastructure issue"). You're left managing the escalation between two vendors while your production system is degraded.
Before any material marketplace purchase, define in writing: who handles initial triage for cross-layer issues, what the maximum escalation response time is, and who owns the issue until resolution regardless of root cause. The ISV is your primary contact for this — the cloud provider will not accept responsibility for cross-vendor support gaps.
EDP and MACC Counting Rules
One of the primary commercial drivers of marketplace purchasing is the potential to count transactions toward EDP (AWS Enterprise Discount Program) or MACC (Microsoft Azure Committed Consumption) commitments. The rules are nuanced and frequently misunderstood.
AWS Marketplace and EDP
AWS Marketplace transactions may count toward EDP eligible consumption, but the rules are product-type specific. Generally, ISV software charges that flow through AWS Marketplace billing count toward EDP spending thresholds. However, there are important caveats:
- Marketplace transactions count at the marketplace price, not any separately negotiated price. If you have a direct agreement with the ISV at a 30% discount and then purchase through marketplace at list price to count toward EDP, you may be paying more for the discount credit than the EDP discount is worth.
- Some marketplace product categories are explicitly excluded from EDP counting — including certain professional services, data products, and Government marketplace offerings.
- EDP discounts do not automatically apply to marketplace charges unless your EDP agreement explicitly states they do. Many EDP agreements exclude third-party marketplace transactions from discounted pricing.
Azure Marketplace and MACC
Azure Marketplace transactions count toward MACC commitments for "Azure Benefit Eligible" products — a designation ISVs must apply for. Not all marketplace products are eligible. Verify eligibility at the product listing level before assuming marketplace purchases accelerate your MACC drawdown.
Direct vs. Marketplace: Decision Framework
The right purchasing channel depends on the specific software, spend level, and your commercial priorities. Use this framework to guide the decision:
| Factor | Favours Direct Purchase | Favours Marketplace |
|---|---|---|
| Annual spend | $100K+ | Sub-$50K |
| Contract terms importance | Data-sensitive, regulated industry | Standard commercial use |
| SLA requirements | Custom SLA required | Standard ISV SLA acceptable |
| Pricing stability needs | Multi-year price lock required | Annual pricing acceptable |
| EDP/MACC situation | Already meeting commitment thresholds | Need to accelerate commitment drawdown |
| Procurement speed | Standard enterprise process acceptable | Urgent deployment timeline |
Marketplace Private Offers: The Hybrid Option
Many enterprises are unaware that cloud marketplaces support "private offers" — custom pricing and terms that combine marketplace billing convenience with negotiated commercial terms. Private offers are available on AWS Marketplace, Azure Marketplace, and GCP Marketplace for qualifying ISVs and buyers.
A private offer allows the ISV to extend custom pricing, custom contract terms (including modifications to the standard EULA), custom support terms, and multi-year pricing structures through the marketplace billing channel. For the buyer, this means: the convenience of marketplace billing (single invoice, EDP/MACC counting where eligible) combined with negotiated commercial terms.
Private offers are available for transactions above the ISV's threshold — typically $100K+ annually. Initiate the private offer discussion directly with the ISV's sales team: "We want to purchase through marketplace for billing consolidation purposes, but require custom terms. Can you create a private offer?" If the ISV declines, this signals either low spend threshold or a limitation in their marketplace agreement that you should understand before proceeding.
Enterprise Marketplace Governance
As marketplace purchasing scales within organizations, governance becomes critical. Without governance controls, individual teams may subscribe to hundreds of marketplace products — accumulating contract obligations, data processing agreements, and support relationships that legal and procurement teams have never reviewed.
- Define marketplace purchasing authority: Establish spend thresholds above which marketplace purchases require procurement review. A common framework: under $10K/year individual approval, $10K–$100K procurement review, above $100K legal review required.
- Build an approved vendor catalog: Maintain a pre-approved list of marketplace vendors for whom standard EULA review has been completed. Teams can purchase from the catalog without additional review. New vendors require review before first purchase.
- Implement marketplace spend visibility: Use cloud cost management tools (AWS Cost Explorer, Azure Cost Management) to tag and track all marketplace spend separately from native cloud consumption. Without visibility, marketplace spend frequently becomes an unmanaged long tail.
- Audit marketplace subscriptions annually: Run a quarterly or annual audit of all active marketplace subscriptions. Inactive or underused subscriptions should be cancelled — most marketplace agreements allow cancellation with 30-60 days' notice. Unused subscriptions are pure cost with no benefit.
- Negotiate private offers proactively: For any ISV spend that reaches $100K+ annually through marketplace channels, proactively initiate a private offer discussion to obtain better terms. The ISV has incentive to offer it — marketplace private offers count toward their AWS/Azure/GCP partnership incentives.