Merge pull request #8781 from MicrosoftDocs/main

Publish 10/13/2022 3:30 PM PT

Author: Angela Fleischmann

memdocs/intune/enrollment/android-dedicated-devices-fully-managed-enroll.md

@@ -161,14 +161,14 @@ Add a zero-touch configuration in the [zero-touch enrollment portal](https://par
 
     ```json
     {
-        "android.app.extra.PROVISIONING_DEVICE_ADMIN_COMPONENT_NAME": "com.google.android.apps.work.clouddpc/.receivers.CloudDeviceAdminReceiver",
+    "android.app.extra.PROVISIONING_DEVICE_ADMIN_COMPONENT_NAME": "com.google.android.apps.work.clouddpc/.receivers.CloudDeviceAdminReceiver",
+    "android.app.extra.PROVISIONING_DEVICE_ADMIN_SIGNATURE_CHECKSUM": "I5YvS0O5hXY46mb01BlRjq4oJJGs2kuUcHvVkAPEXlg",
+    "android.app.extra.PROVISIONING_DEVICE_ADMIN_PACKAGE_DOWNLOAD_LOCATION": "https://play.google.com/managed/downloadManagingApp?identifier=setup",
+    "android.app.extra.PROVISIONING_ADMIN_EXTRAS_BUNDLE": {
+        "com.google.android.apps.work.clouddpc.EXTRA_ENROLLMENT_TOKEN": "YourEnrollmentToken"
+    }
+}
 
-        "android.app.extra.PROVISIONING_DEVICE_ADMIN_SIGNATURE_CHECKSUM": "I5YvS0O5hXY46mb01BlRjq4oJJGs2kuUcHvVkAPEXlg",
-
-        "android.app.extra.PROVISIONING_DEVICE_ADMIN_PACKAGE_DOWNLOAD_LOCATION": "https://play.google.com/managed/downloadManagingApp?identifier=setup",
-
-        "android.app.extra.PROVISIONING_ADMIN_EXTRAS_BUNDLE": {
-            "com.google.android.apps.work.clouddpc.EXTRA_ENROLLMENT_TOKEN": "YourEnrollmentToken"
  6. Enter your organization's name and support information, which is shown on screen while users set up their devices.   
 
 For more information about how to assign a default configuration or apply a configuration in the zero-touch portal, see [Zero-touch enrollment for IT admins](https://support.google.com/work/android/answer/7514005) (opens Android Enterprise Help docs).  

memdocs/intune/fundamentals/whats-new.md

@@ -96,12 +96,13 @@ In the admin center, you can:
 
 #### Non-compliance warning message includes a link<!--13694184  -->
 
-A link has been added to the notification **View device compliance information** and it allows a helper to learn more about why the device is not compliant in Microsoft Endpoint Manager.
-
-If the device that the helper is connecting to is not compliant with your organization's assigned security policies, then the non-compliance warning about that device is displayed along with a link.
+In Remote help, a link has been added to the non-compliance warning notification **View device compliance information** and it allows a helper to learn more about why the device is not compliant in Microsoft Endpoint Manager.
 
 For more information, go to:
-[Monitor Device compliance](../protect/compliance-policy-monitor.md)
+
+ - [Microsoft Intune Remote Help](../remote-actions/remote-help.md)
+
+ - [Monitor Device compliance](../protect/compliance-policy-monitor.md)
 
 Applies to:
 **Windows 10/11**

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

@@ -384,7 +384,7 @@ New updates for the connector can take a week or more to become available for ea
 > [!IMPORTANT]  
 > Starting April 2022, certificate connectors earlier than version **6.2101.13.0** will be deprecated and will show a status of *Error*. Starting August 2022, these connector versions **won't** be able to revoke certificates. Starting September 2022, these connector versions **won't** be able to issue certificates. This includes both the [PFX Certificate Connector for Microsoft Intune](../protect/certificate-connectors.md#pfx-certificate-connector-release-history) and  [Microsoft Intune Connector](../protect/certificate-connectors.md#microsoft-intune-connector-release-history), which on July 29, 2021 were replaced by the *Certificate Connector for Microsoft Intune* (as detailed in this article).
 
-### September 21, 2202
+### September 21, 2022
 
 Version **6.2206.122.0** - Changes in this release:
 

memdocs/intune/protect/microsoft-tunnel-configure.md

@@ -65,6 +65,10 @@ Use of a *Server configuration* lets you create a configuration a single time an
    - **IP ranges to include**
    - **IP ranges to exclude**
 
+  > [!NOTE]
+  > Do not use an IP range that specifies 0.0.0.0 in any of the include or exclude addresses, Tunnel Gateway cannot route traffic when this range is used.
+  > 
+
 5. On the **Review + create** tab, review the configuration, and then select **Create** to save it.
 
 ## Create a Site

memdocs/intune/remote-actions/remote-help.md

@@ -7,7 +7,7 @@ keywords:
 author: Smritib17
 ms.author: smbhardwaj
 manager: dougeby
-ms.date: 09/02/2022
+ms.date: 10/13/2022
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: remote-actions
@@ -53,9 +53,11 @@ The Remote help app supports the following capabilities:
 
 - **Requires Organization login** - To use remote help, both the helper and the sharer must sign in with an Azure Active Directory (Azure AD) account from your organization. You can’t use remote help to assist users who aren’t members of your organization.
 
-- **Compliance Warnings** - Before connecting to a user's device, a helper will see a non-compliance warning about that device if it’s not compliant with its assigned policies. This warning doesn’t block access but provides transparency about the risk of using sensitive data like administrative credentials during the session.
-
-  Unenrolled devices are always reported as non-compliant. This is because until a device enrolls with Intune it can’t receive policies from Intune and as such is unable to establish its compliance status.
+- **Compliance Warnings** - Before connecting to a user's device, a helper will see a non-compliance warning about that device if it’s not compliant with its assigned policies. This warning doesn’t block access but provides transparency about the risk of using sensitive data like administrative credentials during the session. 
+    
+    - Helpers who have access to device views in Intune will see a link in the warning to the device properties page in Microsoft Endpoint Manager. This allows a helper to learn more about why the device is not compliant.
+ 
+    - Unenrolled devices are always reported as non-compliant. This is because until a device enrolls with Intune it can’t receive policies from Intune and as such is unable to establish its compliance status.
 
 - **Role-based access control** – Admins can set RBAC rules that determine the scope of a helper’s access, like:
   - The users who can help others and the range of actions they can do while providing help, like who can run elevated privileges while helping.

memdocs/intune/user-help/enroll-device-android-company-portal.md

@@ -35,7 +35,7 @@ Enroll your personal or corporate-owned Android device with Intune Company Porta
 Company Portal supports devices running Android 8.0 and later, including devices secured by Samsung KNOX Standard 2.4 and later. To learn how to update your Android device, see [Check & update your Android version](https://support.google.com/android/answer/7680439).  
 
 </br>
-> [!VIDEO https://www.youtube.com/embed/k0Q_sGLSx6o?]
+> [!VIDEO  https://www.youtube.com/embed/k0Q_sGLSx6o]
 
 > [!NOTE]
 > Samsung Knox is a type of security that certain Samsung devices use for additional