Deploy supporting services for Microsoft Fabric workloads

Overview

Every Microsoft Fabric workload requires several supporting services across data governance, monitoring, networking, identity, and cost management. Unlike traditional IaaS migrations, Fabric workloads are SaaS-based and integrated into OneLake, requiring careful orchestration of supporting services at the tenant, workspace, and capacity levels.

Before deploying a Fabric solution, ensure your landing zone is ready, your workspace and capacity design is complete, and your governance and tagging models are in place.

Plan supporting services deployment

When to deploy supporting services

Plan the deployment of supporting services according to their cost model and readiness dependencies:

• Deploy early:

  • Microsoft Purview accounts and collections
  • Azure Monitor Logs workspace (shared or dedicated)
  • Azure Key Vault (for credentials and secrets)
  • Fabric capacities (P1/F64 etc.) and associated Power BI tenants
  • Azure Data Factory integration runtimes (if needed)

• Deploy on-demand / pause-able:

  • Eventstream ingestion endpoints
  • Data pipelines and Lakehouse staging scripts
  • Azure DevOps or GitHub Actions integration for deployment

• Deprovision after use:

  • Testing endpoints (e.g. temporary Fabric KQL endpoints)
  • Test capacities used during migration waves

Use Infrastructure as Code (IaC) with Bicep or Azure CLI scripts for reproducibility.

Required supporting services

Area	Required Services
Resource Organization	Workload subscription (optional if centralized), Fabric workspaces, well-named Lakehouses/Datasets
Networking	Eventstream endpoints (public/private), optional integration with Azure Private Link, secured ingestion zones
Identity & Access	Entra ID security groups, service principals for automation, Microsoft Purview role assignments
Security	Key Vault for secrets, governance rules in Fabric, Azure Policy (via management groups) for enforcement
Monitoring	Azure Monitor (Log Analytics), Kusto-based logging for Eventstream / Lakehouse, Cost Management tagging
Cost Management	Azure Cost Management + Power BI integration, tagging strategy applied to Fabric items (via Metadata)
Management & Deployment	Azure DevOps/GitHub CI/CD, Microsoft Fabric REST API and CLI, workspace templates

Additional recommendations

• Align capacity planning with usage profiles: assign workloads to P SKUs or F SKUs accordingly.
• Use Fabric CLI to automate workspace and artifact creation.
• Use Azure Landing Zone Bicep Modules to preconfigure governance and monitoring structures.
• Coordinate closely with your Entra ID and Microsoft Purview administrators to configure access roles before workload deployment.

Also review the Prepare for management section to understand how to maintain Fabric workloads post-deployment.