Platform SSO (PSSO)

With Relution, macOS devices can be configured so that users sign in with their Microsoft Entra ID account directly at the login window (Platform Single Sign-On). On the first sign-in, a local user account is created that is linked to the Entra ID identity.


Prerequisites

  • macOS 13 (Ventura) or later for Extensible SSO, macOS 15 (Sequoia) or later for the login, unlock and FileVault policies, the grace periods and non-Platform SSO accounts, macOS 26 (Tahoe) for Setup Assistant registration and authenticated guest mode. Microsoft recommends at least macOS 14 (Sonoma).
  • A Mac with Apple Silicon if the recommended Secure Enclave Key method is used (see Choosing the authentication method →). On Intel Macs, only the Password method is available.
  • A Microsoft Entra ID tenant
  • Permission to register devices in Microsoft Entra ID for the users
  • Microsoft Company Portal for Mac must be available as an app and installed before users are targeted for PSSO. For registration during the Setup Assistant (macOS 26+), version 5.2604.0 (April 2026) is required. The latest version is always recommended — it meets both requirements.
  • Network access to the Microsoft/Apple sign-in URLs (see General section →). These URLs must be reachable and excluded from any TLS inspection, otherwise registration fails.

Platform SSO itself does not require Relution to be connected to Microsoft Entra ID; the configuration works without this connection. The connection is only needed if users are also to be synchronized from Entra ID or if Conditional Access → is used: Connect Relution with Entra ID →. Conditional Access additionally requires OIDC →.


Preparation in Microsoft Entra ID

Before the configuration is rolled out in Relution, the following points should be checked in the Microsoft Entra admin center:

  • Device settings: Under Identity → Devices → Device settings, Users may join devices to Microsoft Entra ID must be set to All (or to the relevant target group).
  • Multi-factor authentication: If classic per-user MFA is enabled on the account, PSSO registration can fail. Conditional Access should be used for the MFA requirement instead.
  • Password complexity: For the Password method, the complexity requirements of the local account and Entra ID must match so that synchronization works.

Upload the Company Portal app

  1. The latest version of Microsoft Company Portal for Mac (.pkg) is downloaded from Microsoft → and then uploaded to Relution under Apps → App Store via Add as a Native app (see Native apps for macOS →).
  2. The app must be released to the target group or organization.
The Company Portal app contains the SSO extension com.microsoft.CompanyPortalMac.ssoextension, which is required for Platform SSO. It must be at least version 5.2404.0 (for Setup Assistant registration on macOS 26+: 5.2604.0).
Note on version numbers: Company Portal reports two version strings. The “About this app” version follows the scheme 5.YYMM.x (e.g. 5.2604.0 = April 2026), while the build number visible in the package or via pkgutil looks different — e.g. 4.83.26040910, where 260409 is the build date (2026-04-09). Both refer to the same release; a build from 2026 easily meets the PSSO requirement.

Assign the device group and configurations

  1. A device group is created for the Mac devices on which PSSO is to be rolled out.
  2. In the device group’s Policies section, a macOS policy containing the following two configurations is assigned via Add (one combined policy or two separate ones):
    • Extensible Single Sign-On (see Configuring the Extensible Single Sign-On policy →)
    • App compliance: Under Required apps, the uploaded Company Portal app is added via Add. If the checkbox in the Auto install column is selected (the default when adding an app), Relution installs the app automatically. Without auto install, the device is merely reported as non-compliant if the app is missing.
  3. The configurations only reach the devices once the policy has been published.
Without the Company Portal app installed, the SSO extension cannot register. Relution deploys the SSO profile independently of the app installation; no order between the two is enforced.

Choosing the authentication method

The authentication method determines how users sign in to the device and to apps. It is the most important decision during setup and is set in the Platform SSO section → of the configuration.

MethodPasswordlessLocal passwordMin. macOSSuitable for
Secure Enclave Key (recommended)Yes, phishing-resistantremains unchanged13 / 14Personalized devices, Apple Silicon only
PasswordNosynchronized with Entra ID13 / 14Intel Macs, shared/lab devices
Smart cardYes (via CBA)remains unchanged14+Organizations with physical smart cards

Recommendation: For personalized company Macs (Apple Silicon), the Secure Enclave Key method is recommended — it is passwordless, hardware-bound, and meets phishing-resistant MFA. For Intel devices or shared devices, Password is the appropriate choice.

Smart card is not supported during the Setup Assistant.

Registration during the Setup Assistant (macOS 26+): If PSSO is registered already during the Setup Assistant (Enable registration during Setup Assistant set to ON), then Enable creating first user during Setup Assistant must also be ON — regardless of the selected method. Otherwise no local account is created during setup and registration fails (verified in practice):

  • Secure Enclave Key method: sign-in ends up in a login loop.
  • Password method: the message “Sign-in not possible – Registration failed” appears.

With the toggle set to ON, the first local account is created via PSSO and sign-in completes in both cases.


Configuring the Extensible Single Sign-On policy

In a macOS policy, the Extensible Single Sign-On configuration is added.

General section

ParameterValue
Extension Identifiercom.microsoft.CompanyPortalMac.ssoextension
Denied bundle identifiersleave empty (default)
Extension data → AppPrefixAllowListcom.microsoft.,com.apple.
Extension data → browser_sso_interaction_enabled1
Extension data → disable_explicit_app_prompt1
Realmleave empty
Registration tokenleave empty (not required for Entra ID – see note)
Screen locked behaviorDo not handle (default: Cancel)
Team IdentifierUBF8T346G9 (Microsoft Team ID)
TypeRedirect (default: Credentials)
URLshttps://login.microsoftonline.com
https://login.microsoft.com
https://sts.windows.net

Required fields are Extension Identifier, Team Identifier and, for the Redirect type, URLs. With the Credentials type, the Hosts field appears instead of URLs.

Registration token: For Microsoft Entra ID, no registration token is needed in the Extensible SSO payload; the field remains empty. (The field is intended for other IdP/Kerberos scenarios.)
URLs / TLS: The three sign-in URLs must be reachable on the network and excluded from TLS inspection.

Platform SSO section

ParameterValueNote
Account display nameleave emptyoptional
Authentication MethodUser Secure Enclave KeyRecommended; for Intel/shared devices: Password (default for new configurations)
├─ Login policy– (not applicable)only visible with the Password method; macOS 15+
├─ Unlock policy– (not applicable)only visible with the Password method; macOS 15+
├─ FileVault policy– (not applicable)only visible with the Password method; macOS 15+
├─ Offline grace period– (not applicable)only visible with the Password method; macOS 15+
└─ Authentication grace period– (not applicable)only visible with the Password method; macOS 15+
Non platform SSO accountsnot setmacOS 15+
Login frequency64800 (seconds, equals 18 hrs)Re-auth interval; default 64800, minimum 3600
Use shared device keysONRequired for JIT account creation, see Shared device keys and account creation →; default: OFF
├─ Enable AuthorizationON
└─ Enable create user at loginONJust-in-time provisioning of the local account
Additional groupsnot setoptional
Administrator groupsnot setoptional
Authorization groupsnot setoptional
New user authorization modeStandard
User authorization modeStandard
Allow device identifiers in attestationOFFmacOS 15.4+
Enable creating first user during Setup AssistantON (default)macOS 26+ — required when registering during the Setup Assistant (otherwise registration fails)
New user authentication methodsnot setmacOS 26+; options Password, Smart card and Access Key. With Access Key, additional fields appear for the reader group identifier, terminal identity, issuer certificate and express mode
Synchronize profile pictureOFFmacOS 26+
Enable quick login for Authenticated Guest ModeOFFmacOS 26+
Enable registration during Setup AssistantONmacOS 26+
Account namecom.apple.PlatformSSO.AccountShortNamePlaceholder for the local short name
Full namenamePlaceholder for the full name

With the Password method, the portal additionally shows Login policy, Unlock policy and FileVault policy. Each of these policies offers the options Attempt authentication, Require authentication, Allow offline grace period and Allow authentication grace period; Unlock policy additionally offers Allow Touch ID or watch for unlock. The Offline grace period and Authentication grace period fields (prefilled with 0) can only be edited once the corresponding option Allow offline grace period or Allow authentication grace period is selected in at least one of the three policies. With the Smart card and User Secure Enclave Key methods, these fields are neither shown nor transferred.

The fields marked macOS 26+ only take effect on devices running macOS Tahoe 26 or later and require that registration already occurs during the Setup Assistant.

Relution: “Extensible Single Sign-On” configuration (example with the “Password” method)

The screenshot shows the Password method as an example. With User Secure Enclave Key (recommended, see table), the portal hides Login policy, Unlock policy, FileVault policy and both grace periods; the rest of the configuration is identical.


Further configuration

  • A policy assigned to the device group must additionally contain the App compliance configuration for Company Portal (see Assign the device group and configurations →), so the extension is already available at the time of registration.
  • For Automated Device Enrollment (ADE, DEP in the portal), it is advisable to assign the device group containing the PSSO configurations already in the auto enrollment (Devices → Auto Enrollments, in the device’s entry section Device Groups → Static device groups), so registration can take effect during the Setup Assistant (macOS 26+).

Shared device keys and account creation

Use shared device keys must be ON, because in this flow the local accounts are provisioned via just-in-time provisioning (the Enable Authorization and Enable create user at login toggles). Without shared device keys, user-bound keys would be needed — but those cannot be generated while the user account does not yet exist (chicken-and-egg problem).

Enable Authorization and Enable create user at login can only be changed while Use shared device keys is ON. If it is OFF, both are greyed out and not applied, even if they are still shown as ON. No account is then created at sign-in.

Choosing the method by device type:

  • Personalized device (recommended): Secure Enclave Key method — passwordless, hardware-bound, Touch ID.
  • Shared / multi-user device (e.g. classroom, shift work): Password method, since changing users get by without pre-configured passwordless credentials. Such devices are registered without user affinity; Conditional Access is not supported on shared Macs.

Approving background items for Microsoft AutoUpdate

As of macOS Ventura, background processes such as Microsoft AutoUpdate (MAU) are blocked by default, or users receive a “Background item added” notification and have to confirm it manually. Without this approval, MAU cannot update automatically in the background — this also affects Company Portal, since its updates run through MAU.

Background items can be approved in advance with a profile containing the com.apple.servicemanagement payload (managed login items), for example with a rule for Microsoft’s team ID (UBF8T346G9). Relution has no dedicated configuration for this payload; such a profile can, however, be distributed as a .mobileconfig file via the Apple Configurator 2 configuration (see Apple Configurator 2 Configuration →).

The Relution Login Items configuration is not suitable for this: it defines which apps are launched automatically at login, but does not approve background items.

Without this approval, users repeatedly get system notifications about new background items, and MAU may not reliably update the SSO-relevant components automatically.

Registration by end users

Once the configuration has arrived on the device and the Company Portal app is installed, the initial registration proceeds as follows:

  1. A “Registration Required” notification appears on the device. Alternatively, it can be triggered from System Settings.

  2. Right after the first sign-in, the “Single Sign-On for Mac” dialog opens with the “Register account” item. Registration continues via Continue (it appears equally for the Password and Secure Enclave Key methods).

    macOS: “Single Sign-On for Mac” dialog with “Register account”

  3. Users sign in with their Microsoft Entra ID account and confirm MFA if required (e.g. via Microsoft Authenticator).

  4. The local user account is linked to the Entra ID identity. From now on, single sign-on applies for apps and browsers that use Entra ID.

Allowing passkey autofill for Company Portal

After the first sign-in, a prompt “Allow Company Portal to autofill to use your passkey” appears. For passkey sign-in to work (Platform Credential, especially with the Secure Enclave Key method), users must enable autofill for Company Portal once:

  1. System Settings are opened via Open System Settings (or manually).
  2. There, General → AutoFill & Passwords is opened.
  3. Under AutoFill from, the toggle for Company Portal is enabled.

macOS: “Allow Company Portal to autofill to use your passkey” – Company Portal toggle under “AutoFill from” enabled

Without this approval, Company Portal cannot offer the passkey for sign-in; passwordless sign-in then fails or the prompt reappears repeatedly.
With the Secure Enclave Key method, the local password remains unchanged; after a reboot, the local password is first required to unlock FileVault, after which Touch ID can be used.

Verification

Registration success can be checked as follows:

  • On the device (Terminal): app-sso platform -s shows the registration status of the Platform SSO extension.
  • In Microsoft Entra: Under Devices, the device appears as registered/joined.
  • Company Portal: The device status is shown as compliant/registered.

Possible errors

  • Registration prompt does not appear → it should be checked whether Company Portal (version 5.2404.0+) is installed and the app compliance has already been evaluated.
  • Sign-in fails → the Team Identifier, Extension Identifier, and URLs should be checked for typos; the URLs must be excluded from TLS inspection.
  • Registration aborts at MFA → classic per-user MFA is disabled on the account and Conditional Access is used instead.
  • Secure Enclave not available → affects Intel Macs; the Password method is used there.
  • Login loop or “Sign-in not possible – Registration failed” → when registering during the Setup Assistant (macOS 26+), Enable creating first user during Setup Assistant must be ON — regardless of the method. If the toggle is OFF, no local account is created: with Secure Enclave a login loop occurs, with Password the “Registration failed” message.

For further known issues and diagnostics, see: Microsoft documentation →

How helpful was this article?