Share via

Microsoft Dynamics 365 and Power Platform data residency documentation

The purpose of this document is to provide comprehensive information about data residency and customer data storage for Dynamics 365 and Power Platform.

Overview

Microsoft Dynamics 365 and Power Platform are integrated cloud solutions that help organizations analyze data, automate workflows, and build intelligent agents. Dynamics 365 delivers enterprise-grade CRM and ERP capabilities. Power Platform empowers users to create low-code apps, automate processes, and gain insights.

Products covered

This document encompasses the Dynamics 365 and Power Platform products outlined below.

Dynamics 365

Power Platform

Other

Where your Microsoft Dynamics 365 and Power Platform customer data is stored

Customer data for Microsoft Dynamics 365 and Power Platform is stored in Microsoft Azure datacenters located in various geographic regions around the world. Customers can choose the region (also referred to as "geo") where their customer data will be stored.

Microsoft may replicate customer data to other regions within the same geo for data durability, except where otherwise specified.

Regions where Microsoft Dynamics 365 and Power Platform can be deployed

Explore service availability and deployment regions in Dynamics 365 and Power Platform Availability Reports.

Note

  • Because there is only one region in Brazil, customer data in Brazil South may be replicated to South Central US (Texas) for disaster recovery purposes.

  • For China-specific information, learn more here.

Storing customer data at rest in geo

Microsoft will store customer data at rest in the selected Azure geographic ___location (geo) for Dynamics 365 and Power Platform products except when:

  • It is necessary for Microsoft to provide customer support, troubleshoot the service, or comply with legal requirements.

  • Customers use services that are designed to operate globally, including the following services:

    • Dynamics 365 and Power Platform home page and admin center portals, which store application names, descriptions, and logos globally for performance.

    • Entra ID which may store Active Directory data globally.
      You can find more information here.

    • Azure Multi-Factor Authentication, which may store multi-factor authentication data globally.
      You can find more information here.

    • Customer data collected during the onboarding process by the Microsoft 365 Admin Center.
      You can find more information here.

    • Content Delivery Network (CDN), which provides a global caching service and stores customer data at edge locations around the world.

    • Dataverse table and column names (formerly called entity and field names) are replicated globally for support and troubleshooting purposes, but the content within those database tables remains stored in geo.

    • Services that provide global routing functions and do not process or store customer data. This type of service includes Azure DNS, which provides ___domain name services that route to different regions.

    • Preview, beta, or other pre-release services, which typically store customer data in the United States but may store it globally.

Customers use features that are powered by Microsoft 365 services as described in product documentation. For these features, data will be transferred to Microsoft 365 services and governed by Microsoft 365 terms and data residency commitments.

  • Customers may also configure external services to extend Dynamics 365 products and Power Platform functionality. These configurations may cause customer data to be transferred outside of the selected geo. Examples include:

    • Machine Learning Cognitive Services: If features using cognitive services are activated, customer data for domains such as product recommendations and demand forecasting may be synchronized outside of the configured region. Use of these features is optional. You can find more information here.

    • Data integration: When using Dynamics 365 or Power Platform to work with external services (Microsoft or third-party), customer data may be transferred outside the configured production environment to a geographic ___location designated by the customer.
      Microsoft Power Apps, and Microsoft Power Automate: When connected to Dynamics 365 products, customer data may be sent outside of the designated region to where these services are deployed.

    • Azure Dev Ops: Customers can choose where to store custom code, metadata, and data assets that support their Dynamics 365 implementation. You can find more information about the availability of Visual Studio Team Services here.

    • Microsoft Dynamics Lifecycle Services: The administration portal stores certain customer data on servers located in the United States such as:

      • Your code or metadata, and data packages (for example, master or application configuration data) to support application lifecycle;

      • Business process models and task guides;

      • Usage and diagnostic logs during the application lifecycle process; and Content related to support requests submitted to Microsoft such as support issues, service requests, and hotfix requests.

    • Additionally, certain types of customer data specifically the application name, application description, and application logo will be stored globally.

Regardless of where the customer data is stored, Microsoft does not control or restrict the locations from which customers, or their end users, may access customer data.

The following products contain additional product-specific scenarios where customer data may be stored outside the selected geo. These variations reflect distinct features or positioning relevant to each service.

Product-specific considerations

Product Key variation
Dynamics 365 Customer Insights Email and content delivery may operate globally. Custom schema/display names may be referenced globally, but field values remain in-geo.
Dynamics 365 Finance Electronic invoicing may involve cross-geo transfers.
Dynamics 365 Commerce CSU data syncs to the production instance. Fraud Protection may process data globally.
Dynamics 365 Human Resources Provisioning service stores environment lists in the US. Teams integration may transfer data to the Teams service region.
Power Pages Website name and URL are stored globally.
Copilot Studio If tenant ___location is not listed, data is stored in the US; for France, data is stored in Europe. External configurations (for example, Customer Service hand-off, Facebook, Teams) may transfer data.
Dynamics 365 Contact Center Use of Azure Communication Services for telephony and messaging purposes. In this case, customers do have the ability to choose the ___location where transcription and recordings are temporarily stored. The permanent storage of this data still resides in the geo where the Contact Center operates.
Dynamics 365 Remote Assist and Guides Calling and collaboration features may send customer data to the geo where customer’s Teams service is deployed.

Additional resources