SOLVED

ExternalProtocolDialogShowAlwaysOpenCheckbox policy no longer works in Edge Dev and Canary

%3CLINGO-SUB%20id%3D%22lingo-sub-1205247%22%20slang%3D%22en-US%22%3EExternalProtocolDialogShowAlwaysOpenCheckbox%20policy%20no%20longer%20works%20in%20Edge%20Dev%20and%20Canary%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1205247%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20there%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20the%26nbsp%3BExternalProtocolDialogShowAlwaysOpenCheckbox%20policy%20enabled%20so%20that%20folks%20can%20have%20the%20browser%20remember%20their%20preference%20for%20frequently-used%20protocol%20handler%20links.%20It%20looks%20like%20this%20policy%20still%20works%20in%20Edge%20Beta%26nbsp%3B%3CSPAN%3E81.0.416.20%2C%20but%20stopped%20working%20in%20Edge%20Dev%26nbsp%3B82.0.432.3%20and%20later.%20The%20checkbox%20is%20simply%20not%20shown%20in%20the%20later%20versions.%20I%20tested%20using%20skype%3A%2F%2F%20and%20another%20application%20we%20use%20in-house.%20The%20policy%20is%20visible%20in%20edge%3A%2F%2Fpolicy%2C%20but%20it%20is%20ignored%20for%20whatever%20reason.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThanks!%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EAndrew%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1239856%22%20slang%3D%22en-US%22%3ERe%3A%20ExternalProtocolDialogShowAlwaysOpenCheckbox%20policy%20no%20longer%20works%20in%20Edge%20Dev%20and%20Canary%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1239856%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F458117%22%20target%3D%22_blank%22%3E%40AndrewSAIF%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EStill%20broken%20in%20Canary%26nbsp%3B%3CSPAN%3E82.0.458.0.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAndrew%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1265247%22%20slang%3D%22en-US%22%3ERe%3A%20ExternalProtocolDialogShowAlwaysOpenCheckbox%20policy%20no%20longer%20works%20in%20Edge%20Dev%20and%20Canary%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1265247%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F458117%22%20target%3D%22_blank%22%3E%40AndrewSAIF%3C%2FA%3E%26nbsp%3BThanks%20for%20reaching%20out%20and%20letting%20us%20know.%20We're%20sorry%20to%20hear%20that%20it%20isn't%20working!%20We%20just%20pushed%20%3CSPAN%3E83.0.470.0%3C%2FSPAN%3E%3CSPAN%3E%26nbsp%3Bto%20Canary%3B%20are%20you%20still%20seeing%20this%20behavior%20there%3F%20If%20so%2C%20let%20us%20know%20and%20we'll%20loop%20in%20the%20GPO%20team.%20And%20in%20the%20meantime%2C%20can%20you%20please%20submit%20detailed%20feedback%20and%20diagnostic%20data%20through%20the%20browser%2C%20if%20you%20haven't%20yet%3F%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%3CI%3EFawkes%20(they%2Fthem)Project%20%26amp%3B%20Community%20Manager%20-%20Microsoft%20Edge%3CI%3E%3C%2FI%3E%3C%2FI%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1265888%22%20slang%3D%22en-US%22%3ERe%3A%20ExternalProtocolDialogShowAlwaysOpenCheckbox%20policy%20no%20longer%20works%20in%20Edge%20Dev%20and%20Canary%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1265888%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F484598%22%20target%3D%22_blank%22%3E%40fawkes%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%20Fawkes%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20updated%20Canary%20to%20the%20latest%20version%20and%20got%20the%20same%20result.%20It%20is%20easy%20to%20duplicate%20this%20behavior%20on%20a%20machine%20that%20has%20Office%20installed%20if%20you%20set%20the%20policy%2C%20then%20type%20skype%3A%2F%2F%20into%20the%20address%20bar%20and%20press%20enter.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22AndrewSAIF_0-1585598044532.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F180701i53E37D1FA4565542%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22AndrewSAIF_0-1585598044532.png%22%20alt%3D%22AndrewSAIF_0-1585598044532.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20the%20feedback%20feature%20disabled%20in%20my%20group%20policy%2C%20but%20if%20that%20is%20a%20better%20way%20to%20report%20issues%20I%20can%20set%20up%20a%20test%20machine%20to%20be%20excluded.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks!%3C%2FP%3E%3CP%3EAndrew%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1266071%22%20slang%3D%22en-US%22%3ERe%3A%20ExternalProtocolDialogShowAlwaysOpenCheckbox%20policy%20no%20longer%20works%20in%20Edge%20Dev%20and%20Canary%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1266071%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F458117%22%20target%3D%22_blank%22%3E%40AndrewSAIF%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%20Andrew%2C%3C%2FP%3E%3CP%3EThis%20policy%20to%20show%20the%20checkbox%20was%20recently%20restricted%20to%20only%20work%20from%20secure%20(i.e.%20https)%20pages.%26nbsp%3B%20I%20suspect%20that%20you%20are%20expecting%20to%20see%20the%20checkbox%20from%20a%20non-secure%20page%20and%20that%20it%20is%20not%20showing%20up.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20you%20confirm%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20change%20was%20made%20as%20part%20of%20a%20broader%20set%20of%20changes%20to%20the%20opt-out%20checkbox%2C%20including%3A%3C%2FP%3E%3CUL%3E%3CLI%3EThe%20checkbox%20now%20applies%20per-origin.%26nbsp%3B%20So%20if%20you%20select%20the%20checkbox%20because%20you%20tried%20to%20launch%20skype%3A%20from%20sharepoint.com%2C%20that%20combination%20will%20skip%20the%20prompt%20in%20the%20future%2C%20but%20other%20origins%20will%20still%20see%20the%20prompt%20when%20launching%20skype%3A%20until%20opted%20out.%3C%2FLI%3E%3CLI%3EThe%20checkbox%20will%20be%20turned%20on%20by%20default%20for%20all%20users%20in%20an%20upcoming%20release%2C%20so%20that%20the%20group%20policy%20is%20no%20longer%20needed.%26nbsp%3B%20It%20will%20continue%20to%20be%20possible%20to%20ensure%20the%20checkbox%20is%20never%20shown%20by%20explicitly%20disabling%20the%20policy%20though.%3C%2FLI%3E%3C%2FUL%3E%3CP%3ETodd%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1279207%22%20slang%3D%22en-US%22%3ERe%3A%20ExternalProtocolDialogShowAlwaysOpenCheckbox%20policy%20no%20longer%20works%20in%20Edge%20Dev%20and%20Canary%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1279207%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%20Todd%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20the%20quick%20reply.%20Yes%2C%20I%20am%20expecting%20to%20see%20the%20checkbox%20from%20a%20non-https%20site.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20reason%20this%20policy%20was%20useful%20to%20me%20is%20because%20we%20have%20web%20apps%20on%20an%20http%20intranet%20site%20that%20contain%20protocol%20handler%20links%20to%20open%20a%20separate%20application.%20For%20various%20reasons%2C%20we%20cannot%20easily%20make%20these%20sites%20HTTPS.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20this%20use%20case%2C%20users%20are%20clicking%20several%20of%20these%20links%20in%20a%20short%20timeframe.%20The%20popup%20for%20confirmation%20becomes%20very%20obtrusive.%20I%20was%20excited%20to%20have%20this%20policy%20since%20the%20only%20other%20solution%20at%20the%20time%20was%20to%20manually%20edit%20the%20preferences%20file%20(or%20script%20it).%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThere%20was%20a%20backlash%20when%20this%20checkbox%20was%20removed%20from%20Chrome%20from%20enterprise%20users%2C%20and%20I%20thought%20this%20policy%20was%20a%20response%20to%20that%20backlash.%20I%20don't%20think%20my%20use%20case%20is%20uncommon%20and%20I%20suspect%20this%20will%20be%20a%20big%20deal%20for%20several%20organizations.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDo%20you%20have%20a%20timeline%20or%20version%20target%20for%20when%20the%20checkbox%20is%20available%20by%20default%2C%20and%20when%20this%20happens%20will%20the%20checkbox%20still%20only%20appear%20for%20HTTPS%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F385298%22%20target%3D%22_blank%22%3E%40todd_sahl%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1297015%22%20slang%3D%22en-US%22%3ERe%3A%20ExternalProtocolDialogShowAlwaysOpenCheckbox%20policy%20no%20longer%20works%20in%20Edge%20Dev%20and%20Canary%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1297015%22%20slang%3D%22en-US%22%3E%3CP%3ENot%20the%20solution%20I%20prefer%2C%20but%20it%20looks%20like%20as%20a%20workaround%20I%20can%20just%20throw%20the%20page%20on%20my%20IE%20Mode%20list.%20No%20popups%20at%20all.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAndrew%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1443761%22%20slang%3D%22en-US%22%3ERe%3A%20ExternalProtocolDialogShowAlwaysOpenCheckbox%20policy%20no%20longer%20works%20in%20Edge%20Dev%20and%20Canary%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1443761%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F484598%22%20target%3D%22_blank%22%3E%40fawkes%3C%2FA%3E%26nbsp%3BI%20was%20also%20using%20this%20on%20an%20intranet%20website%20served%20over%20http.%20With%20the%20latest%20update%20to%20edge%20chromium%2C%20it%20suddenly%20stopped%20working.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EAny%20chance%20there's%20an%20override%20for%20certain%20domains%20to%20be%20able%20to%20get%20the%20remember%20checkbox%20in%20conjunction%20with%20%22Enable%20remembering%20protocol%20launch%20prompting%20preferences%22%20being%20enabled%20in%20edge%3A%2F%2Fflags%3F%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EIt%20looks%20like%20edge%20chromium%20no%20longer%20honors%20internet%20options%20in%20control%20panel%20(which%20makes%20sense)%20but%20I'd%20like%20a%20per-domain%20override%20as%20I%20suddenly%20no%20longer%20have%20the%20functionality%20I%20had%2C%20even%20though%20it's%20still%20in%20edge.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1456811%22%20slang%3D%22en-US%22%3ERe%3A%20ExternalProtocolDialogShowAlwaysOpenCheckbox%20policy%20no%20longer%20works%20in%20Edge%20Dev%20and%20Canary%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1456811%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F385298%22%20target%3D%22_blank%22%3E%40todd_sahl%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F484598%22%20target%3D%22_blank%22%3E%40fawkes%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3EHi%20there.%20Is%20there%20any%20update%20on%20the%20status%20of%20this%20policy%3F%20The%20behavior%20appears%20to%20be%20the%20same%20still%20in%20v85.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1463835%22%20slang%3D%22en-US%22%3ERe%3A%20ExternalProtocolDialogShowAlwaysOpenCheckbox%20policy%20no%20longer%20works%20in%20Edge%20Dev%20and%20Canary%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1463835%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F458117%22%20target%3D%22_blank%22%3E%40AndrewSAIF%3C%2FA%3E%26nbsp%3BOur%20customers%20are%20in%20a%20similar%20position%2C%20their%20intranet%20has%20specific%20rules%20which%20mean%20they've%20twice%20tried%20to%20migrate%20from%20IE11%20to%20Edge%20but%20had%20to%20revert%20(the%20most%20recent%20to%20Chrome).%3CBR%20%2F%3EI%20was%20hoping%20with%20the%20Chrome%20based%20version%20of%20Edge%20that%20it%20would%20honour%20ExternalProtocolDialogShowAlwaysOpenCheckbox%20in%20either%20Chrome%20or%20Edge's%20reg%20keys.%3CBR%20%2F%3EThe%20annoyance%20to%20the%20customer%20of%20having%20to%20click%20the%20popup%20confirmation%20each%20time%20is%20a%20deal-breaker%2C%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1466488%22%20slang%3D%22en-US%22%3ERe%3A%20ExternalProtocolDialogShowAlwaysOpenCheckbox%20policy%20no%20longer%20works%20in%20Edge%20Dev%20and%20Canary%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1466488%22%20slang%3D%22en-US%22%3EHi%20Todd%2C%3CBR%20%2F%3E%3CBR%20%2F%3EThis%20restriction%20ruins%20intranet%20app%20experience.%20Will%20there%20be%20a%20change%20in%20this%20restriction%3F%3CBR%20%2F%3E%3CBR%20%2F%3EOmer%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1476591%22%20slang%3D%22en-US%22%3ERe%3A%20ExternalProtocolDialogShowAlwaysOpenCheckbox%20policy%20no%20longer%20works%20in%20Edge%20Dev%20and%20Canary%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1476591%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F458117%22%20target%3D%22_blank%22%3E%40AndrewSAIF%3C%2FA%3E%26nbsp%3B%20%26nbsp%3BCould%20be%20good%20news%20on%20the%20horizon.%3C%2FP%3E%3CP%3EJust%20looked%20on%20the%20beta%20v84%20version%20of%20Edge%2C%20and%20the%20documentation%20says%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%22As%20of%20Microsoft%20Edge%2084%2C%20if%20you%20don't%20configure%20this%20policy%2C%20when%20an%20external%20protocol%20confirmation%20prompt%20is%20shown%2C%20the%20user%20can%20select%20%22Always%20allow%22%20to%20skip%20all%20future%20confirmation%20prompts%20for%20the%20protocol%20on%20this%20site%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EHopefully%20v84%20of%20Edge%20will%20honour%20the%20setting%2C%20same%20as%20Chrome%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployedge%2Fmicrosoft-edge-policies%23externalprotocoldialogshowalwaysopencheckbox%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployedge%2Fmicrosoft-edge-policies%23externalprotocoldialogshowalwaysopencheckbox%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1477950%22%20slang%3D%22en-US%22%3ERe%3A%20ExternalProtocolDialogShowAlwaysOpenCheckbox%20policy%20no%20longer%20works%20in%20Edge%20Dev%20and%20Canary%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1477950%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F699883%22%20target%3D%22_blank%22%3E%40RichardStantonPropsoft%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHm%2C%20maybe%20I'm%20missing%20something%2C%20but%20the%20example%20I%20gave%20(skype%3A%2F%2F)%20still%20shows%20me%20a%20checkbox%20with%20this%20policy%20enabled%20on%20Edge%20Stable%2081%20and%20still%20does%20not%20show%20me%20a%20checkbox%20on%20Edge%20Canary%2085.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1480318%22%20slang%3D%22en-US%22%3ERe%3A%20ExternalProtocolDialogShowAlwaysOpenCheckbox%20policy%20no%20longer%20works%20in%20Edge%20Dev%20and%20Canary%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1480318%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F458117%22%20target%3D%22_blank%22%3E%40AndrewSAIF%3C%2FA%3E%26nbsp%3B%20Ah%20sorry%2C%20just%20tried%20the%20v84%20beta%20and%20you're%20right%20-%20Microsoft%20still%20aren't%20complying%20with%20their%20own%20documentation.%3C%2FP%3E%3CP%3ENot%20reassuring%20that%20you're%20on%20an%20even%20newer%20beta%20than%20me%2C%20and%20that%20version%20is%20also%20incorrect.%3C%2FP%3E%3CP%3EHopefully%20Microsoft%20will%20get%20their%20act%20together%20by%20v86%20and%20comply%20with%20their%20own%20documentation.%3C%2FP%3E%3CP%3EUntil%20then%2C%20our%20customers%20will%20have%20to%20stay%20with%20a%20mix%20of%20IE%20and%20Chrome%2C%20which%20do%20honour%20the%20policy%20setting.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1501064%22%20slang%3D%22en-US%22%3ERe%3A%20ExternalProtocolDialogShowAlwaysOpenCheckbox%20policy%20no%20longer%20works%20in%20Edge%20Dev%20and%20Canary%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1501064%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FDeployEdge%2Fmicrosoft-edge-policies%23externalprotocoldialogshowalwaysopencheckbox%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FDeployEdge%2Fmicrosoft-edge-policies%23externalprotocoldialogshowalwaysopencheckbox%3C%2FA%3E%26nbsp%3Bsays%20nothing%20about%20secure%20and%20non-secure%20sites.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3ECurrently%20Dev%2085%20%3CSTRONG%3Edoesn't%3C%2FSTRONG%3E%20show%20%22always%20open%20checkbox%22%20for%20%3CSTRONG%3Enon%3C%2FSTRONG%3E%20https.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat's%20the%20situation%20right%20now%3F%20Which%20version%20of%20Edeg%2C%20which%20checkbox%20for%20which%20http%2Fhttps%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1520852%22%20slang%3D%22en-US%22%3ERe%3A%20ExternalProtocolDialogShowAlwaysOpenCheckbox%20policy%20no%20longer%20works%20in%20Edge%20Dev%20and%20Canary%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1520852%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F213419%22%20target%3D%22_blank%22%3E%40Thilo%20Langbein%3C%2FA%3Eand%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F699883%22%20target%3D%22_blank%22%3E%40RichardStantonPropsoft%3C%2FA%3E%20hello!%3C%2FP%3E%3CP%3EAlso%20Canary%2086%20doesn't%20work.%3C%2FP%3E%3CP%3EAny%20news%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1526342%22%20slang%3D%22en-US%22%3ERe%3A%20ExternalProtocolDialogShowAlwaysOpenCheckbox%20policy%20no%20longer%20works%20in%20Edge%20Dev%20and%20Canary%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1526342%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F484598%22%20target%3D%22_blank%22%3E%40fawkes%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20just%20encountered%20this%20issue%20too%20and%20would%20like%20to%20add%20my%20voice%20to%20those%20here%20requesting%20a%20fix.%26nbsp%3B%20For%20our%20use%20case%20we%20are%20interested%20in%20the%20behaviour%20when%20a%20custom%20URL%20is%20entered%20directly%20into%20the%20address%20bar%2C%20as%20well%20the%20case%20where%20the%20link%20is%20placed%20in%20a%20page%20with%20an%20HTTP%20URL%20rather%20than%20HTTPS.%26nbsp%3B%20As%20others%20have%20said%2C%20in%20all%20cases%20this%20impacts%20UX%20quite%20badly%2C%20it%20is%20a%20blocker%20for%20Edge%20adoption%20for%20us%20at%20this%20time.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EKind%20regards%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMike%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1529876%22%20slang%3D%22en-US%22%3ERe%3A%20ExternalProtocolDialogShowAlwaysOpenCheckbox%20policy%20no%20longer%20works%20in%20Edge%20Dev%20and%20Canary%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1529876%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F484598%22%20target%3D%22_blank%22%3E%40fawkes%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F385298%22%20target%3D%22_blank%22%3E%40todd_sahl%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EIt%20looks%20like%20a%20solution%20to%20this%20problem%20is%20to%20add%20the%20URLAllowlist%20policy%2C%20then%20add%20your%20handler%20to%20that%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FDeployEdge%2Fmicrosoft-edge-policies%23urlallowlist%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FDeployEdge%2Fmicrosoft-edge-policies%23urlallowlist%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUse%20this%20format%3A%3C%2FP%3E%3CP%3Ehandlername%3A%2F%2F*%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20this%20helps%20someone.%20This%20definitely%20wasn't%20clear%20from%20the%20description%20of%20the%20policy.%20Maybe%20this%20isn't%20even%20intended%20behavior%2C%20but%20I'm%20sure%20glad%20it%20works.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAndrew%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1530211%22%20slang%3D%22en-US%22%3ERe%3A%20ExternalProtocolDialogShowAlwaysOpenCheckbox%20policy%20no%20longer%20works%20in%20Edge%20Dev%20and%20Canary%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1530211%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F458117%22%20target%3D%22_blank%22%3E%40AndrewSAIF%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThank%20you%2C%20all!%20We'll%20look%20into%20this.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CI%3EFawkes%20(they%2Fthem)%3CBR%20%2F%3EProgram%20Manager%20%26amp%3B%20Community%20Manager%20-%20Microsoft%20Edge%3CI%3E%3C%2FI%3E%3C%2FI%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1534942%22%20slang%3D%22en-US%22%3ERe%3A%20ExternalProtocolDialogShowAlwaysOpenCheckbox%20policy%20no%20longer%20works%20in%20Edge%20Dev%20and%20Canary%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1534942%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20worked%20fine%20for%20me%2C%20thank%20you!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1535123%22%20slang%3D%22en-US%22%3ERe%3A%20ExternalProtocolDialogShowAlwaysOpenCheckbox%20policy%20no%20longer%20works%20in%20Edge%20Dev%20and%20Canary%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1535123%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F458117%22%20target%3D%22_blank%22%3E%40AndrewSAIF%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20Andrew%20for%20being%20able%20to%20offer%20the%20fix%20that%20Microsoft%20couldn't.%3CBR%20%2F%3EThis%20works%20perfectly%2C%20and%20will%20allow%20us%20to%20finally%20migrate%20our%20customers'%20intranets%20from%20a%20mix%20of%20IE11%20and%20Chrome%20to%20Microsoft%20Edge%20v84%20without%20the%20constant%20prompts.%3CBR%20%2F%3E%3CBR%20%2F%3EThis%20puts%20Microsoft%20back%20in%20the%20game%2C%20brilliant.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1556775%22%20slang%3D%22en-US%22%3ERe%3A%20ExternalProtocolDialogShowAlwaysOpenCheckbox%20policy%20no%20longer%20works%20in%20Edge%20Dev%20and%20Canary%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1556775%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20looks%20like%20there%20will%20be%20a%20dedicated%20policy%20for%20this%20as%20of%20v85%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FDeployEdge%2Fmicrosoft-edge-policies%23autolaunchprotocolsfromorigins%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FDeployEdge%2Fmicrosoft-edge-policies%23autolaunchprotocolsfromorigins%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor

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 like this policy still works in Edge Beta 81.0.416.20, but stopped working in Edge Dev 82.0.432.3 and later. The checkbox is simply not shown in the later versions. I tested using skype:// and another application we use in-house. The policy is visible in edge://policy, but it is ignored for whatever reason.

 

Thanks!

Andrew

 

 

21 Replies

@AndrewSAIF Thanks for reaching out and letting us know. We're sorry to hear that it isn't working! We just pushed 83.0.470.0 to Canary; are you still seeing this behavior there? If so, let us know and we'll loop in the GPO team. And in the meantime, can you please submit detailed feedback and diagnostic data through the browser, if you haven't yet?

 

Fawkes (they/them)
Project & Community Manager - Microsoft Edge

@Deleted 

 

Hi Fawkes,

 

I updated Canary to the latest version and got the same result. It is easy to duplicate this behavior on a machine that has Office installed if you set the policy, then type skype:// into the address bar and press enter. 

 

AndrewSAIF_0-1585598044532.png

 

I have the feedback feature disabled in my group policy, but if that is a better way to report issues I can set up a test machine to be excluded. 

 

Thanks!

Andrew

best response
Solution

@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

 

Hi Todd,

 

Thanks for the quick reply. Yes, I am expecting to see the checkbox from a non-https site. 

 

The reason this policy was useful to me is because we have web apps on an http intranet site that contain protocol handler links to open a separate application. For various reasons, we cannot easily make these sites HTTPS. 

 

For this use case, users are clicking several of these links in a short timeframe. The popup for confirmation becomes very obtrusive. I was excited to have this policy since the only other solution at the time was to manually edit the preferences file (or script it). 

 

There was a backlash when this checkbox was removed from Chrome from enterprise users, and I thought this policy was a response to that backlash. I don't think my use case is uncommon and I suspect this will be a big deal for several organizations. 

 

Do you have a timeline or version target for when the checkbox is available by default, and when this happens will the checkbox still only appear for HTTPS? 

 

@todd_sahl 

Not the solution I prefer, but it looks like as a workaround I can just throw the page on my IE Mode list. No popups at all. 

 

Andrew

@Deleted I was also using this on an intranet website served over http. With the latest update to edge chromium, it suddenly stopped working. 

Any chance there's an override for certain domains to be able to get the remember checkbox in conjunction with "Enable remembering protocol launch prompting preferences" being enabled in edge://flags?

It looks like edge chromium no longer honors internet options in control panel (which makes sense) but I'd like a per-domain override as I suddenly no longer have the functionality I had, even though it's still in edge.

@todd_sahl @Deleted 
Hi there. Is there any update on the status of this policy? The behavior appears to be the same still in v85.

 

Thanks!

@AndrewSAIF Our customers are in a similar position, their intranet has specific rules which mean they've twice tried to migrate from IE11 to Edge but had to revert (the most recent to Chrome).
I was hoping with the Chrome based version of Edge that it would honour ExternalProtocolDialogShowAlwaysOpenCheckbox in either Chrome or Edge's reg keys.
The annoyance to the customer of having to click the popup confirmation each time is a deal-breaker,

Hi Todd,

This restriction ruins intranet app experience. Will there be a change in this restriction?

Omer

@AndrewSAIF   Could be good news on the horizon.

Just looked on the beta v84 version of Edge, and the documentation says:

 

"As of Microsoft Edge 84, if you don't configure this policy, when an external protocol confirmation prompt is shown, the user can select "Always allow" to skip all future confirmation prompts for the protocol on this site"

 

Hopefully v84 of Edge will honour the setting, same as Chrome

 

https://docs.microsoft.com/en-us/deployedge/microsoft-edge-policies#externalprotocoldialogshowalways... 

 

@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  Ah sorry, just tried the v84 beta and you're right - Microsoft still aren't complying with their own documentation.

Not reassuring that you're on an even newer beta than me, and that version is also incorrect.

Hopefully Microsoft will get their act together by v86 and comply with their own documentation.

Until then, our customers will have to stay with a mix of IE and Chrome, which do honour the policy setting.

https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-policies#externalprotocoldialogshowalways... says nothing about secure and non-secure sites.

Currently Dev 85 doesn't show "always open checkbox" for non https.

 

What's the situation right now? Which version of Edeg, which checkbox for which http/https?

@Deleted 

 

Hi,

 

I just encountered this issue too and would like to add my voice to those here requesting a fix.  For our use case we are interested in the behaviour when a custom URL is entered directly into the address bar, as well the case where the link is placed in a page with an HTTP URL rather than HTTPS.  As others have said, in all cases this impacts UX quite badly, it is a blocker for Edge adoption for us at this time.

 

Kind regards,

 

Mike

@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

 

@AndrewSAIF 

 

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

 

Fawkes (they/them)
Program Manager & Community Manager - Microsoft Edge