From e2749573a64fc6019f690c162a1164a2f111b190 Mon Sep 17 00:00:00 2001
From: VLG17 <41186174+VLG17@users.noreply.github.com>
Date: Mon, 25 Jan 2021 15:26:33 +0200
Subject: [PATCH] update hybrid scenario naming and add link to description

https://github.com/MicrosoftDocs/windows-itpro-docs/issues/8703
---
 .../create-wdac-policy-for-fully-managed-devices.md             | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/security/threat-protection/windows-defender-application-control/create-wdac-policy-for-fully-managed-devices.md b/windows/security/threat-protection/windows-defender-application-control/create-wdac-policy-for-fully-managed-devices.md
index bec0d684e1..643145b624 100644
--- a/windows/security/threat-protection/windows-defender-application-control/create-wdac-policy-for-fully-managed-devices.md
+++ b/windows/security/threat-protection/windows-defender-application-control/create-wdac-policy-for-fully-managed-devices.md
@@ -42,7 +42,7 @@ Alice previously created a policy for the organization's lightly-managed devices
 Alice identifies the following key factors to arrive at the "circle-of-trust" for Lamna's fully-managed devices:
 
 - All clients are running Windows 10 version 1903 or above;
-- All clients are managed by Microsoft Endpoint Manager (MEM) either with Configuration Manager (MEMCM) standalone or hybrid mode with Intune;
+- All clients are managed by Microsoft Endpoint Manager (MEM) either with Configuration Manager (MEMCM) standalone or [Co-Managed](https://docs.microsoft.com/en-us/mem/configmgr/comanage/overview) with Intune;
 
 > [!NOTE]
 > Microsoft Endpoint Configuration Manager was previously known as System Center Configuration Manager (SCCM)