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

MCP Servers

Browse, deploy, and connect Model Context Protocol (MCP) servers so Loom Copilot can call their tools — including the curated Microsoft MCP servers and ~30 Microsoft agent skills that ground Copilot in Azure-native tools.Every Microsoft/Azure remote server is on by default (opt-out) — Microsoft Learn is connected day-one with no auth, and the rest go live as their per-user Microsoft Entra On-Behalf-Of consent, GitHub PAT (Key Vault), or GA endpoint is satisfied; until then each shows an honest gate naming the exact env var, scope, or secret to provide. Disable any server per-tenant from its Configure dialog. Microsoft Fabric / Power BI MCP servers are the one exception — they never sit on a default path (no-fabric-dependency).
External MCP Tools
Loom IQ — published MCP surface