Published 2026-05-22 by TechNet New England
When a client reports that a Windows 365 Cloud PC is showing content from the wrong country, the first thing to confirm is the Windows 365 license type. Windows 365 Business and Windows 365 Enterprise behave very differently when it comes to region control, and most of the confusion in this scenario comes from people assuming the two products are interchangeable.
Windows 365 Business: no manual region control
In Windows 365 Business, Cloud PCs are created automatically the moment a license is assigned to a user. There is no provisioning policy in Microsoft Intune where an administrator can pick the Cloud PC region. Microsoft selects the location for you based on the organization's billing country or region and available Microsoft datacenter capacity. This is documented directly by Microsoft (see Windows 365 Business Cloud PC location).
Because of this, changing the Windows display language, regional settings, browser language, or the user's physical location does not move the Cloud PC to another country. The hosting region is locked in at provisioning time by Microsoft, not by the administrator.
This is also why an administrator can see active Cloud PCs in their tenant but not find the provisioning policy options in Intune. Windows 365 Business does not expose those Enterprise management controls. The Cloud PCs work normally, but the deeper geography settings simply are not there.
A typical example: a tenant on Windows 365 Business 2 vCPU, 8 GB RAM, 128 GB storage has users in Canada. Their Cloud PCs end up in a Canadian datacenter. Some websites then identify the Cloud PC's IP address as Canadian, and certain services that require a US IP block access or render the wrong content. With the Business license, there is no supported way to manually move that Cloud PC to a US region from Intune.
Windows 365 Enterprise: full region control through Intune
Windows 365 Enterprise is the Microsoft-supported answer when region matters. With Enterprise, administrators create provisioning policies in Intune and choose the Cloud PC geography and region directly. The organization can place Cloud PCs in a specific US region and manage them more like corporate endpoints, including Intune compliance policies, Conditional Access targeting, and standard endpoint configuration profiles. The full provisioning policy workflow is documented in Create provisioning policies for Windows 365.
Microsoft uses a Geography to Region Group to Region selection model for Enterprise Cloud PCs. The current list of supported geographies and regions (including newer additions like Mexico Central, Spain Central, and Israel Central) is maintained in the Windows 365 requirements documentation.
Moving an existing Enterprise Cloud PC to another region
If the Cloud PC is already provisioned under Windows 365 Enterprise, the administrator can update the provisioning policy and apply the new region to existing Cloud PCs. This is not a Windows setting change. It physically moves the Cloud PC infrastructure to the selected region. The supported procedure is documented at Move a Cloud PC.
A few important operational points pulled from Microsoft's guidance:
- You can move up to 100 devices in a single operation.
- Cloud PCs are shut down and inaccessible for up to several hours during the move.
- The recommended window is over a weekend to minimize user impact.
- Notify users in advance so they can save work and sign out.
- Start with a small batch of non-critical Cloud PCs and verify success before moving critical workloads.
- You cannot move different Cloud PCs in the same policy to different regions in a single edit; you must do them separately.
- You cannot use the edit-provisioning-policy method to change virtual network or subnet. For VNet or subnet changes, create a new Azure Network Connection and then move the Cloud PCs to it.
What to do if the Cloud PC is currently on Business
If the user is on Windows 365 Business and the organization needs US-based Cloud PCs, the path is:
- Switch the user to the equivalent Windows 365 Enterprise license.
- Create a US-based provisioning policy in Intune.
- Reprovision the Cloud PC under that policy, or move the Cloud PC once it is associated with the new policy.
A side-by-side feature comparison is available at Compare Windows 365 Business and Enterprise.
Why a VPN is not the same as changing the region
A VPN inside the Cloud PC can be used as a workaround, but it does not change the Cloud PC's hosting region. A VPN only changes the public IP address that websites see for outbound traffic. If the Cloud PC connects to a US-based VPN endpoint, websites may see a US IP address, but the Cloud PC itself is still hosted wherever Microsoft originally placed it.
VPNs can also introduce routing problems, especially if Remote Desktop Protocol traffic is forced through the VPN tunnel instead of using split tunneling. The Microsoft guidance on RDP routing for Cloud PCs is in Network requirements for Windows 365, which explicitly notes that changing network routes at the Cloud PC layer (including VPN) can break the connection to the Azure Virtual Desktop RDP broker.
For compliance scenarios (data residency, regulated industries), a VPN is not a substitute for actually placing the Cloud PC in the correct region.
Quick reference
Windows 365 Business
- No manual region control.
- No Intune provisioning policy for region selection.
- Region is automatically selected by Microsoft.
- Changing Windows regional settings does not move the Cloud PC.
- A VPN may change website-visible IP location but not the actual hosting region.
- Up to 300 seats per tenant.
Windows 365 Enterprise
- Region can be controlled through Intune provisioning policies.
- Cloud PCs can be provisioned into a selected geography or region.
- Existing Cloud PCs can be moved to a different supported region.
- Full Intune management, custom images, and Conditional Access targeting.
- Better suited for organizations that need consistent IP location, compliance control, and predictable deployment.
The short answer for a Canada-to-US scenario
Yes, you can do it, but only with Windows 365 Enterprise. If the user is on Windows 365 Business, the region cannot be changed manually from Intune. The clean fix is to switch the user to the equivalent Windows 365 Enterprise license, build a US provisioning policy, and either reprovision or move the Cloud PC into a US region.
A common misconception
This is not a user-location problem after the Cloud PC is built. If the Cloud PC is provisioned in the United States and the user later signs in from Canada, the Cloud PC stays in the United States. Most websites will see the US datacenter IP address. Some apps or browsers may use the physical device's location if the user grants location permission in the browser, but that does not change the Cloud PC's actual hosting region.
Bottom line
If the goal is for the Cloud PC to consistently behave as a US-based machine, Windows 365 Enterprise with a US provisioning policy is the supported, durable solution. Windows 365 Business is simpler and cheaper, and it works well for organizations that do not care about region. The moment region or compliance matters, you need Enterprise.
References
- What is Windows 365? (Microsoft Learn)
- What is Windows 365 Enterprise? (Microsoft Learn)
- Compare Windows 365 Business and Enterprise (Microsoft Learn)
- Windows 365 Business Cloud PC location (Microsoft Learn)
- Create provisioning policies for Windows 365 (Microsoft Learn)
- Move a Cloud PC (Microsoft Learn)
- Provisioning in Windows 365 (Microsoft Learn)
- Windows 365 requirements (supported geographies and regions) (Microsoft Learn)
- Network requirements for Windows 365 (Microsoft Learn)
- Optimal provisioning of Cloud PCs (Microsoft Learn)
- Cross-region disaster recovery in Windows 365 (Microsoft Learn)
If you are running into region or licensing issues with Windows 365 and need help mapping out the cleanest migration path, contact TechNet New England at info@technetnewengland.com or (413) 459-9663.