# Network Flow Logs on Azure | ZopNight

> Every check ZopNight runs on your Network Flow Logs on Azure: 4 in total, across compliance, orphaned resources and rightsizing.

Source: https://zop.dev/zopnight/rules/azure/network-flow-log

---

_Azure · 4 checks_

## Network Flow Logs on Azure, checked for you.

ZopNight runs 4 checks on your Network Flow Logs in Azure, covering orphaned resources, compliance and rightsizing.

- 4 — checks
- 3 — categories
- Manual — fixes, spelled out
- 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 Duplicate Flow Logging](https://zop.dev/zopnight/rules/azure-duplicate-flow-logging)
- [Azure Flow Log on a Gateway Subnet](https://zop.dev/zopnight/rules/azure-flow-log-on-a-gateway-subnet)

### Rightsizing

Resources sized for headroom they never use. A smaller size runs the same workload for less.

- [Azure Traffic Analytics on the 10-Minute Interval](https://zop.dev/zopnight/rules/azure-traffic-analytics-on-the-10-minute-interval)

### Compliance

Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.

- [Azure NSG Flow Logs Past End-of-Life](https://zop.dev/zopnight/rules/azure-nsg-flow-logs-past-end-of-life)

## Find these on your own Network Flow Logs.

Connect a read-only role and ZopNight inventories the Network Flow Logs you run, then runs all 4 checks against them.

[object Object]