Azure Key Vault Unused
The vault carries per-operation and per-key charges and, more importantly, an unused vault is key material and access policies nobody is reviewing.
Free to start. No card. The playground just needs your work email.
Azure
Found, explained, fixed.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across Azure, with read-only access to the account.
Explain
Every finding says exactly what to change: Delete the unused key vault. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
After a guided review, where you confirm the change, ZopNight deletes the resource, then checks the change took.
- Applies to
- Key Vaults on Azure
- The fix, by hand
- Key vaults → the resource → Monitoring → confirm zero operations in the last 30-90 days.
- List contents (Secrets, Keys, Certificates). Export anything still referenced elsewhere.
- Resolve any access policies / RBAC role assignments pointing to the vault.
- Delete the vault. It enters soft-delete for 90 days (recoverable).
- If purge protection is on, you cannot manually purge before the 90-day window. Plan accordingly.
ZopNight does this for you after a guided review.
- Category
- Orphaned resources. Resources no longer attached to anything that needs them, such as unattached volumes and unassigned IPs.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1370- Full reference
Related checks
See the orphaned resources in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.