CSA LoomCSA Loom
Home
Ctrl K
Sign in
HomeWorkspacesBrowse
Lakehouse catalogSearchMarketplaceData productsConnectionsGovernance
Real-Time IntelligenceData ScienceOrchestration (Warp)Estate builderAgent MeshDeveloper
DeploymentWorkload hubScheduler
LineageAssetsMonitorReportsCopilot
  1. Home
  2. Admin portal

Tenant-wide settings, capacity, governance, audit, and usage for everyone in your organization.
Reliability & performanceHealth & ReliabilityPerformance & benchmarksReal-user monitoringReadinessDiagnosticsIncident console
Capacity & costCapacity & computeScale by SKUFinOps & chargeback
Configuration & gatesTenant settingsRuntime configurationGate registryRuntime flagsAPI Management
Catalog & domainsExternal-engine federation (Iceberg)DomainsCustom attributes
Access & security governanceSecurity & governancePolicy as codeFeature permissionsAccess governanceBatch labelingEmbed codesOrganizational visualsDSPM for AI
AI operationsAI operationsAutopilotMCP Servers
Audit & usageAudit logsUsage metricsEvent subscriptionsAPI tokens
Platform (network / updates)MigrateDeployment plannerLanding zonesUsers & licensesWorkspacesNetwork & DNSUpdates & version sync

Runtime configuration

These are the deployment environment variables that turn Loom features on and point them at your Azure services — set them here instead of the Azure portal's Container Apps → Environment variables blade. Each key is grouped by what it drives:
  • Identity & session — Entra app + session settings that gate sign-in and tenant-admin access.
  • Data plane — the Cosmos endpoint + containers that are Loom's own store.
  • Azure services — the AOAI, Synapse, ADX, Event Hubs, AI Search, and related endpoints each editor calls; a feature that isn't wired shows an honest gate naming the exact key to set.
  • Permissions & security posture — Purview account, role-assignment principals, and security toggles.
Values are stored as desired-state — every Save persists to Cosmos and applies a real ARM PATCH (a new container-app revision).
Power BI backendOpt in to the Fabric-family Power BI path for BI models and reports. Azure-native is the default.
Azure MapsRuntime config for the geo / tapestry / map editors' live basemap. No build var — set it here.