A man monitors a colorful cloud infrastructure dashboard on a large screen in a neon-lit office.
Microsoft says Database Hub in Microsoft Fabric is now generally available. It is the company's attempt to give database teams one place to see, monitor and investigate a sprawling database estate. For admins, the less obvious news is that the tenant setting is on by default from the same day.

Microsoft announced the general availability of Database Hub in Microsoft Fabric on November 17, 2026. The Fabric "What's new" page agrees. It lists Database Hub among November 2026 generally available features, describing a unified operational experience across Azure, Fabric, on-premises and supported multicloud environments.

A man monitors a colorful cloud infrastructure dashboard on a large screen in a neon-lit office. From early access to GA in about eight months​

The feature has moved quickly. Microsoft introduced it at FabCon and SQLCon 2026 as "now available in early access." Database Hub went to public preview at Microsoft's European Fabric and SQL conference in Barcelona on September 28. The GA announcement comes roughly seven weeks after that.

The pitch is the same throughout. Many organizations now run hundreds or thousands of databases across cloud, hybrid and multicloud environments. The signals about inventory, health, performance, security and optimization already exist. The hard part is turning them into a decision about what to fix first.

What is generally available​

Microsoft's launch post lists these GA capabilities:

  • Overview: a "what needs attention" view across security, performance and optimization. It shows top issues and recent signal changes across SQL, PostgreSQL and Cosmos DB.
  • Estate inventory: a single inventory of supported Azure and Fabric databases, with their issues and suggestions.
  • Performance monitoring: near real-time CPU, memory and storage trends, aggregated across the estate and per resource. Cosmos DB also gets normalized RU and throttled-request views.
  • Security posture: findings such as public network access, missing private endpoints, Microsoft Entra authentication, audit logging and customer-managed keys.
  • Investigation: drill-down from any finding into the affected resource, real-time dashboards and the tools you already use.

New with GA​

  • Bulk performance monitoring enablement. From the Estate view you can select many resources and turn on performance data collection in one step. This removes per-database setup. Once collection is on, monitored resources appear in Performance Monitoring and the real-time dashboards.
  • Optimization insights. These sit alongside security and performance. They flag resources with a migration assessment ready, license-model opportunities such as pay-as-you-go, and SQL Server instances that aren't reporting usage. They are things to review, not automatic changes.
  • Real-time dashboards. Dashboards for Microsoft SQL, Azure Database for PostgreSQL and Azure Cosmos DB move from preview to GA.
  • SSMS and VS Code entry points. You can open Database Hub from SQL Server Management Studio and from the Microsoft and MSSQL extensions for VS Code. You land in the same estate view with the resources you were working on.
  • Database Hub CLI skill. You can ask about inventory, health, performance and security posture from GitHub Copilot CLI, VS Code Copilot, Claude Code or Cursor. Microsoft's install command is skills-for-fabric --skill databasehub-cli. Its example prompts are "How is my database estate doing?" and "Which databases need attention this week?"

Still in preview​

Not everything in the launch post is GA. Microsoft marks four adjacent features as preview:

  • Copilot investigation of your estate (public preview)
  • Database Agents (public preview). They watch databases you choose, stay quiet while those databases are healthy, and raise an issue with evidence and a recommendation when something needs human judgment. The operator decides what happens next.
  • Alerts for Azure SQL Database (public preview). These are built from templates or performance charts and can send a Teams message or start a Power Automate flow. They are powered by Fabric Activator.
  • Performance monitoring for SQL Server on Azure VMs (preview)

If you plan to rely on the AI and alerting parts, treat "Database Hub is GA" as a statement about the core hub only.

Licensing and cost​

Microsoft says new Fabric users who open Database Hub are automatically given a free Fabric license and taken straight to their estate. The post adds that Fabric capacity is needed to share dashboards, create custom alerts or use Copilot. Microsoft Learn says no Fabric capacity or separate Database Hub license is needed to get started. Resources you create or open from the hub may carry their own licensing or capacity requirements.

Admin note: it's on by default​

Message center item MC1515917 says Fabric enables Database Hub by default on November 17, 2026, and admins can opt out in the Fabric admin portal. The route is Tenant settings, then searching for Database Hub, then disabling the setting after it is enabled. Microsoft says enabling it does not grant additional access or change permissions.

That matters because the hub works from existing permissions. Microsoft Learn says it uses your existing Microsoft Entra ID identity and Azure role-based access control permissions. Several related points follow from the Learn page:

  • Sharing a view shares its configuration, not access to the resources. Two colleagues can open the same view and see different resources.
  • Your databases stay in their existing subscriptions and environments. Nothing has to move into Fabric.
  • Azure discovery runs through Azure Resource Graph. Access to Fabric doesn't automatically grant access to Azure resources. An empty Azure list can simply mean your account lacks Reader access.
  • The Learn page lists prerequisites. Some Microsoft SQL resources need a resource provider registered in each subscription before they appear. Azure SQL Database needs an extended property added, or the Enable Performance Monitoring option in Estate, before performance data is collected.

Caveats before you roll it out​

  • Documentation lags the launch. The Learn overview I retrieved still carries preview wording in places. For example, it lists Cosmos DB in Fabric, mirrored databases in Fabric and Fabric Data Warehouse as not currently supported. The Learn page's limitations section says Database Hub is currently generally available, so the page is inconsistent. Treat its detailed limits as likely current, but verify them in your own tenant.
  • Coverage isn't uniform. Per the Learn page, a resource showing up in Estate doesn't mean every monitoring, agent or action capability exists for it. Elastic pools, Managed Instance and SQL database in Fabric show inventory but not yet Performance-page data. For PostgreSQL flexible server, Estate lists servers rather than individual databases, and performance uses existing Azure Monitor metrics rather than query-level diagnostics.
  • Naming drift. Earlier reporting from the March launch also mentioned Azure Database for MySQL. The GA post's product list does not.
  • Scope. It is an estate-level view with links into native tools. It does not replace them.

Quick checklist​

  1. Check whether your Fabric admin wants the Database Hub tenant setting on, and if not, disable it.
  2. Confirm that people who should see Azure databases hold at least Reader on the relevant subscriptions, and that the required resource providers are registered.
  3. Open Database Hub and check that your resources and telemetry appear. Try the SSMS or VS Code entry points.
  4. Use bulk enablement from Estate to start performance data collection on a test group before scaling up.
  5. Decide who gets Fabric capacity for shared dashboards, alerts and Copilot, and keep preview features out of critical processes until they reach GA.

The bottom line​

The practical gains are a consolidated view, bulk monitoring setup and entry points inside the tools DBAs already use. The AI-heavy pieces, Copilot and Database Agents, are still preview. The default-on tenant setting also makes this a good moment for Fabric admins to check their policy.

 

References

  1. (Launched) Generally Available: Database Hub in Microsoft Fabric Azure Updates 2026-11-17T20:00:32Z
  2. FabCon and SQLCon 2026: Unifying databases and Fabric on a single data platform azure.microsoft.com
  3. Database Hub in Microsoft Fabric is generally available: your entire database estate in one place techcommunity.microsoft.com