Define a list of protocols that can not be silently blocked by anti-flood protection
Explanation
Allows you to create a list of protocols and an associated list of allowed origin patterns, for each protocol. These origins aren't silently blocked from launching an external application by anti-flood protection. The trailing separator shouldn't be included when listing the protocol. For example, list "skype" instead of "skype:" or "skype://".
If you configure this policy, a protocol is only permitted to bypass being silently blocked by anti-flood protection if:
- the protocol is listed
- the origin of the site trying to launch the protocol matches one of the origin patterns in that protocol's allowed_origins list.
If either condition is false, anti-flood protection protection blocks the external protocol launch.
If you don't configure this policy, no protocols can bypass being silently blocked.
The origin-matching patterns use a similar format to those patterns for the 'URLBlocklist' (Block access to a list of URLs) policy, which are documented at https://go.microsoft.com/fwlink/?linkid=2095322.
However, origin-matching patterns for this policy can't contain "/path" or "@query" elements. Any pattern that contains a "/path" or "@query" element is ignored.
This policy doesn't work as expected with file://* wildcards.
Example value:
[
{
"allowed_origins": [
"example.com",
"http://www.example.com:8080"
],
"protocol": "spotify"
},
{
"allowed_origins": [
"https://example.com",
"https://.mail.example.com"
],
"protocol": "msteams"
},
{
"allowed_origins": [
"*"
],
"protocol": "msoutlook"
}
]
Registry
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\EdgeHKEY_CURRENT_USER\Software\Policies\Microsoft\Edge- Value name
- not defined in the ADMX
Enable / disable values: not defined in the ADMX (see the options below).
PowerShell
PowerShell commands that write to the registry what the policy would write. Values in angle brackets (<…>) must be replaced.
Writing directly to the registry bypasses Group Policy: if a GPO manages this value, it will be rewritten at the next gpupdate; otherwise the value stays in place (the "tattooing" effect). Prefer a GPO or, locally, LGPO.exe. Run PowerShell as administrator for HKLM. Some policies need a restart or gpupdate /force.
Computer (HKLM)
Enable
# Enable: msedge/DoNotSilentlyBlockProtocolsFromOrigins
$k = 'HKLM:\Software\Policies\Microsoft\Edge'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
# Define a list of protocols that can not be silently blocked by anti-flood protection
Set-ItemProperty -Path $k -Name 'DoNotSilentlyBlockProtocolsFromOrigins' -Value '<value>' -Type StringDisable
# Disable: msedge/DoNotSilentlyBlockProtocolsFromOrigins
# No value is written in the "Disabled" state (nothing defined in the ADMX)Revert to "Not configured"
# Revert to "Not configured": msedge/DoNotSilentlyBlockProtocolsFromOrigins
$k = 'HKLM:\Software\Policies\Microsoft\Edge'
Remove-ItemProperty -Path $k -Name 'DoNotSilentlyBlockProtocolsFromOrigins' -ErrorAction SilentlyContinueUser (HKCU)
Enable
Disable
Revert to "Not configured"
Options (1)
| Label | Control | Registry value | REG type | Constraints / details |
|---|---|---|---|---|
| Define a list of protocols that can not be silently blocked by anti-flood protectionDoNotSilentlyBlockProtocolsFromOrigins | Text boxtext | DoNotSilentlyBlockProtocolsFromOrigins | REG_SZ | Max length: 1000000 |
Application
Microsoft Edge (+ Edge Update, WebView2) (Microsoft) — November 2026 templates
Official templates downloaded on November 12, 2026.