Where an organization's Customer Service Insights data is located

Customer Service Insights can be deployed into the Microsoft Azure datacenters (also referred to as “regions”) listed below.

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.

Data locations

Azure geographic areas (geos) Azure datacenters (regions)
Europe West Europe (Netherlands)
North Europe (Ireland)
United States East US (Blue Ridge, VA)
South Central US (Des Moines, IA)
West US (Quincy, WA)
Australia Australia East (New South Wales)
Australia Southeast (Victoria)
Asia Pacific Southeast Asia (Singapore)
East Asia (Hong Kong)
United Kingdom UK South (London)
UK West (Cardiff, Durham)
Brazil Brazil South (São Paulo State)
Canada Canada Central (Toronto)
Canada East (Québec City)
India Central India (Pune)
South India (Chennai)
Japan Japan East (Tokyo, Saitama)
Japan West (Osaka)
France France Central (Paris)
Framce South (Marseille)

Customer data at rest in geo

Microsoft will not transfer customer data outside the selected Azure geographic location (geo) for Dynamics 365 Customer Service Insights 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:
    • Email marketing sending used to send marketing messaging globally as configured by the customer.
    • 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.
    • Additionally, certain types of customer data (specifically the application name, application description, and application logo) will be stored globally, rather than in the primary storage geo.
  • Customers configure external services to extend Dynamics 365 for Customer Service Insights 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 Customer Service Insights 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 Customer Service Insights 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 for Customer Service Insights implementation. You can find more information about the availability of Visual Studio Team Services here.
    • Dynamics 365 Customer Engagement geo to geo migration: Customers can request to change the geo location of their Dynamics 365 Customer Engagement instance by doing a geo to geo migration. However, this action will not automatically migrate your Dynamics 365 Customer Service Insights (CSI) workspaces created before the geo to geo migration. As a result, such CSI workspaces may be in a different geo location than your other Dynamics 365 Customer Engagement data. CSI workspaces created after the geo to geo migration will be in the same region as the rest of your Dynamics 365 Customer Engagement instance. You can find more information here.