A buyer-side reading list on AWS, Microsoft Azure and Google Cloud. The Enterprise Discount Program, the Microsoft Azure Consumption Commitment, the Google Cloud committed-use envelope. Reserved Instances and Savings Plans. BYOL bridges into the hyperscalers. The Bedrock, Azure OpenAI and Vertex AI commercial surfaces. The pages below cluster the firm’s cloud commentary into a single editorial reading set.
A cloud bill reads, on the surface, as consumption. A closer read finds three load-bearing commercial layers: the published rate-card, the cloud-vendor commitment instrument (EDP, MACC, EDP Cloud) and the embedded software entitlements (BYOL, marketplace, native services). Each layer carries its own renewal cycle, its own ramp, its own audit posture.
The procurement implication is that a cloud commitment is not a FinOps optimisation problem. It is a multi-year commercial commitment that interacts with the buyer’s wider software portfolio. An AWS engagement, an Azure engagement or a Google Cloud engagement sizes the commitment against the deployed workload, structures the discount curve against the right tenor and protects the buyer against the publisher’s standard ramp design.
This pillar groups the cloud commentary into ten editorial sections. Each section names the load-bearing mechanic, links the deeper spoke articles and points to the practice page and the relevant white papers for the buyer who wants the engagement methodology.
AWS, Microsoft Azure and Google Cloud each operate a private discount instrument that sits above the public rate-card. AWS calls it the Enterprise Discount Program (and its variants, the Private Pricing Addendum and the Strategic Collaboration Agreement). Microsoft calls it the Microsoft Azure Consumption Commitment. Google calls it the Google Cloud Enterprise Discount Program.
The three instruments share a common architecture. The buyer commits to a multi-year consumption envelope (typically three years, sometimes five). The publisher returns a discount that grows with commitment size and tenor. The envelope counts against named eligible services. The unconsumed envelope is, by default, forfeit at expiry. The buyer-side methodology designs the envelope size against the deployed and forecast workload (not against the publisher’s aspirational forecast), the eligible-service mix and the ramp curve.
The full methodology sits in three companion white papers: AWS EDP Commitment Design, Microsoft Azure MACC and Google Cloud EDP Design.
The AWS Enterprise Discount Program is the private discount instrument that converts a multi-year consumption commitment into a stepped discount against the AWS public rate-card. The standard tenor is three years. The discount curve grows with commitment level, eligible-service breadth and the architectural commitment to AWS-native services.
The buyer-side question is the commitment’s size relative to the deployed workload. A commitment sized to the publisher’s forecast typically over-commits by 15 to 35 percent against the realised consumption. A commitment sized to the firm’s own trailing-twelve-month consumption (with a defensible growth curve added on top) sits inside the realised envelope and leaves the buyer protected against over-commitment.
The Private Pricing Addendum is the contractual document that records the EDP discount. The PPA carries protective clauses (RI consumption inclusion, marketplace inclusion, services exclusions, true-down protections, mid-term re-sizing rights) that the buyer should negotiate explicitly rather than accept on default. The full reading sits in the EDP Commitment Design paper.
The Microsoft Azure Consumption Commitment is the Microsoft equivalent. The MACC is a three-year (sometimes five-year) consumption commitment that counts against Azure consumption (and against Marketplace transactions billed through Azure) in exchange for an enterprise discount and access to publisher incentive programmes.
The buyer-side question runs on the same axis as EDP: is the commitment sized to the realised consumption or to the account team’s aspirational forecast. The Admodum methodology sizes the MACC against trailing consumption, against the named workload migrations with realistic timelines, and against a contestable growth assumption. Marketplace inclusion is the load-bearing clause: a MACC that consumes Marketplace transactions extends the envelope to a wider eligible-spend base than a MACC restricted to Azure native services.
The MACC is also a negotiating instrument inside the wider Microsoft Enterprise Agreement. A MACC commitment can be packaged with the EA renewal as a commercial vehicle that releases discount across the wider Microsoft portfolio. The full reading sits in the Microsoft Azure MACC paper.
Google Cloud operates two related commercial instruments. The Google Cloud Enterprise Discount Program is the multi-year consumption commitment that delivers an enterprise discount against the GCP rate-card. Committed-Use Discounts are the workload-level commitments (one-year and three-year) that bind specific resource families (Compute, Memorystore, Cloud SQL) to a fixed discount in exchange for a usage commitment.
The buyer-side methodology stacks the two. The Google Cloud EDP delivers the enterprise-wide discount and access to Google’s solution funding. CUDs deliver the workload-level discount on the steady-state base. The combination sits below the rate-card and protects the buyer against the publisher’s tendency to design the EDP around a single discount layer.
Vertex AI consumption sits inside the EDP envelope where the contractual document includes Vertex AI as an eligible service. The Admodum methodology negotiates the Vertex AI inclusion explicitly rather than accepting the default. The full reading sits in the Google Cloud EDP Design paper.
Reserved Instances and Savings Plans are the workload-level commercial instruments that sit inside the wider EDP / MACC / EDP envelope. AWS operates Standard RIs, Convertible RIs, Compute Savings Plans and EC2 Instance Savings Plans. Azure operates Reserved Instances and the newer Azure Savings Plan for Compute. Google operates Committed-Use Discounts on Compute and on a growing list of managed services.
The buyer-side question is the right mix of tenor (one-year versus three-year), the right mix of instrument type (Standard / Convertible / Savings Plan / CUD), and the right coverage ratio (the percentage of the steady-state base covered by commitment instruments). The Admodum methodology runs the trailing-twelve-month consumption against the instrument families and produces a recommendation that protects the buyer against tenor lock-in while delivering the discount envelope.
The instruments interact with the EDP / MACC / EDP envelope in non-obvious ways. RI consumption counts against the EDP envelope (so an aggressive RI position can over-commit the EDP envelope and waste the discount). The Admodum methodology sizes the two layers together to avoid double commitment.
A material share of the cloud-licensing position runs through the BYOL (Bring Your Own Licence) bridges that connect on-premise software entitlements to hyperscaler deployments. Oracle Database on AWS, Azure or GCP runs against the Oracle Cloud Authorisation document. SQL Server on AWS or GCP runs against the Microsoft Product Terms with the Azure Hybrid Benefit exception. Windows Server on the three hyperscalers runs against License Mobility through Software Assurance.
The buyer-side methodology reads the BYOL bridges as commercial instruments and not as technical artefacts. A BYOL bridge that is read correctly extends the buyer’s on-premise licence portfolio into the cloud at no incremental publisher cost. A BYOL bridge that is read incorrectly creates a compliance gap that the publisher will surface inside the next audit.
The Admodum methodology produces the BYOL inventory at the start of any cloud commitment engagement. The inventory reads as a per-publisher, per-product, per-deployment list of contractually eligible BYOL workloads. The inventory becomes the input to the EDP / MACC / EDP sizing exercise.
AWS Bedrock, Microsoft Azure OpenAI Service and Google Vertex AI are the three principal hyperscaler generative-AI commercial surfaces. Each operates on a Provisioned Throughput Unit construct (with naming variations) that converts on-demand token-based pricing into a reserved-capacity commitment at a per-hour rate.
The buyer-side methodology sizes the PTU commitment against trailing sustained consumption (not against the publisher’s aspirational rollout assumption). The break-even point between on-demand and PTU sits at a defined utilisation ratio per model; the Admodum methodology runs the arithmetic on the buyer’s own consumption telemetry and sizes the PTU envelope at the right utilisation ratio.
The PTU commitment interacts with the EDP / MACC envelope. Bedrock spend on AWS counts against the EDP envelope where the contractual document includes Bedrock as an eligible service. Azure OpenAI spend counts against the MACC envelope on the same basis. The Admodum methodology negotiates the inclusion explicitly. The full reading sits in three papers: AWS Bedrock Commitment, AI Vendors PTU Design and the AI Vendors practice page.
FinOps is the operational practice that optimises cloud consumption against the realised workload (right-sizing, scheduling, storage class management, idle-resource cleanup). Licensing is the commercial practice that designs the multi-year commitment instruments against the realised consumption. The two practices interact but are not interchangeable.
The buyer-side methodology runs FinOps as the input layer to the licensing exercise. The FinOps team produces the trailing-twelve-month consumption telemetry, the realised utilisation curve and the optimisation potential. The licensing team uses the telemetry as the sizing input for the EDP / MACC / EDP envelope, the RI / Savings Plan / CUD coverage ratio and the PTU commitment.
The Admodum methodology runs both layers in sequence. The FinOps optimisation pass establishes the realised consumption baseline. The licensing design pass sizes the commitment envelope against the baseline plus a defensible growth curve. The combined output sits below the rate-card and inside the realised utilisation envelope.
The pillar groups cloud commentary into ten sections above. The spoke band below opens the forty named articles inside the cluster, each one a deep-read on a specific cloud-commercial mechanic. The white papers below sit alongside the pillar as the methodology deliverables; the practice pages sit alongside as the engagement entry points.
A short follow-up checklist for the reader who is closing this page: visit the AWS, Microsoft or Google Cloud practice for the engagement entry point; visit the AWS knowledge hub for the aggregated reading; request the cloud-commitment papers (AWS EDP, Azure MACC, Google Cloud EDP, AWS Bedrock, AI Vendors PTU); or open a private conversation with a senior Admodum cloud advisor through /contact/.
Forty named articles inside the cloud cluster. Each one is a deep-read on a specific cloud-commercial mechanic, written from the buyer’s seat.
A senior Admodum cloud advisor will run the methodology through with your CIO, CFO, procurement team or FinOps lead on a private call. The engagement runs as fixed fee, contingency or annual retainer. EDP, MACC and EDP renewals route into the Renewal Programme.