Enhanced Cloud PC Move Capabilities for Windows 365 with Microsoft Intune

On Dec. 11^th, 2024, Microsoft announced a significant step in simplifying Cloud PC management with the latest enhancements to the Cloud PC move capability in Windows 365 on Microsoft Intune. This feature allows administrators to seamlessly move devices between regions or Azure network connections (ANCs), ensuring flexibility and scalability. The new enhancements include granular move, enhanced tracking and reporting, and expanded support for Windows 365 Frontline. These updates are rolling out gradually and are expected to be available to all customers by the end of January 2025.

What’s New?

1. Granular Move for Greater Flexibility
   Administrators can now move Cloud PCs in smaller, more manageable batches instead of migrating all Cloud PCs associated with a policy at once. This flexibility is especially useful for organizations that require phased migrations to reduce disruptions or test network connectivity.
2. Enhanced Tracking and Reporting
   Monitoring move progress is now easier than ever. The Cloud PC actions report provides detailed insights into the status of initiated moves at a batch level. Admins can track progress, view success or failure statuses, and assess time elapsed for each move, streamlining troubleshooting and ensuring transparency.
3. Support for Windows 365 Frontline
   Previously limited to Windows 365 Enterprise Cloud PCs, the move capability now extends to Windows 365 Frontline. This inclusion allows administrators to migrate dedicated Cloud PCs seamlessly, further enhancing the reach and usability of Windows 365 in frontline operations.

Why These Updates Matter

These enhancements empower IT teams with:

• Improved flexibility in Cloud PC migrations, catering to diverse organizational needs.
• Comprehensive visibility into migration progress for better planning and execution.
• Broader applicability with support for both Enterprise and Frontline Cloud PCs.

These updates reflect Microsoft’s commitment to streamlining device management and optimizing the Cloud PC experience for businesses worldwide.

Why Move Your Cloud PC?

Before diving into the technical steps, it’s important to understand why you might need to move your Cloud PCs. Some common reasons include:

Performance Optimization: Relocating to a region closer to your user base can significantly reduce latency and improve performance.

Compliance Requirements: Certain industries and regions have specific data residency laws that necessitate keeping data within particular geographic boundaries.

Cost Management: Different regions may offer varying costs for cloud services, allowing for potential savings.

Preparation: Planning Your Move

Upgrade Your Browser

Firstly, ensure you are using a supported browser for the best experience. Microsoft Edge is recommended due to its compatibility with the latest features, security updates, and technical support.

Step by Step Guide to Moving Cloud PCs

Accessing the Microsoft Intune Admin Center

To begin the process, sign in to the Microsoft Intune admin center. Here’s how:

1. Navigate to the Intune admin center.

2. Select Devices.

3. Under Provisioning, choose Windows 365.

4. Select Provisioning policies.

5. Choose the policy you wish to edit.

Editing the Provisioning Policy

Once you’ve accessed the required policy, follow these steps to make the necessary changes:

For Entra ID Join you can either:

• On a Microsoft hosted network, change the Geography and/or Region
• On an Azure network connection, change the ANC used.

If the join type is Hybrid Microsoft Entra join, then you can only change the ANC, obviously you would need an extra ANC to move the devices to.

For this test, I am moving an Entra ID Join device which is on the Microsoft hosted network, therefore I have to change the Geography and Region. Currently my devices are in India in the Central India region.

I have decided to move them to South East Asia Region

Applying Configuration Changes

After making the necessary edits, you’re ready to move the existing Cloud PCs:

1. Select Apply this configuration.

2. Ensure that the domain defined in the new ANC matches that of the Cloud PCs you want to move. The domain used in the original ANC must be reachable from the new ANC.

3. All Cloud PCs provisioned after these changes will be created in the new region.

Points to note.

1. Before transferring all Cloud PCs to the new region, a backup process is initiated to safeguard their data. This backup may require some time to complete and can commence while the user is actively signed in and using the Cloud PC.
2. Once the backup process is finished, the Cloud PC is subsequently powered down.
3. The Cloud PC now undergoes relocation, and during this process, which may span several hours, it becomes temporarily inaccessible.

Throughout the move, you can track the progress by checking the status in the All Cloud PCs section. Whilst moving, the Status will state Moving region or network. The move is considered complete once the status displays Provisioned.

Best Practices for Moving Cloud PCs

Timing the Move

The best time to perform Cloud PC moves is over the weekend. This timing helps to minimize the impact on users, as Cloud PCs will be shut down and inaccessible for up to several hours during the move process. It’s advisable to notify users in advance so they can save their work and sign out.

Gradual Transition

When moving many devices to a new region, it’s prudent to start with a few noncritical Cloud PCs. This allows you to check for success and iron out any issues before moving the more critical Cloud PCs.

Monitoring and Managing the Move

Tracking the Move

You can track the status of moving Cloud PCs using the Cloud PC actions report. This report provides insights into the progress and any potential issues that may arise during the move.

Post Move Considerations

New Cloud PCs created by the edited provisioning policy will be assigned to the new region or ANC. It’s important to note that:

• Cloud PCs can’t be moved from one provisioning policy to another.
• You can’t move some Cloud PCs to one region and other Cloud PCs to another region in the same policy edit operation.
• You can’t move Cloud PCs from one virtual network or subnet to another using the edit provisioning policy method. Instead, create a new ANC with the updated vNet/subnet and then move the Cloud PCs to the new ANC.

Moving Cloud PCs can seem like a daunting task, but with careful planning and execution, it can be managed efficiently. By following the steps outlined in this guide and adhering to best practices, you can ensure a smooth transition with minimal disruption to your users.

That’s all about today; you have a great time ahead.