Jamf or Intune for a Mac fleet?

Ten years ago this was not a question — if you managed Macs seriously, you ran Jamf. Intune’s macOS support has improved enough that the comparison is now genuine, and the answer depends on things that have very little to do with the feature grid.

We run both in production. Here is how we actually decide.

Where Intune wins

You already own it. Intune is in the bundles most organisations hold. If the Mac population is a minority of a Windows-first estate and the requirements are ordinary, adding a second product with its own licence, its own console and its own operational knowledge is a real cost against a marginal gain.

One compliance picture. Device compliance flows into Conditional Access from the same place for every platform, and the report covers the whole estate rather than two-thirds of it. For organisations whose central question is “can I state the compliance posture of every endpoint”, this matters more than depth of Apple control.

One team, one console. The people running your Windows estate can run the Mac estate. That is a genuine operational saving and it is the argument that decides most mid-sized environments.

Baseline coverage is now adequate. Enrolment through Apple Business Manager, configuration profiles, FileVault with key escrow, update enforcement, app deployment and compliance all work.

Where Jamf wins

Depth and timing on new Apple capabilities. Jamf ships support for new macOS and iOS management features earlier and more completely. If your requirements sit at the edge of what Apple exposes, that gap is the whole decision.

Complex application packaging and patching. Jamf’s ecosystem around third-party application deployment and patch management is substantially more mature. In an environment with a long tail of specialist macOS software — creative, research, engineering — this is where the time goes, and it is where the difference is largest.

Scripting and extension attributes. Arbitrary inventory attributes, smart groups built on them, and policies triggered by conditions you define. If your Mac management involves genuine automation rather than a policy baseline, this is a category difference rather than a feature difference.

Mac-heavy or Mac-only estates. Where the Apple fleet is the primary estate rather than a subset, the specialist tool pays for itself in operational time.

Education. Jamf’s school-specific tooling has no real equivalent.

The questions that actually decide it

How many Macs, and are they growing? Below roughly fifty, in a Windows-first organisation, with ordinary requirements — Intune, almost always. Above a few hundred, or growing, the specialist tooling starts to pay back.

Who operates it? A team that lives in the Microsoft admin centres will operate Intune well and Jamf occasionally. A team with real Apple expertise will get far more out of Jamf. Buying a platform your team will not learn is worse than buying a lesser one they will use properly.

How much specialist software is there? Count the macOS applications that need packaging, licensing and patching outside the App Store. If the answer is more than a handful, weight Jamf heavily.

Are you also managing iOS through the same platform? Consolidating iPhone and Mac management is a reasonable objective and both platforms do it. It matters more which one your fleet requirements fit.

How fast do you need new OS support? If a new macOS release has to be supported and enforced in the first weeks, that is a Jamf argument.

Running both

It is more common than the vendors suggest, and it is not automatically a failure of decision-making. A frequent pattern is Intune as the compliance and identity anchor across the whole estate, with Jamf handling deep Mac management — with Jamf reporting compliance into Intune so Conditional Access still has one source of truth.

It costs more and it is two things to operate. It is the right answer when the Mac estate genuinely needs specialist management and the organisation genuinely needs one compliance picture, and neither requirement will yield.

The answer we give most often

For a Windows-first organisation with a modest, ordinary Mac population: use Intune, because you own it and your team will actually run it.

For a Mac-significant estate, a long tail of specialist software, or an education environment: use Jamf, and expect to invest in the skills.

The wrong answer in both directions is choosing on the feature grid. Both grids are long enough to justify either decision, and neither of them tells you who will be operating the platform in two years.

More on how we manage Apple fleets, and on what changes when you bring Macs into a Windows shop.