Skip to main content

Deploy the Firefox Extension via Kandji or Jamf

This guide shows you how to force-install the Anzenna Firefox extension on managed Macs with a .mobileconfig profile. The same file works in Kandji, Jamf Pro, Addigy, and any other MDM that delivers Apple configuration profiles.

Prerequisites​

  • MDM admin access with permission to create configuration profiles

  • Mozilla Firefox 136 or later installed on target devices

  • Your organization's domain and the client token from Anzenna support

Required Step

Before beginning deployment, contact Anzenna support to obtain your client token. The extension cannot report without it.

Overview​

Firefox reads enterprise policy from a configuration profile with the org.mozilla.firefox payload type. One profile carries both halves of the deployment: the ExtensionSettings policy that force-installs the extension from Anzenna's servers, and the 3rdparty policy that hands the extension your organization's configuration.

  • The extension installs silently and users cannot remove it

  • The extension is enabled in private windows automatically

  • Firefox reads the profile at startup, so users see the extension after their next launch

Step-by-Step Instructions​

1. Generate the .mobileconfig File​

Enter the values Anzenna support provided and download a ready-to-upload .mobileconfig. The installation URL always points at the current release, so the profile never needs updating for a new version.

Enter the values Anzenna support provided, then download. The file is a ready-to-upload .mobileconfig that force-installs the extension and hands it your organization's configuration.

2. Upload the Profile​

Kandji:

  1. Navigate to Library in the left sidebar

  2. Click Add new, then select Custom Profile

  3. Set the Name to "Firefox - Force Install - Anzenna"

  4. Click Upload File, select the downloaded .mobileconfig, then click Save

  5. Open the Library Item and assign it to the Blueprints that should receive the extension

Jamf Pro:

  1. Navigate to Computers > Configuration Profiles

  2. Click Upload and select the downloaded .mobileconfig

  3. Confirm the Distribution Method is Install Automatically

  4. On the Scope tab, target the computers or groups that should receive the extension, then click Save

Deployment Timeline

The profile lands on the next MDM check-in. Firefox reads it the next time it starts, so a user with Firefox already open sees the extension after quitting and relaunching.

Editing the profile

Re-upload the generated file for any change. Editing a custom payload inside the MDM console can rewrite it and drop keys.

Verifying Deployment​

Verify on End-User Device​

  1. Go to System Settings > General > Device Management and confirm a profile named "Anzenna Extension - Firefox" is installed

  2. Quit and relaunch Firefox

Verify in Firefox​

  1. Open about:policies. Both ExtensionSettings and 3rdparty appear under Active

  2. Open about:addons. Anzenna is listed with no remove option, which means the policy installed it

Troubleshooting​

about:policies says the Enterprise Policies Service is inactive​

Firefox found no policy at all. Either the profile has not reached the device yet, or Firefox was not fully restarted after it arrived. Quit Firefox from its menu rather than closing windows, since a closed window can leave the process running, and relaunch.

Policies are active but the extension is not installed​

Check the Firefox version in about:support; the profile is built for Firefox 136 or later. Confirm the device can reach crx.anzenna.ai.