Forum Discussion

Iron Contributor

Mar 02, 2020

Solved

ExternalProtocolDialogShowAlwaysOpenCheckbox policy no longer works in Edge Dev and Canary

Hi there, We have the ExternalProtocolDialogShowAlwaysOpenCheckbox policy enabled so that folks can have the browser remember their preference for frequently-used protocol handler links. It looks...

todd_sahl
Mar 30, 2020
AndrewSAIF

Hi Andrew,
This policy to show the checkbox was recently restricted to only work from secure (i.e. https) pages. I suspect that you are expecting to see the checkbox from a non-secure page and that it is not showing up.

Can you confirm?

This change was made as part of a broader set of changes to the opt-out checkbox, including:
The checkbox now applies per-origin. So if you select the checkbox because you tried to launch skype: from sharepoint.com, that combination will skip the prompt in the future, but other origins will still see the prompt when launching skype: until opted out.
The checkbox will be turned on by default for all users in an upcoming release, so that the group policy is no longer needed. It will continue to be possible to ensure the checkbox is never shown by explicitly disabling the policy though.
Todd

AndrewSAIF

Iron Contributor

Jun 19, 2020

RichardStantonPropsoft

Hm, maybe I'm missing something, but the example I gave (skype://) still shows me a checkbox with this policy enabled on Edge Stable 81 and still does not show me a checkbox on Edge Canary 85.

AndrewSAIF

Iron Contributor

Jul 17, 2020

Deleted todd_sahl

It looks like a solution to this problem is to add the URLAllowlist policy, then add your handler to that:

https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-policies#urlallowlist

Use this format:

handlername://*

Hope this helps someone. This definitely wasn't clear from the description of the policy. Maybe this isn't even intended behavior, but I'm sure glad it works.

Andrew

RichardStantonPropsoft
Copper Contributor
Jul 21, 2020
AndrewSAIF

Thank you Andrew for being able to offer the fix that Microsoft couldn't.
This works perfectly, and will allow us to finally migrate our customers' intranets from a mix of IE11 and Chrome to Microsoft Edge v84 without the constant prompts.

This puts Microsoft back in the game, brilliant.
ngiacom
Copper Contributor
Jul 21, 2020
It worked fine for me, thank you!
Anonymous
Jul 17, 2020
AndrewSAIF

Thank you, all! We'll look into this.

Fawkes (they/them)
Program Manager & Community Manager - Microsoft Edge
- AndrewSAIF
  Iron Contributor
  Jul 30, 2020
  
  It looks like there will be a dedicated policy for this as of v85:
  
  https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-policies#autolaunchprotocolsfromorigins