What happened to macOS 27.1? Apple skipped it. Here's 27.2 for business Macs

What happened to macOS 27.1? Apple skipped it. There is no macOS 27.1 for Mac. Apple's own security releases page (opens in a new tab) goes from macOS 27.0.1 on 28 September 2026 straight to 27.2 on 26 October, then 27.2.1 on 9 November. The number 27.1 was used for iOS only, for the iPhone Duo. So if you've been waiting for "the .1 release" before upgrading your Macs, it has already been and gone under a different name. 27.2 is the one with the business fixes: three for Platform SSO, one that stops the upgrade removing Rosetta, and about 260 security fixes. 27.2.1 adds eight more security fixes. The version a business Mac should be on today is 27.2.1, or a fully patched Tahoe 26.7.3 if you're holding back.

We wrote up what broke on macOS 27 three weeks after launch. This is the follow-up, because two updates have shipped since and one of them changes our advice.

Is there a macOS 27.1?

No. Here's every macOS 27 release so far, from Apple's security releases page:

Apple's list of macOS 27 updates (opens in a new tab) shows the same four and nothing in between.

Each one shipped with updates for the older systems too. On 9 November that was Tahoe 26.7.3 and Sequoia 15.8.3.

Why did Apple skip macOS 27.1?

Apple hasn't explained it. The best account is from Howard Oakley at The Eclectic Light Company, who wrote on 12 October (opens in a new tab) that the iPhone Duo "has its own version of iOS 27.1, which won't appear as a general release for other models". His conclusion: "To keep version numbers in sync, Apple is therefore intending not to release x.1 updates for its other operating systems."

So 27.1 belongs to one phone. Everything else, Macs included, jumped to 27.2.

Why does that matter to anyone running a fleet? Two reasons.

"Wait for the .1" now means "wait for 27.2". Plenty of teams hold a new macOS until the first proper update. That update exists. It's just numbered 27.2.

Check your version rules. If a compliance policy, a smart group or an update policy is waiting for 27.1, it will wait forever. Search your MDM for the string and change it.

What does macOS 27.2 fix for business Macs?

Apple's enterprise notes (opens in a new tab) list seven changes in 27.2. Four of them matter to most business fleets.

Platform SSO passwords sync again. Apple's wording: "Platform SSO passwords sync successfully on devices that registered for Platform SSO on macOS 26 or earlier." That covers any Mac that was set up with Platform SSO on Tahoe or earlier and then upgraded.

Okta saw the same thing from its side. Its support article (opens in a new tab) says that during the upgrade, "existing Platform SSO device encryption keys become inaccessible for some users" with Desktop Password Sync, and that "this issue is fully resolved in macOS 27.2". Okta Verify added macOS 27 support in version 9.73.0 (opens in a new tab) on 22 October, so update that too.

The new Platform SSO login screen is opt-in for most setups. Apple says the new login experience "is only used by default when using OpenID or when requiring Touch ID". Read plainly, other setups don't get the new screen unless you switch it on.

Rosetta survives the upgrade. "Rosetta is no longer removed when upgrading to macOS 27." In October we told you to push Rosetta through MDM because the upgrade dropped it. That's now only true for Macs that upgraded on 27.0 or 27.0.1. A Mac that goes from Tahoe to 27.2 or later keeps it.

Remote support tools can move windows again. Apple "resolved an issue where some third-party remote access apps could not move windows on a target Mac". If your helpdesk has been fighting that during remote sessions, this is the fix.

The other three: a login window message about Touch ID that showed when a smart card PIN was required, a MacBook Neo that restarted when using an external camera, and extra HTTP headers that Platform SSO can now send to an identity provider.

On security, Apple's notes for 27.2 (opens in a new tab) list about 260 fixes. None is described as exploited. That's a normal size for the first big update after a launch, and it's the main reason not to sit on 27.0.1.

One thing to know about on the feature side. 27.2 lets Siri AI keep context from earlier conversations and draw on more of what's on the Mac, and adds an Excluded Apps setting. If you've already made a decision about Apple's AI features on work Macs, check it still holds after this update.

What does macOS 27.2.1 fix?

Eight security flaws, listed in Apple's notes (opens in a new tab). Apple doesn't describe any of them as exploited.

• Five are about pairing. They sit in AirPlay, Bluetooth and the services behind them. One allows "a malicious Bluetooth device" to "establish a pairing without user interaction".
• Two are in Messages. One lets "a remote attacker" join an iMessage group chat and receive its messages.
• One is a memory bug in a compression library.

Bluetooth-range attacks need someone nearby, which sounds unlikely until you remember where laptops go: trains, cafes, shared offices, conferences. Install it.

Apple's enterprise notes have no section for 27.2.1, so there's nothing new for MDM in it.

Which version should a business Mac be on now?

The date comes from Cyber Essentials, which expects high and critical security updates within 14 days of release. Apple doesn't publish severity ratings, so we treat every security update as in scope. All three came out on 9 November.

If a Mac is still on 27.0 or 27.0.1, it's also missing everything in 27.2, and that 14-day window closed on 9 November. Move it now.

Staying on Tahoe is still fine. Apple has patched it alongside every macOS 27 update so far.

One practical point. On macOS 27, only Declarative Device Management can enforce an update. If your update policy was built the old way, it isn't pushing 27.2.1 to anything. Our Intune and macOS 27 post covers the settings to use.

Is anything still not ready for macOS 27?

Yes, and it's the same group as October.

Avid. The Pro Tools compatibility chart (opens in a new tab), updated 3 November, still says "macOS 27 Golden Gate is not currently supported with Pro Tools". Avid's Golden Gate page (opens in a new tab) hasn't changed since 1 October and still lists Media Composer as not yet supported. Edit and audio suites stay on Tahoe.

Anything you haven't checked. A point release doesn't change what a vendor supports. Before a team upgrades, look at the vendor's own page for each app they rely on, not a forum post from September.

We didn't find new problems caused by 27.2 or 27.2.1 themselves. One narrow report: The Eclectic Light Company noted on 6 November (opens in a new tab) that some installers for older macOS versions were being reported as damaged, and that 27.2 could be one of the possible causes. That only matters if you downgrade Macs.

What should you do this week?

1. Stop waiting for 27.1. Change any policy, group or note that mentions it.
2. Get macOS 27 Macs to 27.2.1 by 23 November. Use a declarative update policy with a deadline.
3. Patch the Macs you're holding back. Tahoe to 26.7.3, Sequoia to 15.8.3, same date.
4. If you use Platform SSO, make 27.2 your minimum. Update Okta Verify to 9.73.0 or later first.
5. Find Macs that lost Rosetta. Any Mac that upgraded on 27.0 or 27.0.1 and runs an Intel-only app needs it reinstalled.
6. Keep Avid Macs on Tahoe.

If you were holding office Macs back until the first real update, this is it. The Platform SSO fixes and the Rosetta change remove the two things most likely to generate tickets on upgrade day.