Merge branch 'master' of https://cpubwin.visualstudio.com/_git/it-client into FromPrivateRepo

windows/security/identity-protection/hello-for-business/hello-and-password-changes.md

@@ -8,7 +8,7 @@ ms.sitesec: library
 ms.pagetype: security
 audience: ITPro
 author: danihalfin
-ms.author: danihalf
+ms.author: daniha
 manager: dansimp
 ms.collection: M365-identity-device-management
 ms.topic: article

windows/security/identity-protection/hello-for-business/hello-errors-during-pin-creation.md

@@ -9,7 +9,7 @@ ms.sitesec: library
 ms.pagetype: security
 audience: ITPro
 author: danihalfin
-ms.author: danihalf
+ms.author: daniha
 manager: dansimp
 ms.collection: M365-identity-device-management
 ms.topic: troubleshooting

windows/security/identity-protection/hello-for-business/hello-event-300.md

@@ -9,7 +9,7 @@ ms.sitesec: library
 ms.pagetype: security
 audience: ITPro
 author: danihalfin
-ms.author: danihalf
+ms.author: daniha
 manager: dansimp
 ms.collection: M365-identity-device-management
 ms.topic: article

windows/security/identity-protection/hello-for-business/hello-manage-in-organization.md

@@ -9,7 +9,7 @@ ms.sitesec: library
 ms.pagetype: security
 audience: ITPro
 author: danihalfin
-ms.author: danihalf
+ms.author: daniha
 manager: dansimp
 ms.collection: M365-identity-device-management
 ms.topic: article

windows/security/identity-protection/hello-for-business/hello-why-pin-is-better-than-password.md

@@ -9,7 +9,7 @@ ms.sitesec: library
 ms.pagetype: security
 audience: ITPro
 author: danihalfin
-ms.author: danihalf
+ms.author: daniha
 manager: dansimp
 ms.collection: M365-identity-device-management
 ms.topic: article

windows/security/information-protection/windows-information-protection/how-wip-works-with-labels.md

@@ -8,10 +8,10 @@ ms.sitesec: library
 ms.pagetype: security
 author: justinha
 ms.localizationpriority: medium
-ms.date: 11/28/2018
+ms.date: 02/26/2019
 ---
 
-# How Windows Information Protection protects files with a sensitivity label 
+# How Windows Information Protection (WIP) protects a file that has a sensitivity label 
 
 **Applies to:**
 
@@ -29,10 +29,12 @@ Microsoft information protection technologies include:
 
 - [Windows Information Protection (WIP)](protect-enterprise-data-using-wip.md) is built in to Windows 10 and protects local data at rest on endpoint devices, and manages apps to protect local data in use. Data that leaves the endpoint device, such as email attachment, is not protected by WIP. 
 
-- [Office 365 Information Protection](https://docs.microsoft.com/office365/securitycompliance/office-365-info-protection-for-gdpr-overview) is a solution to classify, protect, and monitor personal data in Office 365 and other first-party or third-party Software-as-a-Service (SaaS) apps.
+- [Office 365 Information Protection](https://docs.microsoft.com/office365/securitycompliance/office-365-info-protection-for-gdpr-overview) is a solution to classify, protect, and monitor personal data in Office 365.
 
 - [Azure Information Protection](https://docs.microsoft.com/azure/information-protection/what-is-information-protection) is a cloud-based solution that can be purchased either standalone or as part of Microsoft 365 Enterprise. It helps an organization classify and protect its documents and emails by applying labels. Azure Information Protection is applied directly to content, and roams with the content as it's moved between locations and cloud services.
 
+- [Microsoft Cloud App Security](https://docs.microsoft.com/cloud-app-security/what-is-cloud-app-security) is a cloud access security broker (CASB) solution that allows you to discover, classify, protect, and monitor user data in first-party and third-party Software-as-a-Service (SaaS) apps used by your organization.
+
 End users can choose and apply sensitivity labels from a bar that appears below the ribbon in Office apps:
 
 ![Sensitivity labels](images/sensitivity-labels.png)

windows/security/threat-protection/windows-defender-atp/whats-new-in-windows-defender-atp.md

@@ -32,7 +32,7 @@ The following capabilities are generally available (GA).
 ### In preview
 The following capability are included in the February 2019 preview release. 
 
-- [Reports](https://docs.microsoft.com/windows/security/threat-protection-reports-windows-defender-advanced-threat-protection)<BR>The threat protection report provides high-level information about alerts generated in your organization. 
+- [Reports](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-atp/threat-protection-reports-windows-defender-advanced-threat-protection)<BR>The threat protection report provides high-level information about alerts generated in your organization. 
 
 
 

windows/security/threat-protection/windows-defender-system-guard/system-guard-secure-launch-and-smm-protection.md

@@ -60,10 +60,10 @@ To verify that Secure Launch is running, use System Information (MSInfo32). Clic
 >[!NOTE]
 >To enable System Guard Secure launch, the platform must meet all the baseline requirements for [Device Guard](https://docs.microsoft.com/en-us/windows/security/threat-protection/device-guard/introduction-to-device-guard-virtualization-based-security-and-windows-defender-application-control), [Credential Guard](https://docs.microsoft.com/en-us/windows/security/identity-protection/credential-guard/credential-guard-requirements), and [Virtualization Based Security](https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-exploit-guard/enable-virtualization-based-protection-of-code-integrity).
 
-## Requirements
-Your environment needs the following hardware to run System Guard Secure Launch.
+## Requirements Met by System Guard Enabled Machines
+Any machine with System Guard enabled will automatically meet the following low-level hardware requirements:
 
-|For Intel® vPro™ processors starting with Intel® Coffeelake, Whiskeylake, or later silicon requirements|Description|
+|For Intel® vPro™ processors starting with Intel® Coffeelake, Whiskeylake, or later silicon|Description|
 |--------|-----------|
 |64-bit CPU|A 64-bit computer with minimum 4 cores (logical processors) is required for hypervisor and virtualization-based security (VBS). For more info about Hyper-V, see [Hyper-V on Windows Server 2016](https://docs.microsoft.com/windows-server/virtualization/hyper-v/hyper-v-on-windows-server) or [Introduction to Hyper-V on Windows 10](https://docs.microsoft.com/virtualization/hyper-v-on-windows/about/). For more info about hypervisor, see [Hypervisor Specifications](https://docs.microsoft.com/virtualization/hyper-v-on-windows/reference/tlfs).|
 |Trusted Platform Module (TPM) 2.0|Platforms must support a discrete TPM 2.0. Integrated/firmware TPMs are not supported.|