Blog Post

Microsoft Entra Blog
5 MIN READ

Demystifying macOS Platform SSO: How Apple and Microsoft Entra ID work together

veenasoman's avatar
veenasoman
Icon for Microsoft rankMicrosoft
Nov 20, 2026

Go behind the scenes of macOS Platform SSO and see how Apple, Microsoft Entra ID, and the Microsoft Enterprise SSO plug-in work together.

Platform SSO has been transforming the macOS sign-in experience by bringing Microsoft Entra authentication closer to the operating system. Users can sign in to their Mac and access work applications with fewer authentication prompts, while organizations retain Microsoft Entra device trust and access controls.

As more organizations deploy Platform SSO, new questions have emerged:

  • What actually happens under the hood?
  • Which responsibilities belong to Apple, and which belong to Microsoft?
  • Where are credentials created and protected?
  • Does every application receive the Platform SSO Primary Refresh Token (PRT)?

To help answer these questions, we published a new Microsoft Learn article: Architecture and authentication flow for macOS Platform SSO with Microsoft Entra ID.

Apple Platform SSO is an extensible framework that can work with supported identity-provider extensions. This post focuses on its integration with Microsoft Entra ID through the Microsoft Enterprise SSO plug-in. It provides a practical mental model, highlights the ownership boundaries between Apple and Microsoft, and walks through the key parts of the architecture.

Why the ownership boundary can be difficult to see

From the user's perspective, Platform SSO can feel like one continuous experience. The Mac is enrolled, the user completes registration, and supported applications begin signing in with fewer prompts.

Behind that experience, however, several systems retain distinct responsibilities. MDM (Mobile Device Management) deploys the Platform SSO policy. The Microsoft Enterprise SSO plug-in connects the Mac to Microsoft Entra ID. macOS owns the operating-system experience and protects the platform credentials. Microsoft Entra ID validates the authentication proofs and issues identity credentials. Applications consume only the authorization intended for them.

Platform SSO is a shared architecture across device management, Apple, and Microsoft. The following diagram shows how responsibilities are divided across the end-to-end flow.

Ownership boundaries in macOS Platform SSO with Microsoft Entra ID.

This division of responsibility isn't just an implementation detail. It establishes the security boundaries that allow Platform SSO to reduce authentication prompts without distributing powerful credentials to every application.

Three ideas that make the architecture easier to understand

1. Registration and SSO aren't the same operation

Registration establishes trust. It connects the managed Mac and local user to Microsoft Entra ID, registers the required public-key material, and gives macOS the identity-provider configuration it needs for later authentication.

SSO begins when macOS uses that established trust to obtain and protect the Platform SSO PRT.

Separating these concepts answers many common questions: a registered device doesn't mean every application has already received a token. Registration creates the foundation that allows macOS and the Microsoft Enterprise SSO plug-in to perform supported SSO operations later.

2. The Platform SSO PRT belongs to the Platform SSO architecture—not to applications

Applications don’t receive the Platform SSO PRT, device private keys, or the user's authentication private key. macOS protects the Platform SSO PRT and makes it available to the Microsoft Enterprise SSO plug-in through Apple's supported Platform SSO framework. When an application needs access to a resource, the plug-in uses the PRT as part of the Microsoft Entra authorization flow. The application receives only the token or session issued for its own client and target resource.

This distinction is important: Platform SSO provides a shared sign-in experience without turning the PRT into a shared application credential.

3. Authentication methods change the proof—not the overall architecture

Organizations can configure Password, UserSecureEnclaveKey, or SmartCard as the authentication method. Each method changes how the user proves their identity:

  • Password uses the user's Microsoft Entra credential and can keep the local macOS password synchronized.
  • UserSecureEnclaveKey uses a hardware-bound key protected by the Secure Enclave.
  • SmartCard uses a certificate and its associated private key.

The broader architecture remains the same. macOS obtains the configured user proof, binds the request to the registered Mac, and sends the request to Microsoft Entra ID. Microsoft Entra ID verifies the registered credential and validates the user and device proofs before issuing the Platform SSO PRT.

As a result, choosing an authentication method is primarily a decision about user experience, credential protection, and organizational security requirements—not a completely different SSO architecture.

What this means for customers

Understanding the ownership boundaries helps administrators reason about deployment and troubleshooting:

  • MDM configuration starts the experience. Platform SSO behavior depends on the policy delivered to the Mac.
  • Apple owns the native operating-system integration. macOS controls the sign-in experience and protects the platform credentials.
  • Microsoft connects the Mac to Microsoft Entra ID through the Microsoft Enterprise SSO plug-in. The plug-in performs registration and participates in supported SSO flows.
  • Microsoft Entra ID remains the token-issuing authority. It validates the registered device and the authentication result—including proof from a federated identity provider when applicable—and issues the Platform SSO PRT and subsequent Microsoft Entra tokens.
  • Applications remain isolated. They receive authorization for their own resources rather than direct access to the Platform SSO PRT.

The result is an architecture that combines a native macOS experience with Microsoft Entra device identity, application isolation, and hardware-backed authentication options.

Common misconceptions

"UserSecureEnclaveKey means a password is never needed"

UserSecureEnclaveKey provides passwordless authentication to Microsoft Entra ID, but it doesn't remove every macOS password requirement. FileVault and the startup sequence retain their own requirements, and users generally need the local account password for the first unlock after a restart.

"The registration certificate is the user's credential"

The registration certificate represents the registered device’s signing key. It helps Microsoft Entra ID identify and validate the registered Mac. The user's identity is proved separately through Password, UserSecureEnclaveKey, or SmartCard authentication.

"Applications receive the Platform SSO PRT"

Applications receive tokens or sessions issued for their own client and target resources. macOS protects the Platform SSO PRT and exposes it only to the Microsoft Enterprise SSO plug-in through Apple's supported Platform SSO framework.

"The Microsoft Enterprise SSO plug-in provides Kerberos SSO by itself"

Kerberos SSO is another example of shared ownership. Microsoft Entra ID can return cloud and on-premises Kerberos ticket-granting tickets (TGTs) alongside the PRT in the same protected Platform SSO response. The Microsoft Enterprise SSO plug-in supplies the ticket mappings that tell macOS which TGTs to import. macOS Platform SSO validates the response and imports the selected TGTs into a Kerberos credential cache.

If the Kerberos SSO extension is configured to use Platform SSO TGTs, it consumes a matching TGT from macOS and obtains service tickets for supported cloud or on-premises resources. The Microsoft Enterprise SSO plug-in, macOS Platform SSO, and the Kerberos SSO extension therefore have separate roles; no single component owns the complete Kerberos SSO flow.

Explore the complete architecture

This post intentionally focuses on the mental model and ownership boundaries. The Microsoft Learn architecture page provides the maintained technical reference, including:

  • Device and user registration
  • Platform SSO PRT acquisition and refresh
  • Password, UserSecureEnclaveKey, and SmartCard authentication
  • Cloud and on-premises Kerberos TGTs
  • Platform Credential passkeys
  • Detailed architecture and sequence diagrams

For the complete technical flows and diagrams, see Architecture and authentication flow for macOS Platform SSO with Microsoft Entra ID.

-Veena Soman

Principal Software Engineer, Microsoft | LinkedIn

 

Additional resources

 

Learn more about Microsoft Entra

Prevent identity attacks, ensure least-privilege access, unify access controls, and improve the experience for users with comprehensive identity and network access solutions across on-premises and cloud environments.

Updated Nov 19, 2026
Version 1.0
No CommentsBe the first to comment