Distribute AppNavi Firefox Extension in Enterprises

The AppNavi Firefox Extension is published on Mozilla Add-ons (AMO). Because it's now listed and signed by Mozilla, it no longer needs to be manually signed per organization — it can be centrally deployed and pre-configured using standard Firefox Enterprise Policies, the same way the AppNavi Chrome Extension is distributed via Chrome policies.

This guide covers deploying and configuring the extension so end users never need to install it or enter a tenant ID manually.

Prerequisites

• Firefox 115 ESR or later (or current release channel) on target devices.
• Local administrator or deployment-tool rights on managed devices (GPO, Intune, or SCCM).
• Your AppNavi tenant ID, and organizational unit if your setup uses one.

Choosing a deployment method

All four methods produce the same result: Firefox reads the same policy schema regardless of how it's delivered, so verification (see below) is identical across all of them.

Configure with policies.json

Create or update policies.json in Firefox's distribution folder:

{
  "policies": {
    "ExtensionSettings": {
      "appnavi.firefox@gldjdbpbhhpcpimpiicmglaeeehegflh": {
        "install_url": "https://addons.mozilla.org/firefox/downloads/latest/60aab3306e8249df95f5/latest.xpi",
        "installation_mode": "force_installed"
      }
    },
    "3rdparty": {
      "Extensions": {
        "appnavi.firefox@gldjdbpbhhpcpimpiicmglaeeehegflh": {
          "DefaultTenant": "00000000",
          "EnvironmentConfigurationEnabled": "true",
          "OrganizationalUnit": "org_unit"
        }
      }
    }
  }
}

Replace 00000000 with your AppNavi tenant ID and org_unit with your organizational unit (omit OrganizationalUnit if unused). Restart Firefox on the device to apply the policy.

Alternative: Group Policy (Windows)

If your domain already manages Firefox via GPO, import the Firefox ADMX templates and configure the equivalent ExtensionSettings and 3rdparty policies through Group Policy Management instead of editing policies.json by hand.

Deploy with Microsoft Intune (Windows)

Option A — Win32 app (recommended)

Package a script that writes policies.json to the distribution folder, then deploy it as a Win32 app.

# Deploy-AppNaviPolicy.ps1
$policyDir = "$env:ProgramFiles\Mozilla Firefox\distribution"
New-Item -Path $policyDir -ItemType Directory -Force | Out-Null

$policy = @'
{
  "policies": {
    "ExtensionSettings": {
      "appnavi.firefox@gldjdbpbhhpcpimpiicmglaeeehegflh": {
        "install_url": "https://addons.mozilla.org/firefox/downloads/latest/60aab3306e8249df95f5/latest.xpi",
        "installation_mode": "force_installed"
      }
    },
    "3rdparty": {
      "Extensions": {
        "appnavi.firefox@gldjdbpbhhpcpimpiicmglaeeehegflh": {
          "DefaultTenant": "00000000",
          "EnvironmentConfigurationEnabled": "true",
          "OrganizationalUnit": "org_unit"
        }
      }
    }
  }
}
'@

Set-Content -Path "$policyDir\policies.json" -Value $policy -Encoding UTF8

1. Package the script as a .intunewin file using the Win32 Content Prep Tool.
2. In the Intune admin center, go to Apps → Windows → Add → Windows app (Win32).
3. Set the install command: powershell.exe -ExecutionPolicy Bypass -File Deploy-AppNaviPolicy.ps1
4. Set the detection rule: file exists at %ProgramFiles%\Mozilla Firefox\distribution\policies.json.
5. Assign the app to the target device group, running in system context.

Option B — Administrative Templates

Import the Firefox ADMX templates under Devices → Configuration → Administrative templates → Import ADMX, then configure ExtensionSettings and 3rdparty directly from the Intune UI — no script required.

Deploy with SCCM (Configuration Manager)

1. Save the same policies.json content shown above to a source share.
2. Create an Application (or Package/Program):
   • Deployment type: Script installer.
   • Install command: copy the file into place — e.g. xcopy policies.json "%ProgramFiles%\Mozilla Firefox\distribution\" /Y — or run Deploy-AppNaviPolicy.ps1 via powershell.exe -ExecutionPolicy Bypass -File Deploy-AppNaviPolicy.ps1.
   • Detection rule: file exists at %ProgramFiles%\Mozilla Firefox\distribution\policies.json.
3. Distribute the content to your Distribution Point(s).
4. Deploy to the target device collection, set to Install for System.

Verifying the installation

Notes

• Firefox currently supports the Discovery feature only; additional AppNavi features may be added in future releases.
• For the equivalent Chrome/Edge setup, see Distribute AppNavi Chrome Extension in Enterprises.