Lifecycle & investigation
These tools turn time-sensitive estate signals into an accountable investigation record. They are read-oriented by default: refresh or scan explicitly, interpret scope and freshness, then hand material evidence into a finding, ticket, or case.
| Guide | Use it to |
|---|---|
| Retirement Radar | Map Azure retirements and breaking changes to affected workloads. |
| Reservations Monitor | Track reservation expiry, renewal mode, and utilization. |
| Quota Monitor | Find regional capacity headroom before deployments fail. |
| Telemetry Intelligence | Translate questions to bounded KQL and correlate failures. |
| Evidence Locker | Capture hash-stamped point-in-time evidence. |
| Case Files | Preserve investigation, remediation, and verification history. |
Common operating model
- Select the intended connection and workload, subscription, or component scope.
- Check generated time, cache age, and any truncation or unreadable indicators.
- Refresh only when current Azure state is required.
- Validate AI narrative against displayed queries and source rows.
- Preserve decision-grade evidence, attach it to a case, and record verification before closure.
Never place live tenant IDs, resource IDs, webhook URLs, tokens, or personal data in screenshots or examples.