You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: windows-365/enterprise/requirements-network.md
+10-4Lines changed: 10 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ keywords:
7
7
author: ErikjeMS
8
8
ms.author: erikje
9
9
manager: dougeby
10
-
ms.date: 11/18/2021
10
+
ms.date: 02/08/2022
11
11
ms.topic: overview
12
12
ms.service: cloudpc
13
13
ms.subservice:
@@ -34,16 +34,22 @@ Windows 365 is a cloud-based service that lets users connect through the interne
34
34
35
35
Each customer has its specific requirements based on the workload they use to pre-calculate the network requirements of their Cloud PC environment.
36
36
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
+
37
40
## General network requirements
38
41
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:
40
43
41
44
- 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.
44
45
- Network bandwidth: See [Azure’s Network guidelines](/windows-server/remote/remote-desktop-services/network-guidance).
45
46
- A subnet within the vNet and available IP address space.
46
47
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
+
47
53
## Allow network connectivity
48
54
49
55
You must allow traffic in your Azure network configuration to the following service URLs and ports:
0 commit comments