Tenant-wide settings, capacity, governance, audit, and usage for everyone in your organization.

Scale by SKU

Scale every backing service from inside Loom. Each card hits a real Azure REST endpoint via the BFF — no portal hand-offs. Cost previews are list-price estimates from a lookup table; reserved instances and SLA surcharges are excluded. Apply is async on most services (Fabric capacity, APIM, ADX) — refresh the card after a few minutes to see the new state.
Fabric / Power BI CapacityF-SKU (F2 → F2048) for Fabric; P-SKU for Power BI Premium.
Synapse Dedicated SQL Pool (DWU)DW100c → DW30000c — scale-out via ARM PATCH on sqlPools/{n}.
Azure Data Explorer (ADX)vCore tier (Dev / E2 / E4 / E8 / E16 / E64) + capacity.
Databricks SQL Warehousecluster_size (2X-Small → 4X-Large) via /api/2.0/sql/warehouses/{id}/edit.
Databricks Clusternode_type_id + num_workers via /api/2.0/clusters/edit.
Azure AI SearchSKU (S0/S1/S2/S3/S3HD) + replicas + partitions.
API ManagementSKU (Developer / Basic / Standard / Premium / *V2) + capacity.
Cosmos DB containersPer-container RU/s (manual) or autoscale max RU/s.
Container Apps (Loom services)workload profile (Consumption / D-/E-series) + replicas.
AI Foundry — AML computevmSize + min/max nodes for AmlCompute targets.
Utilization metrics deferred
Current-utilization indicators (DBU / CPU / req-rate / RU consumption) require Azure Monitor metrics per resource — that's a separate piece of work. Today this page surfaces only the dial; the admin runs the scale decision themselves. Per .claude/rules/no-vaporware.md we do not show AI-hallucinated utilization numbers.