Great news! You can now deploy Azure Virtual Desktop (AVD) with FSLogix using Entra-only identities and Azure Files—no domain controllers required. This is a game-changer for organizations moving toward a fully cloud-native architecture. Why This Matters Traditionally, using FSLogix with AVD meant relying on Active Directory or Entra Domain
Managing Azure Virtual Desktop (AVD) environments can be complex—especially when it comes to scaling, security, and automation. Traditionally, administrators had to assign permissions to the AVD service principals and manually add session hosts to a host pool, which introduced operational overhead and potential security risks. But with Session Host
If you’re managing Azure Virtual Desktop (AVD) environments, you’ve probably noticed how frustrating it can be for users to sign in twice, once to the AVD client and again to the session host. This extra step isn’t just annoying; it can lead users to save credentials in insecure ways.
In this post and accompanying video, we walk through creating a Spot VM in the Azure portal, setting eviction policies, and configuring pricing caps. We’ll also see how to check historical pricing and optimize your deployment region for maximum savings. What Are Azure Spot VMs? Azure Spot VMs are
Ephemeral OS Disks in Microsoft Azure can dramatically improve VM performance while reducing costs. In this post, we’ll explore what they are, why they matter, when to use them, and how to deploy them using the Azure Portal and PowerShell. What Are Ephemeral OS Disks? Ephemeral means short-lived. In
