Skip to content

Commit 8071845

Browse files
authored
Merge pull request #82 from goodboyrobot/patch-2
Remove zscaler from local proxies listed as examples
2 parents 2b5d12f + e9e3d51 commit 8071845

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

defender-endpoint/web-content-filtering.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: siosulli
66
author: siosulli
77
ms.reviewer: tdoucett
88
ms.localizationpriority: medium
9-
ms.date: 02/02/2024
9+
ms.date: 08/15/2024
1010
manager: deniseb
1111
audience: ITPro
1212
ms.collection:
@@ -43,7 +43,7 @@ Configure policies across your device groups to block certain categories. Blocki
4343
Web content filtering is available on the major web browsers, with blocks performed by Windows Defender SmartScreen (Microsoft Edge) and network protection (Chrome, Firefox, Brave, and Opera). For more information about browser support, see the [prerequisites](#prerequisites) section.
4444

4545
> [!NOTE]
46-
> Web content filtering does not apply policies to isolated browser sessions (i.e. Microsoft Defender Application Guard). The feature is also restricted to specific browsers via process name. This means that web content filtering doesn't work when there is a local proxy application in place (such as Fiddler, ZScaler), due to the process name being masked.
46+
> Web content filtering does not apply policies to isolated browser sessions (i.e. Microsoft Defender Application Guard). The feature is also restricted to specific browsers via process name. This means that web content filtering doesn't work when there is a local proxy application in place (such as Fiddler), due to the process name being masked.
4747
4848
## Benefits of web content filtering
4949

0 commit comments

Comments
 (0)