Microsoft Store App Deployment During Autopilot – Troubleshooting Guide!

Microsoft Intune provides a streamlined way to manage and deploy applications across Windows devices, including apps from the Microsoft Store. However, IT administrators often encounter deployment issues that can hinder productivity and user experience. These issues can range from installation failures and pending downloads and connectivity problems.

In this article, we will explore common challenges faced for Windows Store app deployment via Intune during Autopilot, along with troubleshooting steps and best practices to ensure a smooth deployment process.

Overview: Microsoft Store App Deployment During Autopilot – Troubleshooting Guide!

Microsoft Intune enables administrators to browse, deploy, and monitor Microsoft Store applications seamlessly. This includes support for Universal Windows Platform (UWP) apps (.appx, .appxbundle, .msix) and Win32 apps (.exe, .msi).

While Intune simplifies app management, deployment issues can arise due to device compatibility, network restrictions, or policy misconfigurations.

To ensure a successful deployment, administrators should first verify that client devices meet the following prerequisites:

• Devices must have at least two core processors to install and run Microsoft Store apps.
• Devices must support the Intune Management Extension (IME) for app installation.
• Devices must have network access to both the Microsoft Store and the destination content. Learn more about Microsoft Store proxy configuration.

In this guide, we will explore common troubleshooting steps to resolve Windows Store app deployment failures during Autopilot. Whether dealing with installation errors, app sync failures, or connectivity issues, this article will help IT admins diagnose and fix problems efficiently.

Add Microsoft Store App

Here’s a step-by-step guide to adding a Microsoft Store app in Intune:

Step 1: Access Microsoft Intune Admin Center

1. Sign in to the Microsoft Intune admin center at https://intune.microsoft.com.
2. In the left navigation panel, go to Apps > Windows.
3. Click on Add to start adding a new application.
4. Under the App type dropdown, select Microsoft Store app (new).
5. Click Select to proceed.

Step 2: Choose the Microsoft Store App

1. Click Search the Microsoft Store app to browse available applications.
2. Enter the app name in the search box and select the desired app.
3. Click Select to confirm your choice.

Step 3: Configure App Information

1. The app details (name, publisher, and description) will be auto-filled from the Microsoft Store.
2. (Optional) Modify any fields as needed.
3. Make sure to modify the install behavior so that the app is installed in the system context “during device setup” or in user context “during account setup”
4. Click Next to proceed.

Step 4: Assign the App to Users or Devices

1. Under Assignments, choose the target group(s) for deployment” it should be the Autopilot device group”
   • Required: Installs the app automatically on assigned devices.
2. Click Next after configuring assignments.

Step 5: Add the store app as a blocking app during Autopilot

Company portal for example

Troubleshooting: Microsoft Store App – Troubleshooting Guide!

The Microsoft Store (new) app is considered a sidecar application, meaning its deployment process closely resembles that of Win32 applications in Intune. However, there are key differences between Win32 and WinGet app deployments, particularly in:

Applicability, Detection, Install, Upgrade, and Uninstall – These steps are managed through AppPackageManager, which interacts with Windows Package Manager (WPM).

Download Process – Unlike Win32 apps, WinGet apps combine the download and install steps into a single operation, eliminating advanced download control.

Understanding whether an app is a UWP or Win32 type helps in troubleshooting:

• From Intune Admin Center: Check the app properties under App Type (listed as either “UWP” or “Win32*”).
• From the Package ID:
  • If the Package ID starts with “9”, it is a UWP app.
  • If the Package ID starts with “X”, it is a Win32 app.

Troubleshooting Steps

Step 1: Collect Required Data

Before deep-diving into troubleshooting, gather the following information:

• Intune Device ID – Found in Intune Admin Center > Devices.
• Store App Name and ID – Located in the app properties.
• ESP policy name and ID, screenshot of the blocking apps
• MDM Diagnostics Logs – Collected via PowerShell or from the device.

Step 2: Check client logs

1. Checking registry dump “MdmDiagReport_RegistryDump.reg”

2. Checking “AppWorkload.log”

• Checking IME installation state and confirm phase
  • [Win32App] Got InstanceID: Sidecar, installationStateString: 3
  • [Win32App] The EspPhase: DeviceSetup.

• Start of check in
  • Getting selected app request for ESP device session Requesting selected apps for ESP

• Shows the policies received from Intune Management Extension service
  • Got result with session id Get policies = [{policies}]

• Start processing subgraph with apps
  • [Win32App][V3Processor] Processing subgraph with app ids:

• Initial detection results (used to determine if action is needed)
  • [Win32App][WinGetApp][WinGetAppDetectionExecutor]

• Applicability results (used to determine if action is needed)
  • [Win32App][WinGetApp][WinGetAppApplicabilityExecutor]

• Install start
  • [Win32App][WinGetApp][WinGetAppExecutionExecutor]

Update ESP state and start execution

State changed from Not Started – Enqueued – Install in progress

Download Started

Download Completed

Download Troubleshooting – UWP Installer Type

• UWP (apps/appxbundle/msix) installers are downloaded and installed using the Microsoft Store.

• The content should be coming from a Microsoft CDN.

Download Troubleshooting – Win32 Installer Type

• Win32 installers are downloaded by the WPM from 3rd party download locations determined by the app publisher. See WPM logs for detailed download progress and url used for download. or by running “Winget show [packageid]” and looking at the Installer > Installer URL property).

Execution

• Post-install detection results

Interested to read more articles from IntuneBytes, this is the link for all posts