แชร์ผ่าน


Requirements for Windows 365

To use Cloud PCs, you must meet the following requirements:

Azure requirements

None, if you plan on provisioning Microsoft Entra joined Cloud PCs on a Microsoft hosted network.

If you choose to provision Cloud PCs on your own network, an active Azure subscription with the following configurations is required:

  • Sufficient permissions to grant Windows 365:
    • A reader role on the Azure subscription.
    • Windows365 network interface contributor role on the specified resource group.
    • Windows365 network user role on the virtual network.

Microsoft Entra ID and Intune requirements

  • A valid and working Intune and Microsoft Entra tenant.
  • Intune default device type enrollment restrictions must be set to Allow Windows (MDM) platform for corporate enrollment. For more information, see Device Enrollment Restrictions Limitations.
  • Infrastructure configuration: If you plan on provisioning Microsoft Entra hybrid joined Cloud PCs, you must configure your infrastructure to automatically Microsoft Entra hybrid join any devices that domain join to the on-premises Active Directory. This configuration lets them be recognized and managed in the cloud.
  • Microsoft Entra Domain Services isn't supported because it doesn't support Microsoft Entra hybrid join.

Domain requirements

None, if you plan on provisioning Microsoft Entra joined Cloud PCs on a Microsoft hosted network.

If you choose to provision Microsoft Entra hybrid joined Cloud PCs, then the following configurations on your domain are required:

  • If an organizational unit is specified, ensure it exists and is valid.
  • An Active Directory user account with sufficient permissions to join the computer into the specified organizational unit within the Active Directory domain. If you don't specify an organizational unit, the user account must have sufficient permissions to join the computer to the Active Directory domain.
  • User accounts that are assigned Cloud PCs must have a synced identity available in both Active Directory and Microsoft Entra ID.

Note

For the user account used to join the Cloud PCs to the Active Directory Domain Services, make sure to set up appropriate delegation following the instructions in Increase the computer account limit in the Organizational Unit.

Licensing requirements

  • You must have an Intune license to use Intune to manage the devices.
  • Windows 365 Enterprise: Users must have licenses for Windows E3, Intune, Microsoft Entra ID P1, and Windows 365 to use their Cloud PC.
  • Windows 365 Frontline: Users must
    • Have licenses for Windows E3, Intune, Microsoft Entra ID P1.
    • Be added to the Microsoft Entra security group in the provisioning policy to use their Cloud PC.

Management requirements

  • You must use Microsoft Intune admin center to manage your Cloud PCs.
  • You must have a Windows 365 Enterprise or Frontline license to manage Cloud PC configurations.

Role and identity requirements

Supported Azure regions for Cloud PC provisioning

Windows 365 manages the capacity and availability of underlying Azure resources as part of the service, partnering closely with Azure to select regions that meet our requirements for availability and capacity. To maximize resiliency and minimize provisioning failures, Windows 365 now uses a three-tier region selection model:

  • Geography: The broadest grouping, such as Europe, Asia, or US East. Selecting a geography includes all region groups and regions within that area.
  • Region Group: Typically maps to a specific boundary (e.g., Germany, Japan, US East). Selecting a region group includes all Azure regions within that boundary.
  • Region: The most granular option, representing a specific Azure region (e.g., Germany West Central, Japan East).

Microsoft strongly recommends using the default selection within your provisioning policy. This maximizes the number of possible regions for Cloud PC deployment, significantly decreasing the chance of provisioning failure and improving overall service resiliency. Learn more about the benefits of multi-region selection with MHN.

You can create a virtual network for use with an Azure Network Connection or use the Microsoft Hosted Network for provisioning Cloud PCs in the following Azure regions (categorized by geography):

Africa

Region Group Region
South Africa South Africa North

Asia

Region Group Region
Hong Kong SAR East Asia
Japan Japan East
Japan Japan West
South Korea Korea Central
Singapore Southeast Asia

Australasia

Region Group Region
Australia Australia East

Canada

Region Group Region
Canada Canada Central

Central America

Region Group Region
Mexico Mexico Central

Europe

Region Group Region
France (EU) France Central
Germany (EU) Germany West Central
Ireland (EU) North Europe
Italy (EU) Italy North
Netherlands (EU) West Europe
Norway Norway East
Poland (EU) Poland Central
Spain (EU) Spain Central
Sweden (EU) Sweden Central
Switzerland Switzerland North
United Kingdom UK South

India

Region Group Region
India India Central

Middle East

Region Group Region
Qatar Qatar Central
Israel Israel Central
UAE UAE North

US Central

Region Group Region
US Central Central US
US Central South Central US

US East

Region Group Region
US East East US
US East East US 2

US West

Region Group Region
US West West US 2 (Restricted)
US West West US 3

Brazil

Region Group Region
Brazil Brazil South (Restricted)

Some features might not be available in some regions.

Next steps

Review network requirements