Sovereign AI for Business

Microsoft EU Data Boundary: EU data residency for Microsoft clouds

The most detailed data-residency commitment from a US cloud. It settles where data is processed; it does not change who owns the provider.

Contents
  1. What the EU Data Boundary covers
  2. Strengths and limits
  3. Pricing
  4. Questions to ask Microsoft or your partner
  5. Sources
TypeUS cloud with EU data commitments
HeadquartersRedmond, Washington, US
PricingPublished
Websitelearn.microsoft.com

The EU Data Boundary is Microsoft's commitment to store and process customer data and personal data for its enterprise online services, including Azure, Dynamics 365, Power Platform and Microsoft 365, within the EU and EFTA, subject to limited circumstances in which data is still transferred⁠1.

Best for: Companies committed to Microsoft 365, Azure or Dynamics 365 that want customer data stored and processed in the EU and EFTA.

Not the right fit for: Companies whose definition of sovereignty excludes a US-headquartered provider, or that want to own and move the system.

What the EU Data Boundary covers

The boundary consists of the EU and EFTA countries, and Microsoft lists data centres in fifteen of them, from Austria to Switzerland. Personal data in system-generated logs must be pseudonymised. Scope depends on the service: Azure regional services deployed in an EU region are in scope; Microsoft 365 customers are in scope by sign-up location, except those with Multi-Geo capabilities; and Dynamics 365 and Power Platform customers must both provision in the EU and EFTA region and keep an EU billing address⁠1.

For companies already on Microsoft 365, this is the lowest-effort way to address data location. It does not address ownership of the system or the provider's US headquarters, which our guide to EU data rules explains.

Strengths and limits

Strengths

  • Covers the productivity and business applications many companies already run.
  • Microsoft documents the limited cases in which data is still transferred outside the boundary.
  • Personal data in system-generated logs must be pseudonymised, according to Microsoft.

Limits

  • Transfers outside the boundary continue in limited, documented circumstances.
  • Microsoft 365 tenants with Multi-Geo capabilities are out of scope even when located in the EU.
  • The provider is US-headquartered, which matters to buyers concerned about US legal reach.

Choose another option if: You want to own the system and move it between hosts, or your definition of sovereignty requires a European-owned provider.

Pricing

Not priced separately; part of Microsoft’s enterprise online services.

Questions to ask Microsoft or your partner

  • Are all the services we use, including AI features, in scope for the EU Data Boundary?
  • Which of the documented transfers apply to our tenant?
  • Does our licence include Multi-Geo, which would take us out of scope?
  • How is support access to our data handled from outside the boundary?

See how the EU Data Boundary compares with the other options in the main guide.

Sources

  1. What is the EU Data Boundary?. Microsoft Learn, 21 Jul 2026. Accessed 8 Nov 2026.