From 0c2dad2ce43bd3ce7da2959d92529a3231d3208d Mon Sep 17 00:00:00 2001 From: Dan Orum <19275382+danorum@users.noreply.github.com> Date: Tue, 4 Aug 2020 16:10:11 -0500 Subject: [PATCH 1/4] Update web-content-filtering.md In order for Network Protection to be used to block 3rd party browsers, it needs to be enabled on the device. --- .../microsoft-defender-atp/web-content-filtering.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/microsoft-defender-atp/web-content-filtering.md b/windows/security/threat-protection/microsoft-defender-atp/web-content-filtering.md index bbcad993a7..1bd463d9d4 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/web-content-filtering.md +++ b/windows/security/threat-protection/microsoft-defender-atp/web-content-filtering.md @@ -49,7 +49,7 @@ Before trying out this feature, make sure you have the following: - Windows 10 Enterprise E5 license - Access to Microsoft Defender Security Center portal - Devices running Windows 10 Anniversary Update (version 1607) or later with the latest MoCAMP update. -Note that if SmartScreen is not turned on, Network Protection will take over the blocking. +Note that if SmartScreen is not turned on, Network Protection will take over the blocking. This requires enabling Network Protection [on the device](https://docs.microsoft.com/en-us/windows/security/threat-protection/microsoft-defender-atp/enable-network-protection). ## Data handling From 8944262a60017091b6e2b7dfde61057c8c1f7a9b Mon Sep 17 00:00:00 2001 From: andreiztm Date: Wed, 5 Aug 2020 19:55:05 +0300 Subject: [PATCH 2/4] Add clarification for FAQs regarding Target Version policy --- windows/deployment/update/waas-wufb-group-policy.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/windows/deployment/update/waas-wufb-group-policy.md b/windows/deployment/update/waas-wufb-group-policy.md index d9b74223ef..fc5d903422 100644 --- a/windows/deployment/update/waas-wufb-group-policy.md +++ b/windows/deployment/update/waas-wufb-group-policy.md @@ -118,6 +118,8 @@ Now all devices are paused from updating for 35 days. When the pause is removed, If you need a device to stay on a version beyond the point when deferrals on the next version would elapse or if you need to skip a version (for example, update fall release to fall release) use the **Select the target Feature Update version** setting instead of using the **Specify when Preview Builds and Feature Updates are received** setting for feature update deferrals. When you use this policy, specify the version that you want your device(s) to use. If you don't update this before the device reaches end of service, the device will automatically be updated once it is 60 days past end of service for its edition. +When configuring the Target Version policy, if you specify a Feature Update version that is older than your current version or is an invalid value the device will not receive any Feature Updates until the policy is updated. When the Target Version policy is specified your Feature Update deferrals will not be in effect. + ### Manage how users experience updates #### I want to manage when devices download, install, and restart after updates From b3eda39ea7953ce912b10fd173e9c4a2054537d6 Mon Sep 17 00:00:00 2001 From: Jaime Ondrusek Date: Wed, 5 Aug 2020 11:53:26 -0700 Subject: [PATCH 3/4] Update waas-wufb-group-policy.md Corrected capitalization and voice. --- windows/deployment/update/waas-wufb-group-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/update/waas-wufb-group-policy.md b/windows/deployment/update/waas-wufb-group-policy.md index fc5d903422..8707f69961 100644 --- a/windows/deployment/update/waas-wufb-group-policy.md +++ b/windows/deployment/update/waas-wufb-group-policy.md @@ -118,7 +118,7 @@ Now all devices are paused from updating for 35 days. When the pause is removed, If you need a device to stay on a version beyond the point when deferrals on the next version would elapse or if you need to skip a version (for example, update fall release to fall release) use the **Select the target Feature Update version** setting instead of using the **Specify when Preview Builds and Feature Updates are received** setting for feature update deferrals. When you use this policy, specify the version that you want your device(s) to use. If you don't update this before the device reaches end of service, the device will automatically be updated once it is 60 days past end of service for its edition. -When configuring the Target Version policy, if you specify a Feature Update version that is older than your current version or is an invalid value the device will not receive any Feature Updates until the policy is updated. When the Target Version policy is specified your Feature Update deferrals will not be in effect. +When you set the target version policy, if you specify a feature update version that is older than your current version or set a value that isn't valid, the device will not receive any feature updates until the policy is updated. When you specify target version policy, feature update deferrals will not be in effect. ### Manage how users experience updates From b6580df67c0d55084fa7cbe81e092a0f49be9a4f Mon Sep 17 00:00:00 2001 From: Beth Woodbury <40870842+levinec@users.noreply.github.com> Date: Wed, 5 Aug 2020 12:35:14 -0700 Subject: [PATCH 4/4] Update web-content-filtering.md --- .../microsoft-defender-atp/web-content-filtering.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/microsoft-defender-atp/web-content-filtering.md b/windows/security/threat-protection/microsoft-defender-atp/web-content-filtering.md index 1bd463d9d4..cbe01b56e6 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/web-content-filtering.md +++ b/windows/security/threat-protection/microsoft-defender-atp/web-content-filtering.md @@ -49,7 +49,7 @@ Before trying out this feature, make sure you have the following: - Windows 10 Enterprise E5 license - Access to Microsoft Defender Security Center portal - Devices running Windows 10 Anniversary Update (version 1607) or later with the latest MoCAMP update. -Note that if SmartScreen is not turned on, Network Protection will take over the blocking. This requires enabling Network Protection [on the device](https://docs.microsoft.com/en-us/windows/security/threat-protection/microsoft-defender-atp/enable-network-protection). +Note that if SmartScreen is not turned on, Network Protection will take over the blocking. This requires enabling Network Protection [on the device](enable-network-protection.md). ## Data handling