1 Sep 202655d agoAct by , as Microsoft's metadata states
Schedule dates changed in the text
Date phrases in schedule sentences differ between the versions this installation saw
Seen 28 Aug 2026September 1, 2026
Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.
What the notice says
Microsoft’s text, with source markup removed
Updated August 28, 2026: We have updated the timeline. Thank you for your patience. What and Why As first announced on July 1st, automated investigation and response (AIR) for Defender for Endpoint will no longer run as a separate investigation experience or be available for manual triggering in Microsoft Defender. There is no change to AIR functionality in Microsoft Defender for Office 365. The protection capabilities of AIR are already embedded within Microsoft Defender’s always-on antivirus protection stack today. Detection and response run automatically as part of default protection, without requiring a separate investigation workflow. This change is part of our ongoing “shift left” effort to lift the onus of protection from customers by automating detection and response processes, helping ensure consistent outcomes across endpoints without reliance on a separate, manually initiated investigation experience. With this update, the standalone AIR investigation experience is removed. For on-demand investigations, teams can run full antivirus scans as needed. Rollout Schedule Transition (Worldwide, GCC, GCC High, DoD): Beginning and completing in early September 2026 Impact on Your Organization Who is affected Admins and security teams using Microsoft Defender for Endpoint and Microsoft Defender XDR Platforms/Services Microsoft Defender for Endpoint across supported platforms What will happen Manual triggering of automated investigation and response (AIR) will no longer be available. AIR will no longer run as a separate investigation experience. Detection and response will occur automatically as part of always-on antivirus protection. Full antivirus scans replace manual AIR investigations for on-demand analysis. Any playbooks, scripts, or integrations that initiate AIR will stop working after September 1, 2026, and must be updated before that date. Protection remains enabled by default. Action Required / Recommendations If you are not using AIR manually or through automation, no action is required to maintain protection. Action is required for organizations using AIR in playbooks, scripts, or integrations, as thesewill no longer function after September 1, 2026. Review and update any playbooks, scripts, or integrations that initiate AIR before September 1, 2026. Replace AIR-based workflows with full antivirus scan workflows for on-demand investigations. Update internal documentation that references AIR investigations. Inform security and helpdesk teams of this change. Learn more: Microsoft Defender Antivirus full scan considerations and best practices | Microsoft Defender for Endpoint | Microsoft Defender | Microsoft Learn Overview of automated investigations | Microsoft Defender for Endpoint | Microsoft Defender | Microsoft Learn Compliance considerations Question Answer Does the change alter how admins can monitor, report on, or demonstrate compliance activities? Yes. AIR will no longer appear as a distinct investigation type, which may affect monitoring and reporting workflows.
Updated August 28, 2026: We have updated the timeline. Thank you for your patience. What and Why As of September 1, 2026,first announced on July 1st, automated investigation and response (AIR) for Defender for Endpoint will no longer run as a separate investigation experience or be available for manual triggering in Microsoft Defender. There is no change to AIR functionality in Microsoft Defender for Office 365. The protection capabilities of AIR are already embedded within Microsoft Defender’s always-on …
· first version seen
Linked documentation
Microsoft pages the notice links to
The 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.