Where your Microsoft Dynamics 365 for Talent data is stored

Microsoft will not transfer customer data outside the selected Azure geographic location for Dynamics 365 for Talent except when:

• It is necessary for Microsoft to provide customer support, troubleshoot the service, or comply with legal requirements.
• The customer uses a Microsoft service that is designed to operate globally including the following:
  • Dynamics 365 home page, which stores application names, descriptions, and logos globally for performance;
  • Dynamics 365 for Talent provisioning service¹ stores a list of environments accessible to each user, which is stored in the United States;
  • 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 Traffic Manager, which provides load balancing, and 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.
• The administration portal for Dynamics 365 for Talent, known as Microsoft Dynamics Lifecycle Services (LCS)¹, stores certain customer data on servers located in the United States such as:
  • Data packages (e.g., master or application configuration data) to support the Dynamics 365 for Talent application lifecycle;
  • Business process models and task guides;
  • Usage and diagnostics logs collected 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 Talent collects usage and diagnostic logs where customer data is stored in the United States.
• Customers configure external services to extend Dynamics 365 for Talent, such customer configurations may cause customer data to be transferred outside of the selected geo. Examples of customer configurable external services include:
  • Data integration: Configuration of Dynamics 365 for Talent 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 Talent 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.