Tenant-wide settings, capacity, governance, audit, and usage for everyone in your organization.
Capacity & compute
Underlying Azure services Loom orchestrates. Live inventory from Azure Resource Manager, month-to-date cost from Cost Management, and 24h utilization from Azure Monitor — no hardcoded counts or numbers. Select a row for full metric charts. Where Cost Management or a platform metric is unavailable (e.g. some Azure Government offers), the cell shows an honest gate, never a fake value.
A capacity here is the pool of Azure compute + storage that backs your Loom workloads — the resources listed below are what actually run your lakehouses, warehouses, pipelines, and analytics. Loom is Azure-native, so a "capacity" is one or more of these services rather than a single Microsoft Fabric SKU.
SKUs & equivalents — where Fabric uses one F-SKU dial (F2–F2048), Loom sizes each service on its own scale: Synapse DWU, ADX vCore tiers, Databricks cluster sizes, AI Search replicas/partitions. Roughly, an F64 of Fabric compute maps to a mid-tier Synapse pool plus an ADX cluster.
Pause / resume & cost — most engines can pause (Synapse dedicated pools, ADX, Databricks auto-terminate) so idle compute stops billing while data persists. Month-to-date cost per resource comes live from Azure Cost Management; 24h utilization comes from Azure Monitor.
