MC1220762 - Retirement notice: MDE and XDR Advanced Hunting APIs retiring; migrate to Microsoft Graph Security API

Message Center

Summary

Microsoft is retiring the Microsoft Defender for Endpoint and Defender XDR Advanced Hunting APIs by February 1, 2027. Organizations must manually migrate workflows to the Microsoft Graph Security API by January 31, 2027, to ensure continued functionality and improved security integration.

Last Updated

Jan 28, 2026

Published Jan 22, 2026

View version history

Service

Microsoft Defender XDR

Tag

Major change
Updated message
User impact
Admin impact
Retirement

Act by

Jan 31, 2027

More information

Updated January 26, 2026: We have updated the content. Thank you for your patience. 

Introduction

We’re retiring the Microsoft Defender for Endpoint (MDE) Advanced Hunting API and Microsoft Defender XDR Advanced Hunting API and transitioning customers to the Microsoft Graph Security API. This update aligns our security integrations with a unified interface and schema across Microsoft Defender products. The Microsoft Graph Security API provides broader data coverage, improved consistency, and better scalability for automation and security workflows.

When this will happen 

  • Retirement start: February 6, 2026
  • Full retirement: February 1, 2027
  • After February 1, 2027, the MDE and XDR APIs will no longer function.

How this affects your organization

Who is affected: 

  • Organizations using the MDE or XDR Advanced Hunting API for automation, integration, or custom workflows.
  • You are receiving this message because our reporting indicates your organization may be using these APIs.

What will happen:

  • The MDE and XDR Advanced Hunting APIs will stop functioning after February 1, 2027.
  • Existing scripts, automations, and workflows that rely on these APIs will fail if not updated.
  • The Microsoft Graph Security API will be the supported API for accessing Microsoft security data.
  • No automatic migration will occur; manual updates will be required.

What you can do to prepare

  • Migrate all existing API workflows to the Microsoft Graph Security API by January 31, 2027.
  • Update internal documentation, automation scripts, and integration endpoints to use the Microsoft Graph Security API.
  • Communicate these changes to your security operations, engineering, and development teams.
  • Review Microsoft documentation to plan your migration: Use the Microsoft Graph security API.
  • If your organization uses custom solutions, validate that new queries and response schemas work as expected before the retirement date.

Learn more:

Compliance considerations

No compliance considerations identified. Review as appropriate for your organization.

Version history

3 versions tracked

Updated 2 times since Jan 22, 2026. Microsoft Message Center only ever shows the current version; this archive preserves the history.

Compare any two versions

From
To
  1. Jan 28, 2026 · 05:09 PMLatest · v3

    Changed: Body

  2. Jan 26, 2026 · 08:42 PMv2

    Changed: Title, Body, Tags

  3. Jan 22, 2026 · 12:47 AMOriginal · v1

    Changed: Initial version