From 41e8463d7402ad2bf686a9bf44223a306ca0f930 Mon Sep 17 00:00:00 2001 From: Joyce Y <47188252+mypil@users.noreply.github.com> Date: Fri, 22 May 2020 17:56:26 -0300 Subject: [PATCH 01/15] Fixed typo in line 85 symlinkevalution = symlinkevaluation Resolves #6786 --- .../security-policy-settings/create-symbolic-links.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/security-policy-settings/create-symbolic-links.md b/windows/security/threat-protection/security-policy-settings/create-symbolic-links.md index e361acf1d9..c07cb74837 100644 --- a/windows/security/threat-protection/security-policy-settings/create-symbolic-links.md +++ b/windows/security/threat-protection/security-policy-settings/create-symbolic-links.md @@ -82,7 +82,7 @@ When a local setting is greyed out, it indicates that a GPO currently controls t ### Command-line tools -This setting can be used in conjunction with a symbolic link file system setting that can be manipulated with the command-line tool to control the kinds of symlinks that are allowed on the device. For more info, type **fsutil behavior set symlinkevalution /?** at the command prompt. +This setting can be used in conjunction with a symbolic link file system setting that can be manipulated with the command-line tool to control the kinds of symlinks that are allowed on the device. For more info, type **fsutil behavior set symlinkevaluation /?** at the command prompt. ## Security considerations From db3244cb0b3a34b4110c685e1fe4011537b1ccf8 Mon Sep 17 00:00:00 2001 From: rogersoMS <44718379+rogersoMS@users.noreply.github.com> Date: Sat, 23 May 2020 11:48:06 +1000 Subject: [PATCH 02/15] Removed note regarding Edge Chromium lack of WIP support @Dansimp Edge Chromium v81 (from April 13th) and later now has support for WIP, as per https://docs.microsoft.com/en-au/deployedge/Microsoft-Edge-security-windows-information-protection and https://docs.microsoft.com/en-us/deployedge/microsoft-edge-relnote-stable-channel#version-81041653-april-13 hence removing Edge as a known issue from this page. Please verify with Narendra Acharya if necessary --- .../windows-information-protection/limitations-with-wip.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/security/information-protection/windows-information-protection/limitations-with-wip.md b/windows/security/information-protection/windows-information-protection/limitations-with-wip.md index 3fc752f3ca..1e2b9fade3 100644 --- a/windows/security/information-protection/windows-information-protection/limitations-with-wip.md +++ b/windows/security/information-protection/windows-information-protection/limitations-with-wip.md @@ -145,8 +145,8 @@ This table provides info about the most common problems you might encounter whil > [!NOTE] > When corporate data is written to disk, WIP uses the Windows-provided Encrypting File System (EFS) to protect it and associate it with your enterprise identity. One caveat to keep in mind is that the Preview Pane in File Explorer will not work for encrypted files. -> [!NOTE] -> Chromium-based versions of Microsoft Edge (versions since 79) don't fully support WIP yet. The functionality could be partially enabled by going to the local page **edge://flags/#edge-dataprotection** and setting the **Windows Information Protection** flag to **enabled**. + + > [!NOTE] > Help to make this topic better by providing us with edits, additions, and feedback. For info about how to contribute to this topic, see [Contributing to our content](https://github.com/Microsoft/windows-itpro-docs/blob/master/CONTRIBUTING.md). From 64b7099f22fdef4f23f77bf6ba439ea8e9cad039 Mon Sep 17 00:00:00 2001 From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com> Date: Sat, 23 May 2020 11:28:17 +0530 Subject: [PATCH 03/15] replaced two invalid links to new links As per the user report #6782. so i removed two invalid links to new links below are the new links **https://docs.microsoft.com/windows/security/threat-protection/windows-defender-application-control/wdac-and-applocker-overview** **https://docs.microsoft.com/windows/security/threat-protection/windows-defender-application-control/feature-availability** --- .../windows-defender-application-control.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control.md b/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control.md index 02dad7adfd..adeefea1ee 100644 --- a/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control.md +++ b/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control.md @@ -45,8 +45,8 @@ Windows 10 includes two technologies that can be used for application control de | Topic | Description | | - | - | -| [WDAC and AppLocker Overview](plan-windows-defender-application-control-management.md) | This topic describes the decisions you need to make to establish the processes for managing and maintaining WDAC policies. | -| [WDAC and AppLocker Feature Availability](understand-windows-defender-application-control-policy-design-decisions.md) | This topic lists the design questions, possible answers, and ramifications of the decisions when you plan a deployment of application control policies. | +| [WDAC and AppLocker Overview](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-application-control/wdac-and-applocker-overview) | This topic describes the decisions you need to make to establish the processes for managing and maintaining WDAC policies. | +| [WDAC and AppLocker Feature Availability](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-application-control/feature-availability) | This topic lists the design questions, possible answers, and ramifications of the decisions when you plan a deployment of application control policies. | ## See also From 8a9d95b2c9ba3236e7d31b060d675b89245aaa56 Mon Sep 17 00:00:00 2001 From: VLG17 <41186174+VLG17@users.noreply.github.com> Date: Sat, 23 May 2020 14:04:05 +0300 Subject: [PATCH 04/15] remove TMP group policy path https://github.com/MicrosoftDocs/windows-itpro-docs/issues/5951 --- .../deployment/deploy-windows-mdt/set-up-mdt-for-bitlocker.md | 1 - 1 file changed, 1 deletion(-) diff --git a/windows/deployment/deploy-windows-mdt/set-up-mdt-for-bitlocker.md b/windows/deployment/deploy-windows-mdt/set-up-mdt-for-bitlocker.md index c6400f67e9..4872285d93 100644 --- a/windows/deployment/deploy-windows-mdt/set-up-mdt-for-bitlocker.md +++ b/windows/deployment/deploy-windows-mdt/set-up-mdt-for-bitlocker.md @@ -88,7 +88,6 @@ Following these steps, you enable the backup of BitLocker and TPM recovery infor 3. Do not enable BitLocker until recovery information is stored in AD DS for operating system drives 2. Enable the **Configure TPM platform validation profile for BIOS-based firmware configurations** policy. 3. Enable the **Configure TPM platform validation profile for native UEFI firmware configurations** policy. - Computer Configuration / Policies / Administrative Templates / System / Trusted Platform Module Services > [!NOTE] > If you consistently get the error "Windows BitLocker Drive Encryption Information. The system boot information has changed since BitLocker was enabled. You must supply a BitLocker recovery password to start this system." after encrypting a computer with BitLocker, you might have to change the various "Configure TPM platform validation profile" Group Policies, as well. Whether or not you need to do this will depend on the hardware you are using. From 92c742902c2798e35cf46001f9f439d33883bfb3 Mon Sep 17 00:00:00 2001 From: VLG17 <41186174+VLG17@users.noreply.github.com> Date: Sat, 23 May 2020 14:18:09 +0300 Subject: [PATCH 05/15] add note about URLs that need to be whitelisted https://github.com/MicrosoftDocs/windows-itpro-docs/issues/5886 --- .../microsoft-defender-atp/production-deployment.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/windows/security/threat-protection/microsoft-defender-atp/production-deployment.md b/windows/security/threat-protection/microsoft-defender-atp/production-deployment.md index c2a4429c26..f952916126 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/production-deployment.md +++ b/windows/security/threat-protection/microsoft-defender-atp/production-deployment.md @@ -144,6 +144,9 @@ Appendix section in this document for the URLs Whitelisting or on [Microsoft Docs](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-atp/configure-proxy-internet-windows-defender-advanced-threat-protection#enable-access-to-windows-defender-atp-service-urls-in-the-proxy-server). +>[!NOTE] +>For a detailed list of URLs that need to be whitelisted, please see [this article](https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-antivirus/configure-network-connections-windows-defender-antivirus). + **Manual static proxy configuration:** - Registry based configuration From 0e9567075b338a6fa6725f37ce62dcfe2d2d3571 Mon Sep 17 00:00:00 2001 From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com> Date: Sun, 24 May 2020 15:57:08 +0530 Subject: [PATCH 06/15] Update windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control.md accepted Co-authored-by: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- .../windows-defender-application-control.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control.md b/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control.md index adeefea1ee..a24ae4663e 100644 --- a/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control.md +++ b/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control.md @@ -45,8 +45,8 @@ Windows 10 includes two technologies that can be used for application control de | Topic | Description | | - | - | -| [WDAC and AppLocker Overview](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-application-control/wdac-and-applocker-overview) | This topic describes the decisions you need to make to establish the processes for managing and maintaining WDAC policies. | -| [WDAC and AppLocker Feature Availability](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-application-control/feature-availability) | This topic lists the design questions, possible answers, and ramifications of the decisions when you plan a deployment of application control policies. | +| [WDAC and AppLocker Overview](wdac-and-applocker-overview.md) | This topic describes the decisions you need to make to establish the processes for managing and maintaining WDAC policies. | +| [WDAC and AppLocker Feature Availability](feature-availability.md) | This topic lists the design questions, possible answers, and ramifications of the decisions when you plan a deployment of application control policies. | ## See also From f928e335f90948dfdedcbcf8a8aa10b5ba0b2e9c Mon Sep 17 00:00:00 2001 From: ImranHabib <47118050+joinimran@users.noreply.github.com> Date: Mon, 25 May 2020 10:52:37 +0500 Subject: [PATCH 07/15] Adding a new error As reported, the new error information has been added in the document. Problem: https://github.com/MicrosoftDocs/windows-itpro-docs/issues/6399 --- windows/deployment/windows-autopilot/known-issues.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/windows/deployment/windows-autopilot/known-issues.md b/windows/deployment/windows-autopilot/known-issues.md index b85fc9b010..488e49ba8c 100644 --- a/windows/deployment/windows-autopilot/known-issues.md +++ b/windows/deployment/windows-autopilot/known-issues.md @@ -29,6 +29,9 @@ ms.topic: article Blocking apps specified in a user-targeted Enrollment Status Profile are ignored during device ESP. The services responsible for determining the list of apps that should be blocking during device ESP are not able to determine the correct ESP profile containing the list of apps because they do not know the user identity. As a workaround, enable the default ESP profile (which targets all users and devices) and place the blocking app list there. In the future, it will be possible to instead target the ESP profile to device groups to avoid this issue. +That username looks like it belongs to another organization. Try signing in again or start over with a different account. + Confirm that all of your information is correct at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Provisioning\Diagnostics\AutoPilot see Troubleshooting Windows Auto Pilot for more details. + Windows Autopilot user-driven Hybrid Azure AD deployments do not grant users Administrator rights even when specified in the Windows Autopilot profile. This will occur when there is another user on the device that already has Administrator rights. For example, a PowerShell script or policy could create an additional local account that is a member of the Administrators group. To ensure this works properly, do not create an additional account until after the Windows Autopilot process has completed. From 10f157ac3c6d786fc5cda214913c17c85dd2979a Mon Sep 17 00:00:00 2001 From: ImranHabib <47118050+joinimran@users.noreply.github.com> Date: Mon, 25 May 2020 14:03:51 +0500 Subject: [PATCH 08/15] Update windows/deployment/windows-autopilot/known-issues.md Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com> --- windows/deployment/windows-autopilot/known-issues.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopilot/known-issues.md b/windows/deployment/windows-autopilot/known-issues.md index 488e49ba8c..8dbec94be5 100644 --- a/windows/deployment/windows-autopilot/known-issues.md +++ b/windows/deployment/windows-autopilot/known-issues.md @@ -30,7 +30,7 @@ ms.topic: article The services responsible for determining the list of apps that should be blocking during device ESP are not able to determine the correct ESP profile containing the list of apps because they do not know the user identity. As a workaround, enable the default ESP profile (which targets all users and devices) and place the blocking app list there. In the future, it will be possible to instead target the ESP profile to device groups to avoid this issue. That username looks like it belongs to another organization. Try signing in again or start over with a different account. - Confirm that all of your information is correct at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Provisioning\Diagnostics\AutoPilot see Troubleshooting Windows Auto Pilot for more details. + Confirm that all of your information is correct at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Provisioning\Diagnostics\AutoPilot. See Troubleshooting Windows Auto Pilot for more details. Windows Autopilot user-driven Hybrid Azure AD deployments do not grant users Administrator rights even when specified in the Windows Autopilot profile. This will occur when there is another user on the device that already has Administrator rights. For example, a PowerShell script or policy could create an additional local account that is a member of the Administrators group. To ensure this works properly, do not create an additional account until after the Windows Autopilot process has completed. From 7648e6b398112ea262e426bb361eaedfb2dbd9e7 Mon Sep 17 00:00:00 2001 From: VLG17 <41186174+VLG17@users.noreply.github.com> Date: Mon, 25 May 2020 13:36:11 +0300 Subject: [PATCH 09/15] Update windows/security/threat-protection/microsoft-defender-atp/production-deployment.md Co-authored-by: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- .../microsoft-defender-atp/production-deployment.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-atp/production-deployment.md b/windows/security/threat-protection/microsoft-defender-atp/production-deployment.md index f952916126..0f4c5a7201 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/production-deployment.md +++ b/windows/security/threat-protection/microsoft-defender-atp/production-deployment.md @@ -144,8 +144,8 @@ Appendix section in this document for the URLs Whitelisting or on [Microsoft Docs](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-atp/configure-proxy-internet-windows-defender-advanced-threat-protection#enable-access-to-windows-defender-atp-service-urls-in-the-proxy-server). ->[!NOTE] ->For a detailed list of URLs that need to be whitelisted, please see [this article](https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-antivirus/configure-network-connections-windows-defender-antivirus). +> [!NOTE] +> For a detailed list of URLs that need to be whitelisted, please see [this article](https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-antivirus/configure-network-connections-windows-defender-antivirus). **Manual static proxy configuration:** From b050b2001fbbc705e6dbef796a078d0e14096544 Mon Sep 17 00:00:00 2001 From: Kannan B <59028488+kannanb-github@users.noreply.github.com> Date: Tue, 26 May 2020 16:29:13 +0530 Subject: [PATCH 10/15] Update Event Id 4624 In the Network information section, the workstation name is mentioned with 'machine name from which logon attempt was performed.' that has been modified to "machine name to which logon attempt was performed." (please notice 'to' instead of 'from'). The workstation name has to be the computer name of the target computer not the source computer. Please check the issue reported on https://github.com/MicrosoftDocs/windows-itpro-docs/issues/6438, thanks. --- windows/security/threat-protection/auditing/event-4624.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/auditing/event-4624.md b/windows/security/threat-protection/auditing/event-4624.md index d9b5265f75..a7f80d6745 100644 --- a/windows/security/threat-protection/auditing/event-4624.md +++ b/windows/security/threat-protection/auditing/event-4624.md @@ -230,7 +230,7 @@ This event generates when a logon session is created (on destination machine). I **Network Information:** -- **Workstation Name** \[Type = UnicodeString\]**:** machine name from which logon attempt was performed. +- **Workstation Name** \[Type = UnicodeString\]**:** machine name to which logon attempt was performed. - **Source Network Address** \[Type = UnicodeString\]**:** IP address of machine from which logon attempt was performed. From 39d6a66bc0554b1c1f05686d971b40047d7bc913 Mon Sep 17 00:00:00 2001 From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com> Date: Tue, 26 May 2020 18:16:54 +0530 Subject: [PATCH 11/15] removed one note section from the two note secition as per the user report #6808 , so i removed one note section from two. So please verify and approve this PR. Thanks --- windows/client-management/mdm/policy-csp-browser.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/windows/client-management/mdm/policy-csp-browser.md b/windows/client-management/mdm/policy-csp-browser.md index d3fa4df77e..9a0c8951da 100644 --- a/windows/client-management/mdm/policy-csp-browser.md +++ b/windows/client-management/mdm/policy-csp-browser.md @@ -19,9 +19,6 @@ ms.localizationpriority: medium
-> [!NOTE] -> You've reached the documentation for Microsoft Edge version 45 and earlier. To see the documentation for Microsoft Edge version 77 or later, go to the [Microsoft Edge documentation landing page](https://docs.microsoft.com/DeployEdge/). - ## Browser policies From af81e4c6b72a6b515e6be0b5fb5ec0b1488f55be Mon Sep 17 00:00:00 2001 From: VARADHARAJAN K <3296790+RAJU2529@users.noreply.github.com> Date: Tue, 26 May 2020 23:41:08 +0530 Subject: [PATCH 12/15] Update windows/client-management/mdm/policy-csp-browser.md Accepted. Co-authored-by: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- windows/client-management/mdm/policy-csp-browser.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/windows/client-management/mdm/policy-csp-browser.md b/windows/client-management/mdm/policy-csp-browser.md index 9a0c8951da..4b686d7c13 100644 --- a/windows/client-management/mdm/policy-csp-browser.md +++ b/windows/client-management/mdm/policy-csp-browser.md @@ -17,8 +17,6 @@ ms.localizationpriority: medium > [!NOTE] > You've reached the documentation for Microsoft Edge version 45 and earlier. To see the documentation for Microsoft Edge version 77 or later, go to the [Microsoft Edge documentation landing page](https://docs.microsoft.com/DeployEdge/). -
- ## Browser policies @@ -4307,4 +4305,3 @@ Footnotes: - 6 - Added in Windows 10, version 1903. - From 00c965e024caddf7b370ad6144a6204a49d901d6 Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Tue, 26 May 2020 14:48:38 -0700 Subject: [PATCH 13/15] Update windows-defender-application-control.md --- .../windows-defender-application-control.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control.md b/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control.md index a24ae4663e..7f723913e2 100644 --- a/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control.md +++ b/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control.md @@ -14,7 +14,7 @@ author: denisebmsft ms.reviewer: isbrahm ms.author: deniseb manager: dansimp -ms.date: 04/15/2020 +ms.date: 05/26/2020 ms.custom: asr --- @@ -43,12 +43,12 @@ Windows 10 includes two technologies that can be used for application control de ## In this section -| Topic | Description | -| - | - | -| [WDAC and AppLocker Overview](wdac-and-applocker-overview.md) | This topic describes the decisions you need to make to establish the processes for managing and maintaining WDAC policies. | -| [WDAC and AppLocker Feature Availability](feature-availability.md) | This topic lists the design questions, possible answers, and ramifications of the decisions when you plan a deployment of application control policies. | +| Article | Description | +| --- | --- | +| [WDAC and AppLocker Overview](wdac-and-applocker-overview.md) | This article describes the decisions you need to make to establish the processes for managing and maintaining WDAC policies. | +| [WDAC and AppLocker Feature Availability](feature-availability.md) | This article lists the design questions, possible answers, and ramifications of the decisions when you plan a deployment of application control policies. | -## See also +## Related articles - [WDAC design guide](windows-defender-application-control-design-guide.md) - [WDAC deployment guide](windows-defender-application-control-deployment-guide.md) From 26f6d105e97076cfe4df2295d4bf86d166ac8348 Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Tue, 26 May 2020 14:57:27 -0700 Subject: [PATCH 14/15] Update onboard-offline-machines.md --- .../microsoft-defender-atp/onboard-offline-machines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/microsoft-defender-atp/onboard-offline-machines.md b/windows/security/threat-protection/microsoft-defender-atp/onboard-offline-machines.md index e29bf3379b..1f798a3ece 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/onboard-offline-machines.md +++ b/windows/security/threat-protection/microsoft-defender-atp/onboard-offline-machines.md @@ -40,7 +40,7 @@ For more information about onboarding methods, see the following articles: - [Onboard servers to the Microsoft Defender ATP service](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/configure-server-endpoints#windows-server-2008-r2-sp1--windows-server-2012-r2-and-windows-server-2016) - [Configure machine proxy and Internet connectivity settings](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/configure-proxy-internet#configure-the-proxy-server-manually-using-a-registry-based-static-proxy) -## On-premise machines +## On-premises machines - Setup Azure Log Analytics (formerly known as OMS Gateway) to act as proxy or hub: - [Azure Log Analytics Agent](https://docs.microsoft.com/azure/azure-monitor/platform/gateway#download-the-log-analytics-gateway) From c680d435d7f48c6977ff3f48b2e27058d93341b8 Mon Sep 17 00:00:00 2001 From: Tina Burden Date: Wed, 27 May 2020 09:04:17 -0700 Subject: [PATCH 15/15] pencil edit --- .../microsoft-defender-atp/production-deployment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/microsoft-defender-atp/production-deployment.md b/windows/security/threat-protection/microsoft-defender-atp/production-deployment.md index 0f4c5a7201..3e320c90a9 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/production-deployment.md +++ b/windows/security/threat-protection/microsoft-defender-atp/production-deployment.md @@ -145,7 +145,7 @@ Appendix section in this document for the URLs Whitelisting or on Docs](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-atp/configure-proxy-internet-windows-defender-advanced-threat-protection#enable-access-to-windows-defender-atp-service-urls-in-the-proxy-server). > [!NOTE] -> For a detailed list of URLs that need to be whitelisted, please see [this article](https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-antivirus/configure-network-connections-windows-defender-antivirus). +> For a detailed list of URLs that need to be whitelisted, please see [this article](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-antivirus/configure-network-connections-windows-defender-antivirus). **Manual static proxy configuration:**