Managing a handful of Azure virtual networks is straightforward. Managing dozens across multiple subscriptions, teams, and regions, without losing control of your security posture or drowning in manual peering configurations, is a different problem entirely. Azure Virtual Network Manager was built for exactly that, yet many teams either don't know it exists or find the docs confusing. In this session, we go deep. You'll get a clear picture of AVNM's architecture: network groups, connectivity configurations, and security admin rules. But also, how they compose into a governance model that actually scales.

We’re good at creating and onboarding Landing Zones. The gap is what happens afterwards. A Landing Zone can remain active long after its original purpose has disappeared, or it can become a candidate for deletion without enough evidence to know whether deleting it is actually safe. That leaves us with two bad choices: keep paying for something nobody owns, or delete something we may later need to recover. The goal isn't to delete more subscriptions. It's to make the entire Landing Zone lifecycle visible, governed, and ultimately safe to retire.