Edit

Azure Virtual Desktop post-deployment

  • Article

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:

Post-deployment

After the release has been completed, it's common to add logging and diagnostics to better operate Azure Virtual Desktop. It's also common for operations teams to onboard the pooled hosts and desktop virtual machines into the Azure server management best practices to manage reporting, patching, and business continuity and disaster recovery configurations.

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.