# VNet Peerings on Azure | ZopNight

> Every check ZopNight runs on your VNet Peerings on Azure: 1 in total, across orphaned resources. Each one says why it matters and exactly what to change.

Source: https://zop.dev/zopnight/rules/azure/vnet-peering

---

_Azure · 1 check_

## VNet Peerings on Azure, checked for you.

ZopNight runs 1 check on your VNet Peerings in Azure, covering orphaned resources. 1 of them it can fix after a guided review.

- 1 — check
- 1 — category
- 1 — check fixable in the product
- No — checks only, not scheduled

Free to start. No card. The playground just needs your work email.

## Every check, grouped by what it protects.

Each one opens with why it matters and exactly what to change.

### Orphaned resources

Resources no longer attached to anything that needs them, such as unattached volumes and unassigned IPs.

- [Azure VNet Peering Disconnected](https://zop.dev/zopnight/rules/azure-vnet-peering-disconnected)

## Find these on your own VNet Peerings.

Connect a read-only role and ZopNight inventories the VNet Peerings you run, then runs its one check against them.

[object Object]