How to block Chrome extensions in Intune
AI agent extensions read every page your staff open and can click, type and submit inside their signed-in sessions. Intune can stop them on every managed Windows PC and Mac, as long as you pick the right setting and keep the list of IDs current.
Enabled
Next step
AI Agent Blocklist: the extension IDs to paste into Intune
Chrome and Edge extension IDs of AI agent and AI assistant extensions, each with a risk grade, in lists you can drop straight into an Intune policy and refresh every day.
- Chrome, Edge and Firefox extension IDs
- Risk grade on every entry
- macOS and Windows app identifiers
- 2,600+ AI agent domains for your firewall
From $99 a month for one organisationOne company, school or district. Updated every day.
See plans Ask a questionWhy Chrome extensions became an Intune problem
Most extensions are still ad blockers and small helpers, but a growing group are AI agents: they take a task, open tabs and act on websites as the signed-in user. Users install them from the Chrome Web Store in seconds, without admin rights.
They read every page
Many AI extensions ask for access to all sites. That covers the CRM, the HR portal, webmail and any internal tool that opens in Chrome.
They act as the user
Agent extensions fill forms, send messages and click buttons. Whatever they do carries the user's session, so logs show a normal employee at work.
They update silently
Chrome updates extensions in the background. A harmless helper today can gain new permissions or a new owner later, and nobody is asked again.
No admin rights needed
Extensions install into the user's Chrome profile. Removing local admin rights does not stop them, which is why a browser policy is needed.
They hide from inventory
Device app inventory lists installed programs. Browser extensions live inside Chrome profiles, so they rarely show up where you usually look.
Prompt injection
An agent that reads a web page can be steered by hidden text on that page. Researchers showed this many times in 2025 against AI browsers and agents.
Signs AI extensions are already in use
- Side panels with chat boxes on staff screens
- Requests to approve "an assistant" that wants Google or Microsoft account access
- Firewall or DNS logs with traffic to AI agent services from Chrome
- Extensions with the "read and change all your data" permission on chrome://extensions
- Help desk tickets about a tool that "did something by itself"
Who is most exposed
- Finance staff with banking and payment portals open
- HR and recruiting teams with personal data in web apps
- Admins signed in to cloud consoles in the same browser
- Sales teams who connect AI helpers to webmail and the CRM
- Developers who test agent extensions out of curiosity
Pick the right Intune route for each device
Intune has four ways to put a Chrome extension policy on a device. Most organisations need two of them: the settings catalog for Windows and a preference file for Macs.
| Devices | Intune route | Where you set it | When to use it |
|---|---|---|---|
| Windows 10 and 11, Chrome | Main route Settings catalog, Google Chrome settings | Devices > Manage devices > Configuration > Create > New policy, Settings catalog | Always first. Chrome settings are built in, no ADMX import needed. |
| Windows, a Chrome policy newer than the catalog | Fallback Imported ADMX | Devices > Manage devices > Configuration > Import ADMX tab > Import | Only when you need a policy the catalog does not list yet. The feature is in public preview. |
| macOS, Chrome | Main route Templates > Preference file | New policy, platform macOS, preference domain com.google.Chrome | Every managed Mac that runs Chrome. |
| Windows and macOS, Edge | Main route Settings catalog, Microsoft Edge | New policy, Settings catalog, search for Edge | Any device where Edge is allowed. Edge has its own extension IDs. |
| Older tenants | Legacy Custom OMA-URI profile | Custom profile with ADMX ingestion | Microsoft notes this was the earlier way. Move such policies to the settings catalog when you can. |
Microsoft says the Chrome settings in the catalog can be one or two Chrome versions behind the latest release. The extension policies on this page have existed for years, so they are all there.
Block Chrome extensions with the Intune settings catalog
This is the core build for Windows. It blocks named extensions, disables any that are already installed and stops users from installing them again from the Chrome Web Store.
Open a new policy
In the Intune admin center go to Devices > Manage devices > Configuration > Create > New policy. You need at least the Policy and Profile Manager role.
Choose platform and type
Platform: Windows 10 and later. Profile type: Settings catalog. Name it clearly, for example "Chrome: AI extension blocklist (device)".
Find the setting
Select Add settings and search for extension installation blocklist. Pick the result in the Google Chrome extensions category. If you see a device version and a (User) version, choose one, not both.
Enable and add the IDs
Set Configure extension installation blocklist to Enabled. Add each 32 character extension ID as a separate value, one ID per line.
Add a message (optional)
If you also use Extension management settings, you can show users a short reason when an install is blocked. Keep both policies in one profile so one team owns them.
Assign to a pilot group
Assign the policy to a small device group first. After the next check-in, open chrome://policy on a pilot PC and confirm the policy shows status OK.
Widen the assignment
When the pilot is clean, add the production groups. Keep the pilot group in scope so every future list change reaches it first.
Three entries from our list: the Manus browser operator extension, HARPA AI and Nanobrowser, all agent extensions that act on web pages. The full list is far longer and grows every week.
Intune Chrome extension allow list: block all, allow a few
An allowlist is the strict option: nothing installs unless you approved it. A blocklist is the lighter option: everything installs except what you listed. Our guide on choosing an allowlist or a blocklist for AI agents covers the trade-offs in depth.
Blocklist only
- Configure extension installation blocklist with the IDs you want gone
- Users keep every other extension
- New AI extensions are covered only when your list adds them
- Low help desk load, fits most offices
Allowlist mode
- Blocklist set to a single entry: *
- Configure extension installation allow list with approved IDs
- Anything new is blocked by default, AI or not
- Needs a request process for new extensions
The allow list only lifts entries from the blocklist. On its own, without the asterisk, it changes nothing.
Before you switch on the asterisk, export the extension IDs your staff already use from a few typical PCs. Forgetting the single sign-on or password manager extension is the most common cause of a busy Monday.
Even in allowlist mode, keep the AI blocklist. If someone later adds an AI extension to the allow list by mistake, the review against our risk grades catches it. The full method is on our Chrome extension allowlist page.
Extension management settings: one JSON policy for finer control
The Chrome policy ExtensionSettings, shown in Intune as Extension management settings, takes one line of JSON. It can block, remove or force install extensions and also limit what allowed extensions may do.
The extension cannot be installed. Already installed copies are disabled.
Blocks the extension and removes existing copies from the browser.
Text added to the Chrome Web Store error, up to 1,000 characters. Point users to your request process.
Blocks extensions that request a listed API permission, for example debugger, which lets an extension drive pages much like automation software.
Sites that allowed extensions may not read or change. Up to 100 host patterns, such as your HR or finance portals.
Settings for every extension that has no entry of its own. Use it to set a default mode or blocked permissions.
Paste the JSON as a single line with no line breaks. Test it in a JSON validator first, because one missing quote leaves Chrome unable to read the policy.
When Extension management settings and the separate blocklist or allow list policies disagree about an extension, the JSON policy wins. Pick one approach per fleet, or make sure both say the same thing.
Block Chrome extensions on Macs with Intune
Chrome for Mac is not part of the macOS settings catalog, so Intune uses a preference file. The policy keys are the same as on Windows; only the delivery differs.
Prepare the plist
Create a file with only key and value pairs. Intune rejects files wrapped in plist or dict tags, so remove those and any XML header.
Create the policy
Go to Devices > Manage devices > Configuration > Create > New policy, platform macOS, profile type Templates > Preference file.
Set the domain
Enter com.google.Chrome as the preference domain name and upload the file. Intune does not check the keys inside, so test on one Mac first.
Assign and confirm
Assign to a pilot group of Macs. On a test Mac open chrome://policy, select Reload policies and look for ExtensionInstallBlocklist with status OK.
If your Macs are managed by Jamf rather than Intune, the same keys go into a different payload. See how to block Chrome extensions on Macs with Jamf.
Do the same for Microsoft Edge
Blocking AI extensions in Chrome only moves users to Edge if Edge stays open. The Edge settings sit in the Microsoft Edge category of the settings catalog, on Windows and macOS.
| Goal | Chrome setting in Intune | Edge setting in Intune |
|---|---|---|
| Block named extensions | Configure extension installation blocklist | Control which extensions cannot be installed |
| Approve exceptions | Configure extension installation allow list | Allow specific extensions to be installed |
| One JSON policy | Extension management settings | Configure extension management settings |
| Check on the device | chrome://policy | edge://policy |
Extensions from the Edge Add-ons store have different IDs from their Chrome Web Store versions. Edge users who install from the Chrome Web Store use the Chrome IDs. Block both lists in Edge. Details are on our Edge extension blocklist page.
Device scope, user scope and policy conflicts
Most "Intune Chrome policy not working" threads come down to scope. Device scoped settings write to HKLM, user scoped settings write to HKCU, and Chrome does not simply add the two together.
Device scope
Applies to every person who signs in to the PC. Machine level Chrome policy outranks user level policy for the same setting. This is the usual choice for a security blocklist.
User scope
Settings marked (User) apply to the users you target. Useful for an exception group, but if a device scoped copy exists, the device copy wins and the user list is ignored.
Merging lists
By default Chrome takes the list from the highest priority source. The Chrome policy Allow merging list policies from different sources can merge a named list policy across sources of the same scope and level.
Do not split one blocklist over two Intune profiles that hit the same device. Intune reports a conflict and you cannot predict which list Chrome ends up with.
Check that the block works
Run these checks on two or three pilot devices before you widen the assignment. They take about ten minutes per device.
On the device
- chrome://policy, Reload policies: the blocklist shows status OK
- The value list matches what you entered in Intune
- A blocked extension that was installed is now disabled and cannot be switched on
- Trying to add it from the Chrome Web Store fails, with your message if you set one
- Approved extensions still run, including single sign-on
In Intune
- The policy shows Succeeded, not Error or Conflict
- Per-setting status shows no conflicts for the blocklist
- Devices > Monitor > Assignment failures lists nothing for this policy
- Export the policy as JSON and keep it with your change record
- The Edge policy reached the same devices
What to block, what to watch, what to allow
Every entry in our list carries a risk grade, so you do not have to treat a grammar helper and an autonomous browser agent the same way.
Block
- Browser agent and operator extensions that act on pages
- Extensions of general autonomous agents
- Higher risk grades across all AI extensions
- Unknown AI extensions with all-sites access
Watch
- AI meeting note extensions that join calls
- Reading and summary sidebars
- Writing helpers inside webmail
- Pair with firewall logs of the matching domains
Allow
- The AI assistant your company licensed
- Single sign-on and password manager extensions
- Line of business extensions you build
- Each with an owner and a review date
Which AI extensions are risky and why is covered in are AI Chrome extensions safe. For one specific tool, see how to block Claude in Chrome.
Keep the list current without rebuilding the policy
New AI extensions appear every week, and existing ones change names. A static list typed in once goes stale within a month.
Our list updates. New agent extensions are added with their tool name, category and risk grade.
Compare the new file with the IDs in your Intune policy and paste the additions into the same setting.
The pilot group gets the change first. Check chrome://policy on one device.
Production groups receive the same policy at their next check-in. No new profile needed.
Extensions are one layer. AI browsers such as Comet or ChatGPT Atlas are separate apps, and agent services are reached over the network. Our guide to blocking AI with Intune covers apps and web filtering, and removing AI browsers covers the apps themselves.
Stop typing extension IDs by hand
The AI Agent Blocklist gives you the IDs, already sorted by category and risk grade, in formats Intune accepts.
- Chrome and Edge extension block lists for Intune, Group Policy and the Google Admin console
- macOS bundle IDs and Windows package IDs and process names of AI browsers and agent apps
- 2,600+ AI agent domains as plain lists, CSV, JSON and firewall formats
- Updated every day, download access set up within one business day of your order
From $99 a month for one organisationPlans for MSPs and product makers on the pricing page.
See plans Ask a questionAsk us or order a plan
Tell us what you need to block and where your rules live. We reply within one business day.
- Files for firewalls, DNS filters, secure web gateways, MDM and browser policies
- Updated every day as new AI browsers, agents and extensions appear
- Plans for one organisation, for MSPs and for product makers, or a hosted filter we run for you
Intune Chrome extension questions
How do I block Chrome extensions in Intune?
Create a policy under Devices > Manage devices > Configuration > Create > New policy, choose Windows 10 and later and Settings catalog, then add the Google Chrome setting Configure extension installation blocklist. Enable it, add one extension ID per entry and assign it to a pilot group first.
Chrome disables blocked extensions that are already installed.
Do I need to import the Chrome ADMX files into Intune?
Usually not. Google Chrome settings are built into the Windows settings catalog. Microsoft notes the catalog can be one or two Chrome versions behind, so import the ADMX files only if you need a policy that is newer than the catalog.
How do I build an Intune Chrome extension allow list?
Set Configure extension installation blocklist to a single entry, an asterisk, which blocks every extension. Then add the extensions you approve to Configure extension installation allow list. Only the listed extension IDs can be installed.
Does an Intune blocklist remove extensions that are already installed?
A blocked extension that is already installed is disabled and the user cannot turn it back on. If you want Chrome to remove it as well, use Extension management settings with the installation mode removed for that extension ID.
Can Intune block Chrome extensions on a Mac?
Yes. Chrome for Mac is not in the macOS settings catalog, so you use a macOS policy with the profile type Templates > Preference file, the preference domain com.google.Chrome and a plist file that holds the ExtensionInstallBlocklist key.
Why is my Intune Chrome extension policy not applied?
Open chrome://policy on the device and select Reload policies. Common causes are a second policy that sets the same setting, a user scoped and a device scoped copy of the same setting, Extension management settings overriding the blocklist, or a typing error in an extension ID.
Can the same approach block AI extensions in Microsoft Edge?
Yes. The Microsoft Edge category in the settings catalog has Control which extensions cannot be installed, Allow specific extensions to be installed and Configure extension management settings. Edge add-ons have their own IDs, so use the Edge list, not the Chrome list.
Managing Chrome from the cloud instead? See blocking Chrome extensions in the Google Admin console. On domain-joined PCs without Intune, use Group Policy and the registry. For the wider picture, start with how to block AI browser extensions.
Microsoft, Intune, Windows, Microsoft Edge and Microsoft Entra are trademarks of the Microsoft group of companies. Google, Chrome, Chrome Web Store and Google Admin console are trademarks of Google LLC. Apple, Mac and macOS are trademarks of Apple Inc. Jamf is a trademark of Jamf Software, LLC.
Perplexity and Comet are trademarks of Perplexity AI, Inc. ChatGPT and ChatGPT Atlas are trademarks of OpenAI. Claude is a trademark of Anthropic, PBC. Manus, HARPA AI and Nanobrowser are trademarks of their respective owners.
Names are used only to identify the products discussed. AI Agent Blocklist is not affiliated with, sponsored or endorsed by these companies.