Apple Platform Single Sign-on, UAE

The Mac local password and the company password have been two different things for twenty years.

Platform Single Sign-on ends that. The local account password synchronises with your identity provider whenever it changes, locally or remotely, local accounts can be created on demand when somebody signs in with a company identity, and the whole thing works from the login window rather than after it.

Apple Platform Single Sign-on for UAE organisations
  • macOS 13+The stated minimum version
  • Five methodsPassword, web, smart card, Secure Enclave, access key
  • Password syncLocal and identity provider, either direction
  • Accounts on demandCreated at first sign-in
How this differs from Jamf Connect

One is Apple framework. The other is a product that uses it.

We work with both and the distinction matters when deciding what to deploy, because they are not alternatives in the way people assume.

  • Platform Single Sign-on is an Apple capability in macOS. It requires a device management service that supports Extensible Single Sign-on configuration and a compatible extension from your identity provider. It is the underlying mechanism rather than a thing you buy.
  • Jamf Connect is a Jamf product addressing Mac identity, and it fits into a Jamf-managed estate with Jamf tooling around it. For organisations already running Jamf Pro, that integration and the surrounding capability set are the argument.
  • The practical question is therefore not which of the two, but what your device management service and your identity provider each support, and whether you want the Apple framework configured directly or a product experience built around it.
  • Where an organisation is already invested in one platform, that usually decides it. Where an organisation is choosing, the deciding factors are the identity provider extension available, the macOS versions in the fleet, and whether the shared device key requirements fit the way the Macs are used.
Ask which route fits your Mac estate
What it does

Eight things about Platform SSO that decide whether it fits your estate.

Apple describes Platform Single Sign-on as available in macOS and providing a seamless login and authentication experience. It requires a device management service supporting Extensible Single Sign-on configuration and a compatible extension from your identity provider, so it is a framework rather than a product.

Password synchronisation, in both directions

Apple states that when enabled, the local user password automatically synchronises with the identity provider whenever a user changes their password, either locally or remotely. That single behaviour removes the oldest and most persistent Mac support problem in a corporate estate: the local password and the company password drifting apart until somebody cannot get into their own machine.

Local accounts created on demand

Apple describes creating additional local user accounts on demand when a user signs in with credentials from an identity provider account, with administrators able to specify which identity provider attribute becomes the account name. For shared Macs, hot-desking, laboratories and any device more than one person uses, this removes the account pre-creation exercise entirely.

A Secure Enclave-backed key, which is the interesting one

Apple describes a user who signs in to their Mac with a local account password being able to use a Secure Enclave-backed key to authenticate. That binds the authentication to the hardware in the machine rather than to something the user knows and could be persuaded to reveal, which is a meaningfully different security property from a synchronised password, and it is the option worth considering for anybody whose account would be valuable to an attacker.

Web-based authentication, for the flows you already use

Web-based flows are supported with multifactor authentication and QR code scanning. For organisations whose identity provider already runs a specific sign-in journey, including conditional policies and second factors, this means the Mac login experience uses that journey rather than a parallel simplified one that bypasses the controls you have configured.

Smart card and access key options

Smart card authentication is supported and requires registration with the identity provider. There is also an access key approach described as pass-based authentication through Apple Wallet. Between five methods, most organisations find one that matches what they already use rather than having to adopt something new for the Mac population specifically, which is usually the fastest route to a decision.

It works with your device management service, whichever it is

The requirement Apple states is a device management service that supports Extensible Single Sign-on configuration, plus a compatible extension from your identity provider. That means Platform SSO is not tied to one management platform, and organisations running Intune, Jamf or another service can use it provided both halves of that requirement are met.

Shared device keys, which gate several features

Apple states shared device keys are mandatory for several capabilities, naming Automated Device Enrollment, Touch ID, web authentication, guest mode, on-demand accounts and network authorisation. That is a design consideration rather than a footnote, because several of those are precisely the features organisations adopt Platform SSO for in the first place.

Version requirements that need checking against your fleet

Apple states Platform SSO is available from macOS 13 or later, and that more advanced capabilities require later macOS versions. Which specific features need which version is something we confirm against your actual estate rather than assuming, because a Mac fleet in a real organisation spans several versions and the answer determines what is achievable now.

How we approach it

Four things that decide whether a Platform SSO rollout is smooth.

This changes how people sign in to their own machine every morning, which makes it one of the few configurations where the communication matters as much as the design.

We confirm both halves of the prerequisite before anything else

Apple requires a device management service supporting Extensible Single Sign-on configuration and a compatible extension from your identity provider. Both, not either. Confirming those two facts and the macOS versions in your fleet takes a short conversation and determines whether this is a configuration project or a prerequisites project.

We choose the authentication method from what you already run

Five approaches are supported: password including federated environments, web-based flows with multifactor and QR code scanning, smart card, a Secure Enclave-backed key, and an access key through Apple Wallet. The right one is almost always whichever matches your existing identity approach, rather than the most technically interesting.

We plan around the shared device key requirements

Apple names Automated Device Enrollment, Touch ID, web authentication, guest mode, on-demand accounts and network authorisation as requiring shared device keys. Several of those are the reasons organisations want Platform SSO at all, so establishing the requirement early prevents a design that assumes a capability it has not enabled the prerequisite for.

We handle the existing Macs deliberately

A fresh Mac enrolling into Platform SSO is straightforward. A Mac somebody has used for three years, with a local account whose password diverged from the company one long ago, is a migration. Working out that starting state across the fleet, and sequencing the change, is what separates a quiet rollout from a week of login problems.

Where this matters most

Six UAE situations where Mac identity is worth solving properly.

Mac estates in this market are growing, frequently in the parts of the business least tolerant of friction, and they are consistently the least integrated part of the identity picture.

A design, media or engineering team on Macs

Almost every organisation here has one, and it is usually the group with the least patience for IT process and the most autonomy in choosing tools. A sign-in experience that matches the rest of the company, with the password they already know, removes a daily irritation and makes every subsequent management conversation easier.

A regulated firm needing consistent identity controls

Where multifactor authentication, conditional policies and access reviews apply across the estate, a Mac population authenticating against a local password that nothing governs is a genuine gap. Web-based authentication with multifactor support means the Mac login uses the same journey and the same controls as everything else.

An organisation with shared or hot-desked Macs

Creating local accounts on demand when somebody signs in with a company credential is exactly what this population needs, and it removes the pre-provisioning exercise that shared Mac estates otherwise require. Note that on-demand accounts are among the features Apple names as requiring shared device keys.

Education and training environments

Laboratories, teaching rooms and shared machines where different people use the same Mac through the day. Accounts created at first sign-in, with the account name derived from an identity provider attribute you choose, makes the estate manageable without an administrator preparing accounts for every possible user.

A helpdesk fielding Mac password calls

The most common and most avoidable Mac support call: somebody changed their company password, the Mac local password did not follow, and now they cannot sign in. Password synchronisation in both directions removes that category of ticket entirely, which is usually the fastest way to justify the work internally.

An organisation moving towards phishing-resistant authentication

A Secure Enclave-backed key binds authentication to the hardware in the machine rather than to a shared secret, which is a materially different property from a synchronised password. For organisations already moving towards passkeys and hardware-bound credentials elsewhere, extending that thinking to Mac sign-in is a natural next step.

Three positions

How Mac identity actually works in UAE organisations.

The right column is the default state of any Mac estate nobody has deliberately configured, and it is the source of a recurring and entirely avoidable category of support call.
Local password matches the company password
Platform SSO configuredYes
A directory binding or productUsually
Local accounts, unconnectedNo
Password change propagates automatically
Platform SSO configuredYes
A directory binding or productSometimes
Local accounts, unconnectedNo
Local accounts created without pre-provisioning
Platform SSO configuredYes
A directory binding or productSometimes
Local accounts, unconnectedNo
Company multifactor policy applies at sign-in
Platform SSO configuredYes
A directory binding or productVaries
Local accounts, unconnectedNo
Hardware-bound authentication available
Platform SSO configuredYes
A directory binding or productVaries
Local accounts, unconnectedNo
Works from the login window
Platform SSO configuredYes
A directory binding or productVaries
Local accounts, unconnectedNot applicable
Depends on a directory connection
Platform SSO configuredNo
A directory binding or productFrequently
Local accounts, unconnectedNo
Shared Macs practical to run
Platform SSO configuredYes
A directory binding or productAwkward
Local accounts, unconnectedNo
Password reset generates a support call
Platform SSO configuredRarely
A directory binding or productSometimes
Local accounts, unconnectedRoutinely
Frequency in the UAE market
Platform SSO configuredRare
A directory binding or productUncommon
Local accounts, unconnectedVery common
The authentication methods

Five approaches, and where each one belongs.

Drawn from the published descriptions. Most organisations find one that matches their existing identity approach rather than needing to adopt something new for the Mac population.
MethodWhat it involves
PasswordCredential-based, including WS-Trust for federated environments
Web-basedFlexible flows with multifactor support and QR code scanning
Smart cardHardware token, requiring registration with the identity provider
Secure Enclave-backed keyLocal account password sign-in using a key bound to the device hardware
Access keyPass-based authentication through Apple Wallet
Local account creationAccounts created on demand at first sign-in with an identity provider credential
Password synchronisationLocal password syncs with the identity provider on change, locally or remotely
How a deployment runs

Five steps, and the prerequisites check comes first.

Typically three to six weeks depending on fleet size and how many existing Macs need migrating. Fresh devices are simple. Established Macs with divergent local passwords take the time.
  1. 1

    Confirm the prerequisites and the fleet

    A device management service supporting Extensible Single Sign-on configuration, a compatible extension from your identity provider, and the macOS versions actually present across the estate against the stated minimum of macOS 13 or later. Any Macs below that become a refresh conversation rather than a configuration one.

  2. 2

    Choose the authentication method and the account model

    Which of the supported methods fits your existing identity approach, whether password synchronisation is enabled, which identity provider attribute becomes the local account name, and whether accounts should be created on demand for shared devices. These decisions shape everything that follows.

  3. 3

    Enable the prerequisites the features depend on

    Including shared device keys, which Apple names as mandatory for Automated Device Enrollment, Touch ID, web authentication, guest mode, on-demand accounts and network authorisation. Several of those are usually the reason for the project, so this is not an optional configuration detail.

  4. 4

    Pilot on both new and established Macs

    A freshly enrolled Mac and a Mac somebody has been using for years with a diverged local password behave differently, and the second is the one that reveals the real migration work. Testing both, with real users rather than IT staff, is what determines the shape of the rollout.

  5. 5

    Communicate, then roll out in waves

    This changes how people sign in to their own machine, so a short clear message about what will look different and what to do if it does not work is worth more than any technical preparation. Then waves by team, with the group most tolerant of a hiccup first.

Straight answers

What organisations ask about Platform Single Sign-on.

Before deploying

Fifteen questions worth answering first.

The first group is whether the prerequisites are met. The second is the design. The third is what happens to the Macs you already have, which is the part that determines the rollout shape.

Prerequisites

  • Does your device management service support Extensible SSO?
    A stated Apple requirement.
  • Does your identity provider have a compatible extension?
    The other half of the requirement.
  • What macOS versions are in your fleet?
    macOS 13 or later is the stated minimum.
  • Are the Macs enrolled in management already?
    Configuration is delivered through the management service.
  • Do you use Automated Device Enrollment?
    Shared device keys are required for it.

Design

  • Which authentication method fits your identity approach?
    Five are supported.
  • Do you want password synchronisation enabled?
    It works in both directions.
  • Which identity attribute becomes the local account name?
    Administrators specify this.
  • Do any Macs need accounts created on demand?
    Shared, laboratory and hot-desk devices.
  • Is Touch ID or guest mode in scope?
    Both are named as requiring shared device keys.

Existing Macs

  • How many local accounts already exist per Mac?
    The starting state affects the migration.
  • Do local and company passwords currently differ?
    They almost always do.
  • Are any Macs below the minimum macOS version?
    That is a refresh or upgrade question.
  • How will users be told what is changing?
    This affects their daily sign-in.
  • What is the fallback if something goes wrong?
    Sign-in changes deserve a rollback path.
Next step

Check two things: your management service and your identity provider.

Tell us about macOS versions, identity provider, account setup and the sign-in problems users experience. We will confirm the requirements and proposed scope with you.