Add AntiBait to the force-install list. The browser installs it from the store, keeps it updated, and users cannot remove it. On Windows, apply these registry keys or set ExtensionInstallForcelist with Group Policy.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\ExtensionInstallForcelist]
"1"="<chrome-extension-id>;https://clients2.google.com/service/update2/crx"

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallForcelist]
"1"="<edge-extension-id>;https://edge.microsoft.com/extensionwebstorebase/v1/crx"

In Google Admin console, add the extension by ID under Apps and extensions and set it to Force install. In Intune, use the same ExtensionInstallForcelist setting from the Chrome or Edge administrative templates.

Pin settings

A setting set by policy overrides the user's choice and shows as locked in the extension. Chrome reads it from the extension's 3rdparty policy key:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\<chrome-extension-id>\policy]
"autoScan"="auto"
"showBanner"=dword:00000001
"linkWarnings"=dword:00000001

For Edge, set the same values under the Edge key below. In Google Admin console, enter them as JSON in the extension's Policy for extensions field.

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions\<edge-extension-id>\policy

Firefox installs the Mozilla-signed AntiBait file straight from antibait.io and keeps it updated from there. Put this policies.json in the distribution folder of the Firefox installation, or set the same values with Group Policy or a macOS configuration profile.

{
  "policies": {
    "ExtensionSettings": {
      "[email protected]": {
        "installation_mode": "force_installed",
        "install_url": "https://antibait.io/downloads/firefox/latest.xpi"
      }
    },
    "3rdparty": {
      "Extensions": {
        "[email protected]": {
          "autoScan": "auto",
          "showBanner": true,
          "linkWarnings": true
        }
      }
    }
  }
}

latest.xpi always serves the current release. The 3rdparty block pins settings; leave it out to let users choose.

Thunderbird supports the same ExtensionSettings policy. Put this policies.json in the distribution folder of the Thunderbird installation.

{
  "policies": {
    "ExtensionSettings": {
      "[email protected]": {
        "installation_mode": "force_installed",
        "install_url": "https://antibait.io/downloads/thunderbird/latest.xpi"
      }
    }
  }
}

We document settings policies for Chrome, Edge and Firefox only. In Thunderbird, set them in the add-on's options.

Deploy the Outlook add-in from the Microsoft 365 admin center. It works in Outlook on Windows, Mac and the web.

1. 01

   Sign in to the Microsoft 365 admin center and open Settings, then Integrated apps.

2. 02

   Choose Upload custom apps, select Office Add-in, and provide the link to the manifest file below.

3. 03

   Choose the users or groups who should get the add-in, and finish the deployment.

4. 04

   Ask people to open AntiBait from the message toolbar and sign in once.

https://antibait.io/outlook-addin/manifest.xml

A deployed add-in can take several hours to appear in Outlook. Without an admin, a person can add it themselves: Get Add-ins, My add-ins, Add a custom add-in, Add from URL.

antibait.io publishes the SHA-256 of every file it serves at /downloads/index.json. Compare it with the file before you stage it for deployment.

curl -s https://antibait.io/downloads/index.json
sha256sum antibait-firefox-*.xpi

(Invoke-RestMethod https://antibait.io/downloads/index.json).firefox.sha256
Get-FileHash -Algorithm SHA256 .\antibait-firefox-*.xpi