Dynamics 365 for Retail can be deployed into the Microsoft Azure datacenters (also referred to as “regions”) listed below.
With Dynamics 365 for Retail, customers can specify the region where their customer data will be stored. Microsoft may replicate customer data to other regions available within the same geography for data durability, except as specified below. No matter where customer data is stored, Microsoft does not control or limit the locations from which customers or their end users may access customer data.
|Australia||Australia East (New South Wales)
Australia Southeast (Victoria)
|Asia Pacific||East Asia (Hong Kong)
Southeast Asia (Singapore)
|Brazil||Brazil South (São Paulo State)1|
|Canada||Canada Central (Toronto)
Canada East (Québec City)
|Europe||North Europe (Ireland)
West Europe (Netherlands)
|India||Central India (Pune)
South India (Chennai)
West India (Mumbai)
|Japan||Japan East (Tokyo, Saitama)
Japan West (Osaka)
|United States||East US (Virginia)
East US 2 (Virginia)
North Central US (Illinois)
Central US (Iowa)
South Central US (Texas)
West Central US (Utah)
West US (California)
West US 2 (Washington)
|United Kingdom (UK)||UK South (London)
UK West (Cardiff, Durham)
Storing customer data
Microsoft will not transfer customer data outside the selected Azure geographic location (geo) for Dynamics 365 for Retail 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:
- Dynamics 365 home page, which stores application names, descriptions, and logos globally for performance;
- Azure Active Directory, 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 Office 365 Admin Center. You can find more information here;
- Services that provide global routing functions and do not process or store customer data. This includes Azure DNS, which provides domain name services that route to different regions; or
- Preview, beta, or other pre-release services, which typically store customer data in the United States but may store it globally.
- Customer data that is stored locally in the Retail Server Scale Unit (RSSU) is synchronized to the production instance location the customer has chosen based on the above section “Azure regions where Dynamics 365 for Retail can be deployed.”
The administration portal for Dynamics 365 for Retail known as Microsoft Dynamics Lifecycle Services (LCS), stores certain customer data on servers located in the United States such as:
- Your code or metadata, and data packages (e.g., master or application configuration data) to support the Dynamics 365 for Retail 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.
- Dynamics 365 for Retail collects usage and diagnostic logs where customer data is stored in the United States.
Customers configure external services to extend Dynamics 365 for Retail such customer configurations may cause customer data to be transferred outside of the selected geo. Examples of customer configurable external services include:
- Machine Learning Cognitive Services: If features that use cognitive services are activated, customer data for domains such as product recommendations and demand forecasting can be synchronized outside of the configured region. Use of these features is optional. You can find more information here.
- Data integration: Configuration of Dynamics 365 for Retail data management features that work with external services (whether provided by Microsoft or a third party) may result in the transfer of core customer data outside of the region configured for the production environment to a geographic location that customers designate. You can find more information here.
- Microsoft Power BI, Microsoft PowerApps, and Microsoft Flow: Customers who connect their Power BI, PowerApps, or Flow deployment to Dynamics 365 for Retail may send customer data outside of the designated region to the geographic area where their Power BI, PowerApps, or Flow is deployed. You can find more details here.
- Microsoft Visual Studio Team Services: Customers can choose where to store custom code, metadata, and data assets that support their Dynamics 365 Retail implementation. You can find more information about the availability of Visual Studio Team Services here.
Frequently asked questions
You can find the details for current and planned availability of country localization and language in the Product availability, localization and translation guide.