Resource Graph Checks
Custom governance/waste checks written directly against Azure Resource Graph — unattached network interfaces, unattached managed disks, empty resource groups, and (when configured) resources missing a required tag. Required tag(s): owner.
Findings by check type
Groups current findings by the AFP check that produced them (unattached NIC/disk, empty resource group, missing tag); bars count findings, not their remediation cost.1 finding(s)ⓘ Why this matters
A tall bar for one check type usually means a systemic gap (e.g. no tagging policy enforced) rather than isolated mistakes — fixing the underlying cause can close many findings of that type at once.
Findings by resource group
Ranks resource groups by their number of current AFP findings, from all four checks combined.1 resource group(s) with a findingⓘ Why this matters
A resource group with disproportionately many findings is worth a focused cleanup pass — check the Findings table below filtered to that group before treating each finding as unrelated.
- rg-blue-harbor-prod-app: 1 finding(s)
- rg-app-frontend: 1 finding(s)
- rg-data-platform: 1 finding(s)
- rg-network-shared: 1 finding(s)
- rg-devtest: 1 finding(s)
Findings
Lists every current point-in-time finding's check type, affected resource, resource group, and a plain-language reason; findings are re-evaluated on each poll, not accumulated as a history.1 finding(s)ⓘ Why this matters
These are candidates to review, not confirmed waste — an empty resource group awaiting a planned deployment, or an unattached disk kept intentionally as a backup, are both legitimate reasons a finding might not need action.
| Check | Resource | Resource group | Detail | Est. monthly cost |
|---|---|---|---|---|
| Unattached network interface | nic-bh-app-01 | rg-blue-harbor-prod-app | No virtual machine attached to this network interface. | — |