Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
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.
There are two types of nonregional services:
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.
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.
Generally, most nonregional services are either global or geographic, but not both. For example, Azure Front Door 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.
For most nonregional services that store customer data, you can select a specific region for data storage. To learn more, see Data residency in Azure.
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), which is a nonregional service, you can choose the Azure region where your host pool (virtual machines) resides.
Microsoft publishes a a list of services, which includes nonregional services. 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.
Product | Global | Geographic | Notes |
---|---|---|---|
Azure AD B2C | |||
Azure Advisor | |||
Azure AI Bot Service | |||
Azure Blueprints | |||
Azure Content Delivery Network | |||
Azure DevOps | |||
Azure DNS | |||
Azure Front Door | |||
Azure Information Protection | |||
Azure Lighthouse | |||
Azure management groups | |||
Azure Maps | |||
Azure Migrate | |||
Azure Peering Service | |||
Azure Performance Diagnostics | |||
Azure Policy | |||
Azure portal | |||
Azure Resource Graph | |||
Azure Stack Edge | |||
Azure Static Web Apps | |||
Azure subscriptions | |||
Azure Traffic Manager | |||
Azure Virtual Desktop | Some data is stored in a geographic area. Host pools are located in a specific region. | ||
Microsoft Cost Management | |||
Microsoft Defender for Cloud | |||
Microsoft Defender for Identity | |||
Microsoft Defender for IoT | |||
Microsoft Entra ID | Select location during Microsoft Entra tenant creation, which can be geographic or worldwide. See Microsoft Entra ID and data residency. | ||
Microsoft Graph | |||
Microsoft Intune | |||
Microsoft Sentinel |