Skip to content

Commit c797872

Browse files
committed
reword
1 parent 4469f51 commit c797872

1 file changed

Lines changed: 15 additions & 4 deletions

File tree

windows-365/enterprise/requirements-network.md

Lines changed: 15 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ Each customer has its specific requirements based on the workload they use to pr
4141

4242
### [Windows 365 Enterprise](#tab/enterprise)
4343

44-
To use your own network and provision Azure AD joined Cloud PCs, you must meet the following requirements:
44+
To use your own network and provision Azure Active Directory (Azure AD) joined Cloud PCs, you must meet the following requirements:
4545

4646
- Azure virtual network: You must have a virtual network (vNET) in your Azure subscription in the same region as where the Windows 365 desktops are created.
4747
- Network bandwidth: See [Azure’s Network guidelines](/windows-server/remote/remote-desktop-services/network-guidance).
@@ -56,10 +56,22 @@ To use your own network and provision Hybrid Azure AD joined Cloud PCs, you must
5656

5757
All of the Windows 365 Enterprise requirements apply to [Windows 365 Government](introduction-windows-365-government.md) with the following additions:
5858

59-
To use your own network and provision either Azure AD joined or Hybrid Azure AD joined Cloud PCs, you must meet the following requirements:
59+
#### Azure Active Directory joined Cloud PCs
60+
61+
To use your own network and provision Azure AD joined Cloud PCs, you must meet the following requirements:
6062

6163
- The customer must have a subscription in the Azure Government environment.
62-
- Azure virtual network: You must have a virtual network (vNET) in your Azure Government subscription in the same region as where the Windows 365 Cloud PCs are created. For Government Community Cloud (GCC) and Government Community Cloud - High (GCCH), this will be a US Gov region.
64+
- Azure virtual network: You must have a virtual network (vNET) in your Azure Government subscription in the same region as where the Windows 365 Cloud PCs are created. For Government Community Cloud (GCC) and Government Community Cloud High (GCCH), this will be a US Gov region.
65+
- Network bandwidth: See [Azure’s Network guidelines](/windows-server/remote/remote-desktop-services/network-guidance).
66+
- A subnet within the vNet and available IP address space.
67+
68+
#### Hybrid Azure AD joined Cloud PCs
69+
70+
To use your own network and provision Hybrid Azure AD joined Cloud PCs, you must meet the above requirements, and the following requirements:
71+
72+
- The customer must have a subscription in the Azure Government environment.
73+
- The Azure virtual network must be able to resolve DNS entries for your Active Directory Domain Services (AD DS) environment. To support this resolution, define your AD DS DNS servers as the DNS servers for the virtual network.
74+
- The Azure vNet must have network access to an enterprise domain controller, either in Azure or on-premises.
6375

6476
---
6577

@@ -196,7 +208,6 @@ To make it easier to configure network security controls, use Azure Virtual Desk
196208

197209
Changing the network routes of a Cloud PC (at the network layer or at the Cloud PC layer like VPN) might break the connection between the Cloud PC and the Azure Virtual Desktop RDP broker. If so, the end user will be disconnected from their Cloud PC until a connection be re-established.
198210

199-
200211
## DNS requirements
201212

202213
As part of the Hybrid Azure AD Join requirements, your Cloud PCs must be able to join on-premises Active Directory. That requires that the Cloud PCs be able to resolve DNS records for your on-premises AD environment.

0 commit comments

Comments
 (0)