macOS 27 Golden Gate ends the Intel era on the Mac

Six releases in one day, and one clean cut

On Monday, 14.09.2026, Apple shipped macOS 27, iOS 27, iPadOS 27, watchOS 27, tvOS 27 and visionOS 27 at the same time. macOS 27 installs only on Macs with Apple silicon from the M1 onwards. Intel Macs stay on macOS Tahoe 26. Apple has committed to security updates for that line until autumn 2028. macOS Tahoe 26.7 arrived alongside as the fallback for anyone not moving yet.

On the iPhone the picture is calm. iOS 27 supports the same devices as iOS 26, so iPhone 11 and newer. No model drops out, and the test matrix for mobile layouts stays as it is. The same applies to iPadOS 27.

macOS 27 is the last release with Rosetta 2 fully present. With macOS 28 in autumn 2027 it disappears apart from a narrow remnant for older games. The upgrade to Golden Gate already uninstalls an existing Rosetta 2. The first launch of an Intel app then prompts for a reinstall. The trickier cases are authentication and pre-login extensions with a Rosetta dependency, because those no longer load at all under macOS 27. New in this release is a list under System Settings, General, About, Intel-based apps that shows every program which will stop launching under macOS 28. The Boot Camp Assistant and the AFP client have also been removed.

The MDM break gives no warning

Across all 27 systems Apple has removed legacy software update management. The old MDM commands, queries and restrictions for enforcing OS updates no longer work. There is no transition period and no error message. The change was signposted from macOS Tahoe onwards and confirmed at WWDC on 08.06.2026.

Declarative Device Management is now the only way to enforce an update on a current Apple device. Where a declaration and an old command overlap, the declaration wins. In day to day operations a device that jumps to 27 quietly stops patching under control. You may only notice at the next audit.

Security round and application status

The September round was large. On 16.09.2026 ZDI counted 273 individual CVEs across all supported systems. iOS 27 accounted for more than 100 of them, iOS 26.7 for more than 80, with 75 of those identical. There was no actively exploited zero day in this round. Staying on 26.7 therefore gets you the bulk of the same fixes.

As of mid September, Adobe had not documented official Creative Cloud support for macOS 27, and the compatibility page listed Tahoe as the highest confirmed version. Check directly with Adobe to see whether that has changed. Separately, support for the old Outlook for Mac ends in October 2026. Schedule that migration ahead of the system upgrade.

What to do now

For production fleets with Adobe workflows, macOS Tahoe 26.7 is the quieter choice this quarter. A pilot group on 27 still makes sense, ideally with people who have no hard deadline and a representative tool stack. On the iPhone it is enough to wait for 27.0.1 or stay on 26.7.

These items are worth clearing regardless of the upgrade decision:

• Check whether update enforcement in your MDM runs through Declarative Software Update or still relies on the old commands.

• Verify on one or two test devices that an update scheduled via DDM actually completes, including the behaviour on a forced logout.

• Check authentication and pre-login extensions for Rosetta dependencies before the first Mac moves to 27.

• Read out the list of Intel-based apps on every Apple silicon Mac and keep it as an inventory for macOS 28 planning.

• Test access to older NAS and archive shares, since the AFP client is gone.

• Budget replacements for Intel Macs with autumn 2028 as the target horizon.