Microsoft Edge

Microsoft Edge extension blocklist for AI extensions

Edge installs extensions from two stores, and the same AI extension has a different ID in each. A blocklist built for Chrome alone leaves half the door open on every Edge laptop.

Edge Add-onsMicrosoft's store, used by defaultSider Operator: kgkeacnfccpmbaiklacgpnlheandnlmi
Chrome Web StoreAfter Allow extensions from other storesSider Operator: mokiolnliafiddobcgmmnmhbmimpccon
Both install into the same Edge profile

Next step

AI Agent Blocklist: Edge Add-ons and Chrome Web Store IDs of AI extensions in one Edge policy file

Ready for Group Policy, Intune and the Edge management service, with a risk grade on every entry. Updated every day.

From $99 a month for one organisation

Two stores, two IDs for the same AI extension

Edge Add-ons and the Chrome Web Store each publish their own package of an extension, and the ID comes from that package. These three AI extensions from our list show the pattern.

ExtensionEdge Add-ons IDChrome Web Store IDCategoryRisk grade
Sider OperatorkgkeacnfccpmbaiklacgpnlheandnlmimokiolnliafiddobcgmmnmhbmimpcconBrowser assistant with agent modeGraded
NanobrowserajdioenfpgabnjlclgckbbnjjhdnjkhnimbddededgmcgfhfpcjmijokokekbkalBrowser agents and web automationGraded
Read AIogdmafmclboiecjpbedkbgdnaklohhkmaiamjjeggglngiggkmmbnpnpeejjejafMeeting assistantsGraded

If your Edge blocklist holds only the Edge Add-ons IDs, a user who turns on Allow extensions from other stores can install the Chrome Web Store copy of the same agent. Edge keeps the Chrome ID for that copy, so it is not caught.

Our files carry both ID sets for every AI extension we track, plus Firefox IDs. Read why AI extensions need a policy at all in how to block AI browser extensions.

Edge Add-ons ID

Open the extension in Edge Add-ons. The ID is the last part of the page address in the address bar.

Chrome Web Store ID

Open the extension in the Chrome Web Store. The 32-letter ID is again the last part of the page address.

On a device

Open edge://extensions, switch on Developer mode in that page and read the ID under each installed extension. It tells you which store copy the user has.

What goes wrong with AI extensions in Edge

Edge is the default browser on most Windows fleets, so it is where AI extensions turn up first. These are the gaps we see admins miss.

The other store is one toggle away

Users can switch on Allow extensions from other stores themselves. The policy for that setting only sets its default; Microsoft states it cannot stop installs from other stores.

Sidebar apps open on their own

Some extensions open as sidebar apps next to every page. They read what the user is looking at, internal pages included.

Sync brings extensions back

A user who signs in to Edge with a personal profile can sync extensions from home onto the work laptop.

Agents act inside work sessions

Agent extensions click and type in the tabs where the user is signed in to Microsoft 365, the CRM and the finance portal. Hidden page text can steer them.

Researchers showed in 2025 that instructions hidden in web pages and documents can steer AI agents that act in the browser. Treat any extension that can act on its own as high risk until you have reviewed it. Our checklist on whether AI extensions are safe applies to Edge too.

Who is exposed, and the signs to look for

Edge holds the work identity on most Windows laptops, so an AI extension in Edge sees Microsoft 365 mail, files and admin portals by default.

Most exposed

  • IT and cloud admins signed in to admin centers in Edge
  • Finance staff who approve payments in web portals
  • Support and sales teams working in CRM and ticket tools all day
  • HR, legal and health staff who handle personal data
  • Shared and kiosk devices where many people use one profile

Signs an AI extension is active

  • Unfamiliar IDs in your extension inventory or on edge://extensions
  • A sidebar app or floating AI button on internal pages
  • The other-stores toggle switched on in user profiles
  • Traffic from managed laptops to AI agent domains
  • Help desk questions about extensions that stopped after a sync

Where the Edge extension blocklist lives

One policy, five places to set it. Pick the one that already manages your Edge browsers; mixing several makes conflicts hard to trace.

Group Policy

Administrative Templates > Microsoft Edge > Extensions > Control which extensions cannot be installed

Needs the Edge administrative templates (MSEdge.admx) in your central store. Supported from Edge 77.

Registry

SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallBlocklist under HKLM, with string values named 1, 2, 3 and so on.

Useful for machines outside your domain or for a quick test.

Intune

Devices > Configuration > Create, platform Windows 10 and later, profile type Settings catalog. Search the settings picker for Control which extensions cannot be installed.

More Intune routes for AI are in blocking AI with Intune.

Edge management service

Microsoft 365 admin center > Settings > Microsoft Edge > Configuration policies. Extensions get their own step in the policy wizard.

Applies to users signed in to Edge with a work account.

macOS

Preference domain com.microsoft.Edge, key ExtensionInstallBlocklist as an array of strings.

Deploy as a Preference file profile in Intune or a Custom Settings payload in Jamf. See our Jamf guide for the profile steps.

Set the Edge blocklist with Group Policy

This is the most common route on domain-joined Windows. The steps are the same in local policy for a single machine.

  1. Load the templates

    Download the Edge policy templates and copy MSEdge.admx and its language file into your central store, so the Microsoft Edge folder appears in the editor.

  2. Open the Extensions folder

    In the Group Policy Management Editor go to Computer Configuration > Policies > Administrative Templates > Microsoft Edge > Extensions.

  3. Enable the blocklist

    Open Control which extensions cannot be installed, select Enabled, then Show. Enter one extension ID per row: both the Edge Add-ons ID and the Chrome Web Store ID of each AI extension.

  4. Decide on block all

    For the strict model enter * as the only row and list approved IDs in Allow specific extensions to be installed. Our allowlist guide explains the logic, which Edge shares with Chrome.

  5. Stop external installs

    Enable Blocks external extensions from being installed, so software that drops an extension on the machine cannot add one. This one needs a browser restart.

  6. Check on a test machine

    Run gpupdate, open edge://policy and confirm ExtensionInstallBlocklist lists your IDs. Then try to add a blocked extension from both stores.

The same policy names work for Chrome under the Google folder. If you manage both browsers, our Chrome Group Policy guide shows the Chrome side.

Edge extension blocklist in the registry and on Mac

Both examples block the Edge and Chrome copies of the same agent extension, plus one Chrome-only agent. Replace them with the full list from your download.

edge-blocklist.reg
Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallBlocklist] "1"="kgkeacnfccpmbaiklacgpnlheandnlmi" "2"="mokiolnliafiddobcgmmnmhbmimpccon" "3"="cecngibhkljoiafhjfmcgbmikfogdiko"
com.microsoft.Edge (key and value only)
<key>ExtensionInstallBlocklist</key> <array> <string>kgkeacnfccpmbaiklacgpnlheandnlmi</string> <string>mokiolnliafiddobcgmmnmhbmimpccon</string> <string>cecngibhkljoiafhjfmcgbmikfogdiko</string> </array>

The third ID is Manus AI Browser Operator from the Chrome Web Store, graded High in our list. It shows why Chrome IDs belong in an Edge policy: Edge can install it once the other stores toggle is on.

Use the Edge management service in the Microsoft 365 admin center

If your users sign in to Edge with work accounts, Microsoft's cloud console can push the same extension rules without Group Policy. It also lets users request extensions you can approve or deny.

  1. Sign in to the Microsoft 365 admin center and go to Settings > Microsoft Edge.
  2. Open the Configuration policies tab and select Create policy.
  3. On Basics, name the policy, choose the platforms and pick a Cloud or Intune policy type.
  4. On Extensions, set the Default extension settings for all extensions, for example blocked.
  5. Under Managed extensions, select Add extension for each approved Edge add-on, sidebar app or external extension.
  6. Assign the policy to Microsoft Entra groups and finish with Review and create.

Good to know

  • Needs Edge 115.0.1901.7 or later and the Microsoft Edge Administrator role
  • Settings reach users who are signed in to Edge with their work account
  • Extension requests are a Cloud policy feature
  • Intune type policies made here also show up in Intune under Devices > Configuration, and edits sync both ways
  • A Group Policy or MDM setting on the device wins over the cloud setting on conflict
  • Not offered to GCC customers at the time of writing; check the current admin center

ExtensionSettings recipes for AI extensions in Edge

Edge's Configure extension management settings policy takes one JSON string. It overrides the older list policies and can do things they cannot. These recipes cover the jobs admins ask about most.

Block the Chrome Web Store as a source

Block the Chrome Web Store's update URL with an update_url key and installation_mode blocked. Extensions you still list on the allow list or force list keep working.

This is the cleanest answer to the other-stores toggle, because the toggle no longer matters. Copy the exact update URL from Microsoft's ExtensionSettings documentation.

Block named AI extensions with a message
{"ajdioenfpgabnjlclgckbbnjjhdnjkhn,imbddededgmcgfhfpcjmijokokekbkal": {"installation_mode": "blocked", "blocked_install_message": "AI agent extensions need IT approval."}}

One key can hold several comma-separated IDs, here the Edge and Chrome copies of Nanobrowser. Users see your message instead of a bare error.

Block everything, allow approved tools
{"*": {"installation_mode": "blocked", "blocked_install_message": "Ask IT for approved extensions."}, "approved_edge_extension_id": {"installation_mode": "allowed"}}

The * entry blocks every extension from both stores. Each approved ID gets its own entry with installation_mode allowed. Replace the placeholder with real IDs from your approved list, and keep this policy for the groups that need the strict model.

Keep every extension off sensitive apps
{"*": {"runtime_blocked_hosts": ["*://*.finance.yourcompany.example", "*://hr.yourcompany.example"]}}

runtime_blocked_hosts stops extensions from reading or changing the listed sites. It does not stop installs, so pair it with the blocklist.

Block risky permissions
{"*": {"blocked_permissions": ["debugger"]}}

An installed extension that needs a blocked permission does not run. It is disabled, not removed. Test this in a small group first, because some approved tools may need the same permission.

Stop sidebar apps opening on their own

Set sidebar_auto_open_blocked to true on an extension's entry, and its sidebar app will not open automatically. Use it for approved assistants that you want people to open on purpose.

Write the JSON on one line for Group Policy, or let Intune and the Edge management service build it for you. Validate it before you deploy: an invalid JSON string shows as an error on edge://policy and is not applied.

What to block, monitor and allow in Edge

Use the risk grade in our files to set the line, then keep the Edge rules in step with your Chrome rules.

ActionWhat it coversEdge setting
BlockAgent extensions that operate the browser, and anything graded High or SevereControl which extensions cannot be installed, with Edge and Chrome IDs
BlockExtensions dropped by other softwareBlocks external extensions from being installed
Block or limitChrome Web Store installs in generalConfigure extension management settings with the store's update_url
MonitorModerate graded assistants and meeting toolsYour extension inventory and traffic to AI agent domains
AllowLicensed AI tools for named groupsAllow specific extensions to be installed, scoped by group
Allow, fencedApproved tools near sensitive dataruntime_blocked_hosts for finance, HR and admin portals

Extension rules do not cover AI agents that run as websites. Block their domains too, with your firewall or with Microsoft Defender for Endpoint.

Check that the Edge blocklist works

Run these checks on a test machine after every change, and again after each daily list update for the first week.

edge://policy

ExtensionInstallBlocklist shows your IDs with status OK. Use Reload policies after a change.

Edge Add-ons install

Adding a blocked extension from Edge Add-ons fails with your message or the standard block notice.

Chrome Web Store install

With the other-stores toggle on, the Chrome copy of the same extension is blocked too.

edge://extensions

An AI extension that was installed before the policy now shows as disabled and cannot be turned on.

Approved tools

Extensions on your allow list still install, update and run on the sites they need.

Copilot

Copilot behaves as your Copilot policies say. The blocklist does not change it.

Copilot is built into Edge, not an extension. From Edge 149 the Microsoft365CopilotChatIconEnabled policy controls whether Copilot shows in the toolbar. For Copilot Mode and related settings see disabling Copilot Mode in Edge.

The AI Agent Blocklist

One file for Edge, with both stores covered

Typing IDs from two stores by hand is how gaps appear. Our Edge file lists the Edge Add-ons and Chrome Web Store IDs of every AI agent and assistant extension we track, and it changes every day as new ones appear.

Edge Add-ons IDs
Chrome Web Store IDs
Firefox add-on IDs
Risk grade per entry
Group Policy, Intune and plist files
2,600+ AI agent domains
CSV and JSON with all columns
Access within one business day

Ask 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

We use your details only to answer you. No newsletters.

Edge extension blocklist questions

What is the Edge extension blocklist policy called?

The policy is ExtensionInstallBlocklist. In Group Policy it is called Control which extensions cannot be installed, under Administrative Templates > Microsoft Edge > Extensions.

In the registry it is the subkey SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallBlocklist with values named 1, 2, 3.

Does the Edge blocklist block Chrome Web Store extensions?

Yes, if you add their Chrome Web Store IDs. Edge can install Chrome Web Store extensions, and those keep their Chrome IDs.

Put both the Edge Add-ons ID and the Chrome Web Store ID of each AI extension on the list, or block the Chrome Web Store as a source with the ExtensionSettings policy.

Why does the same extension have different IDs in Edge and Chrome?

Each store publishes its own package of the extension, and the ID comes from that package. So an AI extension listed in both Edge Add-ons and the Chrome Web Store usually has two IDs, and a blocklist needs both.

How do I block all extensions in Edge except approved ones?

Set Control which extensions cannot be installed to * and list the approved IDs in Allow specific extensions to be installed. Only packed, signed extensions on the allow list can then be installed.

Extensions you force install with Control which extensions are installed silently are also allowed.

Does blocking an extension in Edge uninstall it?

No. An installed extension that you add to the blocklist is disabled and the user cannot enable it again, but it stays installed. If you later remove it from the blocklist, Edge enables it again automatically.

How do I find an extension ID in Edge?

For a store listing, the ID is the last part of the extension's page address in Edge Add-ons or the Chrome Web Store. On a device, open edge://extensions, turn on Developer mode on that page and read the ID under each extension.

Does the extension blocklist turn off Copilot in Edge?

No. Copilot is built into Edge and is not an extension. It has its own Edge policies; from Edge 149 the Microsoft365CopilotChatIconEnabled policy controls whether Copilot shows in the toolbar.

Microsoft, Microsoft Edge, Microsoft 365, Microsoft Intune, Microsoft Defender, Microsoft Entra, Copilot and Windows are trademarks of Microsoft Corporation. Google, Chrome and Chrome Web Store are trademarks of Google LLC.

Firefox is a trademark of the Mozilla Foundation. Apple, Mac and macOS are trademarks of Apple Inc. Jamf is a trademark of JAMF Software, LLC. Sider, Nanobrowser, Read AI and Manus 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.