Migrate from Windows 365 Enterprise to Windows 365 Flex Dedicated

Nerdio Manager lets you migrate Windows 365 Enterprise Cloud PCs to Windows 365 Flex Dedicated Cloud PCs, reusing the source Cloud PC's disk so the migrated Cloud PC keeps the user's profile, apps, and OS state. Both single Cloud PC and bulk (multi-select) migration are supported, with preflight validation before the migration starts and progress shown for each Cloud PC. For an overview of all supported migration paths, see Nerdio Migrate overview.

Flex Dedicated is currently the only Windows 365 Flex mode supported as a migration destination. Microsoft's Cloud PC provisioning API triggers provisioning through an individually assigned license, the same way Windows 365 Enterprise works. Shared (pooled) Flex licensing has no per-user assignment to trigger against, so it can't be used as a migration target.

Note

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

For each Cloud PC, Nerdio Manager does the following:

  1. Places the source Cloud PC under review, so that its disk can be exported.

  2. Exports the source Cloud PC's disk to the storage account that you select.

  3. Imports the exported disk as a Windows 365 snapshot for the user.

  4. Only after the import succeeds, deprovisions the source Cloud PC and unassigns its Windows 365 Enterprise license.

  5. Adds the user to the target Entra ID group, which starts provisioning of the Flex Dedicated Cloud PC from the snapshot.

  6. Removes the temporary Entra ID group and Enterprise provisioning policy that it created for the snapshot import.

To import the exported disk, Nerdio Manager creates a temporary Entra ID group (Nerdio-CPC-Flex-migration-<JobId>-temporary) and a temporary Windows 365 Enterprise provisioning policy (Nerdio temporary Enterprise policy - job <JobId>). The Windows 365 service needs them to import the snapshot. Nerdio Manager removes both when the migration completes. Nerdio Manager also creates the target Entra ID group that you name in the Licensing step, and uses it to assign the Flex Dedicated provisioning policy to the migrated users.

Important

The migration deprovisions every source Cloud PC and unassigns its Enterprise license. End users lose access to their desktop until the Flex Dedicated Cloud PC is provisioned.

Prerequisites

System and environment requirements

Ensure the following requirements are met before starting a migration:

  • The source Cloud PCs must be Windows 365 Enterprise Cloud PCs with a status of Provisioned or ProvisionedWithWarnings, and they must not already be under review. Cloud PCs that aren't eligible are skipped.

  • Each source Cloud PC must have an assigned user. Each user can have only one source Cloud PC in the same migration, and the source Cloud PC names must be unique within the batch.

  • The migration is available for Cloud PCs in the identity tenant. Cloud PCs in linked tenants aren't supported.

  • The Cloud PCs that you select for one migration must use the same provisioning policy.

  • The tenant needs at least one Windows 365 Flex service plan with enough spare licenses and Cloud PC capacity for every selected Cloud PC. In Flex Dedicated mode, one license provisions up to three Cloud PCs. If no plan qualifies, the Licensing step shows no available Cloud PC sizes and you can't continue.

  • You need a Flex Dedicated provisioning policy, or you must create one during the migration. Only Flex Dedicated provisioning policies can be used as a migration target.

  • The provisioning policy must use the same network as the source Cloud PCs, so that users keep access to the resources they rely on.

  • You need a Windows 365 user settings policy with Snapshot as the provisioning source, or you must create one during the migration. Every Windows 365 user settings policy that is assigned to the target users must use a Snapshot provisioning source. If an assigned policy uses an image-based source, Windows 365 provisions the Cloud PC from the image instead of the migrated snapshot, and the user's existing profile, apps, and data are discarded. If the wizard blocks the migration, remove any conflicting assignments.

  • You need a storage account in the same Azure region as the source Cloud PCs. The source Cloud PC disks are exported to this storage account.

  • The target user must not already have a Cloud PC provisioned through the target provisioning policy.

  • The target user must not have an existing Windows 365 snapshot import. Delete it before you migrate.

  • Microsoft limits the number of Cloud PCs that can be under review at the same time (10 by default). If other Cloud PCs in your tenant are already under review, the migration waits for a free slot. If no slot can free up, the wizard blocks the migration.

  • The migration unassigns each source Cloud PC's license and removes the user from the Cloud PC's provisioning group. This can't be done automatically for groups with dynamic membership, or for role-assignable groups. Change the membership rule, or assign the license through a group that isn't role-assignable, before you migrate those Cloud PCs. Otherwise, exclude them from the selection.

  • By default, a migration is limited to 50 Cloud PCs. This limit is a configurable app setting, not a hard cap.

Role-based access control (RBAC) and permissions

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 module allows the user to work with the source Cloud PCs, including removing them, and to provision the target Cloud PCs.

  • License management access is required if the source Cloud PCs use a directly assigned license, because the migration unassigns it.

  • Manage access to User Groups in the Intune permissions allows the user to create the Entra ID groups that the migration uses.

Note

Without the required permissions, the Migrate Enterprise to Flex Dedicated action isn't shown at all, which can look like an unsupported Cloud PC rather than a permissions gap.

Additional permissions

  • Intune must be configured as follows: Cloud PC must be enabled, and Group membership must be set to Manage, not Read-only. If you remove directly assigned licenses, License management must also be set to Manage.

  • The Microsoft Graph permission Group.ReadWrite.All is required. Nerdio Manager creates an Entra ID group for the migrated users, and assigns the provisioning policy and user settings to it. It also creates a temporary Entra ID group, which it removes when the migration completes. This is a delegated permission if Intune runs in user-context mode, and an application permission otherwise.

  • The Microsoft Graph permissions that come with the Intune settings are also used: GroupMember.ReadWrite.All (Group membership - Manage) and LicenseAssignment.ReadWrite.All (License management - Manage).

  • Nerdio Manager doesn't request the RoleManagement.ReadWrite.Directory permission, so it can't change the membership of role-assignable groups.

  • Nerdio Manager is given the Contributor role on the storage account that you select for the disk export.

Preparatory steps

The Windows 365 Flex service plan and the licenses that you plan to use must already exist in the tenant before you start the migration wizard. Nerdio Manager doesn't purchase Flex service plans or licenses on your behalf. The storage account for the disk export must also already exist. Nerdio Manager creates the target Entra ID group during the migration.

Migrate Enterprise Cloud PCs to Flex Dedicated

To start the migration:
  1. Go to Cloud Desktops > Windows 365 > Enterprise, and select the Cloud PCs area.

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

  3. Select Select bulk action, and then select Migrate Enterprise to Flex Dedicated. This opens the Migrate Cloud PC Enterprise to Windows 365 Flex Dedicated wizard, which is marked as Public preview in the product. Migration is available only from the bulk actions menu, even for a single Cloud PC.

    Note

    The menu item is disabled if none of the selected Cloud PCs is eligible. Selected Cloud PCs that aren't eligible (not Enterprise, or not Provisioned or ProvisionedWithWarnings) are skipped, and the wizard shows how many were skipped. By default, you can migrate up to 50 Cloud PCs in one batch. If you select more, a message shows the limit, and you can reduce the selection.

Complete the migration wizard

To configure and submit the migration:
  1. Provisioning policy: select Select existing or Create new.

    • If you select an existing policy, only Flex Dedicated provisioning policies are listed.

    • If you create a new policy, enter a Name and Description, and select the Language & Region and the Default Cloud PC Image. Windows 365 redeploys the Cloud PC from this image if the Cloud PC is reset.

    • For the network, select an existing Azure network connection, or a Microsoft-hosted network region. The network must be the same one that the source Cloud PCs use. If it differs, the step shows a warning and you can't continue.

    • Single sign-on: select Enabled to enable Microsoft Entra single sign-on.

  2. User settings: select existing user settings, or create new ones. Importing a snapshot requires a Windows 365 user settings policy with Snapshot as the provisioning source, so only user settings with that source are listed, and Snapshot is the only supported value for this migration.

  3. Licensing: select the Flex service plan for the migrated Cloud PCs, and enter the target group. The wizard detects how the source Enterprise licenses are assigned (through a group, directly, or both) and removes them during the migration. If a license is assigned directly and you don't have the License management permission, or the license comes from a dynamic or role-assignable group, the wizard blocks the step and explains why.

    • Cloud PC size: select the Cloud PC size. Only Flex service plans with enough spare licenses and Cloud PC capacity for every selected Cloud PC are listed. The number of available sizes is shown in the field label.

    • Target group name: enter a name for the new Entra ID group. Nerdio Manager creates this group, adds the migrated users to it, and assigns the Flex Dedicated provisioning policy to it. The name can be up to 64 characters, can contain only ASCII characters, and can't contain spaces or any of the following characters: @ ( ) / [ ] ' ; : < > ,

    • Allotment name and Number of licenses: optionally, reserve a Flex allotment for the migrated Cloud PCs. Enter both values or neither. In Flex Dedicated mode, one license provisions up to three Cloud PCs, so the allotment for a batch of Cloud PCs needs at least one third of that number of licenses, rounded up. It can't exceed the available licenses. If you don't enter an allotment, the migrated Cloud PCs use unallotted licenses.

  4. Disk export: select the Storage account used to place the source Cloud PCs under review and to export their disks.

    • The storage account must be in the same region as the source Cloud PCs. Storage accounts are grouped by region. If you select an account in a different region, the step shows a warning and you can't continue.

    • This step also shows how many of the selected Cloud PCs start migrating right away, and that the rest wait for a free under-review slot. If no slot is free and none is expected to free up, the step blocks the migration. Remove other Cloud PCs from review, or reduce the selection, and try again.

  5. Cleanup: choose whether to keep the exported disk (VHD) after the migration completes.

    • Take snapshot of source VM(s) before migration: select this check box to keep the exported VHD in the storage account after the migration. Clear it to delete the exported VHD after a successful migration.

    • Remove snapshot: turn on to delete the exported VHD automatically on a date that you choose. Then set the Snapshot deletion date, the Snapshot deletion time, and the Snapshot deletion time zone. If you turn it off, the exported VHD stays in your storage account until you remove it yourself.

    Note

    A retained VHD stays in your storage account, so storage costs may apply.

  6. Bulk job settings: configure how the migration runs:

    • Cloud PCs migrated in parallel: enter how many Cloud PCs are migrated at the same time, from 1 to 10. Each Cloud PC is placed under review while its disk is exported, so this number can't exceed Microsoft's under-review limit.

    • Number of failures before aborting: enter how many failed migrations to tolerate before the job stops automatically. The value must be 1 or greater. This surfaces problems early and prevents a bulk migration from continuing while a problem is present.

  7. Review: check the summary of the disk export, provisioning policy, user settings, licensing, cleanup and bulk job settings, and the list of Cloud PCs to migrate. Then submit the migration.

    Note

    If a source Cloud PC can't be deprovisioned, for example because its user belongs to a provisioning group with dynamic membership or a role-assignable provisioning group, the step lists it and asks you to exclude it from the selection. Exclude the Cloud PC to continue.

Monitor and manage the migration

After you submit the migration, track its progress from Cloud Desktops > Migrate > Migrations. Single migrations are listed as Windows 365 Enterprise Cloud PC to Flex Dedicated, and bulk migrations as Bulk Windows 365 Enterprise Cloud PCs to Flex Dedicated. Open a migration to see its details and job tasks.

Note

If a migration fails before the source Cloud PC removal starts, Nerdio Manager restores the user's group memberships, and the source Cloud PC stays as it was. If a migration fails after the source license removal has started, the imported snapshot and the exported VHD are kept, even if you chose to delete them, because they are the only way back to a working desktop. Full rollback isn't guaranteed. You can restart a failed migration from the Migrations list.

From the Migrations list, you can also:

  • Cancel a migration.

  • Resume a failed migration. This retries the migration from the last failed step.

  • Clean up a migration.

Troubleshooting

The wizard validates your selections before it lets you continue. The following table lists the most common blockers.

Message

What to do

No Flex service plan has enough available licenses and Cloud PC capacity for the selected Cloud PCs.

Add Flex licenses or capacity, or reduce the number of selected Cloud PCs.

The allotment must have at least the required number of licenses to cover the migrated Cloud PCs.

Increase the number of licenses in the allotment. One license covers up to three Cloud PCs.

The selected network differs from the one the source Cloud PCs use.

Select the same network that the source Cloud PCs use.

The selected storage account is in a different region from the source Cloud PCs.

Select a storage account in the same region as the source Cloud PCs.

Cloud PCs are currently under review outside of this migration.

Remove some of those Cloud PCs from review, or reduce the selection.

The selected Cloud PCs get their license from a group with dynamic membership, or from a role-assignable group.

Update the membership rule in Entra ID, or assign the license through a group that isn't role-assignable, before migrating the Cloud PCs.

The selected Cloud PCs use a directly assigned license, and unassigning it requires the License management permission.

Ask an administrator with the License management permission to run the migration, or to grant you that permission.

The migration deprovisions every source Cloud PC, but a Cloud PC cannot be deprovisioned.

Exclude the listed Cloud PC from the selection.

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.