Skip to content

Commit fd7eb0b

Browse files
committed
acro fixes
1 parent 59970da commit fd7eb0b

1 file changed

Lines changed: 6 additions & 6 deletions

File tree

windows-365/enterprise/requirements-network.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ ms.collection: M365-identity-device-management
3030

3131
# Network requirements
3232

33-
Windows 365 is a cloud-based service that lets users connect through the internet from any device, from any place, to a Windows Desktop running in Azure. To support these internet connections, you must comply with the networking requirements listed below.
33+
Windows 365 is a cloud-based service that lets users connect through the internet from any device, from any place, to a Windows Desktop running in Azure. To support these internet connections, you must follow the networking requirements listed below.
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

@@ -39,7 +39,7 @@ Each customer has its specific requirements based on the workload they use to pr
3939
To use Cloud PCs, you must meet the following requirements:
4040

4141
- 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 is, define your AD DS DNS servers as the DNS servers for the virtual network.
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.
4343
- The Azure vNet must have network access to an enterprise domain controller, either in Azure or on-premises.
4444
- Network bandwidth: See [Azure’s Network guidelines](/windows-server/remote/remote-desktop-services/network-guidance).
4545
- A subnet within the vNet and available IP address space.
@@ -99,7 +99,7 @@ Configure your Azure Virtual Network where the Cloud PCs are provisioned as foll
9999
>[!TIP]
100100
>Adding at least two DNS servers, as you would with a physical PC, helps mitigate the risk of a single point of failure in name resolution.
101101
102-
See the Azure docs for more information on [configuring Azure Virtual Networks settings](/azure/virtual-network/manage-virtual-network#change-dns-servers).
102+
For more information, see [configuring Azure Virtual Networks settings](/azure/virtual-network/manage-virtual-network#change-dns-servers).
103103

104104
## Remote Desktop Protocol requirements
105105

@@ -120,7 +120,7 @@ Windows 365 uses the Remote Desktop Protocol (RDP).
120120

121121
Microsoft Teams is one of the core Microsoft 365 services within Cloud PC. Windows 365 offloads the audio and video traffic to your endpoint to make the video experience like Teams on a physical PC.
122122

123-
The network quality is very important per scenario. Make sure that you have the proper bandwidth available for the quality that you want to offer.
123+
The network quality is important per scenario. Make sure that you have the proper bandwidth available for the quality that you want to offer.
124124

125125
Full HD (1920x1080p) isn’t a supported resolution for Microsoft Teams on Cloud PCs.
126126

@@ -134,11 +134,11 @@ Full HD (1920x1080p) isn’t a supported resolution for Microsoft Teams on Cloud
134134

135135
## Traffic interception technologies
136136

137-
Some enterprise customers use traffic interception, SSL decryption, deep packet inspection, and other similar technologies for security teams to monitor network traffic. Cloud PC provisioning may need direct access to the virtual machine. These traffic interception technologies can causes issues with running on-premises network connection checks or Cloud PC provisioning. Make sure no network interception is enforced for Cloud PCs provisioned within the Windows 365 service.
137+
Some enterprise customers use traffic interception, SSL decryption, deep packet inspection, and other similar technologies for security teams to monitor network traffic. Cloud PC provisioning may need direct access to the virtual machine. These traffic interception technologies can cause issues with running on-premises network connection checks or Cloud PC provisioning. Make sure no network interception is enforced for Cloud PCs provisioned within the Windows 365 service.
138138

139139
## Bandwidth
140140

141-
Windows 365 uses the Azure network infrastructure. An Azure subscription is required when a virtual network is selected while deploying Windows 365 Enterprise. Bandwith charges for Cloud PC usage include:
141+
Windows 365 uses the Azure network infrastructure. An Azure subscription is required when a virtual network is selected while deploying Windows 365 Enterprise. Bandwidth charges for Cloud PC usage include:
142142

143143
- Network traffic into a Cloud PC is free.
144144
- Outbound (egress) traffic incurs charges against the Azure subscription for the virtual network.

0 commit comments

Comments
 (0)