Merge pull request #6167 from MicrosoftDocs/master

11/18/2021 AM Publish

Author: Taojunshen

memdocs/intune/protect/certificate-connector-overview.md

@@ -219,7 +219,7 @@ All events are tagged with a Task Category to aid in filtering.  Task categories
 
 Updates for the Certificate Connector for Microsoft Intune are released periodically. When we update the connector, you can read about the changes here.
 
-New updates for the connector can take several days to become available for each tenant. If an update isn’t available for your tenant yet, check back in a day or so.
+New updates for the connector can take a week or more to become available for each tenant.
 
 ### November 17, 2021
 

memdocs/intune/protect/mde-security-integration.md

@@ -7,7 +7,7 @@ keywords:
 author: brenduns
 ms.author: brenduns
 manager: dougeby
-ms.date: 11/17/2021
+ms.date: 11/18/2021
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: protect
@@ -66,7 +66,7 @@ When a device that is domain joined creates a trust with Azure Active Directory,
 - Azure Active Directory Connect (AAD Connect) must be synchronized to the tenant that is used from Microsoft Defender for Endpoint
 - Hybrid Azure Active Directory Join must be configured in your environment (either through Federation or AAD Connect Sync)
 - AAD Connect Sync must include the device objects *in scope* for synchronization with Azure Active Directory (when needed for join)
-- AAD Connect rules for sync must be modified for Server 2012 R2 (when support for Server 2012 R2 is needed)
+- AAD Connect rules for sync must be modified for Server 2012 R2 (when support for Server 2012 R2 is needed). For more information see [Instructions for applying Computer Join rule in AAD Connect](/microsoft-365/security/defender-endpoint/troubleshoot-security-config-mgt?view=o365-worldwide#instructions-for-applying-computer-join-rule-in-aad-connect)
 
 ### Connectivity Requirements
 

memdocs/intune/protect/windows-10-update-rings.md

@@ -31,7 +31,7 @@ ms.collection: M365-identity-device-management
 
 Create update rings that specify how and when Windows as a Service updates your Windows 10/11 devices with [*feature* and *quality* updates](/windows/deployment/update/get-started-updates-channels-tools#types-of-updates). With Windows 10/11, new feature and quality updates include the contents of all previous updates. As long as you've installed the latest update, you know your Windows devices are up to date. Unlike with previous versions of Windows, you now must install the entire update instead of part of an update.
 
-Update rings can also be used to upgrade your eligible Windows 10 devices to Windows 11. To do so, when creating a policy you use the setting named *Upgrade Windows 10 devices to Latest Windows 11 release* by configuring it as *Yes*. When you use update rings to upgrade to Windows 11, devices install the most current version of Windows 11. If you later set the upgrade setting back to *No*, devices that haven't started the upgrade will not start while devices that are in the process of upgrading will continue to do so. Devices that have completed the upgrade will remain with Windows 11. For more information on eligibility, see [Windows 11 Specs and System Requirements | Microsoft](/windows/windows-11-specifications).
+Update rings can also be used to upgrade your eligible Windows 10 devices to Windows 11. To do so, when creating a policy you use the setting named *Upgrade Windows 10 devices to Latest Windows 11 release* by configuring it as *Yes*. When you use update rings to upgrade to Windows 11, devices install the most current version of Windows 11. If you later set the upgrade setting back to *No*, devices that haven't started the upgrade will not start while devices that are in the process of upgrading will continue to do so. Devices that have completed the upgrade will remain with Windows 11. For more information on eligibility, see [Windows 11 Specs and System Requirements | Microsoft](https://www.microsoft.com/windows/windows-11-specifications).
 
 Windows update rings support [scope tags](../fundamentals/scope-tags.md). You can use scope tags with update rings to help you filter and manage sets of configurations that you use.
 

memdocs/intune/protect/windows-update-settings.md

@@ -77,7 +77,7 @@ Update settings control what bits a device will download, and when. For more inf
 - **Upgrade Windows 10 devices to Latest Windows 11 release**  
   **Default**: No
 
-  When set to *Yes*, eligible Windows 10 devices will upgrade to the most current Windows 11 release. For more information on eligibility, see [Windows 11 Specs and System Requirements | Microsoft](/windows/windows-11-specifications).
+  When set to *Yes*, eligible Windows 10 devices will upgrade to the most current Windows 11 release. For more information on eligibility, see [Windows 11 Specs and System Requirements | Microsoft](https://www.microsoft.com/windows/windows-11-specifications).
 
 - **Set feature update uninstall period (2 – 60 days)**  
   **Default**: 10  

memdocs/intune/remote-actions/device-rename.md

@@ -51,13 +51,16 @@ This feature doesn't support renaming hybrid Azure AD Windows devices.
 
 1. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
 2. Choose **Devices** > **All devices** > choose a device > **...** > **Rename device**.
-3. In the **Rename device** pane, type the new name in the text box. You can use letters, numbers, and hyphens. The name must contain at least one letter or hyphen. Android Enterprise dedicated devices are an exception, and don’t require a letter or hyphen.
+3. In the **Rename device** pane, type the new name in the text box. You can use letters, numbers, and hyphens. The name must contain at least one letter or hyphen. Android Enterprise dedicated, fully managed, and corporate-owned work profile devices are an exception, and don’t require a letter or hyphen.
 4. If you want to restart the device after renaming it, choose **Yes** next to **Restart after rename**.
 5. Choose **Rename**.
 
 > [!NOTE]
 > If you have an enrollment profile (iOS) that uses a Device Name Template, the device will be renamed but will revert to using the template upon the next sync with Intune.
 
+> [!NOTE]
+> It may take 10 minutes or more for a renamed Android Enterprise device to update in the Devices blade.
+
 ## Windows device rename rules
 
 When renaming a Windows device, the new name must follow these rules:

windows-365/enterprise/create-custom-image-support-teams.md

@@ -41,7 +41,7 @@ The following steps are only needed when you aren’t using the Windows 365 gall
     - Type: DWORD
     - Value: 1
 2. Install the [latest Visual C++ runtime](https://support.microsoft.com/help/2977003/the-latest-supported-visual-c-downloads). This is required for the Teams WebRTC protocol redirection to work.
-3. Install the [WebRTC Redirector (websocket) plugin](https://query.prod.cms.rt.microsoft.com/cms/api/am/binary/RE4AQBt). For instructions on how to install, see [Install the Teams WebSocket Service](/azure/virtual-desktop/teams-on-avd#install-the-teams-websocket-service). The plugin is required for Teams to function properly in a Cloud PC environment with the optimizations.
+3. Install the [WebRTC Redirector (websocket) plugin](https://query.prod.cms.rt.microsoft.com/cms/api/am/binary/RWNg9F). For instructions on how to install, see [Install the Teams WebSocket Service](/azure/virtual-desktop/teams-on-avd#install-the-teams-websocket-service). The plugin is required for Teams to function properly in a Cloud PC environment with the optimizations.
 
 > [!NOTE]
 > Don’t install the Microsoft Teams desktop application. If you want Microsoft Teams on the Cloud PC, install Microsoft 365 Apps + Teams by using Microsoft Endpoint Manager.

windows-365/enterprise/requirements-network.md

@@ -7,7 +7,7 @@ keywords:
 author: ErikjeMS  
 ms.author: erikje
 manager: dougeby
-ms.date: 08/02/2021 
+ms.date: 11/18/2021 
 ms.topic: overview
 ms.service: cloudpc
 ms.subservice:
@@ -30,7 +30,7 @@ ms.collection: M365-identity-device-management
 
 # Network requirements
 
-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.
+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.
 
 Each customer has its specific requirements based on the workload they use to pre-calculate the network requirements of their Cloud PC environment.  
 
@@ -39,7 +39,7 @@ Each customer has its specific requirements based on the workload they use to pr
 To use Cloud PCs, you must meet the following requirements:
 
 - 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.
-- 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.
+- 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.
 - The Azure vNet must have network access to an enterprise domain controller, either in Azure or on-premises.
 - 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.
@@ -84,13 +84,11 @@ You must allow traffic in your Azure network configuration to the following serv
   - global.azure-devices-provisioning.net (443 & 5671 outbound)
   - hm-iot-in-*.azure-devices.net (443 & 5671 outbound)
 
-
-
 All endpoints connect over port 443.
 
 ## 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-prem Active Directory. That requires that the Cloud PCs be able to resolve DNS records for your on-prem AD environment.
 
 Configure your Azure Virtual Network where the Cloud PCs are provisioned as follows:
 
@@ -101,7 +99,7 @@ Configure your Azure Virtual Network where the Cloud PCs are provisioned as foll
 >[!TIP]
 >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.
 
-See the Azure docs for more information on [configuring Azure Virtual Networks settings](/azure/virtual-network/manage-virtual-network#change-dns-servers). 
+For more information, see [configuring Azure Virtual Networks settings](/azure/virtual-network/manage-virtual-network#change-dns-servers).
 
 ## Remote Desktop Protocol requirements
 
@@ -122,7 +120,7 @@ Windows 365 uses the Remote Desktop Protocol (RDP).
 
 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.
 
-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.
+The network quality is important per scenario. Make sure that you have the proper bandwidth available for the quality that you want to offer.
 
 Full HD (1920x1080p) isn’t a supported resolution for Microsoft Teams on Cloud PCs.
 
@@ -136,7 +134,18 @@ Full HD (1920x1080p) isn’t a supported resolution for Microsoft Teams on Cloud
 
 ## Traffic interception technologies
 
-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.
+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.
+
+## Bandwidth
+
+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:
+
+- Network traffic into a Cloud PC is free.
+- Outbound (egress) traffic incurs charges against the Azure subscription for the virtual network.
+- Office data (like email and OneDrive for Business file sync) incurs egress charges if the Cloud PC and a user’s data reside in different regions.
+- RDP networking traffic always incurs egress charges.
+
+For more information about costs associated with data transfers, see [Bandwidth pricing]( https://azure.microsoft.com/pricing/details/bandwidth/).
 
 <!-- ########################## -->
 ## Next steps