Description: This policy allows administrators to silently install specific extensions in Microsoft Edge without user interaction. The listed extension (by ID) is automatically installed and cannot be remove. Configure the list of force-installed apps and extensionsd or disabled by users. All required permissions are granted automatically, including access to sensitive APIs like enterprise.deviceAttributes and enterprise.platformKeys. If the extension is removed from the list, it is automatically uninstalled. For non-domain-joined Windows devices, only extensions from the Microsoft Edge Add-ons store can be force-installed.

Why It's Important: This setting ensures that a specific extension is automatically installed and locked in place—so users don’t have to install it themselves and can’t remove it. It’s like giving every employee a secure, pre-approved tool that’s always available and ready to use. SHIELD uses this policy to guarantee that essential extensions—like security or productivity tools—are consistently deployed across all devices, helping maintain compliance and reduce support issues.

Learn More

Description: List specific extensions that users can NOT install in Microsoft Edge. When you deploy this policy, any extensions on this list that were previously installed will be disabled, and the user won't be able to enable them. If you remove an item from the list of blocked extensions, that extension is automatically re-enabled anywhere it was previously installed. Use "*" to block all extensions that aren't explicitly listed in the allow list. If you don't configure this policy, users can install any extension in Microsoft Edge.

Example value: extension_id1 extension_id2.

Why It's Important: This setting helps keep users safe by blocking risky or unwanted browser extensions. It prevents people from installing tools that could slow down their computer, show ads, or even steal data. SHIELD enables this policy to make sure only trusted extensions are allowed—like having a security guard that checks every tool before it enters the workspace. It’s a smart way to prevent problems before they happen.

Learn More

Description: Sets the ProcessExtensionPointDisablePolicy on Microsoft Edge's browser process to block code injection from legacy third party applications. If you enable or don't configure this policy, the ProcessExtensionPointDisablePolicy is applied to block legacy extension points in the browser process. If you disable this policy, the ProcessExtensionPointDisablePolicy is not applied to block legacy extension points in the browser process. This has a detrimental effect on Microsoft Edge's security and stability as unknown and potentially hostile code can load inside Microsoft Edge's browser process. Only turn off the policy if there are compatibility issues with third-party software that must run inside Microsoft Edge's browser process.

Why It's Important: This policy blocks legacy third-party applications from injecting code into Microsoft Edge’s browser process. It strengthens security and stability by preventing untrusted or outdated software from interfering with browser operations or introducing vulnerabilities.

Learn More

Description: Allows users to import extensions from another browser into Microsoft Edge. If you enable this policy, the Extensions check box is automatically selected in the Import browser data dialog box. If you disable this policy, extensions aren't imported at first run, and users can't import them manually. If you don't configure this policy, extensions are imported at first run, and users can choose whether to import them manually during later browsing sessions. You can also set this policy as a recommendation. This means that Microsoft Edge imports extensions on first run, but users can select or clear the extensions option during manual import. Note: This policy currently only supports importing from Google Chrome (on Windows 7, 8, and 10 and on macOS).

Why It's Important: This policy blocks Microsoft Edge from importing extensions from other browsers. It helps prevent potentially unverified or non-compliant extensions from being transferred into managed environments, reducing the risk of security vulnerabilities and maintaining control over browser add-ons.

Learn More

Description: Control the installation of external extensions. If you enable this setting, external extensions are blocked from being installed. If you disable this setting or leave it unset, external extensions are allowed to be installed.

Why It's Important: This policy blocks extensions that are installed from outside the Microsoft Edge Add-ons Store. It helps prevent unverified or malicious extensions from being added, protecting users and devices from data theft, tracking, or unauthorized code execution.

Learn More

Description: This policy blocks specific extension IDs from being installed in Microsoft Edge.

Why It's Important: This setting helps keep users safe and focused by blocking specific browser extensions that may be risky, distracting, or not approved by your organization. It’s like preventing employees from installing unauthorized software on their work computers. SHIELD uses this policy to ensure only trusted tools are used in the browser—helping maintain security, compliance, and productivity across all devices.

Learn More

Description: [Coming soon]

Why It's Important: This setting makes sure that important browser extensions—like security tools or productivity apps—are automatically installed and locked in place. Users don’t have to do anything, and they can’t remove or disable these extensions. SHIELD enables this policy to ensure every device has the right tools installed and working securely. It’s like giving every employee a toolkit they can’t lose or break—ready to go, every time they open the browser.

Learn More