Managing third-party antivirus transition to MDE

Published Jan 11, 2024 • Updated May 1, 2026

Overview

Moving from legacy AV to Microsoft Defender for Endpoint needs a coexistence and cutover plan to avoid coverage gaps.

Discovery

  1. Inventory current AV: vendor, central console, policy features (firewall, device control, web filter).
  2. Map feature parity gaps—plan compensating controls (e.g., web filtering via proxy or DNS).

Coexistence phase

  • Follow Microsoft and third-party limited periodic scanning or passive mode guidance; do not run two active real-time scanners without vendor approval.
  • Validate policy import: exclusion lists, USB rules, custom IOCs.

Cutover

  1. Push MDE onboarding and confirm active protection.
  2. Remove or disable old AV agent via vendor’s clean removal tool (not Add/Remove only).
  3. Reboot if required; verify single AV reporting healthy in services and Defender status.

Validation window

Monitor for 7 days: performance complaints, app blocks, and missed detection tests.

Commercial notes

Align renewal cancellation with cutover date; capture savings in QBR.

Related Articles

EDR deployment checklist for new workstations

## Overview Use this runbook when onboarding a new Windows workstation or re-imaging a device that...

security-endpoint-protection msp +1

Handling Defender for Business false positives

## Overview False positives waste analyst time and train users to ignore alerts. This article stand...

security-endpoint-protection msp +1

Application allowlisting with Windows Defender ASR rules

## Overview Attack Surface Reduction (ASR) rules reduce exploit surface by constraining Office macr...

security-endpoint-protection msp +1