Azure SLAs, Service Lifecycle, and Support Plans

Quick Answer: An SLA guarantees monthly uptime and pays service credits (not refunds) on a breach. A composite SLA is the product of each dependent service's SLA, so it is always lower than any single one. Free and Preview services have no SLA. Support tiers run Basic (free) to Unified, with Professional Direct offering the fastest 15-minute critical response.

Reading SLA percentages

A Service Level Agreement is Microsoft's contractual uptime commitment per service. Convert percentages to a monthly downtime budget to reason about scenarios.

Note what raises an SLA: spreading VMs across Availability Zones lifts the VM SLA to 99.99%; many PaaS services publish higher SLAs than raw IaaS; adding redundancy so an alternate path takes over improves resilience.

Composite SLA math

When an application depends on several services in series, multiply their SLAs.

Example: App Service (99.95%) calling SQL Database (99.99%) calling Storage (99.9%): 99.95% x 99.99% x 99.9% = 99.84% — lower than any single component. Each dependency you chain in reduces the combined number. To improve it, add redundancy to the weakest link (for example a failover database), which raises that component's effective availability and therefore the composite.

Service credits, not refunds

If Azure misses the committed SLA, you must file a claim; Microsoft then applies a service credit to a future bill. Typical tiers:

On the Exam: Credits are percentage discounts on your next bill, never cash refunds, and you must request them.

The service lifecycle: Preview to GA

The single most-tested fact here: Preview features carry no SLA and should never run production workloads; only GA services are SLA-backed and fully supported.

Azure support plans

Worked example: A startup runs a production app and needs round-the-clock help for outages but cannot justify four-figure monthly fees. Standard is the cheapest plan with 24/7 technical support and a ~1-hour critical response. Developer only offers business-hours email, so it fails the 24/7 requirement; Professional Direct meets it but is far more expensive than necessary.

Every plan, including free Basic, includes documentation, community forums, Azure Advisor recommendations, and Azure Service Health notifications.

How SLA, lifecycle, and support intersect with the exam itself

These three topics anchor the "manage and govern" portion of AZ-900, so be ready for blended questions. A scenario might ask why a Preview feature "cannot be relied on for a production launch" — the answer is the missing SLA, not pricing. Another might give you a multi-tier app and ask which design "meets a 99.99% target," steering you toward Availability Zones and away from a single-region single-VM build whose composite SLA falls short once you multiply dependencies.

As context, the AZ-900 exam itself costs about $99 USD, presents roughly 40 to 60 questions with a 45-minute answering window (about 65 minutes of total seat time), and requires a scaled score of 700 out of 1000 to pass. There is no SLA on a certification, of course, but knowing the logistics helps you budget study time across these governance topics, which are heavily weighted.

Staying informed

Know the distinction the exam draws: the public Azure Status page reports broad outages affecting many customers, while Azure Service Health is personalized to the subscriptions and resources you actually use and can fire alerts. Azure Advisor is different again — it does not report outages but recommends optimizations across cost, security, reliability, performance, and operational excellence.

On the Exam: "Cheapest plan with 24/7 technical support" = Standard. "Fastest critical response" = Professional Direct (15 min). "Personalized outage alerts" = Service Health. "Broad platform-wide outage status" = Azure Status. "Tailored best-practice recommendations" = Advisor.