Public mode

No tenant, Graph, or device access. Every item links to its source. What this means

Some sources or documents need attention: 253/255 feeds/APIs · 417/444 docs · checked 12:24 UTC Customize Public modeDiscuss ChangeIntel on Discord

(Updated) Retirement notice: MDE and XDR Advanced Hunting APIs retiring; migrate to Microsoft Graph Security API

Versions captured by this deployment. Earlier versions and notices may be missing; first observed is not first published.

Action date

in 3 months Act by , as Microsoft's metadata states
Microsoft's start date
22 Jan 2026
Last changed by Microsoft
28 Jan 2026
First seen here
19 Oct 2026
Versions seen
1

What the notice says

Microsoft's text, with its sections, lists and tables; source markup removed

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.

What changed

Between the versions this installation saw, newest first

This installation has seen one version of this notice, first on 19 Oct 2026. Later changes will show here.

Linked documentation

Microsoft pages the notice links to

The notice links to no Microsoft Learn or Support page that this installation reads.

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 19 Oct 2026: this installation first saw the notice after Microsoft posted it.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Oct 12:24 UTC · 253 of 255 readable · 252 fully read · documentation 417/444 current