Use the Microsoft Enterprise SSO plug-in on iOS/iPadOS devices

The Microsoft Enterprise SSO plug-in is a feature in Microsoft Entra ID that provides single sign-on (SSO) features for Apple devices. This plug-in uses the Apple single sign-on app extension framework.

The SSO app extension provides single sign-on to apps and websites that use Microsoft Entra ID for authentication, including Microsoft 365 apps. It reduces the number of authentication prompts users get when using devices managed by Mobile Device Management (MDM), including any MDM that supports configuring SSO profiles.

This article applies to:

This article shows how to create an SSO app extension configuration policy for iOS/iPadOS Apple devices with Intune, Jamf Pro, and other MDM solutions.

App support

For your apps to use the Microsoft Enterprise SSO plug-in, you have two options:

  • Option 1 - MSAL: Apps that support the Microsoft Authentication Library (MSAL) automatically take advantage of the Microsoft Enterprise SSO plug-in. For example, Microsoft 365 apps support MSAL. So, they automatically use the plug-in.

    If your organization creates its own apps, then your app developer can add a dependency to the MSAL. This dependency enables your app to use the Microsoft Enterprise SSO plug-in.

    For a sample tutorial, go to Tutorial: Sign in users and call Microsoft Graph from an iOS or macOS app.

  • Option 2 - AllowList: Apps that don't support or weren't developed with MSAL can use the SSO app extension. These apps include browsers like Safari and apps that use Safari web view APIs.

    For these non-MSAL apps, add the application bundle ID or prefix to the extension configuration in your Intune SSO app extension policy (in this article).

    For example, to allow a Microsoft app that doesn't support MSAL, add to the AppPrefixAllowList property in your Intune policy. Be careful with the apps you allow, they can bypass interactive sign-in prompts for the signed in user.

    For more information, go to Microsoft Enterprise SSO plug-in for Apple devices - apps that don't use MSAL.


To use the Microsoft Enterprise SSO plug-in on iOS/iPadOS devices:

  • The device is managed by Intune.

  • The device must support the plug-in:

    • iOS/iPadOS 13.0 and newer
  • The Microsoft Authenticator app must be installed on the device.

    Users can install the Microsoft Authenticator app manually. Or, admins can deploy the app using Intune. For information on how to install the Microsoft Authenticator app, go to Manage Apple volume-purchased apps.

  • The Enterprise SSO plug-in requirements are configured, including the Apple network configuration URLs.


On iOS/iPadOS devices, Apple requires that the SSO app extension and the Microsoft Authenticator app be installed. Users don't need to use or configure the Microsoft Authenticator app, it just needs to be installed on the device.

Microsoft Enterprise SSO plug-in vs. Kerberos SSO extension

When you use the SSO app extension, you use the SSO or Kerberos Payload Type for authentication. The SSO app extension is designed to improve the sign-in experience for apps and websites that use these authentication methods.

The Microsoft Enterprise SSO plug-in uses the SSO Payload Type with Redirect authentication. The SSO Redirect and Kerberos extension types can both be used on a device at the same time. Be sure to create separate device profiles for each extension type you plan to use on your devices.

To determine the correct SSO extension type for your scenario, use the following table:

Microsoft Enterprise SSO plug-in for Apple Devices Single sign-on app extension with Kerberos
Uses the Microsoft Entra ID SSO app extension type Uses the Kerberos SSO app extension type
Supports the following apps:
- Microsoft 365
- Apps, websites or services integrated with Microsoft Entra ID
Supports the following apps:
- Apps, websites or services integrated with AD

For more information on the single sign-on app extension, go to SSO overview and options for Apple devices in Microsoft Intune.

Create a single sign-on app extension configuration policy

In the Microsoft Intune admin center, create a device configuration profile. This profile includes the settings to configure the SSO app extension on devices.

  1. Sign in to the Microsoft Intune admin center.

  2. Select Devices > Configuration > Create.

  3. Enter the following properties:

    • Platform: Select iOS/iPadOS.
    • Profile type: Select Templates > Device features.
  4. Select Create:

    Screenshot that shows how to create a device features configuration profile for iOS/iPadOS in Microsoft Intune.

  5. In Basics, enter the following properties:

    • Name: Enter a descriptive name for the policy. Name your policies so you can easily identify them later. For example, a good policy name is iOS: SSO app extension.
    • Description: Enter a description for the policy. This setting is optional, but recommended.
  6. Select Next.

  7. In Configuration settings, select Single sign-on app extension, and configure the following properties:

    • SSO app extension type: Select Microsoft Entra ID.

      Screenshot that shows the SSO app extension type and Microsoft Entra ID for iOS/iPadOS in Intune.

    • Enable shared device mode:

      • Not configured: Intune doesn't change or update this setting.

        For most scenarios, including Shared iPad, personal devices, and devices with or without user affinity, select this option.

      • Yes: Select this option only if the targeted devices are using Microsoft Entra shared device mode. For more information, go to Shared device mode overview.

    • App bundle ID: Enter a list of bundle IDs for apps that don't support MSAL and are allowed to use SSO. For more information, go to Applications that don't use MSAL.

    • Additional configuration: To customize the end user experience, you can add the following properties. These properties are the default values used by the Microsoft SSO Extension, but they can be customized for your organization needs:

      Key Type Description
      AppPrefixAllowList String Recommended value:

      Enter a list of prefixes for apps that don't support MSAL and are allowed to use SSO. For example, enter, to allow all Microsoft and Apple apps.

      Be sure these apps meet the allowlist requirements.
      browser_sso_interaction_enabled Integer Recommended value: 1

      When set to 1, users can sign in from Safari browser, and from apps that don't support MSAL. Enabling this setting allows users to bootstrap the extension from Safari or other apps.
      disable_explicit_app_prompt Integer Recommended value: 1

      Some apps might incorrectly enforce end-user prompts at the protocol layer. If you see this problem, users are prompted to sign in, even though the Microsoft Enterprise SSO plug-in works for other apps.

      When set to 1 (one), you reduce these prompts.


      For more information on these properties, and other properties you can configure, see Microsoft Enterprise SSO plug-in for Apple devices.

      When you're done configuring the settings and are allowing Microsoft & Apple apps, then the settings look similar to the following values in your Intune configuration profile:

      Screenshot that shows the end user experience configuration options for the Enterprise SSO plug-in on iOS/iPadOS devices in Intune.

  8. Continue creating the profile, and assign the profile to the users or groups that will receive these settings. For the specific steps, go to Create the profile.

    For guidance on assigning profiles, go to Assign user and device profiles.

When the device checks in with the Intune service, it receives this profile. For more information, go to Policy refresh intervals.

To check that the profile deployed correctly, in the Intune admin center, go to Devices > Configuration > select the profile you created and generate a report:

Screenshot that shows the iOS/iPadOS device configuration profile deployment report in Intune.

End user experience

End user flow chart when installing SSO app app extension on iOS/iPadOS devices.

  • If you're not deploying the Microsoft Authenticator app using an app policy, then users must install it manually. Users don't need to use the Authenticator app, it just needs to be installed on the device.

  • Users sign in to any supported app or website to bootstrap the extension. Bootstrap is the process of signing in for the first time, which sets up the extension.

  • After users sign in successfully, the extension is automatically used to sign in to any other supported app or website.

You can test single sign-on by opening Safari in private mode (opens Apple's web site) and opening the site. No username and password will be required.

Animation showing SSO experience on iPadOS


Learn more about how the SSO plug-in works and how to troubleshoot the Microsoft Enterprise SSO Extension with the SSO troubleshooting guide for Apple devices.