Skip to main content

Deploy the Firefox Extension via Intune

This guide shows you how to force-install the Anzenna Firefox extension on Windows devices with Microsoft Intune. Firefox's configuration keys for the extension are not in Intune's settings catalog, so you import a small administrative template first and then build one profile from it.

Prerequisites​

  • Microsoft Intune administrator access with the Policy and Profile Manager role

  • Windows 10 or later devices enrolled in Intune

  • 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.

Step-by-Step Instructions​

1. Download the Template and Generate Your Values​

Download both template files, then enter the values Anzenna support provided. The two JSON values shown are what you paste into the profile in step 3.

Value for "Extension install"
{"anzenna-selfhosted@anzenna.ai":{"installation_mode":"force_installed","install_url":"https://crx.anzenna.ai/firefox/anzenna-latest.xpi","private_browsing":true}}
Value for "Extension configuration"
Enter your domain and client token above.

Import the two files into Intune once, then paste each value into its setting when you build the profile below.

2. Import the Template​

  1. Sign in to

    Microsoft Intune admin center

  2. Navigate to Devices > Windows > Configuration and open the Import ADMX tab

  3. Click Import, upload anzenna-firefox.admx as the ADMX file and anzenna-firefox.adml as the ADML file, then click Next and Create

  4. Wait for the Status column to show Available. This can take a few minutes; click Refresh to update it

3. Create the Profile​

  1. On the Policies tab, click Create > New policy

  2. Select platform Windows 10 and later, profile type Templates, then Imported Administrative templates (Preview), and click Create

  3. Name the profile "Firefox - Anzenna extension" and click Next

  4. Under Anzenna Firefox Extension, open Extension install, set it to Enabled, paste the "Extension install" value from step 1, and click OK

  5. Open Extension configuration, set it to Enabled, paste the "Extension configuration" value from step 1, and click OK

4. Assign and Deploy​

  1. Click Next through Scope tags

  2. Under Assignments, add the device groups that should receive the extension

  3. Click Next, review the settings, and click Create

Deployment Timeline

The profile applies over two device syncs: the first delivers the template to the device and the second applies the settings. Firefox reads them the next time it starts, so a user with Firefox open sees the extension after quitting and relaunching.

Updating the template

Intune refuses to re-import a template it already holds. To install a newer version of the template, delete the profile that uses it, delete the import, then import and rebuild the profile.

Verifying Deployment​

Check Profile Status in Intune​

  1. Open the profile and select Device status

  2. Confirm target devices show Succeeded. Intune's reporting can lag the device by ten minutes or more

Verify in Firefox​

  1. Quit and relaunch Firefox

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

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

Troubleshooting​

The template import fails​

Delete the failed row on the Import ADMX tab before trying again; a failed upload left in place blocks a retry under the same name.

about:policies says the Enterprise Policies Service is inactive​

Firefox found no policy at all. Check the profile's device status in Intune, sync the device again, and quit Firefox from its menu rather than closing windows, since a closed window can leave the process running.

Firefox already manages other extensions​

The "Extension install" setting writes the same registry value as Firefox's own ExtensionSettings policy. If another profile already sets that policy, merge the Anzenna entry into its JSON rather than enabling both.