Data residency in Azure

Most Azure services are deployed regionally and enable the customer to specify the region into which the service will be deployed. Examples of such Azure services include virtual machines, storage, and SQL Database. For a complete list of regional services, see Products available by region.

Microsoft will not store or process customer data outside the customer-specified Geo without your authorization.

Microsoft may copy customer data between regions within a given Geo for data redundancy or other operational purposes. For example, geo-redundant storage replicates Blob, File, Queue and Table data between two regions within the same Geo for enhanced data durability in case of a major datacenter disaster.

Microsoft personnel (including subprocessors) located outside the Geo may remotely operate data processing systems in the Geo but will not access Customer Data without your authorization.

The following services may store or process certain data outside the specified Geo:

• Azure Cloud Services, which backs up web and worker-role software deployment packages to the United States regardless of the deployment region.
• Azure Data Explorer (ADX) stores partial usage data and service traces on a central cluster located in the EU for a limited time.
• Language Understanding, which may store active learning data in the United States, Europe, or Australia based on the authoring regions which the customer uses. Learn more
• Azure Machine Learning, may store freeform texts of asset names that the customer provides (such as names for workspaces, names for resource groups, names for experiments, names of files, and names of images) and experiment execution parameters aka experiment metadata in the United States for debugging purposes.
• Azure Databricks stores the following identity information in the United States to provide account and access management functionality to customers: username, first name, last name, and email address. This data is stored in the United States to support the global Azure Databricks platform.
• Azure Serial Console, which stores all customer data at rest in the Geo selected by customer, but when used through the Azure Portal may process console commands and responses outside of the Geo for the sole purpose of providing the Console experience inside the Portal.
• Azure OpenAI Service, which stores all customer data at rest in the Geo selected by the customer (except in limited fine-tuning scenarios as described here), but (i) for any model deployment type labeled as ‘Global,’ may process prompts and completions sent to and output by that deployment, for inferencing or fine-tuning, in any Azure OpenAI region globally and (ii) for any model deployment type labeled as ‘DataZone,’ may process prompts and completions sent to and output by that deployment, for inferencing or fine-tuning, within the specified data zone, as defined by Microsoft. When a ‘Global’ or ‘DataZone’ deployment type is selected for fine-tuned models, custom model weights may be stored temporarily outside the selected Geo.  Learn more
• When customers configure select services to an Azure Extended Zone, Microsoft will store and process their Customer Data in the Azure Extended Zone. If customers select an Azure Extended Zone located in a different country from their specified Geo, Customer Data will be stored and processed in the Extended Zone location.
• Preview, beta, or other prerelease services, which typically store customer data in the United States but may store it globally.

Certain Azure services do not enable the customer to specify the region where the service will be deployed. These services may store or process customer data in any Microsoft datacenter within Azure public regions, unless otherwise specified. 

• Azure Content Delivery Network, which provides a global caching service and stores customer data at edge locations around the world. Azure CDN POP locations by region.
• Microsoft Entra ID (formerly Azure Active Directory) operates as a non-regional service and based on customer requirements, including availability and scalability, may store Microsoft Entra directory data globally. Learn more. 
• Microsoft Defender for Cloud, which may store a copy of security-related customer data, collected from or associated with a customer resource (such as virtual machine or Azure AD tenant):
  (a) in the same Geo as that resource, except in those Geos where Microsoft has yet to deploy Microsoft Defender for Cloud, in which case a copy of such data will be stored in the United States; and
  (b) where Microsoft Defender for Cloud uses another Microsoft Online Service to process such data, it may store such data in accordance with the geolocation rules of that other Online Service.
  (c) if a customer provisions its tenant in the European Union or the United States, Microsoft will store Customer Data at rest only within that Geo.
  (d) The geo commitments in (a) and (c) do not apply to the following features: Security-Solution (WAF). 
• Microsoft Defender for IoT may use other Microsoft Online Services to process security-related customer data, this data may be stored in accordance with the geolocation rules of that other Online Service. 
• Microsoft Fabric enables the option to select an Azure region where Customer Data is stored when creating new Microsoft Fabric capacity. The default option listed is the user's tenant home region; if a user selects that region, all associated data, including Customer Data, will be stored in that Geo. If a user selects a different region, some Customer Data will still remain in the home Geo. Learn more. 
• Services that provide global routing functions and do not themselves process or store customer data. This includes Azure Traffic Manager—which provides load balancing between different regions—and Azure DNS—which provides domain name services that route to different regions. 

For a complete list of non-regional services, see Products available by region and select Non-regional.

Additional resources

• European Union Model Clauses
• Access to customer data
• Learn more about the EU Data Boundary