Skip to content

Commit 2adae47

Browse files
authored
Merge pull request #238223 from shlipsey3/reports-tenant-sla-051523
reports-tenant-sla-051523
2 parents 9dad579 + 55bfcac commit 2adae47

File tree

2 files changed

+19
-6
lines changed

2 files changed

+19
-6
lines changed
32.8 KB
Loading

articles/active-directory/reports-monitoring/reference-azure-ad-sla-performance.md

Lines changed: 19 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: active-directory
88
ms.topic: reference
99
ms.workload: identity
1010
ms.subservice: report-monitor
11-
ms.date: 10/31/2022
11+
ms.date: 05/22/2023
1212
ms.author: sarahlipsey
1313
ms.reviewer: besiler
1414

@@ -36,13 +36,13 @@ For full details on SLA coverage and instructions on requesting a service credit
3636

3737
## No planned downtime
3838

39-
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.
39+
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 doesn't plan downtime for Azure AD system maintenance. Instead, maintenance is performed as the service runs, without customer impact.
4040

4141
## Recent worldwide SLA performance
4242

4343
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)](https://azure.microsoft.com/support/legal/sla/active-directory/v1_1/), for all tenants.
4444

45-
The SLA attainment is truncated at three places after the decimal. Numbers are not rounded up, so actual SLA attainment is higher than indicated.
45+
The SLA attainment is truncated at three places after the decimal. Numbers aren't rounded up, so actual SLA attainment is higher than indicated.
4646

4747
| Month | 2021 | 2022 | 2023 |
4848
| --- | --- | --- | --- |
@@ -61,16 +61,29 @@ The SLA attainment is truncated at three places after the decimal. Numbers are n
6161

6262
### How is Azure AD SLA measured?
6363

64-
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:
64+
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 distinction means that the calculation is based on if:
6565

6666
- Users can authenticate
6767
- Azure AD successfully issues tokens for target apps after authentication
6868

69-
The numbers above are a global total of Azure AD authentications across all customers and geographies.
69+
The numbers in the table are a global total of Azure AD authentications across all customers and geographies.
7070

7171
## Incident history
7272

73-
All incidents that seriously impact Azure AD performance are documented in the [Azure status history](https://azure.status.microsoft/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.
73+
All incidents that seriously impact Azure AD performance are documented in the [Azure status history](https://azure.status.microsoft/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, and a root cause analysis of what caused the incident and what steps Microsoft took to prevent future incidents.
74+
75+
## Tenant-level SLA (preview)
76+
77+
In addition to providing global SLA performance, Azure AD now provides tenant-level SLA performance. This feature is currently in preview.
78+
79+
To access your tenant-level SLA performance:
80+
81+
1. Navigate to the [Microsoft Entra admin center](https://entra.microsoft.com) using the Reports Reader role (or higher).
82+
1. Go to **Azure AD** and select **Scenario Health** from the side menu.
83+
1. Select the **SLA Monitoring** tab.
84+
1. Hover over the graph to see the SLA performance for that month.
85+
86+
![Screenshot of the tenant-level SLA results.](media/reference-azure-ad-sla-performance/tenent-level-sla.png)
7487

7588
## Next steps
7689

0 commit comments

Comments
 (0)