5.1.1. Preparing and Deploying Win32, LOB, and Store Apps
💡 First Principle: Windows gives you three ways to deliver an app, and they trade convenience for control. A store app updates itself but offers few knobs. An MSI line-of-business app is quick to add but takes a single command-line argument. A Win32 app takes the most setup — you package it, write install commands and tell Intune exactly how to detect it — and in exchange gives you dependencies, supersedence, requirement rules, restart handling and reliable behavior during Autopilot. When a scenario needs any of those extras, the answer is Win32.
Start with the menu. Every app begins at Apps > All Apps > Create, which opens the Select app type pane. The categories are store apps, LOB apps, built-in apps, web links and apps from other Microsoft services, and each platform has its own formats:
| Platform | Store apps | Line-of-business formats | Other app types |
|---|---|---|---|
| Windows | Microsoft Store app (new) | .msi, .appx, .appxbundle, .msix, .msixbundle; Windows app (Win32) uses .intunewin | Enterprise App Catalog app (Win32), Microsoft 365 Apps, Microsoft Edge, Windows web link |
| iOS/iPadOS | iOS store app (searched inside Intune); volume-purchased apps from Apple Business Manager | .ipa | iOS/iPadOS web clip, built-in app |
| Android | Managed Google Play app (Android Enterprise); Android store app (Play URL) | .apk | Android Enterprise system app, built-in app |
| macOS | Volume-purchased apps from Apple Business Manager | .pkg; macOS app (DMG) uses .dmg | macOS app (PKG) for unmanaged PKGs, Microsoft 365 Apps, Edge, Defender for Endpoint (macOS), macOS web clip |
Two rules from that table come up often. Store and built-in apps update automatically, but for LOB apps "you must update the app" yourself. And size limits differ: Win32 apps can be up to 30 GB each, Windows LOB/AppX/MSIX apps 8 GB and iOS/iPadOS LOB apps 2 GB.
Packaging a Win32 app. A Win32 app starts as a folder of installer files, which the Microsoft Win32 Content Prep Tool (IntuneWinAppUtil.exe) compresses into a single .intunewin file. Its parameters are -c for the setup folder, -s for the setup file, -o for the output folder and -q for quiet mode; run it with no parameters and it prompts for each value. It zips every file and subfolder in the setup folder, so keep the tool itself out of that folder, and use the latest version — Intune warns about packages built with an older one. For an MSI setup file, the tool also extracts the details Intune needs for detection.
The program step defines how the app installs. The Installer type is either Command line or PowerShell script; a script replaces the install command, runs in the same context as the installer, is limited to 50 KB, and its return code decides success or failure. If Multi-Admin Approval is enabled, you can't upload a PowerShell installer script while creating the app — create the app first, then add the script. (App deployments are one of the resource types a Multi-Admin Approval access policy can protect. In a tenant with such a policy, creating, editing, deleting or assigning an app waits for a second administrator to approve, and the requester then selects Complete to apply the change. App protection policies aren't covered by that resource type.) Install behavior is System (all users of the device) or User; use System for Entra registered devices, and remember that a user-context install that needs admin rights fails for a standard user. Installation time required defaults to 60 minutes, up to 1,440. Return codes are typed as Failed, Hard reboot, Soft reboot, Retry or Success — a Retry code makes the agent try three times, five minutes apart.
Requirements and detection decide whether and whether it worked. Requirement rules check OS architecture, minimum OS, disk, memory and CPU, plus optional file, registry or script rules. Detection rules — at least one, and all must be satisfied — can be MSI product code, file, registry or a custom script. A detection script counts the app as installed only when it exits 0 and writes to STDOUT; anything written to STDERR means "not installed".
Dependencies and supersedence relate apps to each other, and the exam loves the difference:
| Dependency | Supersedence | |
|---|---|---|
| Purpose | Install a prerequisite first | Update or replace an older app |
| Targeting | Dependent apps install automatically by default — no assignment needed | Superseding app needs its own assignment |
| Applies to | Win32 apps only (MSI LOB and Store apps can't be dependencies) | Win32 apps only |
| Key option | Automatically install (default Yes); max 100 dependencies including sub-dependencies | Uninstall previous version: No = update, Yes = replace |
Both are added only after the app exists, and creating either needs the Mobile apps > Relate permission.
MSI line-of-business apps suit simple installers. The command-line field accepts only one argument (such as /q) — no msiexec, /i or /x — so if you need more, use Win32. For self-updating MSIs such as Google Chrome, set Ignore app version = Yes so Intune doesn't fight the app's own updater.
Microsoft Store app (new) replaces the retired Microsoft Store for Business integration. You browse and search the Store from inside Intune, and creation takes three steps: App information, Assignments, Review + create. It supports UWP apps, MSIX-packaged desktop apps and Win32 apps (Win32 Store apps are in preview). Clients need at least two processor cores and Intune Management Extension (IME) support; paid apps and ARM64 installers aren't supported. Win32 Store apps are kept updated by Intune and must stay assigned to keep updating, while UWP apps update through the Store itself. The Turn off the Store application policy blocks users from installing arbitrary Store apps but doesn't stop Intune installing them — and winget.exe isn't affected by it either.
Finally, two 2026 delivery changes. Since June 2026 Intune requires HTTPS to deliver Win32 app content (Connected Cache nodes without HTTPS are bypassed and clients fall back to the CDN). And since service release 2609, Intune uses push notifications for admin-initiated Win32 app changes, so devices check in sooner; for push-dependent scenarios, firewalls must allow *.trouter.communications.svc.cloud.microsoft.
⚠️ Exam Trap: Superseding apps aren't targeted automatically — you must assign the new version. Dependencies are the opposite: they install even when unassigned. A scenario where "the new version never installed" after configuring supersedence usually means the superseding app has no assignment.
Reflection Question: A vendor's installer needs three command-line switches and must install only on devices with at least 8 GB of RAM, and the help desk wants Intune to confirm success by checking a registry value. Why does each requirement push you toward a Win32 app rather than an MSI LOB app?