From 59d1a802c87a4d2122aeffb6b1d452530ebb0105 Mon Sep 17 00:00:00 2001 From: Justin Hall Date: Thu, 20 Sep 2018 13:06:43 -0700 Subject: [PATCH] edits to WIP links --- .../how-wip-works-with-labels.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/windows/security/information-protection/windows-information-protection/how-wip-works-with-labels.md b/windows/security/information-protection/windows-information-protection/how-wip-works-with-labels.md index 8629abc64a..f1232c7624 100644 --- a/windows/security/information-protection/windows-information-protection/how-wip-works-with-labels.md +++ b/windows/security/information-protection/windows-information-protection/how-wip-works-with-labels.md @@ -76,9 +76,8 @@ The PDF file doesn't need any other work context beyond the sensitivity label. - [Windows Defender Advanced Threat Protection (WDATP)](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-atp/windows-defender-advanced-threat-protection) scans content for a label and applies corresponding WIP protection - Windows 10, version 1809 - [Sensitivity labels](https://docs.microsoft.com/office365/securitycompliance/labels) need to be configured in the Office 365 Security & Compliance Center -- WIP policy needs to be applied to endpoint devices. For more information, see: - - [Create a WIP policy using Intune for Mobile Device Management (MDM)](windows-information-protection/create-wip-policy-using-intune-azure.md) - - [Create a WIP policy using Intune for Mobile Application Management (MAM)](windows-information-protection/create-wip-policy-using-mam-intune-azure.md) +- [WIP policy](windows-information-protection/create-wip-policy-using-intune-azure.md) needs to be applied to endpoint devices. +