Merge pull request #6738 from MicrosoftDocs/main

v-dihans · web-flow · commit 8e8f95e684a6 · 2022-02-08T11:34:37.000-07:00
Publish 02/08/2022, 10:30 AM
diff --git a/memdocs/intune/apps/apps-deploy.md b/memdocs/intune/apps/apps-deploy.md
@@ -97,7 +97,7 @@ The following table lists the various options for *assigning* apps to users and
 The app is now assigned to the groups that you selected. For more information about including and excluding app assignments, see [Include and exclude app assignments](apps-inc-exl-assignments.md).
 
 > [!Tip]
-> Intune supports assigning apps to nested groups too. For example, if you assigned an app to the "Enineering Global" group and have "Engineering APAC", "Engineering EMEA" and "Engineering US" nested as child groups, the members of those child groups will also be targeted with the assignment.
+> Intune supports assigning apps to nested groups too. For example, if you assigned an app to the "Engineering Global" group and have "Engineering APAC", "Engineering EMEA" and "Engineering US" nested as child groups, the members of those child groups will also be targeted with the assignment.
 
 ## How conflicts between app intents are resolved
 
diff --git a/memdocs/intune/configuration/device-profile-assign.md b/memdocs/intune/configuration/device-profile-assign.md
@@ -153,7 +153,7 @@ Use the following matrix to understand support for excluding groups:
 | 2 | ✔️ Supported </br></br> Assigning a policy to a dynamic device group while excluding a static device group is supported. |
 | 3 | ❌ Not supported </br></br> Assigning a policy to a dynamic device group while excluding user groups (both dynamic and static) isn't supported. Intune doesn't evaluate user-to-device group relationships, and devices of the included users won't be excluded. |
 | 4 | ❌ Not supported </br></br> Assigning a policy to a dynamic device group and excluding user groups (both dynamic and static) isn't supported. Intune doesn't evaluate user-to-device group relationships, and devices of the included users won't be excluded. |
-| 5 | ❌ Not supported </br></br> Assigning a policy to a static device group while excluding a dynamic device group is supported. But, it's not recommended in scenarios that are sensitive to latency. Any delay in exclude group membership calculation can cause policies to be offered to devices. In this scenario, we recommend using [filters](../fundamentals/filters.md) instead of dynamic device groups for excluding devices. |
+| 5 | ❕ Partially supported </br></br> Assigning a policy to a static device group while excluding a dynamic device group is supported. But, it's not recommended in scenarios that are sensitive to latency. Any delay in exclude group membership calculation can cause policies to be offered to devices. In this scenario, we recommend using [filters](../fundamentals/filters.md) instead of dynamic device groups for excluding devices. |
 | 6 | ✔️ Supported </br></br> Assigning a policy to a static device group and excluding a different static device group is supported. |
 | 7 | ❌ Not supported </br></br> Assigning a policy to a static device group and excluding user groups (both dynamic and static) isn't supported. Intune doesn't evaluate user-to-device group relationships, and devices of the included users won't be excluded. |
 | 8 | ❌ Not supported </br></br> Assigning a policy to a static device group and excluding user groups (both dynamic and static) isn't supported. Intune doesn't evaluate user-to-device group relationships, and devices of the included users won't be excluded. |
diff --git a/memdocs/intune/fundamentals/whats-new.md b/memdocs/intune/fundamentals/whats-new.md
@@ -7,7 +7,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 02/01/2022
+ms.date: 02/07/2022
 ms.topic: conceptual
 ms.service: microsoft-intune
 ms.subservice: fundamentals
@@ -60,6 +60,13 @@ You can use RSS to be notified when this page is updated. For more information,
 ### Scripts
 -->
 
+## Week of February 7, 2022
+
+### App management
+
+#### Advanced logging setting in Company Portal app<!-- 12859998  -->
+The **Enable Advanced Logging** setting is available in the Intune Company Portal app versions v5.2202 and higher for iOS/iPadOS and macOS. Device users can able to enable or disable advanced logging on a device. By turning on advanced logging, detailed log reports will be sent to Microsoft to troubleshoot issues. By default, the **Enable Advanced Logging** setting will be off. Device users should keep this setting off unless otherwise instructed by their organization's IT admin. For related information, see [Share Company Portal usage data with Microsoft](../user-help/turn-off-microsoft-usage-data-collection-ios.md) and [Manage Company Portal preferences for macOS](../user-help/intune-company-portal-preferences-macos.md).
+
 ## Week of January 31, 2022
 
 ### Device security
diff --git a/memdocs/intune/user-help/intune-company-portal-preferences-macos.md b/memdocs/intune/user-help/intune-company-portal-preferences-macos.md
@@ -7,7 +7,7 @@ keywords:
 author: lenewsad
 ms.author: lanewsad
 manager: dougeby
-ms.date: 07/19/2021
+ms.date: 02/07/2022
 ms.topic: end-user-help
 ms.prod:
 ms.service: microsoft-intune
@@ -47,6 +47,15 @@ This setting enables Microsoft to collect data about your Intune Company Portal
 
 To turn off data collection in Company Portal, clear the checkbox next to **Allow Microsoft to collect usage data**.  
 
+## Enable or disable advanced logging
+
+The **Enable Advanced Logging** setting is available in the Intune Company Portal app for macOS devices. Device users can able to enable or disable advanced logging on a device. By turning on advanced logging, detailed log reports will be sent to Microsoft to troubleshoot issues. By default, the **Enable Advanced Logging** setting will be off. Device users should keep this setting off unless otherwise instructed by their organization's IT admin.
+
+To modify this setting on an macOS device:
+1. Open the Company Portal app.
+2. Go to the menu bar and select **Company Portal** > **Preferences**. 
+3. Under **Advanced logging**, modify the checkbox next to **Turn on advanced logging**.
+
 ## Next steps  
 
 Still need help? Contact your IT support person. For contact information, check the [Company Portal website](https://go.microsoft.com/fwlink/?linkid=2010980).
diff --git a/memdocs/intune/user-help/turn-off-microsoft-usage-data-collection-ios.md b/memdocs/intune/user-help/turn-off-microsoft-usage-data-collection-ios.md
@@ -8,7 +8,7 @@ author: lenewsad
 
 ms.author: lanewsad
 manager: dougeby
-ms.date: 12/08/2020
+ms.date: 02/07/2022
 ms.topic: end-user-help
 ms.prod:
 ms.service: microsoft-intune
@@ -51,6 +51,15 @@ Change your usage data preferences to turn usage data collection on or off.
 2. Tap **Company Portal**.  
 3. Switch the **Usage Data** toggle to the off position (to stop usage and diagnostic data from being sent to Intune), or to the on position (to allow usage and diagnostic data to be sent to Intune).   
 
+## Enable or disable advanced logging
+
+The **Enable Advanced Logging** setting is available in the Intune Company Portal app for iOS/iPadOS devices. Device users can able to enable or disable advanced logging on a device. By turning on advanced logging, detailed log reports will be sent to Microsoft to troubleshoot issues. By default, the **Enable Advanced Logging** setting will be off. Device users should keep this setting off unless otherwise instructed by their organization's IT admin.
+
+To modify this setting on an iOS/iPadOS device:
+1. Open the **Settings** app.
+2. Find **Comp Portal**.
+3. Under **Diagnostics**, turn on or off the **Enable Advanced Logging** toggle.
+
 ## Next steps  
 
 Still need help? Contact your IT support person. For contact information, check the [Company Portal website](https://go.microsoft.com/fwlink/?linkid=2010980).
diff --git a/windows-365/enterprise/requirements-network.md b/windows-365/enterprise/requirements-network.md
@@ -86,6 +86,15 @@ You must allow traffic in your Azure network configuration to the following serv
 
 All endpoints connect over port 443.
 
+### Remote Desktop Protocol (RDP) broker service endpoints
+
+Azure Virtual Desktop RDP broker service endpoints are critical to Cloud PC performance. These endpoints affect both connectivity and latency. To align with the [Microsoft 365 network connectivity principles](/microsoft-365/enterprise/microsoft-365-network-connectivity-principles?view=o365-worldwide#new-office-365-endpoint-categories), you should categorize these endpoints as **Optimize** endpoints.
+
+To make it easier to configure network security controls, use Azure Virtual Desktop service tags to identity those endpoints for direct routing using an [Azure Networking User Defined Route (UDR)](/azure/virtual-network/virtual-networks-udr-overview). A UDR will result in direct routing between your virtual network and the RDP broker for lowest latency. For more information about Azure Service Tags, see (Azure service tags overview)[/azure/virtual-desktop/network-connectivity].
+
+Changing the network routes of a Cloud PC (at the network layer or at the Cloud PC layer (e.g. VPN)), might break the connection between the Cloud PC and the Azure Virtual Desktop RDP broker. If so, the end user will be disconnected from their Cloud PC until a connection be established.
+
+
 ## 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.
