If your users need fast, frictionless Remote Access to their Virtual Desktop or Remote App, direct launch links are a game changer. In this post, we’ll show you how to build a Direct URL that sends users straight to their Azure Virtual Desktop (AVD) or Windows 365 resource—right from
Managing external access in Microsoft Azure has always been a challenge—especially for organizations using Azure Virtual Desktop (AVD). Until recently, giving users outside your Azure tenant access meant creating new accounts and managing additional credentials. That’s no longer the case. With Entra ID Guest Users and B2B collaboration, you
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.
