A laptop displays a secure cloud authentication system linking users, devices, encryption keys, and apps.
Microsoft has published a new architecture explainer for macOS Platform SSO with Microsoft Entra ID. The goal is to settle a question many Mac admins have been asking: when a Mac "just signs in," who is doing what? The Microsoft Enterprise SSO plug-in connects the Mac to Microsoft Entra ID, and Entra ID validates the authentication proofs and issues identity credentials. Apple's macOS handles the operating-system side. The explainer comes from Microsoft Principal Software Engineer Veena Soman, and a longer Microsoft Learn architecture page backs it up.

This isn't a new feature or a patch. It is a clarification of how the pieces fit, and that is useful for anyone deploying, securing or troubleshooting Macs in a Microsoft-centric shop.

A laptop displays a secure cloud authentication system linking users, devices, encryption keys, and apps. The short version​

Platform SSO is an Apple capability, delivered through an identity provider's SSO extension. Microsoft's Learn page says it isn't a standalone Microsoft credential provider. Applications also don't implement the registration protocol themselves. The responsibilities split like this:

  • MDM (Intune or another supported MDM) deploys the Extensible SSO policy and the Platform SSO configuration.
  • The Microsoft Enterprise SSO plug-in registers the Mac and the user with Entra ID. It also supplies the identity-provider configuration macOS needs.
  • macOS Platform SSO (Apple) owns the operating-system experience. It invokes registration, protects platform credentials, coordinates authentication, and gives the resulting Primary Refresh Token (PRT) to the Microsoft extension through Apple's supported framework.
  • Microsoft Entra ID verifies the registered credential, validates the user and device proofs, and issues the PRT.
  • Apps and browsers receive only the tokens or sessions meant for them.

This split is why Platform SSO can cut sign-in prompts without handing a powerful credential to every app.

Registration is not SSO​

The most useful idea in the explainer is that registration and SSO are separate steps. Registration establishes trust. A registered device doesn't mean every application already holds a token.

The lifecycle runs in this order:

  1. MDM enrollment and policy delivery. The Mac receives an Extensible SSO configuration that names the extension and sets the authentication method and registration behavior.
  2. Key generation. Once the device is enrolled and the policy is in place, macOS generates two Secure Enclave-backed device keys. The signing key signs device-bound requests. The encryption key lets Entra protect responses so only that Mac can read them. This happens before Entra registration, and the private keys aren't exported to apps or to Entra.
  3. Device registration. macOS invokes the plug-in, which sends proof and the public-key material to Entra. Entra creates or updates the device identity. The extension then saves the registration certificate.
  4. User registration. The local macOS user is associated with an Entra identity, and the chosen authentication method is provisioned.
  5. PRT acquisition. macOS uses the stored trust to request and protect the PRT.

Microsoft says the registration certificate holds the device signing public key and binds it to the device identity. It is not the private signing key, and it is not the user's credential.

Three authentication methods, one architecture​

Admins can choose Password, UserSecureEnclaveKey or SmartCard. Microsoft's point is that these change how the user proves identity, not the overall flow. In every case macOS gathers the configured proof and binds the request to the registered Mac. Entra then validates both proofs before it issues the PRT.

MethodHow the user proves identityLocal macOS password
PasswordEntra username and passwordmacOS updates the local password to match after the PRT is issued, and again after later Entra password changes
UserSecureEnclaveKeyAssertion signed with a Secure Enclave private keyStays a separate local credential and is never updated by Platform SSO
SmartCardAssertion signed with the smart card's private key, validated through Entra certificate-based authenticationNot covered in the material reviewed

A few caveats are worth keeping in mind:

  • Microsoft states that the Password method reduces the number of passwords users manage, but it isn't passwordless or phishing-resistant.
  • Microsoft recommends UserSecureEnclaveKey for most Platform SSO deployments.
  • "Passwordless to Entra" does not mean "no Mac password." The Entra blog says FileVault and the startup sequence keep their own requirements. Users generally need the local account password for the first unlock after a restart. Microsoft's PSSO overview also says the local password isn't affected and is required to sign in to the Mac.
  • Version support varies. Microsoft's Intune documentation lists macOS 13.0 and newer for Platform SSO. A separate Intune configuration guide notes that macOS 13 uses a deprecated authentication-method setting. Confirm your macOS, plug-in and MDM versions before promising a method to users. Microsoft's own page warns that exact behavior depends on all of them, plus tenant policy.

Apps never get the PRT​

Applications don't receive the PRT, the device private keys or the user's authentication key. A supported app or browser starts an ordinary Entra sign-in. The plug-in checks whether macOS holds a compatible PRT. If it does, the plug-in uses it to request an app-specific token or to finish a supported web SSO flow. The resulting token is scoped to the requesting client and resource. Microsoft says one application doesn't gain access to another's tokens.

Microsoft also describes how refreshing works. macOS manages PRT refresh automatically. If the tokens are missing, expired or more than four hours old, it tries to refresh them or get new ones. That describes what triggers a refresh attempt. It doesn't guarantee a refresh will succeed.

Kerberos: a three-party job​

A common misconception is that the Microsoft plug-in provides Kerberos SSO on its own. In fact the work is split between three components.

  • Entra can return a cloud Kerberos ticket-granting ticket (TGT), an on-premises TGT, or both, in the same protected response as the PRT. The TGTs are separate from the PRT.
  • The plug-in supplies mappings that tell macOS which TGT fields to import. macOS validates the response and imports the selected tickets into a Kerberos credential cache.
  • If the Kerberos SSO extension is configured with usePlatformSSOTGT, it can consume a matching-realm TGT from macOS. It then obtains service tickets for cloud or on-premises resources, provided the ticket is still valid and the resource configuration allows SSO.

If custom_tgt_setting isn't specified, the plug-in maps both TGTs by default. Admins can map both, only the cloud TGT, only the on-premises TGT, or neither.

Passkeys are an optional extra​

Platform Credential passkeys are related but not required to obtain a PRT. In supported Entra scenarios, the Secure Enclave-backed user key registered through UserSecureEnclaveKey can answer a WebAuthn challenge. PRT acquisition and passkey authentication can use the same registered hardware-backed identity, but they answer different protocol requests. Microsoft's PSSO overview also describes an optional UserSecureEnclaveKeyBiometricPolicy setting. When it is enabled, users are prompted for Touch ID whenever the key is accessed.

What this means for admins​

The documentation doesn't include a formal troubleshooting procedure. But the ownership split suggests a sensible order for diagnosing problems. This is my own inference from that split, not Microsoft guidance:

  1. Policy delivery. Did the Extensible SSO and Platform SSO configuration actually reach the Mac?
  2. Plug-in presence. Is the extension present and at a suitable version? Third-party MDM guides describe it being hosted by Company Portal for macOS.
  3. Registration state. Is the Mac registered? Microsoft's shared-device tutorial describes checking the Network Account Server entry in System Settings for a "Registered" Platform SSO status.
  4. Entra validation and issuance. Did Entra accept the proofs and issue the PRT?
  5. App-level token. Is the specific app or resource getting its own token or session?

Treating Platform SSO as one black box invites wasted hours. Treating it as a relay race lets you find which runner dropped the baton.

One more point from Microsoft's Intune guidance: if you use Platform SSO, configure only Platform SSO. Don't create a separate SSO app extension policy, because the app extension is already included.

Limits of the source material​

This is Microsoft documenting its own product, so expect the framing to be favorable. The explainer is a mental model, and Microsoft says its Learn page is the maintained technical reference. The sources don't establish how Conditional Access behaves in a particular tenant. They also don't promise identical prompts across every app.

The takeaway still holds. Registration builds trust, macOS protects and brokers the platform credential, and Entra issues the PRT only after validating the proofs. Applications get only their own authorization.

 

References

  1. Demystifying macOS Platform SSO: How Apple and Microsoft Entra ID work together Microsoft Entra Blog 2026-11-20T16:00:00+00:00
  2. Demystifying macOS Platform SSO: How Apple and Microsoft Entra ID work together techcommunity.microsoft.com
  3. Architecture and authentication flow for macOS Platform SSO with Microsoft Entra ID - Microsoft Entra ID | Microsoft Learn learn.microsoft.com