Dynamics 365 Business Central (previously known as Dynamics 365 for Finance and Operations, Business edition) can be deployed into the Microsoft Azure datacenters (also referred to as “regions”) listed below.
With Dynamics 365 Business Central, customers select a country on sign-up, and this specifies the geography (also referred to “geo”) where their customer data will be stored. Microsoft may replicate customer data to other regions available within the same geography for data durability. 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.
Canada Central (Toronto)
Canada East (Québec City)
|European Union||North Europe (Ireland)
West Europe (Netherlands)
|France||France Central (Paris)
France South (Marseille)
|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 Business Central except when:
- It is necessary for Microsoft to provide customer support, troubleshoot the service, or comply with legal requirements.
Customer uses 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 could store customer data outside of the provisioned geo.
- Dynamics 365 Business Central collects usage and diagnostic logs where customer data is stored in the United States.
Customers configure external services to extend Dynamics 365 Business Central such customer configurations may
cause customer data to be transferred outside of the selected geo. Examples of customer configurable external services
- Machine Learning Cognitive Services: If features that use cognitive services are activated, customer data could be synchronized outside of the configured region. Use of these features is optional. You can find more information here.
- Extensions and integrations: Configuration of Dynamics 365 Business Central to work with external services (whether provided by Microsoft or a third party) may result in the transfer of customer data outside of the region configured for the production environment. You can find more information here.
- Microsoft Power BI, Microsoft PowerApps, Microsoft Exchange and Microsoft Flow: Customers who connect their Power BI, PowerApps, Exchange or Flow deployment to Dynamics 365 Business Central 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.
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.