You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/reliability/regions-nonregional-services.md
+13-19Lines changed: 13 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,34 +4,24 @@ description: Learn about geographic and global Azure services.
4
4
ms.service: azure
5
5
ms.subservice: azure-availability-zones
6
6
ms.topic: conceptual
7
-
ms.date: 03/05/2025
7
+
ms.date: 03/24/2025
8
8
ms.author: anaharris
9
9
author: anaharris-ms
10
10
ms.custom: subject-reliability
11
11
---
12
12
13
13
# Nonregional Azure services
14
14
15
-
Nonregional services, listed on [Azure global infrastructure products](https://azure.microsoft.com/global-infrastructure/services/?products=all), are services for which there's no dependency on a specific Azure region.
15
+
Nonregional services, listed on [Azure global infrastructure products](https://azure.microsoft.com/global-infrastructure/services/?products=all), are services that a customer doesn't deploy into a specific Azure region.
16
16
17
-
## Types of nonregional services
17
+
There are two categories of nonregional services, each with different characteristics for reliability:
18
18
19
-
There are two categories of nonregional services:
19
+
-**Global services** are deployed to many Azure regions worldwide. If there's a regional failure, an instance in another region continues servicing customers.
20
+
-**Geographic services** aren't deployed to a specific Azure regions, but instead to a geographic area. Within that geographic area, one or more Azure regions might be used to serve customer requests. Consult the service's documentation to understand how to design a resilient solution.
20
21
21
-
-**Geographic services** are deployed to two or more regions within a geography. If there's a regional failure, an instance of the service in another region continues servicing customers.
22
-
-**Global services** are deployed to multiple regions worldwide. If there's a regional failure, an instance in another global region continues servicing customers.
22
+
Some nonregional services enable customers to specify the region where some components are deployed. For example, [Azure Virtual Desktop](https://azure.microsoft.com/services/virtual-desktop/) is a geographic service, so its core components are deployed within a geography instead of a specific Azure region. However, it enables customers to specify an Azure region where their host pool (virtual machines) reside.
23
23
24
-
Some nonregional services enable customers to specify the region where some components are deployed. For example, [Azure Virtual Desktop](https://azure.microsoft.com/services/virtual-desktop/) is a geographic service, so its core components are deployed within a geography instead of a specific Azure region. However, it enables customers to specify the region where their host pool (virtual machines) reside.
25
-
26
-
### Data residency
27
-
28
-
Most Azure services that store customer data allow the customer to specify the specific regions in which their data is stored.
29
-
30
-
When you use [Microsoft Entra ID](https://www.microsoft.com/security/business/identity-access/microsoft-entra-id), you can select geographic placement (such as Europe or North America) to support data residency. Alternatively, in some situations you can select worldwide for global distribution. For more information, see [Microsoft Entra ID and data residency](/entra/fundamentals/data-residency).
31
-
32
-
For more information about data residency in Azure, see [Data residency in Azure](https://azure.microsoft.com/global-infrastructure/data-residency/).
33
-
34
-
## Services by category
24
+
## List of nonregional services
35
25
36
26
| Product | Global | Geographic | Notes |
37
27
| --- | --- | --- | --- |
@@ -40,7 +30,7 @@ For more information about data residency in Azure, see [Data residency in Azure
40
30
| Azure AI Bot Service |✅|||
41
31
| Azure Blueprints |✅|||
42
32
| Azure Cloud Shell |✅|||
43
-
| Azure Communication Services |✅||[Some data is stored in a geography.](../communication-services/concepts/privacy.md)|
33
+
| Azure Communication Services |✅||[Some data is stored in a geographic area.](../communication-services/concepts/privacy.md)|
44
34
| Azure Content Delivery Network |✅|||
45
35
| Azure DevOps ||✅||
46
36
| Azure DNS |✅|||
@@ -59,7 +49,7 @@ For more information about data residency in Azure, see [Data residency in Azure
59
49
| Azure Static Web Apps |✅|||
60
50
| Azure subscriptions |✅|||
61
51
| Azure Traffic Manager |✅|||
62
-
| Azure Virtual Desktop |✅|| <ul><li>[Some data is stored in a geography.](/azure/virtual-desktop/data-locations)</li><li>Host pools are located in a specific region.</li></ul> |
52
+
| Azure Virtual Desktop |✅|| <ul><li>[Some data is stored in a geographic area.](/azure/virtual-desktop/data-locations)</li><li>Host pools are located in a specific region.</li></ul> |
63
53
| Microsoft Cost Management |✅|||
64
54
| Microsoft Defender for Cloud |✅|||
65
55
| Microsoft Defender for Identity |✅|||
@@ -68,3 +58,7 @@ For more information about data residency in Azure, see [Data residency in Azure
68
58
| Microsoft Graph |✅|||
69
59
| Microsoft Intune |✅|||
70
60
| Microsoft Sentinel ||✅||
61
+
62
+
## Next steps
63
+
64
+
-[Data residency in Azure](https://azure.microsoft.com/global-infrastructure/data-residency/).
0 commit comments