Domain 3 β€” Module 1 of 5 20%
18 of 27 overall
Domain 3: Manage Applications Free ⏱ ~11 min read

App Deployment: Prepare & Package

Before you can deploy an app through Intune, you need to understand app types and how to package them. Learn to prepare Win32 apps, LOB apps, web links, and store apps.

Why does app preparation matter?

Simple explanation

Think of Intune as a postal service for apps.

You can’t just hand a loose pile of files to the post office β€” you need to put them in a box (package), attach a label (metadata), and include delivery instructions (install commands). Different items need different boxes: a letter goes in an envelope, a parcel needs a box, a fragile item needs bubble wrap.

Apps work the same way. An MSI installer, a Win32 .exe, a web link, and a store app each need different preparation before Intune can deliver them to devices.

App types in Intune

App TypeFormatPreparation NeededBest For
Win32 app.exe, .msi wrapped as .intunewinConvert with Win32 Content Prep ToolMost desktop apps β€” maximum flexibility
Line-of-business (LOB).msi, .msix, .appx, .appxbundleUpload directlySimple MSI installers, modern MSIX packages
Microsoft Store appStore linkSelect from store catalogModern apps from the Microsoft Store
Web linkURLJust enter the URLShortcuts to web applications
Microsoft 365 AppsBuilt-inConfigure in Intune β€” no file uploadWord, Excel, PowerPoint, Outlook (see Module 20)
iOS/Android store appsStore linkSearch the store in IntuneMobile apps from Apple App Store / Google Play
Managed Google PlayStore linkSearch Managed Google PlayAndroid Enterprise apps

Packaging Win32 apps

Win32 apps offer the most flexibility but require an extra preparation step:

The Win32 Content Prep Tool

  1. Download the Microsoft Win32 Content Prep Tool (IntuneWinAppUtil.exe)
  2. Create a source folder containing your installer and any supporting files
  3. Run the tool:
    IntuneWinAppUtil.exe
    -c <source folder>
    -s <setup file (e.g., setup.exe)>
    -o <output folder>
  4. Output: a .intunewin file that you upload to Intune

Configuring a Win32 app in Intune

SettingWhat You ConfigureExample
App informationName, description, publisher, version”7-Zip 24.08 by Igor Pavlov”
ProgramInstall command, uninstall command, behaviourInstall: 7z2408-x64.msi /qn; Uninstall: msiexec /x {GUID} /qn
RequirementsOS version, disk space, RAM, architectureWindows 10 1903+, 64-bit
Detection rulesHow Intune knows the app is installedMSI product code, file exists, or registry key
DependenciesOther apps that must be installed first.NET Runtime required before app
SupersedenceReplaces an older version of the app7-Zip 24.08 supersedes 7-Zip 23.01
AssignmentRequired, Available, or UninstallRequired for all devices
Exam tip: detection rules are critical

Detection rules tell Intune whether an app is already installed. Without correct detection rules, Intune will try to reinstall the app on every sync β€” or think it’s installed when it isn’t.

Three types:

  • MSI product code β€” automatically detected for MSI installers
  • File β€” check if a specific file exists (e.g., C:\Program Files\7-Zip\7z.exe)
  • Registry β€” check for a registry key/value (e.g., HKLM\SOFTWARE\7-Zip\Path)

The exam tests whether you can pick the right detection rule for a scenario. If the app uses MSI, use the product code. If it’s a custom .exe installer, use file or registry detection.

Assignment types

AssignmentWhat HappensUser Experience
RequiredApp installs automatically, no user action neededApp appears on device silently
AvailableApp appears in Company Portal for self-service installUser chooses to install from Company Portal
UninstallApp is removed from targeted devicesApp disappears from device

Aroha at CloudForge assigns Slack as β€œRequired” (everyone needs it) and Adobe Acrobat as β€œAvailable” (users install if they want it from Company Portal).

Deep dive: supersedence and dependencies

Supersedence and dependencies are Win32-exclusive features:

  • Dependencies: App B requires App A. Intune installs A first, then B. Example: your LOB app depends on .NET Runtime β€” Intune installs .NET first.
  • Supersedence: App v2 replaces App v1. Intune uninstalls v1 and installs v2. Example: 7-Zip 24.08 supersedes 7-Zip 23.01 β€” old version is removed, new version installed.

LOB apps (MSI/MSIX) don’t support supersedence or dependency chains β€” that’s a key reason to use Win32 app format even for MSI files.

🎬 Video walkthrough

Flashcards

Question

What tool converts a Win32 app (.exe/.msi) into .intunewin format?

Click or press Enter to reveal answer

Answer

The Microsoft Win32 Content Prep Tool (IntuneWinAppUtil.exe). It wraps the installer and supporting files into a .intunewin package that can be uploaded to Intune.

Click to flip back

Question

What are the three detection rule types for Win32 apps?

Click or press Enter to reveal answer

Answer

1. MSI product code (auto-detected for MSI installers). 2. File detection (check if a specific file exists at a path). 3. Registry detection (check for a specific registry key or value). Detection rules tell Intune whether the app is already installed.

Click to flip back

Question

What's the difference between Required and Available app assignments?

Click or press Enter to reveal answer

Answer

Required: app installs automatically with no user action. Available: app appears in Company Portal for users to self-service install. Required ensures compliance; Available gives users choice.

Click to flip back

Knowledge Check

Knowledge Check

Aroha needs to deploy a custom .exe installer for a project management tool to all 30 CloudForge devices. The installer doesn't use MSI format. What's the correct preparation?

Knowledge Check

After deploying 7-Zip as a Win32 app, Aroha notices Intune tries to reinstall it on every device sync β€” even on devices where 7-Zip is already installed. What's most likely wrong?


Next up: Deploy Apps with Intune & App Stores β€” pushing apps to devices and deploying from platform-specific stores.