{"id":12980,"date":"2026-09-29T00:00:00","date_gmt":"2026-09-29T07:00:00","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/cosmosdb\/?p=12980"},"modified":"2026-09-25T06:34:54","modified_gmt":"2026-09-25T13:34:54","slug":"announcing-public-preview-for-azure-cosmos-db-in-fabric-database-hub","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/cosmosdb\/announcing-public-preview-for-azure-cosmos-db-in-fabric-database-hub\/","title":{"rendered":"Announcing Public Preview for Azure Cosmos DB in Fabric Database Hub!"},"content":{"rendered":"

Azure Cosmos DB support in Fabric Database Hub<\/strong><\/a> is now available in public preview.<\/p>\n

For the first time, Azure Cosmos DB customers can discover and monitor their accounts from Database Hub alongside other Microsoft database engines.<\/p>\n

Database Hub provides a single place to view every Azure Cosmos DB account you can access, compare health and performance, review key security findings, and create new accounts. Your accounts remain in their existing subscriptions, resource groups, and regions.<\/p>\n

A single view of your Azure Cosmos DB estate<\/strong><\/h2>\n

\"Database<\/p>\n

Most Azure Cosmos DB customers do not operate a single account. Accounts accumulate across subscriptions, regions, and API types, and they are frequently owned by different application teams. Answering an estate-level question, such as which accounts are approaching their provisioned throughput, has generally meant opening the Azure portal one account at a time or building a reporting layer over Azure Monitor.<\/p>\n

Database Hub provides that view natively, and there is nothing to onboard to get it. Baseline discovery and monitoring do not require moving data into Fabric, configuring mirroring, enabling Cosmos DB Fleet Analytics, or turning on diagnostic logs. Database Hub reads the Azure Monitor platform metrics that Azure already collects for your accounts. If your identity has Reader access to a subscription, its accounts appear.<\/p>\n

What’s in the preview<\/strong><\/h2>\n

\"The<\/p>\n

Account discovery in Estate.<\/strong> Filter your inventory to Azure Cosmos DB and browse or search the accounts you have access to. Each entry represents a database account, with its subscription, resource group, and region.<\/p>\n

\"Database\n\"The<\/p>\n

Fleet health in Overview, detail in Performance.<\/strong> Overview summarizes availability and normalized RU consumption across the accounts in view. Performance compares accounts you select, with charts and a sortable grid covering normalized RU consumption, total request units, throttled requests, provisioned throughput, and average server-side latency. Metric coverage varies by API type and account configuration.<\/p>\n

\"Security<\/p>\n

Security findings for three signals.<\/strong> The security card evaluates whether an account enforces Microsoft Entra ID authentication, whether customer-managed keys are enabled, and whether public network access is enabled. These are triage signals rather than a complete security assessment, and they do not replace Microsoft Defender for Cloud.<\/p>\n

\"The<\/p>\n

Create an Azure Cosmos DB for NoSQL account.<\/strong> Choose a subscription, resource group, region, and workload type, and optionally set a throughput cap. The flow creates the account itself. Databases and containers, along with throughput, partition key, and indexing, are configured in the Azure portal or the Azure Databases extension for Visual Studio Code.<\/p>\n

Limitations<\/strong><\/h2>\n