About This Architecture

DTP Microsoft Fabric Landing Zone Future State orchestrates a phased migration of 236 in-scope Power BI workspaces across distributed Premium and Fabric capacities in Australia. Source Premium Capacity P3 (Australia Southeast) feeds 229 portable workspaces into Primary Fabric Capacity F128 (Australia East) via Power BI Admin API bulk reassignment and Fabric Core REST API, while Secondary Fabric Capacity F2 (Australia Southeast) retains non-Power BI items—Lakehouse, Warehouse, Notebooks, Data Pipelines—to avoid cross-region latency. Identity and Operations governance through Entra Tenant, Capacity Administrators, and Migration Operators ensures controlled decommissioning post-validation, with comprehensive monitoring via Fabric Capacity Metrics App and Azure Log Analytics. This architecture demonstrates best-practice multi-region capacity planning, blast-radius isolation, and IaC-driven control planes for enterprise Fabric migrations. Fork, customize, and embed this diagram to document your own landing zone topology, capacity allocation strategy, and migration wave sequencing.

People also ask

How do you design a multi-region Microsoft Fabric landing zone to migrate Power BI workspaces while maintaining governance and avoiding cross-region latency?

The DTP Fabric Landing Zone Future State uses distributed capacities—Primary F128 in Australia East for portable workspaces, Secondary F2 in Australia Southeast for non-Power BI items—with Entra Tenant identity controls, Power BI Admin API bulk reassignment, and phased decommissioning post-validation to isolate blast radius and optimize regional performance.