Join our Newsletter — 33% off our NHI Course
Home› Guides› macOS Platform SSO and Directory Binding Guide: moving…
Guide Endpoint Security

macOS Platform SSO and Directory Binding Guide: moving Mac login from AD binding to your identity provider

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 8 November 2026 12 min read
On this page

Many Mac fleets still bind to Active Directory or keep local passwords that drift away from the corporate identity, which leaves login, FileVault and local administrator rights outside the controls applied to every other sign-in. Platform SSO (PSSO), part of Apple's Extensible Single Sign-on framework since macOS 13, links the Mac login account to a cloud identity provider such as Microsoft Entra ID or Okta, and can use a hardware-bound Secure Enclave key instead of a password. This guide compares PSSO with directory binding and the Kerberos SSO extension, explains the authentication methods, the settings that decide who becomes a local administrator, the device keys and tokens involved, what to log and a hardening baseline. It is for endpoint and identity engineers, and goes deeper on login than our macOS Security Guide for Enterprises.

This is an independent guide from NHI Mgmt Group, based on Apple's public documentation as of November 2026. It is not sponsored or reviewed by Apple. Product features change, so confirm settings against Apple's current documentation.

Key takeaways

  • Binding is legacy; local accounts plus SSO is Apple's model. Apple's Kerberos SSO extension documentation says Macs do not need to join an AD domain and recommends local accounts rather than mobile accounts.
  • The authentication method sets the security level. Password sync keeps a phishable password; the Secure Enclave key method gives a hardware-bound, phishing-resistant credential to the identity provider; smart card and access key need card registration with the identity provider.
  • PSSO can grant local administrator rights. UserAuthorizationMode and AdministratorGroups map identity provider groups to the local admin group at each authentication, so group membership in the identity provider becomes Mac root access.
  • Login policies decide what happens offline. From macOS 15, LoginPolicy, UnlockPolicy and FileVaultPolicy can require live identity provider authentication, with grace periods that you must size deliberately.
  • Shared device keys are a device credential. Apple recommends them and several features require them; treat the device registration they create as a non-human identity with its own lifecycle.

How identity and access work in macOS Platform SSO

PSSO is configured with the Extensible SSO payload (com.apple.extensiblesso, type Redirect) and its PlatformSSO dictionary, delivered by MDM. It needs an identity provider app that contains a PSSO extension, for example Microsoft's Company Portal (version 5.2404.0 or later for Entra ID) or Okta Device Access Desktop Password Sync. The Mac registers with the identity provider, keeps a local account mapped to the identity provider account, and obtains SSO tokens for apps that use that provider.

ApproachHow login worksStrengthsConsiderations
Active Directory binding (mobile accounts)Mac joins the domain with a computer account; AD users log in with cached mobile accountsFamiliar; on-premises group policy-like control via directoryNeeds domain controller reach; password sync breaks for changes made elsewhere; no cloud MFA at login; Apple no longer recommends mobile accounts
Local accounts plus Kerberos SSO extensionLocal account; extension obtains AD Kerberos tickets and syncs the local password with ADNo binding; password expiry notices; access to on-premises Kerberos resourcesNot intended for Entra ID; still password based
Platform SSO, Password methodLocal password is synchronised with the identity provider passwordOne password; supports WS-Trust federationPhishable password remains the login credential
Platform SSO, Secure Enclave keyUser logs in with the local password; a hardware-bound key authenticates to the identity providerPhishing resistant to the identity provider; Microsoft documents it as usable for WebAuthn challengesLocal password still exists and needs its own policy
Platform SSO, Smart card or Access keyCard, token or Apple Wallet pass registered with the identity providerStrong user bindingSmart card not supported in Setup Assistant registration for Entra ID; card logistics

Choosing. Choose the Secure Enclave key method as the default for Entra ID or Okta fleets that want phishing-resistant SSO without hardware tokens. Use Kerberos SSO alongside PSSO only where users still need on-premises Kerberos services; Apple notes a domain can use only one SSO extension, and that combining them requires syncLocalPassword set to false in the Kerberos configuration. Keep AD binding only for Macs that depend on a directory-specific feature you cannot replace, and record them as exceptions. Small organisations can usually go straight to PSSO; large estates should migrate by department with binding removed device by device.

Migrating from directory binding

A bound Mac carries three things that PSSO does not need: a computer account in AD with its own machine password, mobile accounts whose cached credentials depend on the domain, and often a directory group that grants local admin rights. Plan the migration as an identity change, not just a profile push.

  1. Map dependencies: list what still uses the binding, such as file shares, printers, certificate enrolment through AD, and admin groups. Kerberos-based resources can move to the Kerberos SSO extension or PSSO Kerberos SSO.
  2. Convert accounts: mobile accounts must become local accounts before or during PSSO registration. Test the conversion on a pilot Mac and confirm FileVault access survives, since FileVault unlock is tied to the local account.
  3. Register, then unbind: register the Mac for PSSO, confirm SSO and login work, then remove the binding with MDM and delete the computer object, so no stale machine account remains in AD.
  4. Retire the old admin path: remove the AD group that granted local admin, replacing it with the identity provider group in AdministratorGroups.

Versions. Apple lists macOS 13 as the minimum, with on-demand account creation from macOS 14, login policies from macOS 15 and web-based (OpenID) authentication from macOS 27. Microsoft recommends macOS 14 as the minimum for Entra ID PSSO and supports macOS 13 without recommending it.

Admin roles and privileged access

PSSO moves local privilege decisions into the identity provider. The relevant keys in Apple's schema are:

KeyValuesSecurity effect
NewUserAuthorizationModeStandard, Admin, Groups, TemporaryRights given to accounts created at login
UserAuthorizationModeStandard, Admin, GroupsRights reapplied at every authentication
AdministratorGroupsIdentity provider group namesMembers become local administrators
AuthorizationGroupsAuthorization right to group pairsDelegates specific macOS authorization rights to a group
EnableAuthorizationtrue or false (needs shared device keys)Identity provider accounts accepted at authorization prompts
NonPlatformSSOAccountsLocal user namesAccounts exempt from login, unlock and FileVault policies
  • Default to Standard: set UserAuthorizationMode to Standard or Groups, never Admin for everyone. Because Groups mode is reapplied at authentication, removing a user from the admin group in the identity provider removes local rights at next login.
  • Protect the admin group: the identity provider group named in AdministratorGroups is a privileged group. Put it under access reviews and alert on membership changes. See the Okta Security Hardening Guide and the Entra ID Security Guide.
  • Local break-glass and management accounts: the MDM-created management account and any IT admin account belong in NonPlatformSSOAccounts only if they are rotated and vaulted. An exempt account with a static password is a bypass of every login policy (MITRE ATT&CK T1078.003 Local Accounts).
  • Identity provider help desk: a password or authenticator reset in the identity provider now unlocks a Mac. With PSSO, a social engineering call to the help desk can also reach Mac login. Require strong identity verification before any reset.

Integrations, API tokens and service accounts

  • Shared device keys (UseSharedDeviceKeys): signing and encryption keys used for all users on the device, giving the Mac a trusted connection to the identity provider independent of any user. Apple recommends them whenever possible and requires them for Touch ID, Authenticated Guest Mode, user creation at login and authorization. They create a device registration in the identity provider: include it in device lifecycle, and remove stale registrations when a Mac is wiped or retired.
  • User Secure Enclave key: a per-user, non-exportable key. For Entra ID, Microsoft documents an optional biometric policy that requires Touch ID for every use of the key, with no password fallback, and requires re-registration if enabled after deployment. If you restrict FIDO2 keys by AAGUID in Entra ID, Microsoft states that the macOS Platform Credential AAGUID must be allowed.
  • Tokens: PSSO obtains identity provider tokens for SSO (for Entra ID, the extension provides SSO to Entra-protected apps). These tokens are a target for theft on a compromised Mac. See the Entra ID Primary Refresh Token (PRT) Security Guide.
  • Attestation: from macOS 15.4, AllowDeviceIdentifiersInAttestation includes UDID and serial number in PSSO attestations, so the identity provider can match the registration to inventory.
  • Kerberos: optional Kerberos SSO through PSSO gives access to on-premises AD and Entra Kerberos resources. See the Kerberos Security Guide.

Logging and detection

  • Identity provider sign-in logs: PSSO registrations, Mac logins and token refreshes appear in Entra ID or Okta logs. Alert on new device registrations for a user who already has a registered Mac, and on registrations from unmanaged devices. See the Entra ID Sign-In and Audit Log Detection Guide.
  • Group changes: alert on membership changes to the groups in AdministratorGroups and AuthorizationGroups.
  • Mac unified log and EDR: collect AppSSO and authentication events, local admin group changes (dseditgroup or directory service changes) and use of accounts in NonPlatformSSOAccounts.
  • MDM: alert on changes to the Extensible SSO profile, especially authorization mode, grace periods and exempt accounts, which attackers or careless admins can use to weaken login (MITRE ATT&CK T1556 Modify Authentication Process).

Metrics: percentage of Macs registered for PSSO; percentage using the Secure Enclave key or smart card rather than Password; number of Macs still bound to AD; number of users with standing local admin rights; number of exempt local accounts per device; median time for an identity provider disable to block Mac login (test it).

Hardening baseline

  1. Prepare: confirm macOS 14 or later (15 for login policies), deploy the identity provider app and its version requirement, and decide the authentication method per population.
  2. Pilot: deploy the Extensible SSO profile to an IT group with UseSharedDeviceKeys true, Secure Enclave key method, UserAuthorizationMode Groups, and a dedicated admin group.
  3. Login policies: start with AttemptAuthentication for LoginPolicy, UnlockPolicy and FileVaultPolicy, then move high-risk groups to RequireAuthentication with an OfflineGracePeriod sized for travel. Apple notes that FileVault-time authentication needs identity provider reach without VPN, network relay or 802.1X, so test from a hotel-style network.
  4. Frequency: LoginFrequency defaults to 64,800 seconds (18 hours) with a minimum of 3,600; shorten it for privileged users.
  5. Enrolment: for new Macs, use EnableRegistrationDuringSetup (macOS 26) or first-user creation during Setup Assistant so the first account is PSSO from day one.
  6. Unbind: remove AD binding device by device after PSSO registration succeeds, and delete the AD computer objects.
  7. Clean up local admin: remove standing local administrator rights, keep one rotated management account, and see the Local Administrator Password Solution (LAPS) Guide for the equivalent Windows practice.

Rollback: keep FileVault recovery keys escrowed in MDM before enforcing login policies; Apple documents a Personal Recovery Key and a recoveryOS bypass that lasts 12 hours. Removing the PSSO profile returns the Mac to plain local accounts.

FrameworkReferenceFit
NIST SP 800-53 Rev. 5IA-2, IA-5, AC-2, AC-6Central authentication, authenticator management, account lifecycle, least privilege for local admin
NIST CSF 2.0PR.AA-01Identities and credentials managed by the organisation
CIS Controls v8.1Control 5 Account Management, Control 6 Access Control ManagementCentralised accounts, MFA, admin privilege restriction
MITRE ATT&CKT1078.003, T1556Exempt local accounts, weakened authentication settings

Common misconfigurations

  • Password method everywhere: teams deploy PSSO for convenience with password sync and believe login is now phishing resistant. It is not.
  • Admin authorization mode for all users: setting NewUserAuthorizationMode or UserAuthorizationMode to Admin recreates the standing local admin problem PSSO could have solved.
  • Long grace periods: an OfflineGracePeriod of weeks means a disabled user can keep using a stolen Mac with the cached password.
  • Two SSO extensions on one domain: combining PSSO and Kerberos SSO without setting syncLocalPassword false produces password sync conflicts.
  • Stale device registrations: wiped Macs keep registrations in the identity provider, which then trust devices that no longer exist.
  • Half-migrated fleets: Macs both bound to AD and registered for PSSO, with no owner for the remaining binding.

Practitioner checklist

  • Inventory bound Macs, mobile accounts and local admin accounts before migrating.
  • Choose Secure Enclave key or smart card as the default method; restrict Password to documented exceptions.
  • Enable shared device keys and include device registrations in the device lifecycle.
  • Set authorization mode to Standard or Groups and protect the admin group in the identity provider.
  • Keep exempt local accounts to a rotated, vaulted management account.
  • Pilot login policies with AttemptAuthentication before RequireAuthentication, and size grace periods.
  • Escrow FileVault recovery keys before enforcing FileVault policy.
  • Alert on admin group changes, new registrations and Extensible SSO profile changes.
  • Unbind from AD and delete computer objects once PSSO is working.
  • Test quarterly that disabling a user in the identity provider blocks Mac login and unlock within your target time, including when the Mac is offline.

Standards and references

Related NHI Mgmt Group resources: macOS Security Guide for Enterprises · Phishing-Resistant MFA Guide · Apple Declarative Device Management and Managed Device Attestation Guide · Disk Encryption Guide: BitLocker and FileVault

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 8 November 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.