[What and Why:]
Microsoft Fabric is updating the Database Hub tenant setting so Database Hub is enabled by default on November 17, 2026. Database Hub is currently in preview and gives database teams a central place in Microsoft Fabric to discover supported databases across Azure, Fabric, on-premises, and supported multicloud environments.
Database Hub helps teams review available performance, security, utilization, and best-practice findings, investigate issues, and take action through guided experiences and database tools. This change makes Database Hub available without requiring admins to enable it manually.
Default enablement adds no cost, and does not move databases into Fabric or change underlying database resources.
Database Hub uses users’ existing Azure role-based access control (RBAC) permissions for Azure resources and existing Fabric permissions for Fabric resources. Users can view only the resources and insights their permissions allow. Enabling Database Hub does not grant additional access or change these permissions.
Available capabilities depend on permissions, supported resources, configuration, and region. Resources or services customers choose to use through linked experiences remain subject to their own pricing and licensing requirements.
[Rollout Schedule:]
General Availability (Worldwide): Database Hub tenant setting default enablement will begin on November 17, 2026 and is expected to complete on November 17, 2026.
[Impact on Your Organization:]
Who is affected:
- Admins who manage Microsoft Fabric tenant settings.
- Database teams and users who are authorized to view supported database resources and related insights.
Platforms/Services:
- Microsoft Fabric
- Database Hub
- Fabric admin portal
What will happen:
- The Database Hub tenant setting will be enabled by default on November 17, 2026.
- Users with appropriate permissions will be able to access Database Hub without an admin first enabling the tenant setting.
- Admins can disable the Database Hub tenant setting in the Fabric admin portal if Database Hub does not meet their organization’s needs.
- No databases are moved or changed, and no additional permissions are granted by this default enablement.
[Action Required/Recommendations:]
No action is required if your organization wants Database Hub to be available by default.
If your organization does not want Database Hub enabled, admins can go to the Fabric admin portal, open Tenant settings, search for Database Hub, and disable the setting after it is enabled on November 17, 2026.
Admins may also review Database Hub documentation and assess the capability against their organization’s governance and operational needs.
[Compliance considerations:]
| Question | Answer |
| Does the change include an admin control? | Yes. Admins can manage the Database Hub tenant setting in the Fabric admin portal and can disable Database Hub if it does not meet their organization’s needs. |
| Does the change alter how admins can monitor, report on, or demonstrate compliance activities? | Yes. Database Hub can surface available performance, security, utilization, and best-practice findings for supported databases, based on existing permissions and supported resource configuration. |