From 2b94c3a6f1ee88218b98f9885b7e989adea527a0 Mon Sep 17 00:00:00 2001 From: "Nicholas S. White" <104782157+nicholasswhite@users.noreply.github.com> Date: Mon, 11 May 2026 08:41:21 -0400 Subject: [PATCH 1/4] 577582 - Add Known issues callout to Android LOB apps article --- intune/app-management/deployment/add-lob-android.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/intune/app-management/deployment/add-lob-android.md b/intune/app-management/deployment/add-lob-android.md index f778418e4a..4b8a97f6c0 100644 --- a/intune/app-management/deployment/add-lob-android.md +++ b/intune/app-management/deployment/add-lob-android.md @@ -1,7 +1,7 @@ --- title: Add an Android Line-of-Business App to Microsoft Intune description: Learn about how to add a Android line-of-business (LOB) app to Microsoft Intune. -ms.date: 04/23/2026 +ms.date: 05/11/2026 ms.topic: how-to ai-usage: ai-assisted ms.reviewer: bryanke @@ -91,6 +91,14 @@ If **Check apps from external sources** is enabled on the Android device, the us > [!IMPORTANT] > When you upload a new version of an Android line-of-business app, existing app configuration policies associated with the previous version don't automatically apply to the updated app. To apply app configuration settings to the updated app, create and assign a new app configuration policy that targets the new app version. +## Known issues + +The following known issues affect app install status reporting for Android Enterprise line-of-business (LOB) apps that are deployed directly to devices. In all cases, the app installs correctly on the device. Only the status displayed in the Microsoft Intune admin center is affected. These issues are being actively addressed. + +- **Lower version shows as Installed instead of In-Conflict.** When two versions of the same LOB app are assigned to a device, the lower version may continue to show as **Installed** in the admin center instead of **In-Conflict**. +- **Play Store app shows Waiting for install or doesn't appear in the report.** When the same app is assigned as both a Managed Google Play app and a direct LOB app, the Play Store app policy may show **Waiting for install** or may not appear in the policy report, instead of showing **In-Conflict**. +- **Conflict resolution and reporting are inconsistent for mixed install intents.** When two versions of the same LOB app are assigned with different install intents (for example, **Install** for one version and **Uninstall** for another), conflict resolution and reporting may not behave as expected. + ## Next steps - The app that you created appears in the list of apps. You can now assign it to groups that you choose. For help, see [How to assign apps to groups](./assign-groups.md). From f678275264e642d624c1084a4d6447533c5bad5f Mon Sep 17 00:00:00 2001 From: Iris Yuning Ye Date: Thu, 14 May 2026 16:00:42 -0400 Subject: [PATCH 2/4] Admin account username for device without user affinity Added a note recommending specific admin account username formats for macOS ADE enrollment policies without user device affinity. --- intune/device-security/laps/setup-macos.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/intune/device-security/laps/setup-macos.md b/intune/device-security/laps/setup-macos.md index bff2fbc56c..a7ac5a9b5a 100644 --- a/intune/device-security/laps/setup-macos.md +++ b/intune/device-security/laps/setup-macos.md @@ -83,6 +83,9 @@ Whenever any part of the local account configuration, the **Await final configur The following are examples of the available configuration options. Additional details are accessible through the *Information* icons that follow the name of some settings. +> [!NOTE] +> For macOS ADE enrollment policies without user device affinity, we recommend configuring the 'Admin account username' to {{serialNumber}}-admin or {{serialNumber}}-user because the that serves as the unique identifier of userless ADE devices.' + - **Admin account username** - Specify the account name or use one of the following supported variables to dynamically create the name. By default, this field uses *Admin*. - {{serialNumber}} - for example, **F4KN99ZUG5V2** - {{partialupn}} - for example, **John.Dupont** From 04f93efb69fd97cad6bbfbfd039cabf9ce9bfded Mon Sep 17 00:00:00 2001 From: Laura Newsad Date: Fri, 15 May 2026 12:07:54 -0400 Subject: [PATCH 3/4] Removed TOC preview link --- autopilot/toc.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/autopilot/toc.yml b/autopilot/toc.yml index 453ab0f17c..ae01db6c5a 100644 --- a/autopilot/toc.yml +++ b/autopilot/toc.yml @@ -46,7 +46,7 @@ items: href: device-preparation/tutorial/user-driven/entra-join-corporate-identifier.md - - name: Windows Autopilot device preparation automatic mode for Windows 365 (preview) + - name: Windows Autopilot device preparation automatic mode for Windows 365 href: device-preparation/tutorial/automatic/automatic-workflow.md items: - name: Step 1 - Set up Windows automatic Intune enrollment From 56797013bbba245418922e8673a77b903410cc15 Mon Sep 17 00:00:00 2001 From: Laura Newsad Date: Fri, 15 May 2026 12:53:49 -0400 Subject: [PATCH 4/4] Revise Admin account username guidance for ADE Updated recommendation for Admin account username format to improve clarity on using serial numbers for unique identification. --- intune/device-security/laps/setup-macos.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/intune/device-security/laps/setup-macos.md b/intune/device-security/laps/setup-macos.md index a7ac5a9b5a..d72d5d82c9 100644 --- a/intune/device-security/laps/setup-macos.md +++ b/intune/device-security/laps/setup-macos.md @@ -84,7 +84,7 @@ Whenever any part of the local account configuration, the **Await final configur The following are examples of the available configuration options. Additional details are accessible through the *Information* icons that follow the name of some settings. > [!NOTE] -> For macOS ADE enrollment policies without user device affinity, we recommend configuring the 'Admin account username' to {{serialNumber}}-admin or {{serialNumber}}-user because the that serves as the unique identifier of userless ADE devices.' +> For macOS ADE enrollment policies without user device affinity, we recommend setting **Admin account username** to `{{serialNumber}}-admin` or `{{serialNumber}}-user`. Using the device serial number helps ensure each userless ADE device has a unique identifier. - **Admin account username** - Specify the account name or use one of the following supported variables to dynamically create the name. By default, this field uses *Admin*. - {{serialNumber}} - for example, **F4KN99ZUG5V2**