Azure Verified Modules are genuinely good. Microsoft-backed and community-maintained, best practices baked in, consistent interfaces. What's not to like? Turns out: quite a bit. When you're managing Azure environments at scale, the cracks start showing fast. Most modules are still pre-1.0, so breaking changes are fair game. The provider is mid-migration from AzureRM to AzApi. And the opinionated defaults? Sometimes they're just not your opinions. Multiply that across dozens of environments and suddenly 'community-maintained' starts to feel like a liability. So we wrapped it. Every AVM module we use sits behind our own wrapper: pinned versions, standardised naming, locked defaults. Boring? A little. Production-stable? Very.

In this session, we’ll explore how Azure Virtual Desktop Session Host Configuration changes the way we deploy and manage session hosts. Instead of treating every VM as something that needs to be manually maintained, we’ll define the desired configuration once and let Azure handle the provisioning and lifecycle. We’ll look at what’s inside a Session Host Configuration, including the image, VM size, networking, identity, security and disk configuration. We’ll also explore how ephemeral OS disks can help build truly stateless session hosts.