Should Microsoft maintain a PowerShell Coverage Matrix for Azure services?

[Ayanmullick]

Inspired by tools like the Azure Status Dashboard, I’d like to propose a PowerShell Coverage Matrix maintained by Microsoft, as discussed during the July 25 Community call , @Alex-AZPS. This would help the community and engineering teams visualize where native PowerShell cmdlet support exists (or is missing) across Azure services, especially across different operational planes.

Example Coverage Planes Plane Description Management Create/update/delete resources Monitoring Retrieve metrics & alerts Diagnostic Configure diagnostics & log collection Data / Query Query data-plane (e.g., log queries) Troubleshooting Test-connection, flow logs, etc. Additional planes As required needed

Example Coverage Legend Symbol Meaning ✅ Full native PowerShell support ⚠️ Partial / Unsupported community modules ❌ No native support / will not be covered

Example matrix:

Azure Service	Management	Monitoring	Diagnostic	Data / Query	Troubleshooting
Virtual Machines	✅	✅	✅	⚠️ (via extensions)	✅
Log Analytics Workspace	✅	✅	✅	❌ (must use Kusto)	⚠️ (agent only)
Data Factory	⚠️	❌	❌	❌ (no data/query)	❌ (no test conn.)
Other Services

[Alex-AZPS]

https://github.com/Azure/azure-powershell/blob/main/documentation/azure-powershell-modules.md
Currently we have a simple version, the modules we support, and the version numbers.