Merge pull request #7309 from MicrosoftDocs/main

Publish 04/08/2022, 10:30 AM

Author: v-dihans

memdocs/intune/enrollment/android-samsung-knox-mobile-enroll.md

@@ -132,11 +132,11 @@ Still need help? Check out the complete [KME User Guide](https://docs.samsungkno
 
 ## Frequently asked questions
 
-- **Device Owner support:** - **Device Owner support:** Intune supports enrolling Dedicated and Fully Managed devices by using the KME portal. Other Android enterprise device owner modes will be supported as they become available in Intune.
+- **Device Owner support:** Intune supports enrolling Dedicated and Fully Managed devices by using the KME portal. Other Android enterprise device owner modes will be supported as they become available in Intune.
 
-- **No work profile support:** KME is a corporate device enrollment method and devices enrolled in Android personally-owned work profile ensure work and personal data are separate on personal devices. So, device enrollment to personally-owned work profile using KME isn't a supported scenario in Intune.
+- **Work profile support:** KME is a corporate device enrollment method and devices enrolled in Android personally-owned work profile ensure work and personal data are separate on personal devices. Device enrollment to personally-owned work profile using KME is a supported scenario in Intune.
 
-- **Factory reset to enroll to Android enterprise:** If repurposing devices that have already been set up, devices need to be factory reset when enrolling to Android enterprise.
+- **Factory reset to enroll to Android enterprise:** If repurposing devices that have already been set up, devices need to be factory reset when enrolling to Android Enterprise.
 
 - **Updates using Google Play account:** Google Play account isn't necessary for enrolling the device to Microsoft Intune. But, for Android device administrator enrollments, future updates to the Intune Company Portal app may require a Google Play account on the device. Google Play account isn't required when enrolling to Google Device Owner.
 

memdocs/intune/enrollment/corporate-identifiers-add.md

@@ -37,6 +37,8 @@ As an Intune admin, you can identify devices as corporate-owned to refine manage
 At the time of enrollment, Intune automatically assigns corporate-owned status to devices that are:
 
 - Enrolled with a [device enrollment manager](device-enrollment-manager-enroll.md) account (all platforms)
+- Enrolled by using [Google Zero Touch](android-dedicated-devices-fully-managed-enroll.md#enroll-by-using-google-zero-touch)
+- Enrolled by using [Knox Mobile Enrollment](android-samsung-knox-mobile-enroll.md)
 - Enrolled with the Apple [Device Enrollment Program](device-enrollment-program-enroll-ios.md), [Apple School Manager](apple-school-manager-set-up-ios.md), or [Apple Configurator](apple-configurator-enroll-ios.md) (iOS/iPadOS only)
 - [Identified as corporate-owned before enrollment](#identify-corporate-owned-devices-with-imei-or-serial-number) with an international mobile equipment identifier (IMEI) numbers (all platforms with IMEI numbers) or serial number (iOS/iPadOS and Android)
 - Enrolled as [Android Enterprise corporate-owned devices with work profile](/mem/intune/enrollment/android-corporate-owned-work-profile-enroll)

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

@@ -141,12 +141,12 @@ For more information and command-line examples, see [mst-cli command-line tool f
 
 ## View Microsoft Tunnel logs
 
-Microsoft Tunnel logs information to the Linux server logs in the *syslog* format. To view log entries, use the **journalctl -t** command followed by one or more tags that are specific to Microsoft Tunnel entries:
+Microsoft Tunnel logs information to the Linux server logs in the *syslog* format. To view log entries, use the **journalctl -t** command followed by one or more tags that are specific to Microsoft Tunnel entries:    
 
 - **ocserv** -  Display server logs.
 - **mstunnel-agent**: Display agent logs.
 - **mstunnel_monitor**: Display monitoring task logs.
-
+  
 For example, to view information for only the tunnel server, run `journalctl -t ocserv`.  To view information for all three, you can run `journalctl -t ocserv -t mstunnel-agent -t mstunnel_monitor`.
 
 You can add  `-f` to the command to display an active and continuing view of the log file.   For example, to actively monitor ongoing processes for Microsoft Tunnel, run `journalctl -t mstunnel_monitor -f`.
@@ -157,6 +157,7 @@ More options for *journalctl*:
 - `man journalctl` – Display additional information.
 - `man journalctl.conf` Display information on configuration
 For more information about *journalctl*, see the documentation for the version of Linux that you use.  
+<!-- Pending ocserv-access -->
 
 ## Next steps
 

memdocs/intune/remote-actions/collect-diagnostics.md

@@ -45,7 +45,7 @@ The *Collect diagnostics* remote action is supported for:
 - Windows 10 version 1909 and later.
 - Windows 11
 - Microsoft HoloLens 2 2004 and later.
-- Global Admins, Intune Admins, or a role with **Collect diagnostics** permissions (under **Remote tasks**).
+- Global Admins, Intune Admins, or a role with **Collect diagnostics** (under **Remote tasks**) and **Read** (under **Device compliance policies**) permissions.
 - Corporate-owned devices.
 - Devices that are online and able to communicate with the service during diagnostics.