Make Estate yours: Focus on the databases and issues you own in Database Hub

Database Hub in Microsoft Fabric is now in public preview.

Estate experience brings every supported database you can access into one inventory, with the issues and suggestions found across them. In a large organization, that can mean thousands of resources.

But most people own only part of the estate: a set of production databases, a few subscriptions, one resource group. This post shows how to shape Estate around your part, save it as a custom view, and use it to triage and bring in help.

The examples use Azure SQL Database; the same steps work for PostgreSQL and Azure Cosmos DB.

Which resources are mine?

While in Estate view select Filter to narrow the list by Type, Subscription, Location, Status, Tags, or Resource group. The grid and the resource count update as you select values; Filter (1) shows how many dimensions are active, and Clear all resets them.

Looking for one resource? Search across columns matches names, locations, subscriptions, and more.

Filter by type, subscription, location, status, tags, or resource group to scope Estate to the resources you own.

Which issues should I focus on?

Each row shows its Issues and Suggestions counts and opens expanded, so findings are readable at a glance: issues with a filled Security or Performance tag, suggestions marked with a lightbulb.

Open Category and select Security, Performance, Optimization, or a combination. Use Relevance to keep only resources with Issues or Suggestions. The grid is sorted by issue count, so the resources that need the most attention come first.

Combine categories, for example Security and Performance, to see only the findings your team is responsible for.

How do I get back here tomorrow?

Once Estate shows what you want, save it. An asterisk after the view name (View: All resources *) means your filters have unsaved changes.

1. Select View > Save.
2. Choose Save as new custom view and give it a name that describes the scope, such as sqlDB-sec-perf-issues.
3. Select Apply.

The view now appears under Custom views in the View menu. It saves filters, not results, so you always see the current state of those resources.

Save your filters as a custom view.

And reopen them from the View menu.

What's wrong, and what should I do about it?

Select an issue to open its detail page. Here, the top database reports Public network access is enabled.

The Summary explains why it matters: public reachability increases exposure to credential attacks, scanning, and firewall mistakes. The Recommended action gives the fix and its precondition: Disable public network access after confirming that all clients can connect through approved private connectivity. Resolve in Azure portal opens the resource.

Database Hub doesn't change the resource for you; you make the change in the tool that owns it, under your existing permissions. Back returns you to Estate with your view intact.

Each issue or suggestion explains what's wrong, why it matters, and where to fix it.

Who can help me fix it?

That precondition is often the hard part: confirming every client can connect privately may take your networking or application team. Bring them into the same view.

Select View > Share, then Copy link. The link carries your current filters, so a colleague starts from the same scope. Each person still sees only the resources they already have access to; sharing never grants access.

Share a link to your current filters so teammates start from the same scope, within their own permissions.

Need the list for a change ticket? Select Export view (as .csv). CSV files don't carry sensitivity labels, so handle the file according to your organization's data policies.

What needs attention in my part of the estate?

Your view isn't limited to Estate. Open Overview, select the same view from the View menu, and every card and chart rescopes to it: the Estate issues summary, the Security, Performance, and Optimization cards with their top issues, and the performance trends.

Overview now summarizes your backlog instead of the whole estate. Views are managed in Estate; Manage views (Estate) takes you there.

Select a custom view on Overview to scope issue summaries and performance trends to the resources you own.

More in Estate

Look up a resource without leaving the list

Select a resource name to open its details next to the list: subscription, resource group, and logical server (each linking to the Azure portal), status, location, pricing tier, max storage, and tags. Connection strings for ADO.NET, JDBC, ODBC, PHP, and Go use Microsoft Entra authentication, and Open in Azure portal, Open in VS Code, and Open in SSMS are at the top.

The … menu on each row adds quick actions Copy connection string, Open in editor, Enable performance monitoring, Create monitor from template and Set alert from template. 

Resource details, connection strings, and links to your tools, without losing your place in Estate.

Create a database where you work

Create resource starts a new database from Estate, grouped by engine: SQL database in Fabric, Azure SQL Database, SQL Server instance, Azure Database for PostgreSQL, and Azure Cosmos DB for NoSQL. 

Start a new database from Estate, grouped by engine.

Get started

Open Estate, filter to the resources you own, focus on the categories you triage, and save the result as a view. Then select it on Overview and start with what needs attention.

Database Hub is in public preview; capabilities vary by service and preview configuration. See the Database Hub documentation for supported services and setup, and use Feedback in Database Hub to tell us what you'd like next.