PatchBee docs
Deploying macOS apps
PatchBee packages macOS apps for Intune too (1,321 in the catalog). The flow mirrors Windows, with a few differences worth knowing.
Finding macOS apps
In the App Library, set the Platform filter to macOS, or look for the macOS badge on an app. macOS apps come from a curated set of popular installers.
What is different from Windows
- Zero-config plan. macOS apps deploy with sensible defaults and are detected by their built-in app identity (the bundle ID); there is nothing to configure on the plan.
- Installer types. Both .pkg and .dmg apps are supported, including DMGs with unusual internal layouts; PatchBee reads the app identity out of the image for you.
- Updates are in-place. A new version replaces the app directly (Windows uses supersedence).
- Publish and assign. Package and deploy runs the short wizard: pick the Intune tenant, then set assignments (Entra groups, all users, or all devices, with include and exclude filters), the same as Windows. There is no way-of-publishing step, because macOS updates in place.
Example: deploying Postman to a developer group
Filter the App Library to macOS and open postman (a DMG). Select Package latest: the plan already carries the bundle identity com.postmanlabs.mac and the version for detection, with nothing to fill in. Package and deploy, pick the tenant, assign to the Developers group as Required, and confirm. When Postman ships an update, it appears in Update Candidates like any Windows app, and publishing it replaces the app in place.
Everything else, tracking updates, app sets, rings, works the same as Windows.