(Updated) Microsoft Defender for Endpoint: Migrate legacy MMA devices by February 2027
Action date
What the notice says
Microsoft's text, with its sections, lists and tables; source markup removedUpdated September 4, 2026: We have updated the content. Thank you for your patience.
What and why
We detected devices in your organization that are using Microsoft Defender for Endpoint protection delivered through the Microsoft Monitoring Agent (MMA) and System Center Endpoint Protection (SCEP) on legacy Windows operating systems.
Support for MMA-based protection on Windows 7 and Windows Server 2008 R2, 2012 R2, and 2016 will retire on February 26, 2027. To maintain Microsoft Defender for Endpoint protection and continue receiving supported security capabilities, you must migrate affected devices to the current Defender agent before that date.
For eligible devices, you can use the Defender deployment tool to simplify migration. Existing device records and device timelines will be preserved during the migration process.
Microsoft is also working on a replacement solution for Windows 8.1 devices. Additional guidance will be shared when available.
Rollout schedule
- February 26, 2027: MMA-based Microsoft Defender for Endpoint protection retires for affected legacy Windows operating systems.
Impact on your organization
Who is affected
Organizations with devices running:
- Windows 7
- Windows Server 2008 R2
- Windows Server 2012 R2
- Windows Server 2016
that are using Microsoft Defender for Endpoint through the Microsoft Monitoring Agent (MMA).
Platforms and services
- Microsoft Defender for Endpoint
- Microsoft Defender XDR
- Windows 7
- Windows Server 2008 R2
- Windows Server 2012 R2
- Windows Server 2016
What will happen
- MMA-based Microsoft Defender for Endpoint protection will retire on February 26, 2027.
- Devices that are not migrated before the retirement date may no longer receive expected Defender functionality.
- Device objects and historical device timelines will be preserved during supported migrations using the Defender deployment tool.
- Windows 8.1 devices do not yet have a replacement agent. Additional guidance will be provided in a future communication.
Action required and recommendations
Complete the following actions by February 25, 2027:
- Identify devices in your environment that are using MMA-based Microsoft Defender for Endpoint protection.
- Review migration guidance and device eligibility requirements.
- Use the Defender deployment tool to migrate eligible devices to the current Defender agent.
- Plan and schedule maintenance windows for affected devices.
- Review your strategy for Windows 8.1 devices and prepare for future migration guidance.
Learn more
- Deploy Microsoft Defender endpoint security to Windows devices using the Defender deployment tool | Microsoft Defender for Endpoint | Microsoft Defender | Microsoft Learn
- Updating MMA on Windows devices for Microsoft Defender for Endpoint | Microsoft Defender for Endpoint | Microsoft Defender | Microsoft Learn
Compliance considerations
No compliance considerations identified, review as appropriate for your organization.
- Deploy Microsoft Defender endpoint security to Windows devices using the Defender deployment tool | Microsoft Defender for Endpoint | Microsoft Defender | Microsoft Learn
- Updating MMA on Windows devices for Microsoft Defender for Endpoint | Microsoft Defender for Endpoint | Microsoft Defender | Microsoft Learn
What changed
Between the versions this installation saw, newest firstThis installation has seen one version of this notice, first on 22 Oct 2026. Later changes will show here.
Linked documentation
Microsoft pages the notice links toThe notice links to no Microsoft Learn or Support page that this installation reads.
Related public evidence
No related evidence found in this installation's recent collection. This does not establish that no announcement exists.
Not confirmed here
What this page cannot tell you- Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
- Versions before 22 Oct 2026: this installation first saw the notice after Microsoft posted it.
- Some history or links were left out of the website export to keep it within its size limits.