Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
Deprecation notice: This article is deprecated and is no longer being updated. This article will be removed on October 30, 2026, to ensure the Cloud Adoption Framework remains focused on helping decision makers make better and faster cloud adoption decisions for their organization.
This does not affect the Azure Virtual Desktop application landing zone accelerator on GitHub.
For alternative guidance, see Azure Virtual Desktop architectures and product documentation.
If you would like to save this guidance, you can select Download a PDF at the bottom left of this page or download the files from GitHub.
The release process for the migration or deployment of Azure Virtual Desktop instances is straightforward. This process mirrors the one used during the Azure Virtual Desktop proof of concept:
- Test the performance and latency of application groups and deployed desktops for a sampling of users.
- Onboard end users to teach them how to connect via:
Post-deployment
After the release has been completed, it's common to add logging and diagnostics to better operate Azure Virtual Desktop.
Although the release process is out of scope for this migration scenario, the process might expose the need to migrate additional workloads to Azure during subsequent iterations of migration. If you haven't configured Microsoft 365 or Microsoft Entra ID, your cloud adoption team might choose to onboard into those services upon the release of the desktop scenarios. For a hybrid operating model, operations teams might also choose to integrate Intune, System Center, or other configuration management tools to improve operations, compliance, and security.
Next steps
After the Azure Virtual Desktop migration is complete, your cloud adoption team can begin the next scenario-specific migration. Alternately, if there are additional desktops to be migrated, you can reuse this article series to guide your next Azure Virtual Desktop migration or deployment.
- Plan for Azure Virtual Desktop migration or deployment
- Review your environment or Azure landing zones
- Complete an Azure Virtual Desktop proof of concept
- Assess for Azure Virtual Desktop migration or deployment
- Deploy or migrate Azure Virtual Desktop instances
- Release your Azure Virtual Desktop deployment to production