Coverage
Coverage views compare the estate with operational baselines and expose the connection blind spots that can make an assessment incomplete. Opening a view reads its latest saved result; use the view’s refresh or scan action when current Azure state is required.
| Guide | Use it to |
|---|---|
| Monitoring Coverage | Compare metric alerts with the Azure Monitor Baseline Alerts (AMBA) reference. |
| Alerts Manager | Triage fired alerts and safely manage rules, action groups, and proposed changes. |
| Telemetry Coverage | Find missing diagnostic settings, categories, and approved destinations. |
| Backup & DR Coverage | Assess protection, recovery recency, resilience, and DR pairing. |
| Connection Capability | See which configured connections can reach each required Azure surface. |
Shared operating model
- Choose the intended Azure connection and workload or subscription scope.
- Check the generated time, age, and stale indicator before interpreting a score.
- Refresh explicitly if the saved result is absent or too old for the decision.
- Investigate gaps and unreadable resources separately; an unreadable result is not proof of non-compliance.
- Preview and review every generated artifact. Deployment remains an external, operator-controlled step unless a feature explicitly presents an approved write action.
- Re-scan after remediation to verify the observed state.
Coverage is evidence, not a guarantee. Azure permissions, scan caps, unsupported resource types, and connection capabilities can reduce the observed estate.