Is it possible to migrate Windows 365 virtual devices from one Entra ID tenant to another one?

Windows 365 Cloud PCs themselves cannot be moved directly between Entra ID tenants, but the underlying Azure-based virtual machines can be migrated into Windows 365 in a different tenant by using the Windows 365 Migration API and snapshot-based provisioning.

Key points from the supported migration scenario:

1. Supported source
   • Migration is supported from Azure-based virtual machines (Entra joined or Entra hybrid joined) to Windows 365 Cloud PCs.
   • The migration is snapshot-based: only a fixed-format VHD of the OS disk (no data disks) is supported.
2. What can be migrated
   • The VHD snapshot contains the full OS disk of the source VM, including:
     • Installed third‑party applications
     • Application settings stored on the OS disk
     • User profiles and data that reside on the OS disk (subject to Windows 365 OS and disk-size compatibility)
   • This allows preserving the “image” of the user environment, not just files in Desktop/Documents.
3. Requirements and limitations
   • VM must be Gen2, Windows 10 or later, with a healthy Azure VM agent.
   • No third‑party agents may be present at snapshot time; they must be uninstalled before snapshot creation.
   • Only the OS disk is supported; no additional data disks.
   • The snapshot must be stored as a page blob in a customer-owned Azure Storage account and exposed via SAS URI or appropriate permissions.
   • Cross‑tenant access to the storage account is not supported, so the snapshot must be accessible within the target tenant’s context.
   • Only Enterprise Cloud PCs in the commercial cloud are supported.
   • A snapshot can’t be reused across multiple provisions, and one user can have only one imported VHD at a time.
4. Provisioning into the target tenant
   • Use the Migration API (via Microsoft Graph) with parameters such as:
     • userId (Entra ID of the target user in the new tenant)
     • snapshotLocation (SAS URI or storage account details)
     • Optional policyId to select the provisioning policy.
   • Ensure the target user is in the new tenant and does not already have the same version of Cloud PC.
   • After uploading the snapshot and configuring the user for snapshot-based provisioning, assign the appropriate Windows 365 license to trigger Cloud PC provisioning.
   • Monitor provisioning and errors via Graph API.
5. Practical implication for tenant-to-tenant moves
   • There is no “in-place” tenant switch for an existing Cloud PC.
   • The supported pattern is:
     1. Capture a compliant VHD snapshot of the source Azure VM (representing the old Cloud PC environment).
     2. Store it in an Azure Storage account in the target tenant (or otherwise accessible without cross‑tenant access).
     3. Use the Migration API in the new tenant to provision a Windows 365 Cloud PC from that snapshot for the corresponding user.
   • This approach preserves third‑party applications and their settings as long as they are compatible with Windows 365 and do not rely on disallowed agents or unsupported configurations.

For user files (Desktop, Documents, etc.), OneDrive and other content-migration tools remain appropriate. For application state and configuration, the snapshot-based migration into Windows 365 is the supported mechanism, subject to the constraints above.

References:

• Migration to Windows 365
• Device identity and desktop virtualization
• Microsoft 365 tenant-to-tenant migrations