Data residency in Azure

Azure has more global regions than any other cloud provider—offering the scale and data residency options you need to bring your apps closer to your users around the world.

As a customer, you maintain ownership of customer data—the content, personal and other data you provide for storing and hosting in Azure services. Microsoft will not store customer data outside the geography you specify, except for certain non-regional services. You are in control of any additional geographies where you decide to deploy your solutions or replicate your data. Microsoft cloud operations and Azure services will not access customer data without explicit permission.

Where a service's functionality requires global data replication, details are available below.

  • Microsoft secures your data using multiple layers of security and encryption protocols. Get an overview Microsoft data security capabilities here.

    By default, Microsoft Managed Keys protect your data, and customer data that persists on any physical media is always encrypted using FIPS 140-2 compliant encryption protocols. Customers can also employ customer-managed keys (CMK), double encryption and/or hardware security modules (HSM)for increased data protection.

    All data traffic moving between datacenters is also protected using IEEE 802.1AE MAC Security Standards, preventing physical "man-in-the-middle" attacks.

    Additionally, to minimize privacy risk, Microsoft generates "pseudonymous identifiers" that enable Microsoft to offer a world class 24x7 cloud service (including operating and improving services, billing, and fraud protection). In all cases, pseudonymous identifiers cannot be used to directly identify an individual, and access to the customer data that identifies individuals is always protected as described above.

  • All Azure services can be used in compliance with the GDPR. If customers using Azure services choose to transfer content containing personal data across borders, they will need to consider the legal requirements that apply to such transfers. Microsoft provides customers with services and resources to help them comply with GDPR requirements that may apply to their operations.

    Some Microsoft services share data with third parties acting as its subprocessors to power certain online services. The publicly disclosed Microsoft Online Services Subprocessors List identifies subprocessors authorized to process customer data or personal data. All such subprocessors are contractually obligated to meet or exceed the contractual commitments Microsoft makes to its customers.

    Microsoft will not provide any third party (a) direct, blanket, or unfettered access to customers' data; (b) platform encryption keys used to secure data or the ability to break such encryption; or (c) access to data if Microsoft is aware that the data is to be used for purposes other than those stated in the third party's request. Further information on Microsoft’s approach to legal disclosure of customer data in relation to government demands is available here.

Most Azure services enable you to specify the region where your customer data will be stored. Microsoft may replicate to other regions for data resiliency, but Microsoft will not replicate or move customer data outside the geo (see Additional information on this page). You and your users may move, copy, or access your customer data from any location globally.

More information on Customer Data

Data storage for regional services

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 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 will not store customer data outside the customer-specified geo except for the following regional services:

  • Azure Cloud Services, which backs up web- and worker-role software deployment packages to the United States regardless of the deployment region.
  • 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 about Language Understanding.
  • Azure Machine Learning, which may store freeform text that the customer provides (e.g. names for workspaces, names for resource groups, names for experiments, names of files and names of images) and experiment parameters(a.k.a meta data) in the United States. Just names are stored not the assets and this is done for debugging purposes.
  • Azure Databricks, which stores identity data, and certain table names & object path information in the United States.
  • Azure Sentinel, which generates new security data—such as incidents, alert rules, and bookmarks—that may contain customer data from the customer’s instances of Azure Monitor Logs. Such security data generated by Azure Sentinel will be stored at rest in Europe (for security data generated from the customer’s Monitor Logs workspaces located in Europe) or in the United States (for security data generated from the customer’s Monitor Logs workspaces located elsewhere).
  • Preview, beta, or other prerelease services, which typically store customer data in the United States but may store it globally.

Customers may configure certain Azure services, tiers, or plans to store customer data only in a single region. These include:

1The feature to enable storing customer data in a single region is currently only available in the Southeast Asia Region (Singapore) of the Asia Pacific Geo. For all other regions, customer data is stored in Geo.

2The previewed feature to enable storing customer data in a single region is currently only available in the Southeast Asia Region (Singapore) of the Asia Pacific Geo and Brazil South (Sao Paulo State) Region of Brazil Geo. For all other regions, customer data is stored in Geo.

3For Azure Databricks, identity data, certain table names and object path information are stored in the United States. The capability to enable storing all other customer data in a single region is currently available in the Southeast Asia Region (Singapore) of the Asia Pacific Geo and Brazil South (Sao Paulo State) Region of the Brazil Geo. For all other regions, customer data is stored in Geo (subject to the aforementioned exception).

4ZRS Classic stores data in multiple regions.

Data storage for non-regional services

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

  • Azure Content Delivery Network, which provides a global caching service and stores customer data at edge locations around the world.
  • Azure Active Directory (Azure AD), which may store Azure AD data globally. This does not apply to Azure AD deployments in the United States (where Azure AD data is stored solely in the United States) and in Europe (where Azure AD data is stored in Europe or the United States). Learn more about identity storage for Europe customers in Azure AD.
  • Azure Multi-Factor Authentication, which stores authentication data in the United States. Learn more about Multi-Factor Authentication.
  • Azure Security Center, which may store a copy of security-related customer data, collected from or associated with a customer resource (e.g. virtual machine or Azure AD tenant):

    In the same geo as that resource, except in those geos where Microsoft has yet to deploy Security Center, in which case a copy of such data will be stored in the United States;

    Where Security Center uses another online service to process such data, it may store such data in accordance with the geolocation rules of that other online service.

  • 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.