# Service Level Agreements (SLAs) in Azure

> Chapter 44 of the Courseiva AZ-900 curriculum — https://courseiva.com/learn/az-900/service-level-agreements

**Official objective:** 1.5 — Cloud Concepts

## Introduction

This chapter covers Service Level Agreements (SLAs) in Azure. AZ-900 tests this under objective 1.5, connecting to reliability and predictability concepts covered earlier.

## A Written Promise, Not Just a Hope

A gym might informally hope to keep its equipment in working order, but a formal written guarantee promising equipment will be functional at least 99% of the time — with a specific remedy if it isn't — is a much stronger commitment. A Service Level Agreement (SLA) works the same way for cloud services: it's a formal, documented commitment about a service's expected performance or availability, distinct from an informal, general expectation.

## Core explanation

### What an SLA is
A Service Level Agreement is a formal commitment from a provider about a specific aspect of a service — most commonly availability (how much of the time the service is expected to be operational) — along with what happens if that commitment isn't met.

### How SLAs are typically expressed
Availability SLAs are often expressed as a percentage of uptime over a given period — though the exact percentage varies by service, and shouldn't be treated as a single fixed figure to memorize across all of Azure, since different services can have different SLA commitments.

### Why SLAs matter
SLAs give organizations a formal, documented basis for understanding what level of service reliability to expect, and provide a mechanism for accountability if that commitment isn't met — generally in the form of service credits rather than a guarantee against ever experiencing an issue.

### An important nuance
An SLA is a commitment about a specific service, not a guarantee that nothing will ever go wrong — it typically includes what remedy applies if the commitment isn't met, rather than promising perfect, uninterrupted service indefinitely.

## Real-world context

An organization relying on a specific Azure service checks that service's documented SLA to understand Microsoft's formal availability commitment for it, rather than assuming the same figure applies to every other Azure service by default.

## Exam focus

Objective 1.5 expects candidates to understand what an SLA represents conceptually — a formal availability or performance commitment — without needing to memorize specific percentage figures for every service, since these vary and can change.

A common wrong answer is assuming a single SLA percentage applies uniformly across all Azure services — it varies by service.

Stable terms: **Service Level Agreement (SLA)**. Memory trick: an SLA is a formal, documented commitment with a defined remedy if unmet — not an informal expectation, and not a universal fixed number across every service.

## Step by step

1. **Review the SLA for a specific service** — Since SLA commitments vary by service, check the specific service's documented SLA rather than assuming a single figure applies universally across all of Azure.
2. **Understand what's being measured** — Most commonly availability, though other aspects of a service can also be covered by an SLA depending on the specific service.
3. **Understand what happens if it's not met** — SLAs typically define a remedy — often a service credit — if the committed level isn't met, rather than functioning as an unconditional guarantee against any issue.

## Common misconceptions

- **Misconception:** All Azure services share the same SLA percentage. **Reality:** SLA commitments vary by specific service — there isn't a single universal figure that applies across all of Azure.
- **Misconception:** An SLA guarantees a service will never have any issues. **Reality:** An SLA is a formal commitment with a defined remedy (often a service credit) if the commitment isn't met — it isn't an absolute guarantee against any disruption ever occurring.

## Key takeaways

- A Service Level Agreement (SLA) is a formal, documented commitment from a provider about a specific service aspect, most commonly availability.
- SLA commitments vary by specific Azure service — there's no single universal percentage to memorize.
- SLAs typically define a remedy, like a service credit, if the committed level isn't met, rather than guaranteeing zero disruption.

## FAQ

**What is a Service Level Agreement (SLA)?**

It's a formal, documented commitment from a provider about a specific aspect of a service — most commonly availability — along with what remedy applies if that commitment isn't met.

**Is there one SLA percentage that applies to all Azure services?**

No — SLA commitments vary by specific service. It's important to check the documented SLA for the specific service in question rather than assuming a single figure applies universally.

**Does an SLA guarantee a service will never fail?**

No — an SLA is a formal commitment with a defined remedy (often a service credit) if the commitment isn't met, not an absolute guarantee against any disruption occurring.

---

Interactive version with quiz and diagrams: https://courseiva.com/learn/az-900/service-level-agreements