Jamf vs Microsoft Intune: Which Device Management Platform Fits Your Fleet in 2026?

Updated August 2026

Almost every comparison of these two platforms opens with a price table. Ours can't, and that fact turns out to be the most useful thing on this page.

Microsoft publishes what Intune costs down to the individual add-on. Jamf publishes nothing. jamf.com/pricing lists Jamf for Mac, Jamf for Mobile, Jamf Pro, Jamf School, Jamf Connect, Jamf Protect and Jamf Now, then closes with a line telling you to "Contact a Jamf representative or your local authorized reseller for a detailed quote in your local currency." There is not one dollar figure on the page. The $4.17 per device per month that dozens of comparison articles still repeat as Jamf Pro's price is not there, and buyer contract data suggests it hasn't been close to reality for some time.

Then there's the second problem, which nobody puts in a table at all. Intune bills per user. Jamf bills per device. A designer with a MacBook, an iPhone and an iPad is one Intune unit and three Jamf units. Any comparison that puts "$8" next to "$4.17" in the same row is comparing two different things, and it gets the arithmetic wrong before it gets the conclusion wrong.

This page is for the IT director, systems admin or CIO who has narrowed the shortlist to these two and needs to know what each one does, what each one costs against your fleet shape, and whether the honest answer is "both." Every figure below is either taken from the vendor's own page or labelled (reported) with its source named.

TL;DR

The short verdict. If your fleet is majority Apple and Mac configuration depth is the actual job, Jamf is still the better product, and you will have to sit through a sales call to find out what it costs. If your fleet is mixed and you already pay for Microsoft 365 E3 or E5, Intune is the cheaper and simpler answer because you have already bought it. And if you are Apple-heavy inside a Microsoft shop, the honest answer is frequently both, with Jamf managing the Macs and Intune acting as the compliance authority for Entra Conditional Access. That combination is a real, documented architecture. It is also the most expensive of the three.

Key Facts

• Jamf has been a private company since 30 January 2026. Francisco Partners completed its acquisition that day at $13.05 per share, an enterprise value of roughly $2.2 billion, and Jamf stock was delisted from Nasdaq, per the closing announcement carried on Business Wire. Jamf said in its own October 2025 release that it "will continue to operate under the Jamf name."
• Jamf publishes no per-device price at all. Its pricing page names ten products and carries zero dollar figures, directing buyers to "Contact a Jamf representative or your local authorized reseller." The only price Jamf does publish sits on the Jamf Now product page: "Manage up to 3 devices for free."
• Buyer contract data puts Jamf Pro far above the figure listicles repeat. Procurement platform Vendr's Jamf marketplace page reports observed rates of "$8-$20+ per device per month" for Jamf Pro depending on volume, alongside a median Jamf contract of $30,155 a year drawn from 687 purchases. Vendr sells negotiation services, so read this as buyer-side observed pricing rather than a list price. It is still a great deal closer to what buyers report paying than the $4.17 still in circulation.
• Intune's packaging changed in July 2026, in buyers' favour. Microsoft's Intune pricing page now states that select advanced Intune capabilities are included in Microsoft 365 E3 and E5 from July 2026. E3 picks up Intune Plan 2, Remote Help and Advanced Analytics; E5 adds Endpoint Privilege Management, Microsoft Cloud PKI and Enterprise Application Management on top. Bought standalone, those six items list at $4.00, $3.50, $5.00, $3.00, $2.00 and $2.00 per user per month respectively.
• For an SMB, "you already own Intune" is a $22 per user per month argument. Microsoft's Business Premium page lists Microsoft 365 Business Premium at "$22.00 user/month, paid yearly," and it is the cheapest Microsoft 365 business plan that bundles Intune Plan 1 for "device and app administration across platforms." The same page carries "$26.40 user/month with a monthly subscription," $18.79 paid yearly without Teams, and $32.00 paid yearly for the Copilot variant. Business Basic, Business Standard and Business Premium all "support a maximum of 300 users," so above that headcount you are looking at the enterprise E-series or standalone Intune instead.

The Pricing Asymmetry Nobody Puts in the Comparison Table

Here is what each vendor actually publishes today, and what has to be labelled.

Two things about that table deserve saying plainly.

First, the circulating Jamf numbers do not agree with each other. Search for Jamf Pro pricing and you will find $4.17, $6.25, $8.25, $12.50 and $13.33 per device per month stated with equal confidence on different pages, none traceable to a Jamf URL that currently exists. That spread isn't one writer being sloppy. It's what happens when a vendor stops publishing and a hundred pages keep quoting each other's cached copy of a number that was last true years ago. If you see a Jamf price presented as fact anywhere, including here, check whether the source names a live Jamf page.

Second, Microsoft's transparency has a catch. The $8.00 Plan 1 rate is real and buyable standalone, but hardly anyone buys it that way. Most organisations get Intune inside a Microsoft 365 bundle, and the bundle price is where the money sits. That is the number to model.

Per User or Per Device: The Unit Mismatch That Breaks Most Comparisons

This is the part that changes answers, so it's worth being concrete.

Intune licences a person. Microsoft's own enrollment restriction documentation confirms the device limit per user "from 1 to 15," meaning one licensed user can enrol up to fifteen devices under a single seat depending on how you configure the restriction. Jamf licences a device. Every Mac, iPhone, iPad and Apple TV is its own line on the invoice.

The ratio between the two columns is your whole comparison. At a device-to-user ratio of 1.0, the two billing models behave the same way and you can compare rates directly. At 2.0, Jamf's effective per-person cost doubles while Intune's stays flat. At 3.0 it triples. This is why Jamf tends to look competitive in Mac-only laptop refreshes and expensive in fleets where everybody also carries a company iPhone and an iPad.

Two caveats keep this honest. Intune's device limit is a configurable restriction, not a licensing guarantee, and Microsoft is explicit that "an Intune license is required for any user or device that benefits directly or indirectly from the Microsoft Intune service." Shared and kiosk devices with no assigned user need Intune's separate device-only subscription, which does not support Conditional Access or app protection policies. So the per-user model is genuinely cheaper for the one-person-many-devices case and genuinely awkward for the many-people-one-device case. Jamf's per-device model is the mirror image.

What Three Real Fleets Actually Cost

Every cell states its unit basis, every Jamf figure is a labelled band rather than a price, and Microsoft figures are vendor-published annual-billing rates converted to twelve months. Nothing here is a quote.

Fleet A: a 25-person creative studio, 25 Macs, one device each. Device-to-user ratio 1.0.

Fleet B: the same 25 people, now with a company iPhone each. 50 Apple devices, ratio 2.0.

Fleet C: 200 people, mixed platform. 150 Windows laptops, 50 Macs, 150 company iPhones, 350 devices total.

Four readings come out of those tables.

At ratio 1.0 the two products land in genuinely overlapping territory, and the deciding factor is capability, not cost. At ratio 2.0 Jamf's bill doubles while Intune's does not move at all, which is the single most under-reported fact in this comparison. In the mixed fleet, Jamf cannot be the whole answer at any price, because it does not manage Windows. The relevant question there isn't Jamf or Intune, it's Intune alone or Intune plus Jamf, and the premium for adding Jamf on 100 Apple devices lands somewhere around $10,000 to $24,000 a year on reported rates.

The fourth reading is inside the Microsoft column, and it catches people out. At 200 people you are still under Business Premium's 300-user ceiling, so the gap between $52,800 and $93,600 a year is $40,800 for two plans that both include Intune Plan 1. E3 buys plenty besides device management, but if endpoint management is why you are looking at E3, price the cheaper plan first.

If you want a repeatable way to build this out for your own numbers, our guide to TCO modelling for SaaS walks through the same exercise with add-ons, ramp and renewal uplift folded in.

Same-Day Apple OS Support

This was Jamf's cleanest differentiator for years, and it is the claim most competing comparisons repeat without checking. Worth checking, because the gap has narrowed.

Jamf's position is documented and specific. On 15 September 2025 the company announced same-day support for macOS Tahoe 26, iOS 26, iPadOS 26, tvOS 26, visionOS 26 and watchOS 26 on the day they went generally available, marking "14 consecutive years of offering same-day support." That is Jamf's own claim about Jamf, though the track record behind it is long and publicly checkable.

Microsoft's position has moved. Its Intune Customer Success team published a day zero support post for the same OS 26 wave, stating that existing features work as expected on release day and that the settings catalog was updated for newly released iOS/iPadOS and macOS settings across both declarative device management and classic MDM. Microsoft also raised Intune's floor with that release: its supported platforms reference lists "iOS/iPadOS 17.x and later" and "macOS 14.x and later" as supported, with older versions merely "Allowed to enroll."

The honest 2026 read: "Jamf supports new Apple releases on day one and Intune doesn't" no longer holds as a blanket statement. Both vendors commit to day-one functionality now. Where Jamf still leads is at the edges, the brand-new WWDC capability only a specialist platform bothers to surface in its first quarter. If you adopt new Apple features the week they ship, that edge matters. If you mostly need last year's features to keep working, it doesn't.

macOS and iOS Configuration Depth

This is where Jamf's advantage is real, current and measurable, and where Intune's documentation quietly does the arguing for you.

Intune runs macOS shell scripts through its own management agent, and Microsoft publishes the constraints: the script file "must be less than 1 MB in size", scripts running longer than 60 minutes "are stopped and reported as failed," the agent check-in "occurs every 8 hours," and a script re-runs only when you configure a retry count and the previous run failed. Custom attributes, Intune's answer to Jamf's extension attributes, "are run every 8 hours on managed Macs" and the returned result "must be 20KB or less."

Jamf Pro's model differs in kind, not just degree. Policies fire on event triggers rather than a fixed check-in window, extension attributes feed directly into Smart Groups, and Smart Group membership drives scope automatically. That chain, collect a custom data point, group on it, act on the group, is what Mac admins mean when they say Jamf does something Intune doesn't. Jamf's product page names the pieces: Zero-touch deployment, Self Service+ where "users can install apps, update software and maintain their own devices," Smart Groups, and Blueprints for managing "across all your Apple devices with Declarative Device Management."

If your Mac management is mostly profiles, app deployment, FileVault and compliance, Intune covers it and the gap is theoretical. If your Mac management involves conditional workflows keyed off custom inventory data, the gap is your daily job and Jamf wins on the merits.

Windows, Android and Linux Coverage

This section is short because the answer is one-sided.

Jamf does not manage Windows. It never has, and Jamf Protect covers "macOS, iOS and visionOS" with no Windows or Android in the platform list. Intune's supported platform reference covers Android, iOS/iPadOS, Linux, macOS, Windows and Chrome OS, including Ubuntu LTS 24.04 and 26.04, Red Hat Enterprise Linux 9 and 10, and every Android Enterprise management mode from personally owned work profile through fully managed and dedicated.

For a mixed fleet this settles the base-layer question on its own. Jamf can be a specialist layer on top of something else. It cannot be the only thing you run. Anyone weighing the broader estate should read this alongside our best SaaS management software roundup, since device management and SaaS licence management are separate purchases budget owners routinely confuse.

Zero-Touch Enrollment

Both platforms do zero-touch on Apple, and both do it through Apple's own machinery, so the differences are in what happens after the device finishes setup, not during it.

One nuance worth knowing before you plan a rollout: Intune classifies both macOS and iOS/iPadOS devices as personally owned by default. To count as corporate-owned, a Mac has to be registered by serial number or enrolled via Apple ADE. Get that wrong and your ownership-based policy targeting silently misses devices.

Identity and Conditional Access

Here the asymmetry flips. Intune is not just integrated with Microsoft Entra Conditional Access, it is the thing Conditional Access reads from. Jamf has to be plumbed in.

Microsoft's documentation is unusually blunt about what changed. The Jamf managed device compliance page carries an Important notice: "Jamf macOS device support for Conditional Access is being deprecated. Beginning on January 31, 2025, the platform that Jamf Pro's Conditional Access feature is built on will no longer be supported." The old path under Settings, Global, Conditional Access "is no longer able to accept new configurations." New integrations go through Settings, Global, Device Compliance instead, via a wizard that creates two Entra app registrations. The mechanics have consequences worth pricing in before you commit.

None of that is a reason to avoid running both. Plenty of large Apple estates do exactly this. But it is four or five moving parts that a single-vendor deployment doesn't have, and every one of them is a place a rollout stalls. If you're formally scoring this decision, our SaaS vendor evaluation scorecard is a reasonable frame for weighting integration burden against capability.

Patching and App Lifecycle

Both platforms patch. The difference is which side of the fleet each one is genuinely good at.

Jamf's app lifecycle management sits on the Jamf App Catalog, which Microsoft's own documentation recommends using to keep the Intune Company Portal app current on Jamf-managed Macs, a small but telling endorsement. Jamf handles macOS updates through declarative software update management and its own patch policies, and Self Service+ lets users update software themselves rather than waiting on a maintenance window.

Intune's newest strength here is Enterprise Application Management, which deploys "curated Win32 apps from a Microsoft-hosted Enterprise App Catalog with built-in install settings." Note the scope carefully: Win32, which means Windows. It is a genuinely useful capability and it is not a Mac capability. Intune patches macOS through Apple's software update mechanisms and deploys Mac apps as DMG, PKG or LOB packages, which works, but the curated catalogue advantage is on the Windows side.

Security Posture: Jamf Protect vs Defender for Endpoint

Both vendors sell endpoint security as a separate line item, and both are decent. The split is coverage versus specialisation.

Jamf Protect is built on Apple's own frameworks. Jamf's product page states it "uses the Apple endpoint security API and other native frameworks across macOS, iOS and visionOS," and lists telemetry to SIEM, CVE-based vulnerability management, advanced threat controls against fileless attacks, next-gen antivirus, removable storage controls, jailbreak detection, content filtering and phishing protection. What that list does not contain is Windows or Android.

Microsoft Defender for Endpoint runs on "Windows, macOS, Linux, Android, and iOS" per Microsoft Learn, which also states that "Microsoft 365 E5 and Microsoft 365 E5 Security include Defender for Endpoint Plan 2." So the E5 shop that already pays $60.00 per user per month has EDR on every platform already bought, which is a materially different starting position from an Apple-only shop pricing Jamf Protect as a fresh line item at a reported $3-$8 per Mac per month.

If you want the wider security-tooling picture rather than just the endpoint agent, our roundup of AI tools for cybersecurity covers the detection and response layer that sits above both of these.

Running Both Together

A surprising number of Apple-heavy Microsoft shops land here, so it deserves honest costing rather than a footnote.

The architecture: Jamf Pro manages the Macs and iOS devices, Intune manages Windows and everything else, and the Jamf Device Compliance connector reports Mac compliance into Entra ID so Conditional Access gates Microsoft 365 access uniformly. You get Jamf's Apple depth and Microsoft's identity plumbing. You also pay for both, and the maths is not subtle.

Whether that uplift is worth it comes down to one question: are you buying Jamf for capabilities Intune genuinely lacks, or for a reputation Intune has partly caught up to? On scripting, extension attributes and Smart Group workflows, the gap is real and documented. On day-one OS support, it has narrowed sharply. Answer that honestly before you sign for both.

Admin Skills and Operational Load

The skills each platform demands are different enough that the person who runs one is often not the person who can run the other.

Jamf's own pricing page recommends "an engagement with Jamf Premium Services" for "the best onboarding and implementation." Read that as a real, unpriced professional services line to fold into your first-year budget, not as boilerplate.

Migration Cost in Both Directions

Migrating between MDMs on Apple is harder than almost any other category of software, and both directions have a specific pain.

The core constraint is Apple's: a device can only be supervised by one MDM at a time. Microsoft's own Jamf integration documentation puts it plainly: "Any user with a macOS device that's already enrolled in either Jamf or Intune who is then targeted to enroll with the other MDM must unenroll their device and then re-enroll it with the new MDM before management of the device works properly."

If your Macs are enrolled through Apple Business Manager, migration is unpleasant but tractable, because ADE lets you reassign the MDM server and re-enrol without touching every machine by hand. If they're not, budget for hands-on time per device. Our guide to switching SaaS vendors covers the contractual side, notice periods, data export and overlap windows, which is the part teams forget until renewal is thirty days out.

When Jamf Is the Right Call

• Your fleet is majority Apple and Mac depth is the actual job. Extension attributes feeding Smart Groups feeding scoped policies is a workflow Intune cannot reproduce, and Microsoft's own documented limits on custom attributes confirm it.
• You adopt new Apple capabilities early. Jamf's fourteen consecutive years of same-day support is the company's own claim, but the track record behind it is public and long.
• You run tvOS, visionOS or watchOS devices. Intune's supported platform reference does not list them.
• You have a Mac admin on staff, or the budget to hire one. Jamf rewards specialist expertise and punishes its absence.
• You are a school or university. Jamf School and Jamf's education pricing are a separate, purpose-built path that Intune answers only through Intune for Education, which is bundled into Microsoft 365 Education A3 and A5.
• You can accept a quote-only purchase. If your procurement process needs a list price before a call, Jamf will not give you one.

When Intune Is the Right Call

• Your fleet is mixed. Jamf does not manage Windows, Android, Linux or Chrome OS. That single fact resolves most mixed-fleet decisions on its own.
• You already pay for Microsoft 365 E3 or E5. Intune Plan 1 is included, and from July 2026 E3 also carries Plan 2, Remote Help and Advanced Analytics while E5 adds Endpoint Privilege Management, Cloud PKI and Enterprise Application Management. Those are add-ons you were previously quoted separately.
• Your device-to-user ratio is above 1.5. Per-user billing stops scaling with device count where per-device billing does not.
• Conditional Access is central to your security model. Intune is the native signal source; Jamf needs a connector, two app registrations and a Self Service registration flow.
• You need a published price to budget against. Every Intune figure in this article came off a Microsoft page, which is not something we can say about the other column.
• Your IT team is Microsoft-native. The hiring pool and the console familiarity are both dramatically larger.

One caution against the reflex answer. "We already own it" is only true if you are on the right plan, and an SMB on Business Standard is not. Moving up to Business Premium costs $22.00 per user per month against Standard's $14.00, a step of exactly $8.00, or $2,400 a year across 25 people. That figure should look familiar: it is precisely the standalone Intune Plan 1 rate. Microsoft charges the same $8.00 for Intune whether you bolt it onto a bundle or buy it alone. Compare the Copilot variants instead and the step is $23.50 to $32.00, or $8.50 per user per month.

Now put those two upgrades side by side, because the result is genuinely odd. Base Business Premium at $22.00 is cheaper than Business Standard with Copilot at $23.50. The plan that adds endpoint management across Windows, macOS, iOS and Android costs $1.50 per user per month less than the plan that only adds an AI assistant. That is not an argument against Copilot, it is an argument for pricing both upgrades properly instead of assuming device management is the expensive one. And for an all-Mac 25-person studio, Mosyle's free tier for up to 30 devices may cover the requirement at zero.

If Neither Fits

Plenty of teams read this far and realise the real requirement is smaller than Jamf and more Apple-native than Intune. The Apple MDM market has changed enough in the last year that the received wisdom about the alternatives is also out of date.

Three of those five publish real numbers, which puts them ahead of Jamf on budget predictability alone. Mosyle is the first call for a small all-Apple team. Hexnode is the first call if you want cross-platform coverage at a published per-device rate rather than a per-user one. Addigy suits teams where bundled EDR with managed detection matters more than console depth. Iru is a reasonable shortlist entry for Apple-first shops with some Windows, with the caveat that you land back in the same quote-only conversation you were trying to avoid.

If your evaluation is really about the service desk sitting behind the fleet rather than the fleet itself, that's a different purchase. Start with our how to choose ITSM software guide, then compare the two most common shortlists directly in Freshservice vs Jira Service Management, best Freshservice alternatives and best Jira Service Management alternatives. And if what you are actually replacing is Intune specifically, our best Intune alternatives roundup goes wider than this head-to-head does.

Decision Framework

The verdict. Jamf remains the better Apple management product, and the depth gap in scripting, extension attributes and Smart Group workflows is real and documented rather than marketing. But two things have changed the calculus in 2026. Intune now commits to day-zero Apple OS support, which erodes Jamf's most-quoted differentiator, and Microsoft moved a stack of previously paid Intune add-ons into E3 and E5 in July 2026, improving the value of a licence most enterprises already hold. Against that, Jamf has stopped publishing prices entirely and went private in January. For a Mac-only shop with real configuration complexity, Jamf still earns its quote. For everyone else, Intune is the default, and the burden of proof has shifted onto Jamf to justify the premium you cannot see before you call.

What to Do Next

1. Calculate your device-to-user ratio before you calculate anything else. Total managed devices divided by total people. Below 1.2, compare rates directly. Above 2.0, per-user billing is structurally cheaper and no negotiated Jamf discount is likely to close the gap.
2. Check what your Microsoft licence already includes. If you're on E3 or E5, you gained Intune capabilities in July 2026 that you may still be paying for separately as add-ons. That audit is free and can cancel line items today.
3. Get the Jamf quote early, per device and per year. Since nothing is published, the quote is the only real number. Ask specifically whether Jamf Connect and Jamf Protect are included or separate, since the reported bands suggest they add meaningfully to the per-Mac cost.
4. Trial both against your hardest workflow, not your easiest. Pick the automation you'd genuinely miss and build it in each. If it's keyed off custom inventory data, you'll find Intune's limits in an afternoon. If it isn't, you may find you don't need Jamf.
5. Pressure-test the compliance angle before you shortlist. Our security and compliance review guide is a workable checklist for the questions procurement will ask six weeks later.

---

Related Resources:

• Best SaaS Management Software in 2026
• Best Intune Alternatives in 2026
• Best Freshservice Alternatives in 2026
• Best Jira Service Management Alternatives in 2026
• Freshservice vs Jira Service Management
• How to Choose ITSM Software
• SaaS Vendor Evaluation Scorecard
• TCO Modeling for SaaS
• Switching SaaS Vendors
• Security and Compliance Review
• Best AI Tools for Cybersecurity in 2026