Ctrlk
Changelog NotificationsAPIAikido login

Deploy Aikido Device Protection with Intune

Use Microsoft Intune to deploy Aikido Device Protection across your managed macOS fleet with the required permissions in place.

Installation

1

What you'll need

Before starting, make sure you have the following from the Aikido Device Protection dashboard:

  • Your Device Protection Token (copied from the user group selector)

  • The Shared Root CA Certificate (.pem file — downloaded in the dashboard)

  • The Aikido Device Protection installer (.pkg file — downloaded in the dashboard)

If you're missing any of these, go back to the Aikido Device Protection dashboard, click Connect Device, and complete the pre-flight steps.

2

Add the Aikido Device Protection configuration profile

  1. Download the Aikido .mobileconfig file.

  2. In the Intune admin center, go to Devices → macOS → Configuration → Create → New Policy.

  3. Select macOS as the platform. Under Profile type, select Templates, then choose Custom.

  4. Give the profile a name (e.g. "Aikido Device Protection").

  5. Under Custom configuration profile name, enter a name and browse to the downloaded .mobileconfig file to upload it.

  6. Assign the profile to the target device group.

This profile allows the Aikido Device Protection system extension to load silently, enables the network content filter, and stops users from disabling background services in System Settings → Login Items.

3

Deploy the Aikido Device Protection CA certificate

  1. In the Intune admin center, go to Devices → macOS → Configuration → Create → New Policy.

  2. Select platform macOS, profile type Templates, then choose Trusted certificate.

  3. Upload the Shared Root CA Certificate (.pem file) and assign it to the same device group.

4

Upload the Aikido Device Protection installer

  1. In the Intune admin center, go to Apps → macOS → Add.

  2. Select macOS app (PKG) as the app type.

  3. Upload the Aikido Device Protection .pkg file.

  4. On the Program tab, add a Pre-install script with the content below. Replace AIK_SAFE_CHAIN_TOKEN with your real token.

#!/bin/zsh
echo "AIK_SAFE_CHAIN_TOKEN" > /tmp/aikido_endpoint_token.txt

  1. Complete the remaining tabs (Detection rules, Assignments) and assign the app as Required for the same device group.

Pre-install scripts require the Intune management agent version 2309.007 or later. The script must exit with code 0 for the installation to proceed.

5

Deploy in the right order

Order matters. Both the configuration profile and the CA certificate must reach the device before the pkg. If the pkg installs first, macOS can ask the user for extra permissions.

Intune deploys configuration profiles and apps independently. Make sure both the profile and certificate are assigned and synced before the app reaches devices:

  1. Assign and sync the Aikido Device Protection configuration profile.

  2. Assign and sync the Aikido Device Protection CA certificate.

  3. Verify both appear on a test device before assigning the app.

  4. Then assign the Aikido Device Protection app.

6

Reboot devices after installation

  1. In the Intune admin center, go to Devices → macOS.

  2. Filter to the target device group, select all devices, and click Restart from the bulk-action menu.

The agent fully activates on the next boot.

7

Verify the deployment

On a test device, confirm:

  1. The system extension is activated:

    systemextensionsctl list | grep aikido

    Expect to see the extension marked [activated enabled].

  2. Open System Settings → General → Login Items & Extensions and confirm the Aikido Device Protection entries cannot be toggled off.

Troubleshooting

Problem
Fix

Users still see the popup

Make sure the configuration profile is scoped correctly and installed before the package policy runs

Extension is waiting for user approval

Check the System Extensions payload and confirm the team ID and bundle ID match exactly

The package installs but the device does not connect

Confirm the token script ran before the package install and that the token was copied correctly

Duplicate extension entries appear

Reboot the device

The content filter is not approved silently

Re-upload the .mobileconfig profile and verify it is installed on the device

Last updated

Was this helpful?