DeltaPulse now has a public MCP server. Add / integrate this tool with your Copilot Agent(s).

MCP Documentation

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

Message ID
MC1220762
View in Message Center
Service
Microsoft Defender XDR
Category
Plan for Change
Tags
Major Change User impactAdmin impactRetirement
Act By
January 31, 2027
Rollout
February 2026January 2027February 2027

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.

Details

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.

Change History

Show
January 28, 2026 at 6:30 PM Updated
Summary
Previous
Microsoft Defender for Endpoint (MDE) and XDR Advanced Hunting APIs will retire 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. No automatic migration will occur.
New
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 Date
Previous
2026-01-26T20:42:25.013Z
New
2026-01-28T17:09:23.540Z
Body Content
Previous

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

[Introduction]

We’re retiring the Microsoft Defender for Endpoint (MDE) API and 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.

New

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.

January 26, 2026 at 10:30 PM Updated
Title
Previous
Retirement notice: MDE and XDR APIs retiring; migrate to Microsoft Graph Security API
New
(Updated) Retirement notice: MDE and XDR Advanced Hunting APIs retiring; migrate to Microsoft Graph Security API
Summary
Previous
New
New
Microsoft Defender for Endpoint (MDE) and XDR Advanced Hunting APIs will retire 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. No automatic migration will occur.
Last Updated Date
Previous
2026-01-22T00:47:21.860Z
New
2026-01-26T20:42:25.013Z
Tags
Previous
User impact,Admin impact,Retirement
New
Updated message,User impact,Admin impact,Retirement
Body Content
Previous

[Introduction]

We’re retiring the Microsoft Defender for Endpoint (MDE) API and XDR 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 API or XDR 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 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.

New

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

[Introduction]

We’re retiring the Microsoft Defender for Endpoint (MDE) API and 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.

Never Miss a Microsoft 365 Update

Join thousands of IT professionals who rely on DeltaPulse for real-time Microsoft 365 change intelligence, automated notifications, and community insights.