How to Completely Disable ‘Remote Debugging’ via Group Policy in Microsoft Edge

Remote debugging in Microsoft Edge allows developers to inspect and debug web applications running on the browser from a separate device or tool. While this is an essential feature for developers, leaving remote debugging enabled in production or enterprise environments poses a severe security risk, potentially allowing unauthorized access to browser sessions. This guide explains how to completely disable Remote Debugging via Group Policy.

Prerequisites

Ensure you have administrative privileges on the Windows machine and that the latest Microsoft Edge Administrative Templates are installed in your Group Policy Central Store.

Disable Remote Debugging

Open the Group Policy Editor

Press the Windows Key + R, type gpedit.msc, and hit Enter to launch the Local Group Policy Editor.

Navigate to Edge Policies

In the left pane, navigate to Computer Configuration > Administrative Templates > Microsoft Edge.

Modify the Remote Debugging Policy

Locate the policy named Enable Remote Debugging. Double-click it.

Disable the Feature

Set the policy state to Disabled. Click Apply and then OK to save the changes.

Apply the Policy

Open an elevated Command Prompt and execute gpupdate /force to ensure the Group Policy changes are applied immediately.

Verify the Configuration

Open Microsoft Edge and navigate to edge://policy. Verify that the RemoteDebuggingAllowed policy is listed and its value is set to false. This confirms that remote debugging connections are strictly prohibited by the browser.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.