Let’s go through Intune Application Model Deployment Guide. In this video guide, you will see how to use Intune application model to deploy applications. Following is the step-by-step guide to creating Intune Application model.
NOTE! – Intune application model is adding new features with every new version of Intune. Check out the references section this post to get the latest updated documentation from Microsoft.
- Convert MSI to IntuneWin Packages Smart Package Studio IntuneWin Tool
- Intune Win32 App Deployment using Modern Management
- Intune App Model Troubleshooting Client Side Process Flow
Introduction
Intune Simple MSI Deployment Options is called Line-Of-Business app (“strangely though”). With this Intune Line of business application, option, you can only deploy simple MSI apps.

In this post, I’m not going to cover the “Simple MSI app” deployment using Intune Line of Business App. I have already covered that long back “https://www.anoopcnair.com/intune-azure-end-end-msi-lob-app-deployment-video-guide/”
In this post, I’m going to cover Windows App(Win32) (the real Intune App Model). Windows App (Win32) is a beast which is similar to SCCM Application model.
MSI LOB Application Vs Intune Application Model
Intune LOB applications are technically deployed through Windows 10 built-in MDM agent.
Intune Application model uses a special package called IntuneWin. Most importantly, the IntuneWin package is NOT handled by Windows 10 built-in MDM agent.
IntuneWin app installation is handled by a new agent called Intune Management Extension. This client agent is created by Intune team only for IntuneWin application deployments. Also, this Intune extension agent is not part of the core Windows 10 OS.

Create IntuneWin Packages
You need to use a special package called “IntuneWin” to create the Intune Application Model. Vimal explained how to create IntuneWin packages using the Command Line tool by Microsoft here.
You can use a GUI tool called “Smart Package Studio” to create IntuneWin packages. IntuneWin packages can be used while creating the Intune App model as you can see in the below sections.
You can check out my previous post to get more details about converting MSI packages into IntuneWin. You can check out the following post to learn more – Convert MSI to IntuneWin Packages Smart Package Studio IntuneWin Tool

Specify the Software Setup File
- Navigate to Client apps > Apps > Add from Intune blade.
- Select Windows app (Win32) – Intune application model – from the provided drop-down list from Apps blade
Upload the App Package File (IntuneWin)
- Select App package file to select a file from apps blade
- Click on the browse button. Then, select a Windows installation file with the extension .intunewin.
- Select OK.
Configure App Information
- Select App information to configure the app. Make sure you provide the following information wherever required. Some of the information will get populated automatically depending on the package.
- Name:
- Description:
- Publisher:
- Category:
- Display this as a featured app in the Company Portal
- Information URL:
- Privacy URL:
- Developer:
- Owner:
- Notes:
- Logo:
- Select OK.

Configure App Installation Details
- Select Program to configure the app installation and uninstall command lines for the Intune application. You can get the information from Smart Package IntuneWin Package.
- Add the complete uninstall command line to uninstall the app based on the app’s GUID. You can get MSI product code from the above Intune packaging tool.
- Select OK.

Configure App Requirements
In the Add app pane, select Requirements to configure the requirements that devices must meet before the app is installed.
- In the Add a Requirement rule pane, configure the following information.
- Minimum operating system:
- Disk space required (MB):
- Physical memory required (MB):
- Minimum number of logical processors required:
- Minimum CPU speed required (MHz):
- Click Add to display the Add a Requirement rule blade
- Select the Requirement type to choose the type of rule that you will use to determine how a requirement is validated.
- File: When you choose File as the Requirement type, the requirement rule must detect a file or folder, date, version, or size.
- Path
- Property
- Associated with a 32-bit app on 64-bit clients
- Registry: When you choose Registry as the Requirement type, the requirement rule must detect a registry setting based on value, string, integer, or version.
- Key path
- Value name
- Registry key requirement
- Associated with a 32-bit app on 64-bit clients
- Script: Choose Script as the Requirement type, when you cannot create a requirement rule based on file, registry, or any other method available to you in the Intune console.
- Script file
- Run script as 32-bit process on 64-bit clients
- Run this script using the logged on credentials
- Enforce script signature check
- Select output data type
- Select OK.

Configure App Detection Rules
- Select Detection rules to configure the rules to detect the presence of the app.
- In Rules format field, select how the presence of the app will be detected.
- Manually configure detection rules – You can select one of the following rule types: ( You can get the information from Smart Package IntuneWin Package )
- MSI
- MSI product code
- MSI product version check
- File
- Path
- Detection method
- Associated with a 32-bit app on 64-bit clients
- Select No (default) to expand any path variables in the 64-bit context on 64-bit clients.
- Examples of file-based detection
- Registry – Verify based on value, string, integer, or version.
- Key path
- Value name
- Detection method
- Associated with a 32-bit app on 64-bit clients
- Use a custom detection script
- Script file
- Run script as 32-bit process on 64-bit clients
- Enforce script signature check
- Select Add > OK

Configure App Return Codes for Intune Application Model
- Select Return codes to add the return codes used to specify either app installation retry behavior or post-installation behavior.
- In the Return codes pane, add additional return codes, or modify existing return codes.
- Failed
- Hard reboot
- Soft reboot
- Retry
- Success
- Select OK.
Upload App – Intune Application Model
In the Add app pane, verify that you configured the app information correctly and Select Add to upload the app to Intune.
Dependencies
Application dependencies are applications that must be installed before the actual application (which you are going to deploy) can be installed. Intune application model provides options to include dependencies.

NOTE! – The maximum number of dependencies you can have in Intune application model is 100 dependencies.
More details about the dependencies can be learned from Micrsoft documentation here.
Deployment of Application in Intune
- Select Assignments.
- Select Add Group to open the Add group pane that is related to the app.
- For the specific app, select an assignment type:
- Available for enrolled devices
- Required
- Uninstall
- Select Included Groups and assign the groups that will use this app.
- In the Assign pane, select OK to complete the included groups selection.
- Select Exclude Groups if you want to exclude some devices/users.
- Select OK.
- Select Save.