Home / Integrations / Intune, Group Policy, Google Admin

Deploy browser security with Intune, Group Policy or Google Admin.

Two steps reach every browser of your organisation: the extension is force-installed in Chrome and Microsoft Edge, and a managed setting connects it to your console. Your people do nothing, and they cannot turn it off.

1. Force-install the extension

  • Group Policy or Intune, Google Chrome: add the extension ID bkplloeajblikjdffgdepnhicgajfhcd to the Chrome policy ExtensionInstallForcelist ("Configure the list of force-installed apps and extensions").
  • Group Policy or Intune, Microsoft Edge: add the ID followed by the Chrome Web Store update address (bkplloeajblikjdffgdepnhicgajfhcd;https://clients2.google.com/service/update2/crx) to the Edge policy ExtensionInstallForcelist ("Control which extensions are installed silently"). On its own, an ID makes Edge look in Edge Add-ons instead.
  • Google Admin console: Apps & extensions → Users & browsers → add the extension from the Chrome Web Store and set it to Force install.

In Intune, both browsers' policies are in the Settings catalog (Google Chrome and Microsoft Edge categories); with Group Policy, they come from the browsers' administrative templates.

2. Connect every browser to your console (zero-touch)

The extension reads a managed setting that only the administrator can write. With it, browsers enrol in your console by themselves:

SettingWhat it does
consoleUrlThe HTTPS address of your console.
enrollmentTokenThe enrolment token from Fleet → Enrollment in the console. Create one token per group: a browser joins the group of its token. Used only to enrol, never shown to the user.
tenantIdOptional: the organisation the browser must belong to; a console or signed document of another organisation is refused.
managedModetrue: protection settings come from the console and are locked in the extension, and the user cannot disconnect the browser.
deviceLabelOptional: a name shown in the console, for example the computer name written by your script.
supportContactOptional: a short text shown to the user on the warning page and in the extension, for example "IT Helpdesk, ext. 1234".

These are the extension's own policy settings (the "3rdparty" extension policies of Chrome and Edge), delivered by Group Policy, Intune or Google Admin like any other managed setting. Contact us for a ready template for your management tool.

3. Check it works

  1. Open Devices in the console: each browser appears there after its first start with the policy.
  2. In a browser, open the extension: it shows that it is managed by your organisation, with your support contact.
  3. Events start arriving within seconds; protection never waits for the console.

Good to know

  • One signed policy for everyone: after enrolment, the protection settings, groups and detection modes come from the console, signed, so a page or a user cannot change them.
  • Browsers behind on updates are listed in the console.
  • Plans: deployment with Group Policy, Intune or Google Admin is part of the Business and Enterprise plans. Compare plans.

Related

Stop these attacks before anything runs.

Free browser protection for everyone, in Chrome and Edge. One console for your whole company when you need it.

Get the extension — free