Microsoft has put Microsoft-managed performance monitoring for Azure SQL Managed Instance into public preview. The Azure Updates entry went live on November 12, 2026, and it extends a free monitoring pipeline that already covered Azure SQL Database, Arc-enabled SQL Server and SQL Server running in Azure virtual machines.
The pitch is simple: Microsoft gathers the performance data, runs the collection pipeline and stores the results, so DBAs no longer need home-grown scripts or separate telemetry stores. For teams that run business-critical workloads on managed instances, it offers one place to watch CPU, waits, sessions and storage across many instances.
What Microsoft announced
According to the update, the service gathers performance telemetry from managed instances and keeps it for you. It offers dashboards at the level of a single resource and across a whole estate, aimed at spotting trends, unusual behavior and resource bottlenecks.
For deeper work, you can run Kusto Query Language (KQL) queries over the collected data. Access goes through an Azure Data Explorer proxy endpoint protected by Azure role-based access control, so you do not need to build or pay for your own cluster.
There is one catch worth knowing on day one. The Microsoft Learn documentation states that the Performance page in Database Hub inside Microsoft Fabric does not show managed instances yet. For now, managed instance telemetry is reachable through KQL, while the built-in dashboard view is listed as a later addition.
What data is collected
The telemetry comes from dynamic management views on each monitored instance. Microsoft says no personal information or customer content is gathered, and stored telemetry stays within the same geography as the instance it describes. The collected datasets include:
- CPU and memory utilization
- Wait statistics and active sessions
- Storage I/O and database storage utilization
- Common and detailed performance counters
- Client connections and database properties
- Availability group, replica and database replica state
In the telemetry database, named ArcSqlTelemetry, each platform is tagged by a resource type column. Managed instances appear with the managedInstances type under the Microsoft.Sql provider. A DatabaseName column in the storage I/O, common counters and active sessions tables lets you break results down per database inside an instance.
How to turn it on
For a managed instance, monitoring is switched on with a short T-SQL script run once in the master database. The script adds or updates an extended property called MS_EnablePerformanceMonitoringPreview and sets it to true. Because the property lives in master, it covers the whole instance rather than one database at a time.
Turning it off uses the same script with the value changed to false. Before any data can be read, the Microsoft.Sql resource provider must be registered on each subscription that holds the monitored resources, which takes one Azure CLI command.
To read the data, you sign in to the Azure Data Explorer web UI, add the documented endpoint as a connection and open the ArcSqlTelemetry database. The Kusto.Explorer desktop app is not supported during the preview.
Your account needs at least the Reader role on each subscription. Query results are filtered by your permissions, so two colleagues may see different rows from the same query.
Availability and limits
The preview runs in a list of commercial Azure regions across the Americas, Asia Pacific and Europe, the Middle East and Africa, including East US, West Europe, Central India and Japan East. Government and other isolated sovereign clouds are left out for now.
Microsoft says enabling the feature adds no extra charge, and Database Hub itself is free. The documentation also warns that the endpoint, schema, table names and column names may change while the feature is in preview.
What it means for developers and DBAs
If you look after several managed instances, this removes a chunk of plumbing. Many shops copy DMV snapshots into their own tables or a Log Analytics workspace on a schedule; here the collection is handled for you, and the data lands in a shape you can query across every instance at once.
The KQL route is the real value for now. You can ask which instance burned the most CPU last night or which wait types climbed after a release.
The same queries can feed Grafana, Power BI or a Real-Time Dashboard. Writing your own queries also fills the gap while the built-in managed instance view is still missing.
Treat it as a preview, though. Since table and column names can change, avoid wiring production alerting to it yet, and keep your existing monitoring running in parallel. A sensible first step is to enable it on a non-production instance, check that rows arrive, and compare the numbers with what your current tools report.
For another recent Azure SQL preview aimed at operations teams, see our report on locking point-in-time restore backup immutability in Azure SQL.
Conclusion
Azure SQL Managed Instance now joins Microsoft's free, managed performance monitoring preview, with telemetry collected from DMVs and exposed through a secured KQL endpoint. The dashboard view for managed instances is still pending, but teams can already enable collection with one script in master and start querying their estate.
Sources
- Azure Updates: Public Preview: SQL performance monitoring for Azure SQL Managed Instance
- Microsoft Learn: Enable performance monitoring for Microsoft SQL (preview)
- Microsoft Learn: Query performance monitoring telemetry (preview)
See my articles more often when you search Google.
