Select Microsoft Fabric regions for a migration

Choosing the right Microsoft Fabric region is a critical step in ensuring compliance, performance, and availability of your data workloads. This guidance helps you navigate Fabric-specific considerations like OneLake data residency, regional service availability, and sovereignty requirements.

Document your scenario complexity

Region	Country/region	Local employees	Local external users	OneLake region support	Data sovereignty requirements
West Europe	Netherlands	Yes	Partners and customers	Yes	No
Switzerland North	Switzerland	Yes	Customers	Yes	Yes (Federal)
Germany West Central	Germany	Yes	Government entities	Yes	Yes (BDSG, EU-GDPR)
North Europe	Ireland	No	Partners	Yes	No

Why is the location of users relevant?

Fabric services like Power BI, Data Activator, and Real-Time Intelligence heavily rely on low-latency access. If your users are far from the selected Fabric region or data resides in a different OneLake location, performance degradation may occur.

Why is the location of datacenters relevant?

Microsoft Fabric's OneLake is region-bound for compliance reasons. Data imported or transformed in Fabric is physically stored in the region where the workspace resides. Migration to another region requires data movement and new regional capacity allocation.

Region-to-region replication and backup

Fabric currently doesn't support region-to-region replication natively. Cross-region backup and recovery must be orchestrated via Fabric APIs, Azure Storage replication, or third-party solutions. Always validate recovery plans manually.

Design for compliance

For regulated industries, confirm that the chosen Fabric region supports Microsoft Purview, Customer-managed keys (CMK), and data residency restrictions via Microsoft Trust Center. For European public sector clients, consider sovereign landing zones with Fabric in German or Swiss regions.

[!TIP] For a list of supported Fabric regions and services, visit Microsoft Fabric region availability.