Manage the database estate through Fabric's control plane

Microsoft introduced Database Hub in Fabric as an early-access experience for viewing and managing Microsoft database services through Fabric. This article records the May 2026 announcement and the questions an enterprise team should test.

Early-access scope can change. Check the official Fabric announcement and current Microsoft Learn documentation before relying on a service list or release status.

What the hub changes

Database teams often use separate portals and monitoring paths for operational databases. The announced hub adds an estate-level Fabric view for discovery, health, and governance work.

It does not turn those databases into one engine. Deployment, backup, recovery, performance, networking, permissions, and service-specific limits still belong to each database platform.

The announced database scope

The May 2026 source named Azure SQL Database, Azure Cosmos DB, Azure Database for PostgreSQL, and Azure Database for MySQL. It also named SQL Server enabled by Azure Arc and databases in Fabric.

Treat that list as dated. Confirm the current support matrix and whether a connection is generally available, in preview, or still early access. Also verify regional and licensing requirements.

Observability is not full operations coverage

An estate view can help a team notice a health or usage signal. It does not show that every operational control has moved into Fabric.

Before adoption, map each existing task:

• health and performance monitoring;
• alert routing and incident ownership;
• backup, restore, and recovery testing;
• identity, network, and privileged access;
• configuration and change approval;
• audit evidence and retention.

Keep the current service tool when Database Hub does not cover the task or evidence the owner needs.

Governance needs an ownership model

The announcement describes delegated governance across teams. That can support a federated database estate, but the organisation still needs to define who owns policies, who administers each service, and which actions require central approval.

Microsoft’s Fabric governance overview explains the wider platform boundary and notes that some Microsoft Purview capabilities require additional licensing.

Test the experience with a representative slice

1. Inventory database services, regions, and owners.
2. Select a small group that includes cloud and connected on-premises systems.
3. Compare discovered assets and health signals with the existing source tools.
4. Test permissions for central and delegated administrators.
5. Record gaps in operations, evidence, and incident response.
6. Decide whether the hub supplements or replaces each current workflow.

This produces a supportable adoption decision without assuming that a unified view means unified responsibility.