Compute Contract Terms
Observatory
AI-generated summaries, not legal advice. Every value here is an AI's reading of a provider's public terms, not the terms themselves. It can be wrong, incomplete, or out of date. We link each value to its source document, so verify anything yourself before you rely on it.

Microsoft Azure

Published terms, citations, and change history.

← Back to matrix

Documents archived

Extracted terms

Capacity & reservation terms

Public docs describe On Demand Capacity Reservations for VMs and Capacity Blocks (reservation of compute capacity for a specified duration), each with their own SLA. Broader enterprise commitment vehicles (e.g. Enterprise Agreement pricing/commitments) negotiated, not published. Cancellation may incur fee per Product Terms.

“Capacity Block means a reservation of compute capacity for a specified duration”
Microsoft Azure Consumption Commitment (MACC): negotiated, not published (program page). Microsoft's own docs describe the MACC as a contractual spend commitment associated with a negotiated agreement; the commitment terms themselves are not published.

Data use & AI training

Does not train on customer data by default: Microsoft Generative AI Services will not use Customer Data to train any generative AI foundation model except per Customer's documented instructions. Output Content is Customer Data; Microsoft does not own it.

“will not use Customer Data to train any generative AI foundation model”
Source: Microsoft Product Terms for Online Services · fetched 2026-07-14 · 0853193df492

Suspension rights

Grounds: material breach (non-payment), AUP/Code of Conduct violation, security risk, trade-law risk. 30 days' notice before suspension normally, but immediate suspension if payment declined or to prevent unauthorized access / protect systems. AUP violations suspended only to extent reasonably necessary with reasonable notice unless immediate needed.

“Microsoft will give Customer 30 days' notice before such suspension unless”
Source: Microsoft Customer Agreement (published) · fetched 2026-07-14 · 0d4f51d9d52b

Termination

Termination for convenience: either party on 60 days' notice. Post-termination data retrieval: for non-renewed Online Services, access continues 30 days after expiration; disabled account gives Customer 90 days to extract Customer Data.

“Either party may terminate this Agreement without cause on 60 days' notice”
Source: Microsoft Customer Agreement (published) · fetched 2026-07-14 · 0d4f51d9d52b

Unilateral modification

Microsoft may update the Agreement. General Terms/other terms: at least 60 days' notice, effective on renewal. SLA: at least 90 days' notice for adverse material changes. Product Terms: Material Adverse Changes apply at renewal; other changes effective on posting. No changes during initial subscription term for SLA.

“We will provide at least 90 days' notice for adverse material changes to this…”

Governing law & disputes

Governing law: State of Washington and US federal law. Venue: if Customer sues (non-Europe Affiliate) King County, WA; if Microsoft sues, Customer's HQ; Europe = Ireland. Binding arbitration: no (court venues specified). Class-action waiver: not specified.

“governed by and construed in accordance with the laws of the State of Washington”
Source: Microsoft Customer Agreement (published) · fetched 2026-07-14 · 0d4f51d9d52b

Availability definition

instance-level and cluster/throughput-based (varies by service); VM in Availability Zones 99.99%, Availability Set/Dedicated Host Group 99.95%, Single-Instance VM 99.9% (Premium SSD); AKS API server 99.95% (AZ) / 99.9% (non-AZ); Capacity Blocks capacity-availability based

“Uptime Calculation and Service Levels for Virtual Machines in Availability Zones”

Credit regime

Tiered by service; e.g. VM Availability Zones: <99.99%=10%, <99%=25%, <95%=100%. Standard tier VMs <99.9%=10%, <99%=25%, <95%=100%. Max credit 100% of monthly fees for affected resource. Service Credits are sole and exclusive remedy.

“Service Credits are your sole and exclusive remedy”

Claim mechanics

Customer must submit a claim to Microsoft customer support with detailed description, time/duration of downtime, affected resource names, number/location of affected users, and error description. For Azure, claim must be received within 60 days of the Incident.

“we must receive the claim within 60 days of the Incident”

SLA exclusions

Present: force majeure/outside reasonable control; external network/ISP/third-party; single-datacenter non-geo-resilient; customer fault/misuse; beta/preview/trial; throttling/abuse; exceeding quotas; scheduled/maintenance windows; customer-initiated operations (restart, scale). Performance degradation without unavailability excluded.

“This SLA and any applicable Service Levels do not apply to any performance or…”

Change history

Microsoft Azure: SLA for Microsoft Online Services (consolidated; incl. Azure compute/GPU) sla 2026-07-15
Tracked source document changed; not an edit of the same document. source
Microsoft Azure: SLA for Microsoft Online Services (consolidated; incl. Azure compute/GPU) sla 2026-07-15
+5 / 0 lines removed · source
AI summary of this change

The visible change is limited to an update of the document's title/date stamp, indicating a new version effective July 15, 2026, with no accompanying substantive text changes shown in this passage.

This is an AI-generated description. Verify it against the source document before relying on it.
+ Service Level Agreement for Microsoft Online Services (WW) July 15 2026 English…

Extracted 2026-07-15 03:41 UTC with claude-opus-4-8.