Azure references service level agreements (SLAs) for its cloud services, which define the uptime and performance guarantees Microsoft commits to for specific products. These SLAs are separate documents linked from this legal hub.
This analysis describes what Microsoft Azure's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
SLAs govern what compensation or credits you may receive if Azure services experience downtime, and the specific terms vary by product, meaning some services you use may have stronger or weaker uptime guarantees than others.
Interpretive note: The specific SLA terms, uptime percentages, and service credit formulas are not reproduced on this index page and require review of individual service-specific SLA documents linked from this hub.
Business customers relying on Azure for critical infrastructure need to review the specific SLA for each service they deploy, as uptime guarantees and associated service credits are defined separately per product and may not uniformly apply across an Azure deployment.
Cross-platform context
See how other platforms handle Service Level Agreement References and similar clauses.
Compare across platforms →Monitoring
Microsoft Azure has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 10 platforms.
(1) REGULATORY LANDSCAPE: SLA provisions in cloud service agreements are relevant to operational resilience requirements under various regulatory frameworks, including the EU Digital Operational Resilience Act (DORA) for financial services firms, as well as sector-specific requirements for healthcare (HIPAA) and government workloads. Enforcement authorities depend on the regulated sector of the customer organization. (2) GOVERNANCE EXPOSURE: Medium. Per-service SLA variation means enterprise customers with complex Azure deployments may have inconsistent resilience guarantees across their infrastructure stack. Service credit mechanisms (the standard SLA remedy for downtime) may not adequately compensate for business losses in high-criticality deployments, and customers should assess whether contractual SLA terms align with their operational risk tolerance. (3) JURISDICTION FLAGS: EU financial services firms subject to DORA have explicit third-party ICT provider contractual requirements that may require SLA terms to meet specific minimum standards. UK financial services firms under FCA guidance face similar considerations. These regulatory requirements may create obligations beyond what standard Azure SLAs provide. (4) CONTRACT AND VENDOR IMPLICATIONS: Procurement teams should verify that SLAs for each Azure service meet internal vendor risk management thresholds. Standard Azure SLAs typically provide service credits as the sole remedy for downtime, which represents a common limitation in hyperscale cloud agreements. Customers should assess whether this limitation is consistent with their risk allocation requirements. (5) COMPLIANCE CONSIDERATIONS: Legal teams should document the specific SLA percentages applicable to each Azure service in use and assess whether those commitments satisfy any applicable regulatory or contractual minimum availability requirements imposed on the customer organization.
Full compliance analysis
Regulatory citations, enforcement risk, and due diligence action items.
Free: track 1 platform + weekly digest. Watcher: 10 platforms + same-day alerts. No credit card required.
Professional Governance Intelligence
Need to monitor specific governance provisions?
Professional includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.
Built from archived source documents, structured governance mappings, and historical version tracking.
SLAs govern what compensation or credits you may receive if Azure services experience downtime, and the specific terms vary by product, meaning some services you use may have stronger or weaker uptime guarantees than others.
Business customers relying on Azure for critical infrastructure need to review the specific SLA for each service they deploy, as uptime guarantees and associated service credits are defined separately per product and may not uniformly apply across an Azure deployment.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Microsoft Azure.