How to Completely Disable ‘Web Bluetooth API’ via Group Policy in Microsoft Edge

The Web Bluetooth API allows web applications running in Microsoft Edge to discover, pair with, and interact directly with Bluetooth Low Energy (BLE) devices in the physical vicinity of the workstation. While innovative for specialized IoT management interfaces or consumer wearables, Web Bluetooth introduces an unacceptably high operational security (OPSEC) risk in secure enterprise, military, or compliance-bound environments. If left enabled, a compromised or malicious website could silently scan the local RF environment, attempt unauthorized pairings with secure facility infrastructure, or bridge an air-gap by establishing a covert communication channel over BLE protocols.

This guide explains how to completely disable the ‘Web Bluetooth API’ via Group Policy in Microsoft Edge, enforcing a strict zero-trust model where the browser is cryptographically prevented from accessing the host operating system’s Bluetooth hardware stack.

Disable Web Bluetooth API via Group Policy

To enforce a strict block that permanently severs the browser’s ability to communicate with the OS Bluetooth APIs globally, we must deploy an administrative template. Note that this requires Windows 11 Pro, Enterprise, or Education editions.

1. Log into Windows 11 with an Administrator account.
2. Press the Windows Key + R to open the Run dialogue box.
3. Type gpedit.msc and press Enter to launch the Local Group Policy Editor.
4. In the left-hand navigation pane, strictly follow this exact path:

   Computer Configuration > Administrative Templates > Microsoft Edge > Content settings

5. In the right-hand pane, locate the policy named Default Web Bluetooth guard setting.
6. Double-click the policy to open its configuration window.
7. Select the radio button next to Enabled (Note: We must explicitly enable this policy to assert a specific, restrictive state).
8. In the Options pane below, click the drop-down menu and select 2 – Do not allow any site to request access to Bluetooth devices via the Web Bluetooth API. (By explicitly configuring this policy to “2”, we instruct the Edge rendering and security engines to automatically reject all `navigator.bluetooth.requestDevice()` calls, bypassing the user prompt and denying the hardware interaction unconditionally).
9. Click Apply, then click OK.

Verify the Configuration Lockdown

Group Policy changes require the browser to read the registry upon its next launch.

Close all active instances of Microsoft Edge. To force the policy update immediately across the OS, open Command Prompt as Administrator and run gpupdate /force. To verify the restriction is active, launch Microsoft Edge and navigate to edge://settings/content/bluetooth (or find “Bluetooth devices” under Site Permissions). The toggle dictating whether sites can ask to connect to Bluetooth devices will be locked in the “Off” position (greyed out), accompanied by a briefcase icon and text stating “This setting is managed by your organization.” The browser is now cryptographically bound to a strict, non-transmitting RF state.