diff --git a/windows/deployment/windows-autopilot/white-glove.md b/windows/deployment/windows-autopilot/white-glove.md index 95c0f4f5d7..2945f04f62 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 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 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) 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: 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