Azure Active Directory SLA performance
As an identity admin, you may need to track the Azure Active Directory (Azure AD) service-level agreement (SLA) performance to make sure Azure AD can support your vital apps. This article shows how the Azure AD service has performed according to the SLA for Azure Active Directory (Azure AD).
You can use this article in discussions with app or business owners to help them understand the performance they can expect from Azure AD.
Service availability commitment
Microsoft offers Premium Azure AD customers the opportunity to get a service credit if Azure AD fails to meet the documented SLA. When you request a service credit, Microsoft evaluates the SLA for your specific tenant; however, this global SLA can give you an indication of the general health of Azure AD over time.
The SLA covers the following scenarios that are vital to businesses:
User authentication: Users are able to sign in to the Azure AD service.
App access: Azure AD successfully emits the authentication and authorization tokens required for users to sign in to applications connected to the service.
For full details on SLA coverage and instructions on requesting a service credit, see the SLA for Azure Active Directory (Azure AD).
No planned downtime
You rely on Azure AD to provide identity and access management for your vital systems. To ensure Azure AD is available when business operations require it, Microsoft does not plan downtime for Azure AD 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 Azure AD, we publish past SLA performance. These numbers show the level at which Azure AD met the requirements in the SLA for Azure Active Directory (Azure AD), for all tenants.
The SLA attainment is truncated at three places after the decimal. Numbers are not rounded up, so actual SLA attainment is higher than indicated.
How is Azure AD SLA measured?
The Azure AD SLA is measured in a way that reflects customer authentication experience, rather than simply reporting on whether the system is available to outside connections. This means that the calculation is based on whether:
- Users can authenticate
- Azure AD successfully issues tokens for target apps after authentication
The numbers above are a global total of Azure AD authentications across all customers and geographies.
All incidents that seriously impact Azure AD performance are documented in the Azure status history. Not all events documented in Azure status history are serious enough to cause Azure AD to go below its SLA. You can view information about the impact of incidents, as well as a root cause analysis of what caused the incident and what steps Microsoft took to prevent future incidents.
Submit and view feedback for