Skip to main content

Prepare for Microsoft Fabric adoption

Before Microsoft Fabric workloads can be migrated or built natively, a structured and governed environment must be prepared. In Azure, this concept is known as a Landing Zone. In Microsoft Fabric, the same principles apply, but are reinterpreted to match the SaaS architecture and workspace-based model.

Rethinking Landing Zones for Microsoft Fabric​

In Azure, a landing zone encompasses subscriptions, policies, management groups, and networking. In Fabric, we apply the concept to workspace provisioning, capacity planning, governance setup, and resource deployment pipelines.

The Fabric Landing Zone serves as a standardized, ready-to-use environment that enables secure, scalable, and compliant project execution across departments or teams. While Fabric simplifies infrastructure, careful preparation is still required to avoid sprawl, security issues, and inefficient usage.

Key Fabric-specific adaptations of the landing zone concept include:

  • Bootstrap your Fabric environment
    Set up Fabric capacities, connect Entra ID (Azure AD), and define workspace structure. Use CLI commands like az fabric admin create to automate workspace and capacity setup.

  • Deploy Fabric platform configurations
    Apply global policies, assign administrators, configure Microsoft Purview, and create default Power BI and Data Factory artifacts.

  • Workspace vending
    Use templates or DevOps pipelines to deploy new development, test, and production workspaces consistently. Assign capacities and security groups via Infrastructure-as-Code approaches like YAML, Git repos, or Terraform (via REST proxies).

  • Deploy workloads
    Use Fabric Deployment Pipelines or GitOps-based approaches to release Lakehouses, Datasets, Notebooks, and Reports into the target workspaces and capacities.

Fabric Landing Zone Journey​

From Readiness to Execution​

This Ready phase of the Fabric Adoption Framework prepares the technical foundation needed for governed, secure, and agile deployments in Fabric. It aligns closely with the following companion chapters:

By the end of this phase, your Fabric environment will be ready to support innovation and scale through controlled workspace provisioning, consistent governance, and clearly defined release processes.

Contributors