Skip to content

Commit 31b3874

Browse files
authored
note
1 parent 29e0949 commit 31b3874

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

0_Azure/2_AzureAnalytics/0_Fabric/demos/38_Multi-GeoTenantCapacity.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ Last updated: 2025-03-21
3333
https://github.com/user-attachments/assets/16fd8e90-22cc-48d3-8dce-e79e4ee9789b
3434

3535
> [!NOTE]
36-
> `Multi-Geo allows you to deploy Fabric capacities in regions other than your tenant’s home region`. When you deploy a workspace in a region different from your tenant’s home region, the `workspace’s data resides` in the region of the `capacity`. But, some `metadata and control-plane operations still interact with the tenant’s home region`. This setup supports data residency compliance while maintaining centralized governance. `Egress charges between regions like West US and West US 2 are minimal, especially since they are part of the same Azure geography (United States).`
36+
> When you deploy a workspace in a region different from your tenant’s home region, the `workspace’s data resides` in the region of the `capacity`. But, some `metadata and control-plane operations still interact with the tenant’s home region`. This setup supports data residency compliance while maintaining centralized governance. `Egress charges between regions like West US and West US 2 are minimal, especially since they are part of the same Azure geography (United States).`
3737
3838
## Fabric Object Residency
3939

0 commit comments

Comments
 (0)