Recovery options for Azure Virtual Desktop session host VMs
Last week an update issue caused unresponsiveness and startup failures on Windows machines using the CrowdStrike Falcon agent, including some Azure Virtual Desktop session host virtual machines (VMs). CrowdStrike has released a public statement addressing the matter that includes recommended steps for a workaround. Microsoft also released guidance for resolving the issue for Azure VMs, which detailed restoring from a backup created prior to the update and OS disk repairs.
For Azure Virtual Desktop session host VMs that have been impacted, there are several recovery options. First, we recommend reviewing the recovery options for Azure virtual machines should they be applicable to your environment.
For Azure Virtual Desktop session host VMs specifically, if you are using FSLogix to maintain the user profile separate from the VMs:
- Deploy a new host pool, or add new session hosts to an existing host pool
- Use the existing FSLogix configuration that would enable user profiles and states to be consumed from these new VMs, which are themselves unaffected by the specific CrowdStrike version that has caused the issue.
- You can then, optionally, delete the impacted session host VMs at a time of your choosing.
FSLogix redirects the user profile to a virtual hard disk (VHD) that is stored separately from the VM on a storage service located within Azure. When a user signs in to their session host, their user profile VHD is mounted onto the VM and the user profile is loaded into the session. The user experience is therefore maintained on the new session host, enabling the user to be productive. No user profile data is stored in the VM local disk.
If you used an existing image to create your session hosts, this image should be used so that any applications or configurations that pre-configured within the image are immediately available to users. You can alternatively use the Azure Marketplace to select any supported Windows image. You would then apply any existing policies via Active Directory Group Policy or Microsoft Intune policies, as well as install any software packages via your software distribution tool.
For personal host pools using FSLogix, while FSLogix will return the user profile and the user experience to a new session host, any data stored manually on the local drive(s) or bespoke software installations will be lost. Data can be restored; however, by mounting the impacted VM OS disk to another virtual machine and manually copying the data.
Further information on FSLogix is available in our FXLogix documentation.
Published on:
Learn moreRelated posts
Azure DevOps and GitHub: Journeying into the AI Era
AI is changing how software gets planned, built, and reviewed. As teams adopt agentic development, the platform underneath those workflows mat...
Introducing azure-functions-skills: An AI-Era Workspace for Azure Functions (Preview)
azure-functions-skills gives GitHub Copilot CLI, Claude Code, Codex CLI, and VS Code the skills, MCP configuration, hooks, and instructions ne...
Announcing the Public Preview of Integrated Embeddings in Azure Cosmos DB: Build AI Apps With Embeddings That Stay in Sync
AI applications built on Azure Cosmos DB depend on embeddings for grounded results. Keeping them in sync with your data is the hard part: it m...
Introducing OmniVec: An Open-Source Embedding Platform for AI Apps on Azure
Today we are open-sourcing OmniVec, a platform for building and operating the embedding pipelines that keep the vector representation of your ...
Azure Cosmos DB All Versions and Deletes Change Feed Mode is Now Generally Available
Modern applications don’t just write data and move on. They react to it. A new order triggers an inventory update. A profile change sync...
Change Partition Keys in Azure Cosmos DB is Now Generally Available
We’re excited to announce the general availability of Change Partition Key in Azure Cosmos DB for NoSQL, now with online copy support. Y...
Announcing the General Availability of Per Partition Automatic Failover for Azure Cosmos DB NoSQL
Today, we are excited to announce the General Availability of Per Partition Automatic Failover (PPAF) for Azure Cosmos DB NoSQL API. PPAF is a...
Public Preview: AI-powered Azure Cosmos DB Migration Assistant for RDBMS to NoSQL
Today, we are excited to announce the public preview of the Azure Cosmos DB Migration Assistant for RDBMS to NoSQL, now available in the Azure...
Azure Cosmos DB MCP Toolkit Is Now Generally Available — Bringing Your Database to AI Agents at Scale
Since we introduced the Azure Cosmos DB MCP Toolkit at Ignite 2025 in preview, the response has been clear: developers want a straightforward ...
Announcing General availability of the Azure Cosmos DB vNext emulator
The Azure Cosmos DB vNext emulator is generally available today. It ships as a Docker image that runs on Linux, macOS, and Windows, on both x6...