Insights

macOS 26 Tahoe and macOS 27 in business: upgrade planning for IT teams

macOS 27 runs only on Apple silicon and changes how updates are controlled. Here is how to plan the upgrade across a business Mac estate.

In brief. macOS 27 runs only on Apple silicon Macs, so Intel Macs stop at macOS Tahoe 26. Apple has also switched off the old MDM update controls, so plan upgrades with declarative device management: defer while you test, then enforce a version by deadline.

macOS Golden Gate 27, released on 14 September 2026, runs only on Macs with Apple silicon. Intel Macs stop at macOS Tahoe 26, and Apple lists four Intel models that run Tahoe, including the 2019 Mac Pro and the 16-inch MacBook Pro. Apple still releases security updates for Tahoe 26 and Sequoia 15, most recently on 9 November 2026. In macOS 27, Apple says the old MDM software update commands and deferral restrictions “no longer function”, so upgrades are now controlled through declarative device management (DDM). With DDM you can hold back a major upgrade for up to 90 days while minor updates continue, then enforce a target version with a deadline in each Mac’s local time. At the deadline the Mac quits open apps and restarts. Test in rings first: IT, then a pilot group, then everyone, checking key apps, VPN, security tools and sign-in. List your Intel Macs now and plan their replacement.

macOS Tahoe 26 and macOS 27 at a glance

Apple released macOS Golden Gate 27 on 14 September 2026, alongside Tahoe 26.7 and Sequoia 15.8. Since then it has shipped 27.0.1 (28 September), 27.2 (26 October) and 27.2.1 (9 November). Most business estates now run a mix of three versions, so it helps to know where each one stands.

VersionLatest release (as at 15 Nov 2026)Runs onStatus
macOS Golden Gate 2727.2.1, 9 Nov 2026Apple silicon onlyCurrent major version
macOS Tahoe 2626.7.3, 9 Nov 2026Apple silicon and four Intel modelsStill receiving security updates; last version for Intel Macs
macOS Sequoia 1515.8.3, 9 Nov 2026Apple silicon and IntelStill receiving security updates
macOS Sonoma 1414.8.9, 6 Aug 2026Apple silicon and IntelApple has listed no security release since August 2026

Apple does not publish end-of-support dates for older macOS versions. The reliable check is Apple’s security releases page: if a version stops appearing there, treat it as no longer patched. Macs on Sonoma or earlier should be a priority for upgrade or replacement.

Which Macs can run macOS 27, and which stop at Tahoe

Apple’s wording is simple: “If you have a Mac with Apple silicon, you can upgrade to macOS 27.” Every model on Apple’s macOS 27 compatibility list has an Apple silicon chip.

Mac familyRuns macOS 27Intel models that stop at Tahoe 26
MacBook ProM1 (2020) and later16-inch (2019); 13-inch (2020, four Thunderbolt 3 ports)
MacBook AirM1 (2020) and laterNone
MacBook NeoAll modelsNone
iMac2021 and laterRetina 5K, 27-inch (2020)
Mac mini2020 and later (Apple silicon)None
Mac Studio2022 and laterNone
Mac Pro2023Mac Pro (2019)

Any Intel Mac not in the right-hand column cannot run Tahoe either, so it is already on Sequoia or earlier. Your management tool can produce this list in minutes. In Jamf Pro, a smart group on processor type and model identifier does the job; in Microsoft Intune, filter the device inventory by model and OS version. Export it and share it with whoever owns the hardware budget.

What happens to Intel Macs

Intel Macs stay on macOS Tahoe 26 or earlier. Apple is still releasing security updates for Tahoe, but it has not published an end date on its own support pages, so do not plan around a date you have read in the press. Check Apple’s security releases page each quarter and set your own retirement date for each Intel Mac.

Rosetta, which lets Intel apps run on Apple silicon, matters here too. Apple’s developer documentation says Rosetta “will be available through macOS 27” as a general-purpose tool. Beyond that, Apple says it will keep only a subset aimed at older games that rely on Intel frameworks. That is a roadmap statement, but it is a clear signal: any business app that still needs Rosetta needs a native version or a replacement within the life of macOS 27. Apple also says that from macOS 27.2, upgrading no longer removes Rosetta.

For replacement planning, we suggest three lists: Intel Macs by model and age, apps that run under Rosetta, and staff whose work depends on either. That gives you a budget and a timeline you can defend.

Why macOS 27 changes how you control upgrades

This is the change most IT teams underestimate. Apple says “Legacy software update management no longer functions in all 27.0 operating systems.” That covers software update commands, software update queries, recommended cadence settings, and restrictions “like deferrals and Background Security Improvements”. Apple’s advice is that IT teams “should use declarative software update management to configure and enforce updates”.

In practice, a deferral profile or update policy built the old way will not hold back or push macOS 27. It still applies to Macs on Tahoe 26 and earlier, so most organisations will run both for a while. Jamf’s guidance is to scope the old profiles to earlier OS versions and use Blueprints for macOS 27 and later. Our guide to macOS 27 software updates and DDM explains the model in more detail.

Deferring upgrades with declarative device management

Apple’s declarative software update settings let you defer updates for 1 to 90 days. On a Mac, OS updates, major upgrades and non-OS updates can each have their own deferral, and Apple notes an upgrade can be deferred longer than an update. That is the setting you want: hold macOS 27 back while you test, and keep Tahoe security updates flowing.

Two points catch people out. First, Background Security Improvements ignore the deferral, by design. Second, Jamf notes that an enforcement declaration overrides a deferral and makes the update available straight away, so do not enforce a version you are still testing.

  • Jamf Pro: use the Software Update Settings component in Blueprints for behaviour and deferrals. Jamf says it “does not start or enforce an update”. Blueprints need macOS 15 or later and single sign-on through Jamf Account.
  • Microsoft Intune: use the settings catalog, under Declarative Device Management, Software Update Settings. Microsoft says this can hide updates from users for a set period and control whether users are offered the latest major or minor update. Intune’s declarative update policies need macOS 14 or later.

Enforcing an upgrade with a target version and deadline

Once testing is done, you set a target version and a deadline. Apple describes what happens next. The deadline uses each Mac’s local time. Notifications become more frequent as it approaches, and in the last 24 hours they ignore Do Not Disturb. At the deadline, “macOS force quits all open apps” and restarts to install. If the install fails, it retries within the hour. On macOS 15 or later you can limit notifications to the final hour, with a restart countdown.

In Jamf Pro this is the Software Updates component in Blueprints, which Jamf says “Enforces OS updates by sending each device a target version and a deadline”. In Intune it is the Software Update setting in the settings catalog, with a target OS version and a target date and time in the device’s local time zone. Intune also offers a policy that enforces the latest version after a set number of days.

The forced restart is where unsaved work gets lost, so tell people in advance. Give at least a week’s notice, explain what they will see, and avoid deadlines during month-end or trading hours. For one global trading company with around 1,000 Macs, we used deadline enforcement with seven days’ notice and took update compliance from 65% to 98% in four weeks.

Testing before you upgrade

We recommend rings: IT first, then a pilot group of willing users from each department, then a department at a time, then everyone. Keep each ring on macOS 27 for a week or two before moving on. Check the things that most often break:

  • Line-of-business apps, plug-ins and anything still running under Rosetta.
  • Security tools such as Jamf Protect or another endpoint protection product, including system and network extensions.
  • VPN clients and any content filtering or proxy software.
  • Printers, scanners and card readers.
  • Sign-in through Platform SSO or Jamf Connect, tested on 27.2 or later.
  • FileVault status and recovery key escrow after the upgrade.

Write down what you tested and the result. That record is useful for audits and for the next major release.

Security and identity changes worth planning for

Apple says that on a Mac with macOS 26.4 or later, FileVault is turned on during Setup Assistant by default. That is welcome, but you still need the personal recovery key escrowed to your management tool. With escrow in place, management can also stop users turning FileVault off.

macOS 27 extends Platform SSO. Apple lists OpenID sign-in at FileVault unlock, the Lock Screen and the login window, with multi-factor and QR code sign-in, and the option to require Touch ID or Apple Watch. In 27.2, the new login experience is used by default only with OpenID or when Touch ID is required, and Apple fixed password sync for Macs registered for Platform SSO on macOS 26 or earlier. Test sign-in on 27.2 or later before you roll out.

Apple also added declarative controls in macOS 27, including which apps or binaries may run and restrictions for Siri AI and Visual Intelligence. Review these against your data protection and acceptable use policies before you switch them on.

One more reason to get Macs to Tahoe or later: Apple’s zero-wipe migration between management tools needs macOS 26 or later and enrolment through Automated Device Enrollment. If a move to a new platform is on your roadmap, see our guide to migrating to Jamf.

A 30, 60, 90 day upgrade plan

This is the plan we use with clients. Adjust the timings to your change process.

  • Days 1 to 30: inventory every Mac by model, chip and macOS version. List Intel Macs and Rosetta apps. Move update settings to Blueprints or the Intune settings catalog, and set a deferral for macOS 27 while Tahoe updates continue.
  • Days 31 to 60: upgrade the IT ring, then the pilot group, on macOS 27.2 or later. Work through the test list and fix what breaks. Confirm FileVault escrow and sign-in.
  • Days 61 to 90: tell staff the dates, then enforce macOS 27 by department with deadlines. Track compliance weekly. Agree retirement dates and budget for the Intel Macs that stay on Tahoe.

How we help

We are a Jamf Partner and Jamf MSP, and a Microsoft partner, so we work with Jamf Pro and Intune estates alike. A Jamf Pro health check finds the update settings that stopped working in macOS 27 and what to replace them with. Our Mac IT support includes a review that lists every Mac, flags the Intel Macs that cannot move to macOS 27, and keeps your estate patched by deadline afterwards. See our Apple and Jamf work for the wider picture.

Sources

Frequently asked questions

Can’t see your question? Call us on +44 20 7550 9103 or book a call.

Can my Mac run macOS 27?

Only if it has Apple silicon. Apple says any Mac with Apple silicon can upgrade to macOS Golden Gate 27. Intel Macs stay on macOS Tahoe 26 or earlier, and only four Intel models run Tahoe.

Will Intel Macs still get security updates?

For now, yes. Apple released macOS Tahoe 26.7.3 and Sequoia 15.8.3 on 9 November 2026. Apple does not publish end-of-support dates, so check its security releases page and set your own retirement date for each Intel Mac.

How long can we delay macOS 27 on company Macs?

With declarative software update settings you can defer updates for 1 to 90 days, and Apple says a major upgrade can be deferred longer than a minor update. The old MDM deferral restriction no longer works on Macs already on macOS 27.

Can we force Macs to upgrade by a date?

Yes. Set a target version and a deadline through declarative device management. The deadline uses each Mac’s local time. At the deadline, macOS quits open apps and restarts to install, so give staff notice.

Do our Jamf update policies still work on macOS 27?

Apple says legacy software update management no longer functions in macOS 27, so old settings no longer apply to those Macs. They still apply to Macs on Tahoe 26 and earlier. Jamf recommends Blueprints for macOS 27 and later.

Should we skip macOS Tahoe and wait for macOS 27?

Apple silicon Macs can go straight to macOS 27 once your apps are tested. Intel Macs cannot go beyond Tahoe 26. Most organisations will run both versions for a while, so plan by device rather than by version.

Get new guides by email

Practical updates on Apple, Jamf, Microsoft 365 and security. Unsubscribe at any time.

Sign up

Start with a 1-hour conversation

Tell us what you want your IT to do next. We’ll ask about your people, devices and plans, and tell you honestly whether we’re the right fit.

London head office

Postremo IT Limited

Level 24, One Canada Square
Canary Wharf
London E14 5AB

+44 20 7550 9103
info@postremoit.com

Also in Dubai

Business Bay, Dubai