MacOS Apps
Easy2Patch 4.0
Easy2Patch manages macOS applications as a separate platform branch of the same product catalog. They are entered, versioned, updated and reported like Windows products, but they take a different road to the endpoint, and that road decides almost everything on the pages below.
In this section
Deployment Models
Which Intune application type a DMG and a PKG become, what travels inside the app object, and which Windows concepts have no macOS counterpart.
Application and Update Modes
The single difference between sending a product as an Application and sending it as an Update.
Auto Assignment
Whether the application is assigned to your Entra ID groups automatically once publishing finishes.
Deployment Purpose and Notifications
Available versus Required, and what the end user sees while it happens.
Publish Options and Retire
What happens to the existing application and its assignments when a new version is published.
Package Requirements
The fields, limits and agent versions a macOS package has to satisfy before it can be sent.
Configuration Recommendations
Suggested combinations for the most common situations, in one table.
At a glance
Delivery target
Microsoft Intune only
Package formats
.dmg, .pkg
Intune application types
macOSDmgApp, macOSPkgApp
Uploaded content
The DMG or PKG itself, encrypted. There is no .intunewin package on macOS.
Installation engine
The Intune management agent on the Mac
Detection
Bundle ID, and optionally bundle version — performed by Intune, not by a script
Silent install command line
Not applicable
Assignment target
Entra ID (Azure) groups
What a macOS product needs before it can be deployed
A DMG or PKG package. The file type is read from the package itself; it is not typed in.
A primary bundle ID and bundle version. These are read out of the package where the package allows it, and entered by the operator where it does not. Nothing here is guessed — a field that could not be read is left empty and the reason is shown.
A minimum supported macOS version. See Package Requirements.
At least one Entra ID group, if you expect the application to reach devices on its own. See Auto Assignment.
What macOS does not have
These Windows concepts have no equivalent for a macOS application, and no screen asks you for them:
Silent install and uninstall command lines
Return codes and return-code mapping
Detection methods and detection scripts
Requirement rules
Content folder, distribution point and content distribution
Task sequence / OS deployment integration
The reason is the same in every case: on macOS the Intune management agent performs the installation. The administrator does not supply a command line, so there is no exit code to interpret and no script to run in order to decide whether the application is present. Intune answers that question itself, from the bundle identifiers carried inside the application object.
Last updated