SLA performance for Microsoft Entra ID
As an identity admin, you might need to track the Microsoft Entra service-level agreement (SLA) performance to make sure Microsoft Entra ID can support your vital apps. This article shows how the Microsoft Entra service has performed according to the SLA for Microsoft Entra ID.
You can use this article in discussions with app or business owners to help them understand the performance they can expect from Microsoft Entra ID.
Note
This article applies to both workforce and external tenants. (Learn more about tenant configurations).
How is SLA measured for Microsoft Entra ID?
Details on how downtime is defined and how uptime percentage is calculated are provided in the SLA for Microsoft Entra ID.
Performance is measured in a way that reflects customer authentication experience, rather than simply reporting on whether the system is available to outside connections. This distinction means that the calculation is based on if:
- Users can authenticate
- Microsoft Entra ID successfully issues tokens for target apps after authentication
No planned downtime
You rely on Microsoft Entra ID to provide identity and access management for your vital systems. To ensure Microsoft Entra ID is available when business operations require it, Microsoft doesn't plan downtime for Microsoft Entra system maintenance. Instead, maintenance is performed as the service runs, without customer impact.
Recent worldwide SLA performance
To help you plan for moving workloads to Microsoft Entra ID, we publish past SLA performance. These numbers show the level at which Microsoft Entra ID met the requirements in the SLA for Microsoft Entra ID, for all tenants.
The numbers in the table are a global total of Microsoft Entra authentications across all customers and geographies. The number is truncated at three places after the decimal. Numbers aren't rounded up, so actual SLA attainment is higher than indicated.
| Month | 2021 | 2022 | 2023 | 2024 |
|---|---|---|---|---|
| January | 99.998% | 99.998% | 99.999% | |
| February | 99.999% | 99.999% | 99.999% | 99.999% |
| March | 99.568% | 99.998% | 99.999% | 99.999% |
| April | 99.999% | 99.999% | 99.999% | 99.999% |
| May | 99.999% | 99.999% | 99.999% | 99.999% |
| June | 99.999% | 99.999% | 99.999% | 99.999% |
| July | 99.999% | 99.999% | 99.999% | 99.999% |
| August | 99.999% | 99.999% | 99.999% | 99.999% |
| September | 99.999% | 99.998% | 99.999% | 99.999% |
| October | 99.999% | 99.999% | 99.999% | 99.998% |
| November | 99.998% | 99.999% | 99.999% | 99.998% |
| December | 99.978% | 99.999% | 99.999% |
Incident history
All incidents that seriously affect Microsoft Entra performance are documented in the Azure status history. Not all events documented in Azure status history are serious enough to cause Microsoft Entra ID to go below its SLA. You can view information about the impact of incidents, and a root cause analysis of what caused the incident and what steps Microsoft took to prevent future incidents.