Migrate from Windows 365 Enterprise to AVD Personal

Nerdio Manager lets you migrate a Windows 365 Enterprise Cloud PC into an AVD Personal host pool, reusing the Cloud PC's existing OS disk so the migrated VM keeps its state. Both single-device and bulk (multi-select) migration are supported. For an overview of all supported migration paths, see Nerdio Migrate overview.

Note

This feature is available starting in Nerdio Manager for Enterprise 8.2 and is currently in Public Preview.

Prerequisites

System and environment requirements

Ensure the following requirements are met before starting a migration:

  • The Cloud PC's license type must be Windows 365 Enterprise.

  • The Cloud PC's status must be Provisioned or ProvisionedWithWarnings, and it must not already be under review. Cloud PCs in their grace period are not eligible.

  • The target host pool must be an AVD Personal host pool.

  • The user being migrated must not already be assigned to a host in the target host pool, unless that host pool allows multiple hosts per user.

  • The target VM is created with the Standard security type. Trusted Launch and Confidential VM security types are not available for this path, because Cloud PC VHDs aren't compatible with Trusted Launch.

  • The target disk size cannot be smaller than the source Cloud PC's disk size. Ephemeral OS disks are not supported as a migration target.

  • For an Entra ID target, the host pool's subscription tenant and the network's subscription tenant must both match the Cloud PC's tenant, and the storage account's region must match the selected network's region.

Role-based access control (RBAC) and permissions

This migration touches Windows 365, AVD and, if you use the optional cleanup options, Entra ID group and license membership, so more than one permission area applies.

Nerdio Manager roles

The Admin Nerdio Manager role allows you to carry out the tasks in this procedure.

Nerdio Manager access levels

Following the Principle of Least Privilege (PoLP), you can define one or more Nerdio Manager custom role(s) with the access levels required to carry out the tasks in this procedure:

  • Manage access to the Migrate module allows the user to run migrations.

  • Manage access to the Windows 365 and Workspaces modules allows the user to work with the source Cloud PCs and the target AVD host pool.

Additional permissions

  • If you use the Deprovision Cloud PC toggle, the Microsoft Graph permission GroupMember.ReadWrite.All is required, to remove the user from the Cloud PC's provisioning groups and, optionally, from license-assigning groups.

  • If you select the Also remove the user from the groups that assign the Cloud PC license checkbox, the Microsoft Graph permission LicenseAssignment.Read.All is also required.

  • In the Nerdio Manager Intune configuration, the Group membership setting must be set to Manage.

  • Unassigning a license that's directly assigned to the user (rather than through a group) is only available if the Enterprise license management feature is enabled for the tenant.

Preparatory steps

The target AVD Personal host pool and a storage account must already exist. The host pool's identity (join) type determines some of the migration behavior; see the notes in the procedure.

Migrate Cloud PCs to AVD Personal

To migrate a Cloud PC:
  1. In Nerdio Manager, go to Cloud Desktops > Windows 365 > Enterprise, and select the Cloud PCs tab.

  2. Select the checkbox next to one or more Cloud PCs you want to migrate.

  3. Select Migrate to AVD, either from the actions button in the toolbar or from the actions menu in the Cloud PC's row. This opens the Migrate Cloud PC to Azure Virtual Desktop wizard, which is marked Public Preview in the product.

    Note

    While a migration is in progress, other actions on that Cloud PC (for example, other Intune actions from the device's context menu) are disabled.

  4. Snapshot: choose whether the Cloud PC snapshot should be removed after migration, using the Remove snapshot after migration toggle.

  5. Destination: select the target Host pool, Network, VM size, OS disk, Resource group, and Storage account. All fields are required.

  6. Cloud PC removal: choose whether to deprovision the source Cloud PC using the Deprovision Cloud PC toggle.

    Note

    Deprovision Cloud PC drops the user's provisioning groups, then permanently and immediately deletes the Cloud PC. This can't be undone. The optional license cleanup checkboxes also remove the Cloud PC's license groups or direct license so that it stops billing. If you leave the toggle off, the Cloud PC stays under review and keeps counting against Microsoft's limit until you remove it.

  7. Users & VM names: for each Cloud PC being migrated, confirm the assigned AVD user and the VM name. The VM name is pre-filled with the source Cloud PC's name; change it if the target host pool requires a different name. A row with an unresolved issue is flagged, and you can't continue until it's fixed.

    Note

    On this step, the VM name behavior depends on the target host pool's identity type:

    • If the target host pool is Entra ID-joined, the VM name must differ from the source Cloud PC's name; an unchanged name can block the migration. To avoid renaming each VM manually, accept the name suggested from the host pool's naming convention, or enter your own naming convention to apply it automatically.

    • If the target host pool is hybrid-joined, this restriction does not apply.

  8. Review: check the full summary (host pool, VM size, OS disk, storage account, snapshot and deprovisioning choices, and the list of hosts to migrate with their assigned user and VM name), then select Submit.

  9. Select Close to return to the Cloud PCs list. The migration job is queued for processing; track its progress from Cloud Desktops > Migrate > Migrations.

Bulk migration

To migrate multiple Cloud PCs in one operation, select two or more devices before selecting Migrate to AVD. The Snapshot, Destination, and Cloud PC removal steps apply to the whole batch; the Users & VM names step lists every selected Cloud PC in one table so you can confirm the assigned user and VM name for each individually.

Note

  • Starting a migration places the source Cloud PC under review so that Nerdio Manager can export its VHD. This happens for every migration, not just bulk ones.

  • Microsoft limits Cloud PCs to 10 devices under review at a time. If some Cloud PCs in your tenant are already under review, Nerdio Manager reduces how many you can select for a single bulk migration accordingly, and shows a warning if you try to select more than the remaining allowance. If your tenant regularly needs to migrate more than this, contact Nerdio Support to discuss raising the limit.

Need help?

Raise a support ticket for this item.

Was this article helpful?

0 out of 0 found this helpful
Have more questions? Submit a request

Comments (0 comments)

Article is closed for comments.