Negotiating Cloud EDP and MACC: The Enterprise Commercial Guide

Enterprise Discount Programs (EDP) with AWS and Azure Consumption Commitments (MACC) represent the commercial negotiation layer above published cloud pricing — and they are where the largest additional savings are available for enterprises with significant cloud spend. For a $10M annual AWS estate, the difference between a poorly negotiated EDP and one structured with benchmark data and competitive leverage is typically $500K–$2M per year. Yet most enterprise procurement teams approach these negotiations without the vendor-side intelligence that would enable them to capture full value. This guide is part of our enterprise cloud cost optimisation framework.

EDP and MACC: The Commercial Layer Above List Pricing

Published cloud pricing — including Reserved Instance and Savings Plan rates — represents the self-service pricing tier. It is available to any customer with a credit card and represents the ceiling of what hyperscalers intend large enterprises to pay. Enterprise Discount Programs (AWS EDP), Azure Consumption Commitments (MACC), and GCP private pricing agreements are negotiated instruments that sit below this ceiling, available to enterprises that engage the hyperscaler's commercial organisation with a meaningful spend commitment.

These agreements are not uniformly structured or uniformly discounted. Each is individually negotiated, and the outcome is heavily influenced by deal size, enterprise leverage, competitive context, and the quality of the negotiation process. Two enterprises of comparable size can receive materially different discount levels from the same hyperscaler in the same quarter — the difference is almost always in the negotiation approach rather than in objective factors like spend level.

Who Qualifies

AWS EDP is generally available to enterprises committing to a minimum of $1M in annual AWS spend (though the threshold varies by deal context and growth trajectory). Azure MACC has no formally published minimum but is practically most relevant for enterprises with $500K+ in annual Azure consumption. GCP private pricing agreements become relevant above approximately $1M in annual GCP spend. Enterprises below these thresholds can still negotiate improved pricing through volume discount discussions or through a reseller channel, but the EDP/MACC structure is primarily designed for enterprise-scale engagements.

AWS Enterprise Discount Program (EDP) Deep Dive

The AWS Enterprise Discount Program is a private pricing agreement between AWS and an enterprise customer that provides a negotiated percentage discount across AWS services in exchange for a committed annual spend over a defined term. Key structural elements of an EDP are: the commitment amount (annual spend commitment), the discount percentage (applied against list/on-demand rates), the term (typically 1–3 years), and the scope (which services and accounts are covered).

How EDP Discounts Work

EDP discounts are applied as a percentage reduction against the on-demand list rate for covered services. If an enterprise has an EDP with a 12% discount, their effective on-demand rates for covered services are 12% below published rates. This discount stacks with Reserved Instance and Savings Plan discounts — the RI or SP discount is applied first, and the EDP discount applies to the committed usage charges generated by the RI/SP. This stacking creates substantial compounding benefit: a 66% Savings Plan discount combined with a 12% EDP discount produces an effective 70.1% discount versus on-demand ((1-0.66)*(1-0.12) = 0.299 → 70.1% off).

EDP Negotiation Variables

The negotiable elements of an AWS EDP extend well beyond the headline discount percentage. Enterprises that focus solely on the discount rate and accept AWS's standard terms on other dimensions systematically leave value on the table. Key negotiation variables include:

• Discount tiers by service: EDP discounts can be differentiated by service (higher discounts on Compute, lower on database services, different rates for Marketplace purchases). Structuring service-specific discounts based on your usage mix can yield superior economics versus a flat rate.
• Drawdown flexibility: How the committed spend can be consumed across quarters and years — whether underage in one quarter can be made up in a subsequent quarter, and whether commitment consumption is tracked at the billing account level or the consolidated organisation level.
• Growth commitments vs. fixed commitments: AWS EDPs can be structured with escalating annual commitment levels (year 1: $5M, year 2: $6M, year 3: $7M) — which often unlock higher discounts in exchange for the growth commitment. Whether this structure makes sense depends on the confidence of the enterprise's cloud growth forecast.
• Marketplace inclusion: Whether software purchased through AWS Marketplace counts against EDP commitment consumption. For enterprises that purchase significant third-party software through Marketplace, this can significantly affect the achievability of the commitment.
• Underage penalties: What happens if the enterprise does not meet the committed annual spend. Standard AWS EDP terms require payment for the committed level regardless of actual consumption. Negotiating a smaller penalty, a ramp provision, or a right-to-exit for specific change-in-circumstance scenarios (major M&A, business restructuring) provides meaningful protection against over-committing.

Azure MACC: Mechanics and Negotiation

The Microsoft Azure Consumption Commitment (MACC) is a committed spend agreement that provides Azure credits at a discounted rate in exchange for a multi-year, multi-million dollar spend commitment. MACCs are typically negotiated as part of or alongside a Microsoft Enterprise Agreement (EA) renewal, and their terms interact in important ways with the broader Microsoft commercial relationship.

MACC Structure and Credit Mechanics

Under a MACC, the enterprise commits to a total Azure spend over the agreement period (e.g., $15M over 3 years) and receives the corresponding Azure credits upfront or in annual tranches, typically at a discount to the committed value (e.g., $15M in credits for a $13M payment). The credits are then consumed as Azure services are used.

Critical nuance: a MACC is a committed expenditure, not just a discount arrangement. If the enterprise does not consume the committed Azure credits, the value is lost. This makes MACC sizing — how large a commitment to make — one of the most consequential decisions in the Microsoft commercial relationship. An undersized MACC leaves discount value unrealised; an oversized MACC creates stranded committed spend that generates no return on the payment.

MACC vs Azure Reserved Instances: The Distinction

MACC is frequently confused with Azure Reserved VM Instances. They are distinct mechanisms: Reserved Instances are a discount on specific VM types purchased through the self-service portal. MACC is a committed spend agreement negotiated with Microsoft's enterprise commercial organisation. They operate at different levels of the Azure pricing stack and are not substitutes for each other — optimal Azure cost management typically involves both a MACC and an RI/Savings Plan portfolio.

MACC Negotiation Key Points

The primary MACC negotiation variables are the credit discount rate (the percentage reduction in the credit amount versus the payment made), which services count toward MACC consumption, the annual drawdown flexibility (whether credits can be carried forward), and the interaction between MACC and other Microsoft EA terms. For the full Azure cost management strategy including MACC tactics, our dedicated guide on negotiating Azure Committed Spend and MACC covers these in detail.

GCP Private Pricing

Google Cloud does not have a single branded programme equivalent to AWS EDP or Azure MACC, but Google Cloud's enterprise commercial organisation does negotiate private pricing agreements — custom rate cards — for enterprises with significant GCP spend. These agreements are less standardised than AWS EDP and are negotiated with greater flexibility, reflecting Google Cloud's more aggressive posture in the enterprise market.

GCP private pricing agreements typically provide discounts of 5–25% above the published CUD tiers, in exchange for committed spend levels and potentially exclusivity commitments for specific workload categories. Google Cloud has the most flexible private pricing programme of the three major hyperscalers for enterprises willing to engage competitively. Our dedicated guide on GCP cost optimisation covers the private pricing dimension.

Negotiation Strategy: How to Approach the Conversation

The single most common mistake enterprises make in EDP/MACC negotiations is allowing the hyperscaler to anchor the negotiation. The standard enterprise approach: the account team presents a "customised" offer (which is typically the standard enterprise discount for the spend tier) framed as a special deal, the enterprise procurement team reviews it, makes a small counter-proposal, and the final agreement settles close to the hyperscaler's opening position. This approach leaves 30–50% of the achievable discount on the table.

The Counter-Anchor Approach

The effective counter to anchor negotiation is to establish your own anchor before the hyperscaler presents theirs. This requires benchmark data: documented intelligence on the discount levels that comparable enterprises (same industry, similar spend level, similar workload profile) have recently achieved with the same hyperscaler. An enterprise that opens a negotiation by citing specific benchmark comparables and stating its target discount tier — rather than waiting to react to the hyperscaler's offer — fundamentally changes the negotiation dynamic.

Timing the Negotiation

EDP and MACC negotiations are not immune to timing effects. Cloud hyperscalers have quarterly and annual sales targets, and account teams have more flexibility — and more internal pressure to close deals — at end-of-quarter and end-of-year. Enterprises that initiate EDP/MACC negotiations 60–90 days before the desired execution date and communicate a clear deadline (board approval required by a specific date, for example) create conditions for more aggressive offers than negotiations with no artificial time pressure.

Leverage Mechanics — What Actually Moves Hyperscalers

EDP and MACC negotiations are ultimately driven by the hyperscaler's assessment of deal attractiveness — whether winning this commitment is worth the discount cost. The leverage mechanisms that improve this assessment are specific and learnable.

Competitive Threat: The Most Powerful Lever

Nothing moves a hyperscaler's discount position like a credible competitive threat. An enterprise that is actively evaluating AWS and has a written Azure proposal showing comparable capabilities at lower cost — or vice versa — has fundamentally different leverage than one that is committed to a single provider. The competitive threat must be credible: a perfunctory "we're looking at alternatives" statement carries no weight, but an enterprise that has completed a technical assessment, obtained a competitive commercial proposal, and can articulate a specific migration timeline creates genuine urgency for the hyperscaler account team.

Building a credible competitive threat requires investment: an architectural assessment of workload portability, engagement of the competing hyperscaler's enterprise sales team, and ideally a proof-of-concept or pilot migration. For enterprises considering a major multi-year commitment, this investment is typically recovered many times over in the negotiation outcome.

Commitment Size and Term

Larger commitment amounts and longer terms generate higher discount percentages. The relationship is not linear — moving from $5M to $10M annual commitment may yield a 3–5 percentage point discount improvement; moving from $10M to $20M may yield 2–3 points additional. The marginal discount per dollar of additional commitment decreases at larger deal sizes. Understanding this relationship allows enterprises to model the trade-off between commitment size, discount depth, and commitment risk.

Annual Commitment	Typical AWS EDP Discount Range	Typical Azure MACC Discount Range
$1M – $3M	5–9%	3–7%
$3M – $10M	9–15%	7–12%
$10M – $30M	14–20%	11–17%
$30M+	18–25%+	15–22%+

Note: Ranges are indicative benchmarks. Actual discounts vary significantly based on competitive context, workload type, and negotiation quality.

Benchmark Data: What Enterprises Are Actually Paying

Benchmark data is the single most valuable input to an EDP or MACC negotiation. Hyperscalers maintain internal "deal desks" that track every enterprise discount granted and the terms under which it was approved. Your account team knows what a company of your size with your spend level and workload profile has recently been granted. The enterprise that negotiates without equivalent intelligence is at a structural disadvantage.

Sources of benchmark data: Gartner peer benchmarks (available to Gartner clients), ITAM and sourcing advisory firms that conduct EDP/MACC negotiations across many clients, consortium benchmarking through industry groups, and independent advisors with direct visibility into comparable enterprise deals. IT Negotiations maintains a benchmark database from our 500+ enterprise engagements that provides current-cycle, deal-level intelligence on hyperscaler commercial terms — this data is what we bring to every EDP and MACC negotiation on behalf of clients.

Common EDP/MACC Traps and How to Avoid Them

Beyond the discount percentage, EDP and MACC agreements contain structural terms that can significantly affect the value actually delivered. These traps are well-known to hyperscaler account teams; enterprises without advisory support frequently accept them without realising the downstream consequences.

Trap 1: Commitment Sized to Current Spend, Not Future Spend

Hyperscaler account teams typically propose commitments anchored to the enterprise's current run rate plus a modest growth assumption. If the enterprise's actual cloud growth trajectory is higher than the modelled rate, the enterprise will exceed the commitment and pay on-demand rates for the excess — losing the EDP discount on a material portion of spend. Sizing the commitment to the 75th percentile of the credible spend forecast (not the most likely forecast) provides protection against this scenario.

Trap 2: Accepting the First-Offer Service Scope

AWS EDP and Azure MACC agreements specify which services generate commitment consumption credit. Hyperscalers often present standard scopes that exclude high-growth services (AI/ML services on AWS, Azure OpenAI Service) from commitment consumption — meaning growth in these services burns through budget without generating EDP discount or MACC credit. Reviewing the service scope against the enterprise's actual and anticipated usage mix, and negotiating inclusion of relevant services, is an often-overlooked value lever.

Trap 3: No Ramp Provision for New Commitments

An enterprise signing its first EDP or entering a significantly larger commitment than previously should negotiate a ramp provision: a grace period of 6–12 months in which the effective commitment level is lower than the eventual steady-state level. This protects against the scenario where actual cloud adoption is slower than modelled in the early phases of the agreement, reducing the risk of underage penalties.

For the multi-cloud dimension of EDP and MACC negotiations — including how to use AWS, Azure, and GCP commercially against each other — see our guide on multi-cloud cost optimisation strategy. For the technical optimisation foundation that should precede commercial negotiations, return to our enterprise cloud cost optimisation pillar guide.

Next Steps

EDP and MACC negotiations reward preparation. The enterprises that achieve best-in-class commercial terms are those that enter negotiations with three elements in place: a clean technical baseline (waste eliminated, commitment portfolio optimised, so the enterprise is negotiating on accurate spend projections), benchmark intelligence (data on what comparable enterprises have recently achieved), and competitive leverage (a credible alternative that the hyperscaler account team takes seriously).

IT Negotiations provides independent EDP and MACC negotiation advisory — representing enterprises in commercial discussions with AWS, Azure, and GCP. Our advisors bring benchmark data from recent comparable deals, build the competitive leverage position, and manage the full negotiation process through to execution. Contact us for a no-obligation assessment of your current and upcoming cloud commercial agreements, or take our cloud cost assessment to understand where you stand.