Azure NSG Flow Logs Past End-of-Life
Azure is retiring NSG flow logs and deletes them on the retirement date, logging on or off. Move to virtual network flow logs before then, or the record stops.
Free to start. No card. The playground just needs your work email.
Azure
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across Azure, with read-only access to the account.
Explain
Every finding says exactly what to change: Migrate the flow log to virtual network flow logs.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- Network Flow Logs on Azure
- The fix, by hand
- Create a virtual network flow log on the VNet (or subnet) holding the workloads this NSG protects.
- Confirm flow data is arriving, and re-point traffic analytics at the new flow log if it was enabled.
- Delete the NSG flow log. Leaving both enabled records the same traffic twice and bills for both.
- Check for NSG flow logs on the same workloads at both the subnet and NIC level.
These are the steps the finding carries in the product.
- Category
- Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1404
Related checks
See the compliance findings 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.