Skip to content

Commit c80e802

Browse files
committed
changes
1 parent cf3be8e commit c80e802

1 file changed

Lines changed: 10 additions & 4 deletions

File tree

windows-365/enterprise/requirements-network.md

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ keywords:
77
author: ErikjeMS
88
ms.author: erikje
99
manager: dougeby
10-
ms.date: 11/18/2021
10+
ms.date: 02/08/2022
1111
ms.topic: overview
1212
ms.service: cloudpc
1313
ms.subservice:
@@ -34,16 +34,22 @@ Windows 365 is a cloud-based service that lets users connect through the interne
3434

3535
Each customer has its specific requirements based on the workload they use to pre-calculate the network requirements of their Cloud PC environment.
3636

37+
>[!Note]
38+
>This article only applies if you plan on provisioning Cloud PCs on your own Azure virtual network, as opposed to a Microsoft-hosted network.
39+
3740
## General network requirements
3841

39-
To use Cloud PCs, you must meet the following requirements:
42+
To use your own network and provision Azure AD joined Cloud PCs, you must meet the following requirements:
4043

4144
- 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.
42-
- The Azure virtual network must be able to resolve DNS entries for your Active Directory Domain Services (AD DS) environment. To do this, define your AD DS DNS servers as the DNS servers for the virtual network.
43-
- The Azure vNet must have network access to an enterprise domain controller, either in Azure or on-premises.
4445
- Network bandwidth: See [Azure’s Network guidelines](/windows-server/remote/remote-desktop-services/network-guidance).
4546
- A subnet within the vNet and available IP address space.
4647

48+
To use your own network and provision Hybrid Azure AD joined Cloud PCs, you must meet the above requirements, as well as the following:
49+
50+
- The Azure virtual network must be able to resolve DNS entries for your Active Directory Domain Services (AD DS) environment. To do this, define your AD DS DNS servers as the DNS servers for the virtual network.
51+
- The Azure vNet must have network access to an enterprise domain controller, either in Azure or on-premises.
52+
4753
## Allow network connectivity
4854

4955
You must allow traffic in your Azure network configuration to the following service URLs and ports:

0 commit comments

Comments
 (0)