App Deployment: Prepare & Package

Why does app preparation matter?

App types in Intune

App Type	Format	Preparation Needed	Best For
Win32 app	.exe, .msi wrapped as .intunewin	Convert with Win32 Content Prep Tool	Most desktop apps — maximum flexibility
Line-of-business (LOB)	.msi, .msix, .appx, .appxbundle	Upload directly	Simple MSI installers, modern MSIX packages
Microsoft Store app	Store link	Select from store catalog	Modern apps from the Microsoft Store
Web link	URL	Just enter the URL	Shortcuts to web applications
Microsoft 365 Apps	Built-in	Configure in Intune — no file upload	Word, Excel, PowerPoint, Outlook (see Module 20)
iOS/Android store apps	Store link	Search the store in Intune	Mobile apps from Apple App Store / Google Play
Managed Google Play	Store link	Search Managed Google Play	Android 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

Setting	What You Configure	Example
App information	Name, description, publisher, version	”7-Zip 24.08 by Igor Pavlov”
Program	Install command, uninstall command, behaviour	Install: 7z2408-x64.msi /qn; Uninstall: msiexec /x {GUID} /qn
Requirements	OS version, disk space, RAM, architecture	Windows 10 1903+, 64-bit
Detection rules	How Intune knows the app is installed	MSI product code, file exists, or registry key
Dependencies	Other apps that must be installed first	.NET Runtime required before app
Supersedence	Replaces an older version of the app	7-Zip 24.08 supersedes 7-Zip 23.01
Assignment	Required, Available, or Uninstall	Required 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

Assignment	What Happens	User Experience
Required	App installs automatically, no user action needed	App appears on device silently
Available	App appears in Company Portal for self-service install	User chooses to install from Company Portal
Uninstall	App is removed from targeted devices	App 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

🎬 Video coming soon

App Deployment: Prepare & Package — MD-102 Module 18

App Deployment: Prepare & Package — MD-102 Module 18

~11 min

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?

AConvert the .exe to .intunewin using the Win32 Content Prep Tool, then upload as a Win32 appBUpload the .exe file directly as a Line-of-Business appCPublish the .exe to the Microsoft Store and deploy from thereDCreate a PowerShell script that downloads and installs the .exe

Check Answer

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?

AThe app is assigned as Available instead of RequiredBThe detection rules are incorrect — Intune can't verify the app is installedCWin32 apps always reinstall on every syncDThe .intunewin package is corrupted

Check Answer

---

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