Azure VNet Peering Disconnected
A peering in a disconnected state carries no traffic but still grants a configured path between two networks, so it reads as connectivity that does not work and as attack surface that does.
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: Reconnect or delete disconnected VNet peering. 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
- VNet Peerings on Azure
- The fix, by hand
- Open Portal → Virtual networks → ‹local VNet› → Peerings → the resource, confirm state is Disconnected.
- Look up the remote VNet (Remote virtual network ID). Confirm it's deleted or that the remote-side peering is gone.
- Document any application or NSG rules that still expect routes via this peering.
- Delete the peering. Verify no application broke (try a smoke ping or curl from the local VNet).
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-1364- 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.