Skip to main content

Deploy Browser Extensions via Kandji

This guide shows you how to create a Custom Profile in Kandji to force-install the Anzenna browser extension on managed Mac computers. Kandji uses Apple's standard .mobileconfig format, so the same XML payload structure works for both Chrome and Edge — you just need separate profiles for each browser.

Prerequisites​

  • Kandji admin access with permission to create Library Items

  • Target computers assigned to a Kandji Blueprint

  • Google Chrome or Microsoft Edge installed on target devices

  • Custom installation URL from Anzenna support

Required Step

Before beginning deployment, contact Anzenna support to obtain a custom installation URL for your domain. This link is essential for the configuration process.

Overview​

Kandji delivers browser extension policies as Custom Profiles (Library Items). You provide a .mobileconfig file containing the ExtensionInstallForcelist key for your target browser. Kandji pushes it to all computers in the assigned Blueprint automatically.

  • Works for both Chrome and Edge — use a separate Custom Profile for each browser

  • The extension installs silently; users cannot remove it

  • Profiles apply on the next Kandji agent check-in

Step-by-Step Instructions​

1. Generate the .mobileconfig Files​

Paste the Anzenna-supplied installation link below, then download a ready-to-upload .mobileconfig for each browser you want to deploy. The downloaded files have all UUIDs and payload metadata filled in — only the installation link is customer-specific.

Paste the link Anzenna support provided, then download one or both files. Each file is a ready-to-upload .mobileconfig.

The installation link format is extension-id;update-url. Contact Anzenna support if you don't have it yet.

2. Create a Custom Profile in Kandji​

  1. Log in to your Kandji instance

  2. Navigate to Library in the left sidebar

  3. Click the Add new button in the top-right corner, then select Custom Profile from the options

  4. Set the Name to something descriptive, e.g. "Edge - Force Install - Anzenna" or "Chrome - Force Install - Anzenna"

  5. Click Upload File and select your .mobileconfig file, then click Save

  6. After the Library Item is created, open it and assign it to the appropriate Blueprints so Kandji knows which devices to target

Deployment Timeline

Kandji pushes the profile to enrolled Macs on the next agent check-in. You can trigger an immediate check-in from the Kandji dashboard by selecting the device and clicking Run All under Library Items.

Deploying to Both Browsers

If deploying to both Chrome and Edge, repeat step 2 for each .mobileconfig file. Each browser requires its own Custom Profile.

Verifying Deployment​

Check Profile Status in Kandji​

  1. Navigate to Devices in Kandji

  2. Select a target device and open the Library Items tab

  3. Locate your Custom Profile and confirm the status shows as Pass

Verify on End-User Device (macOS Ventura and later)​

  1. Go to System Settings > General > Device Management

  2. Click the profile named after your Blueprint (e.g., "Corporate Standard")

  3. Inside the Blueprint view, look for the item matching your PayloadDisplayName (e.g., "Anzenna Extension - Chrome")

  4. Double-click that item to confirm the extension ID and update URL are being enforced

Verify in the Browser​

For Edge:

  1. Open Edge and navigate to: 

     edge://extensions

  2. The Anzenna extension will appear with a briefcase icon, indicating it is managed by your organization. The user cannot toggle it off or remove it.

  3. Navigate to edge://policy and confirm ExtensionInstallForcelist is listed under the Microsoft Edge section

For Chrome:

  1. Open Chrome and navigate to: 

     chrome://extensions

  2. The Anzenna extension will appear with a briefcase icon

  3. Navigate to chrome://policy and search for ExtensionInstallForcelist to confirm the extension ID is present

Troubleshooting​

Incorrect Installation String Format​

The policy applies but the extension does not install:

  • Verify the string is exactly extension-id;update-url — no extra spaces, line breaks, or characters

  • The update URL must be a direct link to an XML manifest file, not a browser Web Store landing page

Wrong Browser Targeted​

Profile applies but the extension does not appear in the expected browser:

  • Chrome requires PayloadType: com.google.Chrome

  • Edge requires PayloadType: com.microsoft.Edge

  • These values must also match in PayloadIdentifier. Update the XML, re-upload the file in Kandji, and re-save the Library Item.

Profile Not Appearing on Device​

The Custom Profile is not showing up under Device Management:

  • Confirm the device is assigned to the correct Blueprint

  • Trigger a manual agent check-in from the Kandji dashboard

  • Review the device's Library Item history in Kandji for error messages

Need help? Contact

Anzenna Support

for assistance.