Merge pull request #6833 from MicrosoftDocs/lenewsad-patch-1

Freshness: Update windows-enrollment-status.md

Author: Angela Fleischmann

memdocs/autopilot/troubleshoot-oobe.md

@@ -28,7 +28,7 @@ ms.topic: troubleshooting
 When the out-of-box-experience (OOBE) includes unexpected Autopilot behavior, it's useful to check if the device received an Autopilot profile. If so, check the settings that the profile contained. Depending on the Windows client release, there are different mechanisms available to do that.
 
 > [!NOTE]
-> **[Preview]** With Windows 11, you can enable users to view additional detailed troubleshooting information about the Autopilot provisioning process. The [Windows Autopilot diagnostics page](windows-autopilot-whats-new.md#preview-windows-autopilot-diagnostics-page) provides IT admins and end users with a user-friendly view to troubleshoot Windows Autopilot failures. This feature can be enabled by going to the [ESP profile](../intune/enrollment/windows-enrollment-status.md#available-settings) and selecting **Yes** to **Allow users to collect logs about installation errors**. This feature is currently supported for commercial OOBE, and Autopilot user-driven mode.
+> **[Preview]** With Windows 11, you can enable users to view additional detailed troubleshooting information about the Autopilot provisioning process. The [Windows Autopilot diagnostics page](windows-autopilot-whats-new.md#preview-windows-autopilot-diagnostics-page) provides IT admins and end users with a user-friendly view to troubleshoot Windows Autopilot failures. This feature can be enabled by going to the [ESP profile](../intune/enrollment/windows-enrollment-status.md) and selecting **Yes** to **Allow users to collect logs about installation errors**. This feature is currently supported for commercial OOBE, and Autopilot user-driven mode.
 
 ## Can't connect to MDM terms of use error
 

memdocs/autopilot/windows-autopilot-whats-new.md

@@ -65,7 +65,7 @@ An example of the diagnostics page is shown below. In this example, **Configurat
 ![diagnostics page click](images/oobe-02.png)<br>
 ![diagnostics page expand](images/oobe-03.png)
 
-The diagnostics page can be enabled by going to the [ESP profile](../intune/enrollment/windows-enrollment-status.md#available-settings) and selecting **Yes** to **Turn on log collection and diagnostics page for end users**. 
+The diagnostics page can be enabled by going to the [ESP profile](../intune/enrollment/windows-enrollment-status.md) and selecting **Yes** to **Turn on log collection and diagnostics page for end users**. 
 
 The diagnostics page is currently supported for commercial OOBE, and Autopilot user-driven mode. It is currently available on Windows 11. Windows 10 users can still collect and export diagnostic logs when this setting is enabled in Intune. 
 

memdocs/intune/enrollment/android-enroll.md

@@ -31,7 +31,7 @@ ms.collection:
   - highpri
 ---
 
-# Enroll Android devices
+# Enroll Android devices  
 
 [!INCLUDE [azure_portal](../includes/azure_portal.md)]
 
@@ -41,7 +41,7 @@ As an Intune administrator, you can enroll Android devices in the following ways
     - [**Android Enterprise dedicated**](android-kiosk-enroll.md): For corporate-owned, single use devices, such as digital signage, ticket printing, or inventory management. Admins lock down the usage of a device for a limited set of apps and web links. It also prevents users from adding other apps or taking other actions on the device.
     - [**Android Enterprise fully managed**](android-fully-managed-enroll.md): For corporate-owned, single user devices used exclusively for work and not personal use. Admins can manage the entire device and enforce policy controls unavailable to personally-owned/corporate-owned work profiles.
     - [**Android Enterprise corporate-owned with a work profile**](android-corporate-owned-work-profile-enroll.md): For corporate-owned, single user devices intended for corporate and personal use.
-- [**Android device administrator**](android-enroll-device-administrator.md), including Samsung Knox Standard devices and [Zebra devices](../configuration/android-zebra-mx-overview.md). In areas where Android Enterprise is available, Google is encouraging movement off device administrator (DA) management by decreasing its management support in new Android releases. However, where Android Enterprise or Google Mobile Services (GMS) are unavailable, you'll want to use device administrator and familiarize yourself with these changes. For more information, see [Is Android Enterprise available in my country](https://support.google.com/work/android/answer/6270910)?  
+- [**Android device administrator**](android-enroll-device-administrator.md), including Samsung Knox Standard devices and [Zebra devices](../configuration/android-zebra-mx-overview.md). Device administrator should be used in areas where Android Enterprise or Google Mobile Services (GMS) is unavailable.  Google has decreased support for device administrator (DA) management in areas where Android Enterprise is available, and encourages organizations to migrate to Android Enterprise device management. For a list of countries that support Android Enterprise, see [Is Android Enterprise available in my country](https://support.google.com/work/android/answer/6270910)?  
 - Android (AOSP), currently in public preview, offers a set of enrollment options for devices that aren't integrated with Google Mobile services.  
     - [Corporate-owned, user associated devices](android-aosp-corporate-owned-user-associated-enroll.md): For corporate-owned, single user devices intended exclusively for work and not personal use. Admins can manage the entire device.  
     - [Corporate-owned, userless devices](android-aosp-corporate-owned-userless-enroll.md): For corporate-owned, shared devices. Admins can manage the entire device.