From 23ff7e6d147be3e63db3770254c90441b663e2b2 Mon Sep 17 00:00:00 2001 From: Kurt Sarens <56369685+kurtsarens@users.noreply.github.com> Date: Wed, 29 Jul 2020 12:41:35 -0700 Subject: [PATCH 1/7] Update microsoft-defender-smartscreen-overview.md Adding a note that no SS events will be logged when using Microsoft Edge version 77 or later. --- .../microsoft-defender-smartscreen-overview.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/windows/security/threat-protection/microsoft-defender-smartscreen/microsoft-defender-smartscreen-overview.md b/windows/security/threat-protection/microsoft-defender-smartscreen/microsoft-defender-smartscreen-overview.md index f13b6bff37..9bae1e6575 100644 --- a/windows/security/threat-protection/microsoft-defender-smartscreen/microsoft-defender-smartscreen-overview.md +++ b/windows/security/threat-protection/microsoft-defender-smartscreen/microsoft-defender-smartscreen-overview.md @@ -66,6 +66,9 @@ When submitting Microsoft Defender Smartscreen products, make sure to select **M ## Viewing Microsoft Defender SmartScreen anti-phishing events +> [!NOTE] +> No Smartscreen events will be logged when using Microsoft Edge version 77 or later. + When Microsoft Defender SmartScreen warns or blocks a user from a website, it's logged as [Event 1035 - Anti-Phishing](https://technet.microsoft.com/scriptcenter/dd565657(v=msdn.10).aspx). ## Viewing Windows event logs for Microsoft Defender SmartScreen From b32a12685e5397991d6587db2c0ca20a0f9df2fd Mon Sep 17 00:00:00 2001 From: ashwin-pr <66497769+ashwin-pr@users.noreply.github.com> Date: Thu, 30 Jul 2020 07:49:52 +0530 Subject: [PATCH 2/7] Update android-intune.md Removed, corrected inadvertent references to internal sharepoint links that were part of actual URL, resulting in a broken URL. --- .../microsoft-defender-atp/android-intune.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-atp/android-intune.md b/windows/security/threat-protection/microsoft-defender-atp/android-intune.md index 42d75ed3b8..d2f56eeeb1 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/android-intune.md +++ b/windows/security/threat-protection/microsoft-defender-atp/android-intune.md @@ -26,7 +26,7 @@ ms.topic: conceptual This topic describes deploying Microsoft Defender ATP for Android on Intune Company Portal enrolled devices. For more information about Intune device enrollment, see [Enroll your -device](https://microsoft.sharepoint.com/teams/WDATPIndia/Shared%20Documents/General/PM%20Docs/External%20Documentation/aka.ms/enrollAndroid). +device](https://docs.microsoft.com/mem/intune/user-help/enroll-device-android-company-portal). > [!NOTE] @@ -45,7 +45,7 @@ This topic describes how to deploy Microsoft Defender ATP for Android on Intune Download the onboarding package from Microsoft Defender Security Center. 1. In [Microsoft Defender Security -Center](https://microsoft.sharepoint.com/teams/WDATPIndia/Shared%20Documents/General/PM%20Docs/External%20Documentation/securitycenter.microsoft.com), go to **Settings** \> **Machine Management** \> **Onboarding**. +Center](https://securitycenter.microsoft.com), go to **Settings** \> **Machine Management** \> **Onboarding**. 2. In the first drop-down, select **Android** as the Operating system. @@ -283,7 +283,7 @@ and then your onboarding should be successful. 4. At this stage the device is successfully onboarded onto Microsoft Defender ATP for Android. You can verify this on the [Microsoft Defender Security -Center](https://microsoft.sharepoint.com/teams/WDATPIndia/Shared%20Documents/General/PM%20Docs/External%20Documentation/securitycenter.microsoft.com) +Center](https://securitycenter.microsoft.com) by navigating to the **Devices** page. ![Image of Microsoft Defender ATP portal](images/9fe378a1dce0f143005c3aa53d8c4f51.png) From efeab4a9774a167e572d65b438718da49e230ec9 Mon Sep 17 00:00:00 2001 From: ImranHabib <47118050+joinimran@users.noreply.github.com> Date: Thu, 30 Jul 2020 08:32:39 +0500 Subject: [PATCH 3/7] addition in note As suggested by the user, added information regarding autopilot profile setting. Problem: https://github.com/MicrosoftDocs/windows-itpro-docs/issues/7121 --- windows/deployment/windows-autopilot/white-glove.md | 1 + 1 file changed, 1 insertion(+) diff --git a/windows/deployment/windows-autopilot/white-glove.md b/windows/deployment/windows-autopilot/white-glove.md index 95c0f4f5d7..c1a09ffab6 100644 --- a/windows/deployment/windows-autopilot/white-glove.md +++ b/windows/deployment/windows-autopilot/white-glove.md @@ -62,6 +62,7 @@ To enable white glove deployment, an additional Autopilot profile setting must b The Windows Autopilot for white glove deployment pre-provisioning process will apply all device-targeted policies from Intune. That includes certificates, security templates, settings, apps, and more – anything targeting the device. Additionally, any apps (Win32 or LOB) that are configured to install in the device context and targeted to the user that has been pre-assigned to the Autopilot device will also be installed. Please make sure not to target both win32 and LOB apps to the same device, as this can make troubleshooting difficult if there are app installation failures. For more information, see [Add a Windows line-of-business app to Microsoft Intune](https://docs.microsoft.com/mem/intune/apps/lob-apps-windows). > [!NOTE] +> Select language mode as user specified in autopilot profiles to ensuer easy access into white glove provisioning mode. > The white glove technician phase will install all device-targeted apps as well as any user-targeted, device-context apps that are targeted to the assigned user. If there is no assigned user, then it will only install the device-targeted apps. Other user-targeted policies will not apply until the user signs into the device. To verify these behaviors, be sure to create appropriate apps and policies targeted to devices and users. ## Scenarios From dab9d35a393921b83694cac9a13b8a8c1cbe8840 Mon Sep 17 00:00:00 2001 From: ImranHabib <47118050+joinimran@users.noreply.github.com> Date: Thu, 30 Jul 2020 10:34:21 +0500 Subject: [PATCH 4/7] Update windows/deployment/windows-autopilot/white-glove.md Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com> --- windows/deployment/windows-autopilot/white-glove.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopilot/white-glove.md b/windows/deployment/windows-autopilot/white-glove.md index c1a09ffab6..2945f04f62 100644 --- a/windows/deployment/windows-autopilot/white-glove.md +++ b/windows/deployment/windows-autopilot/white-glove.md @@ -62,7 +62,7 @@ To enable white glove deployment, an additional Autopilot profile setting must b The Windows Autopilot for white glove deployment pre-provisioning process will apply all device-targeted policies from Intune. That includes certificates, security templates, settings, apps, and more – anything targeting the device. Additionally, any apps (Win32 or LOB) that are configured to install in the device context and targeted to the user that has been pre-assigned to the Autopilot device will also be installed. Please make sure not to target both win32 and LOB apps to the same device, as this can make troubleshooting difficult if there are app installation failures. For more information, see [Add a Windows line-of-business app to Microsoft Intune](https://docs.microsoft.com/mem/intune/apps/lob-apps-windows). > [!NOTE] -> Select language mode as user specified in autopilot profiles to ensuer easy access into white glove provisioning mode. +> Select the language mode as the user specified in Autopilot profiles to ensure easy access into white glove provisioning mode. > The white glove technician phase will install all device-targeted apps as well as any user-targeted, device-context apps that are targeted to the assigned user. If there is no assigned user, then it will only install the device-targeted apps. Other user-targeted policies will not apply until the user signs into the device. To verify these behaviors, be sure to create appropriate apps and policies targeted to devices and users. ## Scenarios From 223b7c58dc18b737c715fa66866dd2ec3af05424 Mon Sep 17 00:00:00 2001 From: JesseEsquivel <33558203+JesseEsquivel@users.noreply.github.com> Date: Thu, 30 Jul 2020 13:14:47 -0400 Subject: [PATCH 5/7] Update commercial-gov.md Linux is not currently supported in GCC high. --- .../threat-protection/microsoft-defender-atp/commercial-gov.md | 1 + 1 file changed, 1 insertion(+) diff --git a/windows/security/threat-protection/microsoft-defender-atp/commercial-gov.md b/windows/security/threat-protection/microsoft-defender-atp/commercial-gov.md index 0396320e6c..558f93dfb9 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/commercial-gov.md +++ b/windows/security/threat-protection/microsoft-defender-atp/commercial-gov.md @@ -54,6 +54,7 @@ The following OS versions are not supported: - Windows 8 Pro - Windows 8.1 Enterprise - macOS +- Linux The initial release of Microsoft Defender ATP will not have immediate parity with the commercial offering. While our goal is to deliver all commercial features and functionality to our US Government (GCC High) customers, there are some capabilities not yet available that we'd like to highlight. These are the known gaps as of August 2019: From be6424a162873845158dc073cfeca2443ec3cd57 Mon Sep 17 00:00:00 2001 From: ms-adir <68929429+ms-adir@users.noreply.github.com> Date: Thu, 30 Jul 2020 20:36:52 +0300 Subject: [PATCH 6/7] Update commercial-gov.md Adding Linux to the list of unsupported OSs. --- .../threat-protection/microsoft-defender-atp/commercial-gov.md | 1 + 1 file changed, 1 insertion(+) diff --git a/windows/security/threat-protection/microsoft-defender-atp/commercial-gov.md b/windows/security/threat-protection/microsoft-defender-atp/commercial-gov.md index 0396320e6c..558f93dfb9 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/commercial-gov.md +++ b/windows/security/threat-protection/microsoft-defender-atp/commercial-gov.md @@ -54,6 +54,7 @@ The following OS versions are not supported: - Windows 8 Pro - Windows 8.1 Enterprise - macOS +- Linux The initial release of Microsoft Defender ATP will not have immediate parity with the commercial offering. While our goal is to deliver all commercial features and functionality to our US Government (GCC High) customers, there are some capabilities not yet available that we'd like to highlight. These are the known gaps as of August 2019: From 5195ff7a7c5c7014c18e8be03ae0d44b3d32b979 Mon Sep 17 00:00:00 2001 From: ashwin-pr <66497769+ashwin-pr@users.noreply.github.com> Date: Fri, 31 Jul 2020 16:12:47 +0530 Subject: [PATCH 7/7] Update android-intune.md Fixed a few broken URLs --- .../microsoft-defender-atp/android-intune.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-atp/android-intune.md b/windows/security/threat-protection/microsoft-defender-atp/android-intune.md index 42d75ed3b8..d2f56eeeb1 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/android-intune.md +++ b/windows/security/threat-protection/microsoft-defender-atp/android-intune.md @@ -26,7 +26,7 @@ ms.topic: conceptual This topic describes deploying Microsoft Defender ATP for Android on Intune Company Portal enrolled devices. For more information about Intune device enrollment, see [Enroll your -device](https://microsoft.sharepoint.com/teams/WDATPIndia/Shared%20Documents/General/PM%20Docs/External%20Documentation/aka.ms/enrollAndroid). +device](https://docs.microsoft.com/mem/intune/user-help/enroll-device-android-company-portal). > [!NOTE] @@ -45,7 +45,7 @@ This topic describes how to deploy Microsoft Defender ATP for Android on Intune Download the onboarding package from Microsoft Defender Security Center. 1. In [Microsoft Defender Security -Center](https://microsoft.sharepoint.com/teams/WDATPIndia/Shared%20Documents/General/PM%20Docs/External%20Documentation/securitycenter.microsoft.com), go to **Settings** \> **Machine Management** \> **Onboarding**. +Center](https://securitycenter.microsoft.com), go to **Settings** \> **Machine Management** \> **Onboarding**. 2. In the first drop-down, select **Android** as the Operating system. @@ -283,7 +283,7 @@ and then your onboarding should be successful. 4. At this stage the device is successfully onboarded onto Microsoft Defender ATP for Android. You can verify this on the [Microsoft Defender Security -Center](https://microsoft.sharepoint.com/teams/WDATPIndia/Shared%20Documents/General/PM%20Docs/External%20Documentation/securitycenter.microsoft.com) +Center](https://securitycenter.microsoft.com) by navigating to the **Devices** page. ![Image of Microsoft Defender ATP portal](images/9fe378a1dce0f143005c3aa53d8c4f51.png)