Azure SQL Permissions shows database permission information for a monitored Azure SQL database. Use it to verify access-related data and diagnose missing monitoring permissions.
What To Review
- Database permission rows.
- Permission names.
- Whether required monitoring permissions appear to be available.
- Missing access when other Azure SQL pages return limited data.
Workflow
- Open Permissions for the Azure SQL database.
- Review permission rows.
- Compare with access indicators on Database Summary.
- Update database permissions through your normal access management process.
How To Review Azure SQL Permissions
Azure SQL Permissions helps confirm whether the monitoring login or Entra identity has enough visibility for Mini DBA to collect database metrics. Use this page after adding a connection, after changing access, or when Azure SQL pages show limited data.
Start with the setup guidance in Connect To Azure SQL. That page includes SQL and Entra-oriented examples for creating a monitoring user and granting the required permissions. If query, wait, lock, file, or health data is missing, compare the missing feature with the permissions assigned in the database.
Apply the principle of least privilege. Do not grant broad owner access just to make monitoring easier unless your security process approves it. Use a dedicated monitoring principal where possible and document any additional permissions needed for specific features.
Azure SQL Permissions FAQ
Does Mini DBA need database owner permissions?
Not normally. Many monitoring scenarios work with a dedicated user granted read access to required metadata and performance views.
Why does one Azure SQL database show less data?
The user may have different database-level permissions, the database may be in a different service tier, or collection may not have completed.
Where are the permission examples?
See Connect To Azure SQL for connection steps and example SQL.