From c23a9a27b9d026b02c810436aa3ca5a5bbe3b33b Mon Sep 17 00:00:00 2001
From: Bill Mcilhargey <19168174+computeronix@users.noreply.github.com>
Date: Fri, 27 Jul 2018 15:12:09 -0400
Subject: [PATCH] added MDM reference for Fallbacksources in WDAV

MDM is not mentioned as a possible management point for WDAV Sources.  This adds the MDM part and the policy to reference to configure the fall back sources.
---
 .../manage-protection-updates-windows-defender-antivirus.md   | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/windows/security/threat-protection/windows-defender-antivirus/manage-protection-updates-windows-defender-antivirus.md b/windows/security/threat-protection/windows-defender-antivirus/manage-protection-updates-windows-defender-antivirus.md
index 5eab19050c..fe09121625 100644
--- a/windows/security/threat-protection/windows-defender-antivirus/manage-protection-updates-windows-defender-antivirus.md
+++ b/windows/security/threat-protection/windows-defender-antivirus/manage-protection-updates-windows-defender-antivirus.md
@@ -29,6 +29,7 @@ ms.date: 04/30/2018
 - System Center Configuration Manager
 - PowerShell cmdlets
 - Windows Management Instruction (WMI)
+- Mobile Device Management (MDM)
 
 <a id="protection-updates"></a>  
 <!-- this has been used as anchor in VDI content -->
@@ -147,6 +148,9 @@ SignatureDefinitionUpdateFileSharesSouce
 See the following for more information:
 - [Windows Defender WMIv2 APIs](https://msdn.microsoft.com/en-us/library/dn439477(v=vs.85).aspx)
 
+**Use Mobile Device Management (MDM) to manage the update location:**
+
+See [Policy CSP - Defender/SignatureUpdateFallbackOrder](https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-defender#defender-signatureupdatefallbackorder) for details on configuring MDM.