Forum Discussion
Web content filtering and indicator aren't working on third party browser
Hi Sathya_Sekar520 - not sure if you saw my question but can you please expand on your suggestion? I have a Business Premium license so I'm not sure if what you mentioned is feasible. Thanks.
CharlieAD we have heard from Microsoft support that disabling Quic in chrome will resolve this as network protection for defender does not support quic protocol. Since testing with it disabled in chrome we have seen it working correctly so far. No word whether or not support for this is coming in the future for network protection.
I did the below to test but ended up pushing out in Intune for some of our staff devices to test further
To disable HTTP/3 (QUIC) in Google Chrome, please follow these steps:
Open Google Chrome.
In the address bar, type: chrome://flags#enable-quic
Locate the Experimental QUIC protocol flag.
Set the flag to Disabled.
Relaunch Chrome for the setting to take effect.
25-08-2024 - and still not working as expected.
Your IT administrator would have caused Microsoft Defender Exploit Guard to block a potentially dangerous network connection.
Detection time: 2024-08-26T00:29:29.658Z
User: S-1-12-1-3639746192-1275162949-2184531103-2650002400
Destination: https:// x v i d e o s .com
Process Name: chrome.exeBut google chrome still render it normally the website is properly loaded
Btw, i'm in Brazil region.
No matter if i enable or disable the quic or even try the defender extension on google chrome.
Anyclue on how to fix that ?
- Hey there - was there any document or technical reason cited? We've been told by support to disable the QUIC protocol on our supported browsers (Edge and Chrome) but not why. I cannot find any reference for Network Protection / Web Threat Protection having a bad interaction with QUIC. Moreover, QUIC is supported and is natively enabled in Edge and Chrome so if this protocol wasn't, why would MS leave it in "default" state ?
Thanks a lot in advance! CharlieAD Awesome its great to hear it working beyond our environment. If you use Intune, we setup a Congifuration Profile for Windows 10 and Later, Templates > Administrative Template, Create, then after naming it, if you search "Allow QUIC Protocol" you can see options for Edge and Chrome to disable for user or device based.
We have been testing since yesterday. So once this pushes out to devices for example, we noticed when you go into the chrome settings, it still shows as default (and if changed to enabled), but the pushed out setting from Intune is still taking priority.
