From 61fef03296ea86f5361d9c2818e778e54388d03f Mon Sep 17 00:00:00 2001 From: Joey Caparas Date: Fri, 14 Oct 2016 14:40:01 +1100 Subject: [PATCH] add HTTPS protocol --- ...troubleshoot-windows-defender-advanced-threat-protection.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/windows/keep-secure/troubleshoot-windows-defender-advanced-threat-protection.md b/windows/keep-secure/troubleshoot-windows-defender-advanced-threat-protection.md index 4acdf05f74..fd485e8645 100644 --- a/windows/keep-secure/troubleshoot-windows-defender-advanced-threat-protection.md +++ b/windows/keep-secure/troubleshoot-windows-defender-advanced-threat-protection.md @@ -29,6 +29,9 @@ Configure your browser to allow cookies. ### No data is shown on the portal If no data is displayed on the Dashboard portal even if no errors were encountered in the portal logs or in the browser console, you'll need to whitelist the threat intelligence, data access, and detonation endpoints that also use this protocol. +> [!NOTE] +> You must use the HTTPS protocol when adding the following endpoints. + Depending on your region, add the following endpoints to the whitelist: U.S. region: