How a deployment works
How Avanoo reaches browsers through managed policies, why installation targets computers while identity targets users, and the order of operations.
Avanoo is a browser extension. You deploy it through the browser policies you already manage: Group Policy, Intune, Google Workspace, or an equivalent. There is no installer to run and nothing for users to do. Sign in with platform access to see your organization's values and generated files.
Two channels, two scopes
Every deployment delivers two things through two channels. They fail independently.
| Installation | Identity | |
|---|---|---|
| What it does | Makes the extension present in every managed browser | Tells the extension which person it is running for |
| Target | The computer | The user |
| Where it is written on Windows | Machine policy (HKLM) | The signed-in user's policy hive (HKEY_CURRENT_USER) |
| What it carries | The force-install policy and update URL | A managed userEmail value: the real e-mail address, or <Windows SID>@<primary domain> in Pseudonymous mode |
Installation is machine-wide: every user of the computer gets the extension. Identity is per user: two people sharing a computer each need their own value. Never put identity in the machine policy, or all users of the device are reported as one person.
Google Workspace can install the extension but cannot set a per-user value. A Workspace deployment needs a second, per-user identity channel.
Installation alone identifies nobody: until identity arrives, activity has no person attached. Verify each channel on a pilot before you expand:
- Extension missing: check the installation policy.
- Installed but anonymous: check the identity source.
- Both correct but data is late: wait for the normal background cycle.
The identity value depends on your identity mode.
With Group Policy (GPO)
On domain-joined Windows, use two GPOs:
- Installation: a Computer Configuration GPO linked to an OU of devices. The Avanoo ADMX force-installs the extension in Chrome, Edge and Brave, plus Firefox if selected.
- Identity: a separate User Configuration GPO linked to an OU of users.
Group Policy Preferences (GPP) write each user's value: Active Directory
mailin Identified mode, or the Windows SID at your organization domain in Pseudonymous mode.
Installation follows the computer's OU. Identity follows the user's OU.
With Microsoft Intune
On Intune-managed Windows, use two assignments:
- Installation: a Settings catalog profile assigned to a device group, for Chrome and Edge. Brave uses a platform script.
- Identity: a remediation assigned to a user group. In Identified mode, it
writes the UPN, or Active Directory
mailwhen it differs (hybrid-joined only). In Pseudonymous mode, it writes the Windows SID at your organization domain, on hybrid-joined and Entra-joined devices.
Google Workspace and Firefox follow the same split.
Before you start
- Confirm the organization and the browsers you target.
- Confirm that your system can deliver managed browser policies.
- Get your extension IDs and update URLs through your Avanoo platform access.
- Plan for identity on Google Workspace: it still needs a generated GPP file or Intune package.
- Choose a pilot group.
Order of operations
- Choose your identity mode. It sets the value every later step delivers.
- Choose a pilot: a small group of devices and the matching users.
- Deploy both channels to the pilot.
- Verify each channel: the extension is installed and cannot be removed, then activity appears under the expected identity.
- Widen the device scope and the user scope together.
Private windows need a decision. Extensions do not run there by default, and on Chromium no policy allows them on the user's behalf. The Private windows page in this Deployment section sets out the two options and their cost. The decision can wait until after the pilot, not longer.
To remove Avanoo, withdraw the installation policy first: a force-installed extension cannot be removed while the policy is in place.
Find your procedure
The Deployment section has one page each for Group Policy, Intune, Google Workspace, and Firefox. Follow the page for each system you use. Once you are signed in, each page gives you:
- generated policy files (ADMX bundle, GPP file, or Intune scripts) with your extension IDs and update URLs filled in; and
- the Install, Identify, Verify and Expand steps, in order, then removal.
When something does not work
Find your symptom on the troubleshooting page in this Deployment section. To remove a deployment, follow the uninstall page there.