Edit

Share via

macOS device settings to configure and use kernel and system extensions in Intune

  • Article

Important

This template is deprecated in the August 2024 service release (2408). Existing policies continue to work. But, you can't create new policies using this template.

Instead, use the settings catalog to create new policies that configure the System Extension payload. To learn more about the settings catalog, go to the macOS settings catalog.

Note

This article describes the different kernel and system extension settings you can control on macOS devices. As part of your mobile device management (MDM) solution, use these settings to add and manage extensions on your devices.

This feature applies to:

  • macOS

To learn more about extensions in Intune, and any prerequisites, go to add macOS extensions.

These settings are added to a device configuration profile in Intune, and then assigned or deployed to your macOS devices.

Before you begin

Kernel extensions

This feature applies to:

  • macOS 10.13.2 and newer

What you need to know

  • Kernel extensions don't work on macOS devices with the M1 chip, which are macOS devices running on Apple silicon. This behavior is a known issue, with no ETA.

  • For any macOS devices running 10.15 and newer, we recommend using system extensions (in this article). If you use the kernel extensions settings, then consider excluding macOS devices with M1 chips from receiving the kernel extensions profile.

Settings apply to: User approved device enrollment, Automated device enrollment

Note

You don't have to add team identifiers and kernel extensions. You can configure one or the other.

  • Allow User Overrides: Yes lets users approve kernel extensions not included in the configuration profile. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might prevent users from allowing extensions not included in the configuration profile. Meaning, only extensions included in the configuration profile are allowed.

    For more information on this feature, go to user-approved kernel extension loading (opens Apple's web site).

  • Allowed Team Identifiers: Use this setting to allow one or many team IDs. Any kernel extensions signed with the team IDs you enter are allowed and trusted. In other words, use this option to allow all kernel extensions within the same team ID, which can be a specific developer or partner.

    Enter a team identifier of valid and signed kernel extensions to load. You can add multiple team identifiers. The team identifier must be alphanumeric (letters and numbers) and have 10 characters. For example, enter ABCDE12345.

    After you add a team identifier, it can also be deleted.

    Locate your Team ID (opens Apple's web site) has more information.

    Tip

    The Team ID is stored on the local KextPolicy database. You can get the Team ID using the sqlite3 command from a macOS device that has the same app installed:

    1. On the macOS device, open the Terminal app, and run the following script:

      sudo /Volumes/Macintosh\ HD/usr/bin/sqlite3 /Volumes/Macintosh\ HD/var/db/SystemPolicyConfiguration/KextPolicy "SELECT * from kext_policy"

      • In our example, the volume name is Macintosh HD. Update the script with your volume name.
      • Be sure you have root access, and can run a SUDO command on the device.

    2. Review the output. The first entry is the Team ID. In our example, the Team ID is PXPZ95SK77:

      PXPZ95SK77|com.paloaltonetworks.kext.pangpd|1|Palo Alto Networks|5

  • Allowed Kernel Extensions: Use this setting to allow specific kernel extensions. Only the kernel extensions you enter are allowed or trusted.

    Enter the bundle identifier and team identifier of a kernel extension to load. For unsigned legacy kernel extensions, use an empty team identifier. You can add multiple kernel extensions. The team identifier must be alphanumeric (letters and numbers) and have 10 characters. For example, enter com.contoso.appname.macos for Bundle ID, and ABCDE12345 for Team identifier.

    Tip

    To get the Bundle ID of a kernel extension (Kext) on a macOS device, you can:

    1. In the Terminal app, run kextstat | grep -v com.apple, and note the output. Install the software or Kext that you want. Run kextstat | grep -v com.apple again, and look for changes.

      In the Terminal app, kextstat lists all the kernel extensions on the OS.

    2. On the device, open the Information Property List file (Info.plist) for a Kext. The bundle ID is shown. Each Kext has an Info.plist file stored inside.

System extensions

This feature applies to:

  • macOS 10.15 and newer

Settings apply to: User approved device enrollment, Automated device enrollment

Note

Adding the same Team ID for Allowed system extensions and Allowed team identifiers can result in an error and the profile failing. Don't add the same exact Team Identifier to both settings.

  • Block User Overrides: Yes prevents users from approving system extensions that aren't in the allowed list. When set to Not configured (default), Intune doesn't change or update this setting. By default, the OS might allow users to approve unknown extensions not included in the configuration profile. Meaning, extensions not included in the configuration profile are allowed.

  • Allowed team identifiers: Use this setting to allow one or many team IDs. Any system extensions signed with the team IDs you enter are always allowed and trusted. In other words, use this option to allow all system extensions within the same team ID, which can be a specific developer or partner.

    Enter a Team identifier of valid and signed system extensions to load. You can add multiple team identifiers. The team identifier must be alphanumeric (letters and numbers) and have 10 characters. For example, enter ABCDE12345.

    After you add a team identifier, it can also be deleted.

    Locate your Team ID (opens Apple's web site) has more information.

    Tip

    You can also get the Team ID from a mac where the application is installed

    In the Terminal app, run:

    systemextensionsctl list

    and note the output:

    E.g. UBF8T346G9 com.microsoft.wdav.netext (101.04.48/101.04.48) Microsoft Defender for Endpoint Network Extension

    The first entry is the Team ID you need. UBF8T346G9 in our example

  • Allowed system extensions: Use this setting to always allow specific system extensions. Only the system extensions you enter are allowed or trusted.

    Enter the Bundle identifier and Team identifier of a system extension to load. For unsigned legacy system extensions, use an empty team identifier. You can add multiple system extensions. The team identifier must be alphanumeric (letters and numbers) and have 10 characters. For example, enter com.contoso.appname.macos for Bundle ID, and ABCDE12345 for Team identifier.

  • Allowed system extension types: Enter the Team ID, and system extension types to allow for that Team ID:

    • Team identifier: Enter the Team ID of another system extension you want to allow specific extension types. Or, enter a Team ID you added to Allowed system extensions.

    • Allowed system extension types: Select the system extension types to allow for each Team ID. Your options:

      • Select all
      • Driver extensions
      • Network extensions
      • Endpoint security extensions

      For more information on these extension types, go to System Extensions (opens Apple's web site).

      You can add a team ID from the Allowed system extensions list, and allow a specific extension type. If the extension is a type that isn't allowed, then the extension might not run.

      To allow all extension types for a Team ID, add the Team ID to the Allowed system extensions list. Don't add the Team ID to the Allowed system extension types list. In other words, if a team ID is in the Allowed system extensions list, and not in the Allowed system extension types list, then all extension types are allowed for that team ID.

Assign the profile and monitor its status.