In today’s example, we will look at the tasks that must be carried out if you want to redeploy a Windows 365 desktop to another Azure region.

Who redeploys Windows 365 to another region?

The reality is that we will probably not encounter many cases where we need to change the region of our Cloud PC. In our experience, we have carried out this migration mainly for two reasons. The first is that we had a Cloud PC hosted in a region where nested virtualization was not allowed, which prevented us from enabling Hyper-V and using virtual machines inside our cloud desktop. You can check the Windows 365 regions compatible with Hyper-V from this link.

The other scenario was to improve the latency or response time of our cloud desktop. For example, by migrating our Cloud PCs from the North Europe Azure region, located in Ireland, to France Central, we observed an improvement of about 35 ms in latency. To check which Azure region works best for you, you can use this website. According to Microsoft’s criteria for Azure Virtual Desktop, the user experience is optimal if latency is below 150 ms. Between 150 ms and 200 ms, the experience is acceptable for tasks such as word processing. However, any latency above 200 ms will negatively impact the experience of using the cloud desktop.

How to migrate to another region?

Let’s begin with the scenario in which our Windows 365 instances are hosted in our Azure subscription. First, we access the Windows 365 view within Intune’s device section and create a new Azure network connection. Before proceeding, it is advisable to have already created the subnet in Azure that we plan to use, if it does not already exist.

We fill in the following information according to our needs:

Once the Azure network connection is created, we go to the provisioning policies and edit our current policy to specify that we want to start using the new Azure region.

At this point, it will be enough to click the button to apply the current configuration and select the option to apply the region change.

Now we only need to wait between 20 and 30 minutes for the process to complete successfully and for our cloud desktop to become available again. After this time, the internal identifier of the Cloud PC will change (also known as the UUID in any Windows installation). We may need to re‑register our device in certain systems, as happened when using CLAPS. When the machine ID changes, it is recognized as a completely new device and, for security reasons, access to information stored under the previous ID is blocked.

If our Windows 365 desktops are hosted in Microsoft datacenters, we must follow the same procedure, but change the Cloud PC location options within the provisioning policy instead of using our Azure configuration.

Does Migrating Regions in Windows 365 Pay Off?

Ante la pregunta ¿merece la pena si se redespliega Windows 365 en otra región?, nuestra respuesta es que sí. Pero para llegar a esta conclusión tenemos que detectar primero alguno de los problemas que hemos identificado en este artículo. En condicionales normales, no suele ser habitual ver cómo se redespliega Windows 365 en otra región.

When asked whether redeploying Windows 365 to another region is worth it, our answer is yes. However, to reach this conclusion, we must first identify one of the issues described in this article. Under normal circumstances, it is not common to see Windows 365 being redeployed to another region.

Con esto, ya podremos empezar a disfrutar de nuestro escritorio de Windows 365 desde la nueva región que acabamos de configurar mejorando así la experiencia del usuario final.

With this, we will be able to start enjoying our Windows 365 desktop from the newly configured region, thereby improving the end‑user experience.