The Azure SQL Databases page lists databases discovered under a monitored Azure SQL logical server. It is the entry point from a logical server to individual Azure SQL database monitoring.
The Databases page is the bridge between logical server monitoring and database-level troubleshooting. Use it to confirm which Azure SQL databases Mini DBA discovered, which database belongs to the affected application, and whether the monitored logical server is the correct one.
This matters when logical servers host many databases, tenant databases, or elastic pools. If a user reports that one customer or application is slow, start here to choose the correct database before opening Azure SQL Database Summary, Azure SQL Activity, Azure SQL Queries, or Azure SQL Health Checks.
If a database is missing, check the Azure SQL connection, database-level permissions, firewall or network access, and collection status. The connection workflow and permission examples are documented in Connect To Azure SQL.
It is mainly inventory and navigation. Use the database-level pages for tuning evidence.
The monitoring principal may not have access, the connection may target another logical server, or collection may not have completed.
Use this page to choose a database, then review Azure SQL Elastic Pools if the database shares pool resources.