Skip to main content

index

Implementation Options for Fabric Landing Zones​

Landing zone implementation is a critical step in preparing for scalable and governed adoption of Microsoft Fabric. Depending on your organizational requirements, skill maturity, and operational model, multiple approaches are available.

Environment Development Approaches​

There are two main strategies to consider:

1. Start with the Microsoft Fabric Landing Zone Accelerator​

This is the recommended approach when:

  • A strong foundation in governance, security, identity, and operational best practices is needed from the start.
  • Speed of delivery is critical.
  • The team is skilled in Infrastructure-as-Code (IaC) approaches like Bicep or Terraform.

Benefits:

  • Rapid deployment of scalable environments.
  • Aligns with Microsoft’s best practices and compliance blueprints.
  • Includes modules for networking, identity, monitoring, and RBAC.

2. Customize Your Implementation​

Use this approach if:

  • You need bespoke architectural configurations.
  • Your organization wants to develop deeper internal skills.
  • You’re not constrained by immediate time-to-value.

Benefits:

  • Full flexibility in aligning to specific requirements.
  • Iterative enhancement aligned to your cloud strategy.

⚠️ Note: Even when customizing, aligning eventually with the Fabric Landing Zone conceptual architecture is highly recommended.

Fabric Landing Zone Implementation Options​

Implementation OptionDescriptionDeployment Instructions
Fabric Landing Zone AcceleratorEnterprise-ready platform foundation tailored for Microsoft Fabric. Modular Bicep templates, policy enforcement, logging, and workspace setup included.Deployment Guide on GitHub
Modular Bicep TemplatesCustomizable modules to deploy core Fabric services (e.g., Lakehouse, Pipelines, Warehouse) based on naming conventions and security settings.Bicep Modules Documentation
Terraform Modules for FabricFor teams using Terraform across environments. Mirrors best practices and governance models with reusability across platforms.Terraform Registry Modules
Microsoft Cloud for Sovereignty (Fabric)Adapted Fabric Landing Zone for public sector use. Includes enhanced orchestration and compliance policies.Cloud for Sovereignty Guide
Partner Landing ZonesCertified partner solutions aligned with Microsoft Fabric ready methodology. Useful when internal capabilities are limited.Find a Partner

Guiding Principles for All Implementation Options​

  • Security first: All options integrate with Entra ID, network isolation, and managed identity principles.
  • Governance aligned: Resource hierarchy, tagging, policy enforcement, and RBAC included or easily extendable.
  • Scalability: Designed for scale-out scenarios (multiple tenants, environments, data domains).
  • DevOps Ready: All options support CI/CD pipelines and GitOps workflows.

Let me know if you’d like Mermaid diagrams or YAML examples included for any of the approaches.

Contributors