Skip to content
Updated 24h ago

Microsoft Azure vs Google Cloud SLA

Promised uptime per service, credits, support and what the status pages showed, side by side.
Change vendors (up to four; 2 picked)

Promise vs reality

Promised in the SLAObserved on the vendor's status pagePartial historyShortfall

Best SLA by category

Support: fastest first response

  • Google Cloud Standard4 hP2: 4 hours · P3: 8 hours · P4: 8 hours
  • Google Cloud Enhanced1 hP1: 1 hour · P2: 4 hours · P3: 8 hours · P4: 8 hours
  • Google Cloud Premium15 minP1: 15 minutes · P2: 2 hours · P3: 4 hours · P4: 8 hours
  • Microsoft Azure Basicn/aNo published response targets.
  • Microsoft Azure Developern/aMinimal business impact (Sev C): Within eight business hours
  • Microsoft Azure Standard1 hCritical business impact (Sev A): Within one hour · Moderate business impact (Sev B): Within four hours · Minimal business impact (Sev C): Within eight business hours
  • Microsoft Azure Professional Direct1 hCritical business impact (Sev A): Within one hour · Moderate business impact (Sev B): Within two hours · Minimal business impact (Sev C): Within four business hours
  • Microsoft Azure Unified Enterprise15 minCritical business system down (Sev 1): Within 15 mins for Azure, one hour for all other products · Critical business impact (Sev A): Within one hour · Moderate business impact (Sev B): Within two hours · Minimal business impact (Sev C): Within four business hours

Popular comparisons

Sources: each vendor's own SLA page (re-read monthly) and status page feed (read every Friday). A summary, not the contract: the contract you sign governs. Logos via logo.dev; trademarks belong to their owners.

SLA changes by email

Fridays, only in weeks when a cloud, data or AI vendor changed an SLA.

Double opt-in. Unsubscribe any time.