Identity data storage for European customers in Azure Active Directory

Identity data is stored by Azure AD in a geographical location based on the address provided by your organization when subscribing for a Microsoft Online service such as Microsoft 365 and Azure. For information on where your identity data is stored, you can use the Where is your data located? section of the Microsoft Trust Center.

For customers who provided an address in Europe, Azure AD keeps most of the identity data within European datacenters. This document provides information on any data that is stored outside of Europe by Azure AD services.

Microsoft Azure AD Multi-Factor Authentication

For cloud-based Azure AD Multi-Factor Authentication, authentication is complete in the closest datacenter to the user. Datacenters for Azure AD Multi-Factor Authentication exist in North America, Europe, and Asia Pacific.

  • Multi-factor authentication using phone calls originate from US datacenters and are routed by global providers.
  • Multi-factor authentication using SMS is routed by global providers.
  • Multi-factor authentication requests using the Microsoft Authenticator app push notifications that originate from EU datacenters are processed in EU datacenters.
    • Device vendor-specific services, such as Apple Push Notifications, may be outside Europe.
  • Multi-factor authentication requests using OATH codes that originate from EU datacenters are validated in the EU.

For more information about what user information is collected by Azure Multi-Factor Authentication Server (MFA Server) and cloud-based Azure AD MFA, see Azure Multi-Factor Authentication user data collection.

Password-based Single Sign-On for Enterprise Applications

If a customer creates a new enterprise application (whether through Azure AD Gallery or non-Gallery) and enables password-based SSO, the Application sign in URL, and custom capture sign in fields are stored in the United States. For more information on this feature, please refer to Configure password-based single sign-on

Microsoft Azure Active Directory B2C (Azure AD B2C)

Azure AD B2C policy configuration data and Key Containers are stored in U.S. datacenters. These do not contain any user personal data. For more info about policy configurations, see the Azure Active Directory B2C: Built-in policies article.

Microsoft Azure Active Directory B2B (Azure AD B2B)

Azure AD B2B stores invitations with redeem link and redirect URL information in US datacenters. In addition, email address of users that unsubscribe from receiving B2B invitations are also stored in U.S. datacenters.

Microsoft Azure Active Directory Domain Services (Azure AD DS)

Azure AD DS stores user data in the same location as the customer-selected Azure Virtual Network. So, if the network is outside Europe, the data is replicated and stored outside Europe.

Federation in Microsoft Exchange Server 2013

  • Application identifier (AppID) - A unique number generated by the Azure Active Directory authentication system to identify Exchange organizations.
  • Approved Federated domains list for Application
  • Application’s token signing Public Key

For more info about federation in Microsoft Exchange server, see the Federation: Exchange 2013 Help article.

Other considerations

Services and applications that integrate with Azure AD have access to identity data. Evaluate each service and application you use to determine how identity data is processed by that specific service and application, and whether they meet your company's data storage requirements.

For more information about Microsoft services' data residency, see the Where is your data located? section of the Microsoft Trust Center.

Next steps

For more information about any of the features and functionality described above, see these articles: