Skip to content

Commit 0628239

Browse files
committed
Updates
1 parent 5fcb265 commit 0628239

File tree

1 file changed

+14
-20
lines changed

1 file changed

+14
-20
lines changed

articles/reliability/regions-nonregional-services.md

Lines changed: 14 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -1,44 +1,39 @@
11
---
2-
title: Azure non-regional services
2+
title: Azure nonregional services
33
description: Learn about geographic and global Azure services.
44
ms.service: azure
55
ms.topic: conceptual
6-
ms.date: 03/24/2025
6+
ms.date: 03/25/2025
77
ms.author: anaharris
88
author: anaharris-ms
99
ms.custom: subject-reliability
1010
---
1111

12-
# Azure non-regional services
12+
# Azure nonregional services
1313

14-
Non-regional Azure services are services that you don't deploy into a specific Azure region. This article explains the difference between global and geographic non-regional services, and provides a list of non-regional services that indicates whether each is a global or geographic service.
14+
Nonregional Azure services are services that you don't deploy into a specific Azure region. This article explains the difference between global and geographic nonregional services, and provides a list of nonregional services that indicates whether each is a global or geographic service.
1515

16+
## Types of nonregional services
1617

17-
## Types of non-regional services
18-
19-
There are two types of non-regional services:
20-
21-
- **Global services** are deployed to many Azure regions worldwide. If there's a regional failure, an instance in another region can continue to operate. With Global services, you don't need to specifically design for resiliency as they are automatically resilient to regional failures.
18+
There are two types of nonregional services:
2219

20+
- **Global services** are deployed to many Azure regions worldwide. If there's a regional failure, an instance in another region can continue to operate. With global services, you don't need to specifically design for region-wide outages, because these services are resilient to regional failures.
2321

2422
- **Geographic services** are deployed to a geographic area, and not a specific Azure region. Within that geographic area, one or more Azure regions might be used to serve client requests. To understand the geographic areas, and learn how to design a resilient solution with a geographic service, see the documentation for that service.
2523

26-
Generally, most non-regional services support one or the other, but not both. For example, Azure AD B2C is a global service, while Azure DevOps is a geographic service. However, Microsoft Entra ID is a service that can be either global or geographic, depending on how you configure it.
27-
28-
## Regional dependent service components
24+
Generally, most nonregional services are either global or geographic, but not both. For example, Azure AD B2C is a global service, while Azure DevOps is a geographic service. However, Microsoft Entra ID is a service that can be either global or geographic, depending on how you configure it.
2925

30-
When you use a non-regional service, you don't need to choose a region for the service itself. However, you might need to choose a region for dependent components that you use with the service. For example, if you use [Azure Virtual Desktop (AVD)](https://azure.microsoft.com/services/virtual-desktop/), which is a non-regional service, you can choose the region where your host pool (virtual machines) should reside.
26+
Most nonregional services that store customer data enable you to select a specific region for data storage. To learn more, see [Data residency in Azure](https://azure.microsoft.com/global-infrastructure/data-residency/).
3127

28+
## Regionally dependent service components
3229

33-
## Data storage for non-region services
30+
When you use a nonregional service, you don't choose a specific Azure region for the service itself. However, you might need to choose a region for dependent components that you use with the service. For example, if you use [Azure Virtual Desktop (AVD)](https://azure.microsoft.com/services/virtual-desktop/), which is a nonregional service, you can choose the region where your host pool (virtual machines) should reside.
3431

32+
## List of nonregional services
3533

34+
Microsoft publishes a [a list of services, which includes nonregional services](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/table). The table below also contains the list of nonregional services, but specifies whether each service is global or geographic, and provides additional notes about data residency and configuration.
3635

37-
## List of non-regional services
38-
39-
Although Microsoft publishes a [a list of non-regional services](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/table), the table below also contains the list non-regional service, but specifies whether each service is global or geographic, and provides additional notes about data residency and configuration.
40-
41-
| Product | Global | Geographic | Notes |
36+
| Service | Global | Geographic | Notes |
4237
| --- | --- | --- | --- |
4338
| Azure AD B2C | ✅ | | |
4439
| Azure Advisor | ✅ | | |
@@ -77,4 +72,3 @@ Although Microsoft publishes a [a list of non-regional services](https://azure.m
7772
## Related content
7873

7974
- [Data residency in Azure](https://azure.microsoft.com/global-infrastructure/data-residency/)
80-

0 commit comments

Comments
 (0)