Merge pull request #8080 from ErikjeMS/win365

acrolinx fixes 7

Author: PRMerger12

windows-365/enterprise/rdp-shortpath-public-networks.md

@@ -66,14 +66,14 @@ For more information about RDP Shortpath benefits, see [Key benefits](/azure/vir
 
 ## RDP Shortpath connection process
 
-When using RDP Shortpath, the connection with the Cloud PC proceeds as follows:
+When you use RDP Shortpath, the connection with the Cloud PC proceeds as follows:
 
 1. The RDP connection establishes a TCP-based connection using the reverse connect transport through the Gateway (in the same way as it does for connectivity without RDP Shortpath).
 2. If RDP Shortpath is enabled on the session host (Cloud PC), the service creates a UDP socket on all viable network interfaces.
 3. To test connectivity, the service attempts to connect to a Windows 365 STUN server on the public internet through UDP port 3478. This step also establishes the external IP address of the NAT router.
 4. The session host’s candidate table lists the public IP and listener port that it has reachable connectivity on. This information is provided to the connecting client through the established TCP session.
 5. The client sends its list of reachable public IP addresses/ports to the session host.
-6. Both parties attempt a connection at the same time. Because both are creating outbound connections, this often allows connectivity to be established through firewalls because no inbound initiated connectivity occurs.
+6. Both parties attempt a connection at the same time. Because both are creating outbound connections, it often allows connectivity to be established through firewalls because no inbound initiated connectivity occurs.
 7. If connectivity is successful, the service evaluates if the connection is the fastest path. If it is, all dynamic virtual channels (such as graphics, input, device redirection, and more) switch to the new transport flow.
 
 ## Known issues

windows-365/enterprise/report-remoting-connection.md

@@ -81,7 +81,7 @@ You can review the **Round trip time** and **Sign in time** for each Cloud PC de
 
 ## Device history
 
-When you click on a particular device in one of the reports, you'll see specific information for that device.  
+When you select on a particular device in one of the reports, you'll see specific information for that device.  
 
 ![Screenshot of using the device history](./media/report-remoting-connection/device-history.png)
 

windows-365/enterprise/report-resource-performance.md

@@ -76,7 +76,7 @@ You can review the CPU spike time and RAM spike time scores and percentages by f
 
 ## Device history
 
-When you click on a particular device in one of the reports, you'll see specific information for that device. If device score is below the baseline, you can improve device performance and score by adding more resources to the device and taking a resize action.
+When you select a particular device in one of the reports, you'll see specific information for that device. If device score is below the baseline, you can improve device performance and score by adding more resources to the device and taking a resize action.
 
 ![Screenshot of using the device history](./media/report-resource-performance/device-history.png)
 

windows-365/enterprise/requirements-network.md

@@ -45,7 +45,7 @@ To use your own network and provision Azure AD joined Cloud PCs, you must meet t
 - Network bandwidth: See [Azure’s Network guidelines](/windows-server/remote/remote-desktop-services/network-guidance).
 - A subnet within the vNet and available IP address space.
 
-To use your own network and provision Hybrid Azure AD joined Cloud PCs, you must meet the above requirements, and the following:
+To use your own network and provision Hybrid Azure AD joined Cloud PCs, you must meet the above requirements, and the following requirements:
 
 - 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.
 - The Azure vNet must have network access to an enterprise domain controller, either in Azure or on-premises.
@@ -117,7 +117,7 @@ Changing the network routes of a Cloud PC (at the network layer or at the Cloud
 
 ## DNS requirements
 
-As part of the Hybrid Azure AD Join requirements, your Cloud PCs must be able to join on-prem Active Directory. That requires that the Cloud PCs be able to resolve DNS records for your on-prem AD environment.
+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.
 
 Configure your Azure Virtual Network where the Cloud PCs are provisioned as follows:
 

windows-365/enterprise/resize-cloud-pc.md

@@ -42,7 +42,7 @@ To resize a Cloud PC, the admin must have any of the following built in Azure Ac
 - Global Admin
 - Intune Service Admin
 
-Alternatively, you can assign a custom role that includes the permissions of the built in roles above.
+Alternatively, you can assign a custom role that includes the permissions of the built-in roles above.
 
 To **Resize** a Cloud PC, it must have a status of **Provisioned** in the Windows 365 provisioning node
 
@@ -60,7 +60,7 @@ Resizing isn’t supported for:
 ![Screenshot of resize a Cloud PC](./media/resize-cloud-pc/resize.png)
 3. You’ll see a list with all the possible SKUs that you can upgrade to. You can only increase a Cloud PC’s storage and specifications. Options with lower storage or specifications are grayed out. Select one of the available options.
 4. Select **Resize**.
-    - When triggering a resize, the Cloud PC will be rebooted and the user will be immediately disconnected from their current session. Make sure the user saves all their work to avoid any potential data lost. 
+    - When triggering a resize, the Cloud PC will be rebooted and the user will be immediately disconnected from their current session. Make sure the user saves all their work to avoid any potential data loss.
     - If there are available licenses, the upgrade will take place.
     - If you have a combination of paid and trial licenses, the resize feature will use your paid licenses first. After these licenses run out, the resize operation will use your trial licenses.
     - If there are no licenses in your inventory, the resizing will fail. You can contact your procurement admin to request more licenses. After the license has been purchased and added to the inventory in the Microsoft Admin Center, you can retry the resize operation.

windows-365/enterprise/security-guidelines.md

@@ -32,15 +32,15 @@ ms.collection: M365-identity-device-management
 
 To help improve security for your Cloud PCs, consider the following general guidelines:
 
-1. Apply Conditional Access policies to control the devices and apps that can connect to your email and company resources. Leverage Conditional Access to secure access end user access to Windows 365.Specifically, considering leveraging Azure Active Directory (Azure AD) Multi-Factor Authentication to authenticate users. For more information, see [What is Conditional Access in Azure Active Directory?](/azure/active-directory/conditional-access/overview)
+1. Apply Conditional Access policies to control the devices and apps that can connect to your email and company resources. Use Conditional Access to secure access end user access to Windows 365.Specifically, considering using Azure Active Directory (Azure AD) Multi-Factor Authentication to authenticate users. For more information, see [What is Conditional Access in Azure Active Directory?](/azure/active-directory/conditional-access/overview)
 2. Use Microsoft Defender for Endpoint to identify threats and set devices as non-compliant. You can easily connect Microsoft Defender for Endpoint to Cloud PC devices, apply device compliance policies to Cloud PCs, and use Conditional Access to identify threats. For more information, see [Enforce compliance for Microsoft Defender for Endpoint with Conditional Access in Intune](/mem/intune/protect/advanced-threat-protection).  
 3. Use Intune compliance policies with Conditional Access policies for Cloud PCs. These policies help identify non-compliant devices and users so they can’t access corporate resources until the device risk level is lowered. For more information, see [Windows 10/11 compliance settings in Microsoft Intune](/mem/intune/protect/compliance-policy-create-windows).
 
     >[!Note]
     >Cloud PCs don't support BitLocker. We recommend excluding this setting from compliance policies targeting Cloud PCs.
 
 4. One of the most important elements of device security is OS updates. These updates make sure that devices stay up-to-date and secure while delivering new features and defenses against vulnerabilities. For Cloud PCs, Endpoint Manager can be used by IT admins to configure Intune Windows 10/11 update rings and policies for Windows Update for Business. For more information, see [Manage Windows 10/11 software updates in Intune](/mem/intune/protect/windows-update-for-business-configure).  
-5. By default Windows 365 Enterprise, end users are not administrators of their Cloud PCs. This aligns with Windows 10/11 security guidance. For more information about this guidance, see [Local Accounts](/windows/security/identity-protection/access-control/local-accounts#sec-restrict-protect-accounts) in the Windows documentation.
+5. By default Windows 365 Enterprise, end users aren't administrators of their Cloud PCs. This policy aligns with Windows 10/11 security guidance. For more information about this guidance, see [Local Accounts](/windows/security/identity-protection/access-control/local-accounts#sec-restrict-protect-accounts) in the Windows documentation.
 6. Windows 365 integrates with Microsoft Defender for Endpoint. Security and endpoint admins can work together to manage their Cloud PC environment just like they manage a physical endpoint. If subscribed, Cloud PCs will:
     - Send data through to Microsoft 365 Secure Score.
     - Unhealthy PCs will show up on the Microsoft Defender for Endpoint Security Center and threat analysis dashboards.

windows-365/enterprise/set-conditional-access-policies.md

@@ -41,7 +41,7 @@ By using Conditional Access policies, you can apply the right access controls wh
 
 ## Assign a Conditional Access policy for Cloud PCs
 
-Conditional Access policies are not set for your tenant by default.  You can target CA policies to the Cloud PC first-party app by using either of the following:
+Conditional Access policies aren't set for your tenant by default.  You can target CA policies to the Cloud PC first-party app by using either of the following platforms:
 
 - Azure. For more information, see [Azure AD Conditional Access](/azure/active-directory/conditional-access/).
 - Microsoft Endpoint Manager. The steps below explain this process. For more information, see [Learn about Conditional Access and Intune](/mem/intune/protect/conditional-access).

windows-365/enterprise/teams-on-cloud-pc.md

@@ -42,7 +42,7 @@ Using Microsoft Teams on a Cloud PC is different from using it on a physical PC.
 
 ## Teams optimizations
 
-The [Windows 10/11 images](device-images.md#gallery-images) in the gallery are pre-configured with required optimization components. When you install and use Microsoft Teams in your cloud PC, you get an optimized experience. These optimization components enable peer-to-peer audio and video calls from your physical endpoint to the other person's endpoint. This creates the same experience as you would have on a physical endpoint running Microsoft Teams.
+The [Windows 10/11 images](device-images.md#gallery-images) in the gallery are pre-configured with required optimization components. When you install and use Microsoft Teams in your cloud PC, you get an optimized experience. These optimization components enable peer-to-peer audio and video calls from your physical endpoint to the other person's endpoint. This situation creates the same experience as you would have on a physical endpoint running Microsoft Teams.
 
 Some of the key benefits of the optimizations are:
 
@@ -55,7 +55,7 @@ Some of the key benefits of the optimizations are:
 Media optimization for Microsoft Teams is only available for the Windows and macOS endpoints. Media optimizations require:
 
 - Remote Desktop client for Windows version 1.2.1026.0 or later (ideally the latest version).
-- Remote Desktop client for macOS version 10.7.7 or later ([preview](..\public-preview.md)). If you upgrade from versions earlier than 10.7.7, you'll also need to go to Microsoft **Remote Desktop Preferences** > **General** and turn on Teams optimizations. If you're using the client for the first time and already have version 10.7.7 or later installed, you won't need to do this. In that case, Teams optimizations are turned on by default.
+- Remote Desktop client for macOS version 10.7.7 or later ([preview](..\public-preview.md)). If you upgrade from versions earlier than 10.7.7, you'll also need to go to Microsoft **Remote Desktop Preferences** > **General** and turn on Teams optimizations. If you're using the client for the first time and already have version 10.7.7 or later installed, you won't need to turn that on. In that case, Teams optimizations are turned on by default.
 
 > [!NOTE]
 > Microsoft Teams installs during the first sign in to the Cloud PC. Installation can take a couple of minutes. Make sure to restart Teams to activate the AV optimizations that redirect audio and video. You can also sign out and in again to your Cloud PC to gain the same result.