Microsoft Threat Actor Naming
Doc updateThe Diamond Sleet entry now links to a different Microsoft Security blog article about North Korean threat-actor tradecraft; its listed aliases and country are unchanged.
Daily Defender NewsThe period’s most consequential change is a revised Defender for IoT micro agent retirement date, repeated across deployment, configuration, tutorial, and API guidance. Other meaningful updates include the imminent retirement of two classic Defender for Identity alerts, clearer Defender for Endpoint verification and offboarding requirements, and an announced public preview for unified RBAC in Defender for Cloud Apps App Governance.
Across the micro agent deployment and support guidance, the planned retirement date changed from June 1, 2027, to August 15, 2027. Use the revised date for deployment, migration, and lifecycle planning.
The Suspected identity theft (pass-the-hash) and Remote code execution attempt classic alerts will be retired at the end of November 2026. The documented alternatives are Defender for Endpoint behavioral blocking and containment, plus custom detections in Advanced hunting.
The Windows Defender Deployment Tool guidance now states that online connections require TLS 1.2, proxies used during offboarding must be supplied with -Proxy, and documents proxy selection order on Windows Server 2008 R2 SP1. The -Passive description was also updated.
Get-MpPreference now documents PerformanceModeStatus as 1 when performance mode is enabled and 0 when disabled, which is the opposite of the Intune values. The guidance also directs administrators to See volumes in Windows Security to check an individual volume’s status.
Microsoft 365 Message Center says Defender for Cloud Apps App Governance will support unified Defender XDR RBAC in public preview starting in late November 2026, with rollout completing by mid-January 2027. Custom roles will support delegated viewing, policy, and service management for non-human identities.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
The Diamond Sleet entry now links to a different Microsoft Security blog article about North Korean threat-actor tradecraft; its listed aliases and country are unchanged.
Microsoft Defender for Cloud Apps' App Governance will support unified Defender XDR RBAC in public preview starting late November 2026, enabling delegated, least-privilege access for managing Non-Human Identities. Administrators can assign custom roles for viewing, policy, and service management, with rollout completing by mid-January 2027.
The page now refers to an “MDI sensor” and updates the Sensor activation path to Settings > Identities > Sensors. The page author metadata also changed.
The page author changed from Abbyweisberg to Chrisda, and wording in the Timeline tab description was revised.
The documentation now explains that `Get-MpPreference` reports `PerformanceModeStatus` as `1` when enabled and `0` when disabled, opposite to Intune values. It also directs administrators to **See volumes** in Windows Security to check a volume’s status.
Reviewer and author metadata were updated, and an apostrophe was standardized in the note about monthly security fixes and release notes.
The Defender for Endpoint What's New page now describes per-feature controls for eligible preview features and embedded Windows offboarding through the Defender deployment tool, including keys, package expiry dates, and .exe or .zip downloads.
The page now states that online connections require TLS 1.2 and that proxy use during offboarding must be supplied with `-Proxy`. It also documents proxy selection order on Windows Server 2008 R2 SP1 and updates the `-Passive` description.
The page removes one reviewer from its metadata and changes dash and quotation characters in two release-note entries.
The page’s reviewer and author metadata changed, and the wording in the endpoint security updates link was adjusted.
The page now uses Microsoft Defender and Identity Security terminology, removes “Preview” from the title, updates section wording, and changes the incident description to reference Identity Security.
The Suspected identity theft (pass-the-hash) and Remote code execution attempt classic alerts will be retired at the end of November 2026. Monitoring alternatives are Microsoft Defender for Endpoint behavioral blocking and containment, and custom detections in Advanced hunting.
The page corrects a spelling error in “Microsoft Defender for Identity” and updates the active-identities description to reference activity detected by Microsoft Defender.
The documented Defender for IoT micro agent retirement date changed from June 1, 2027, to August 15, 2027.
The documentation now states that Defender for IoT plans to retire the micro agent on August 15, 2027, instead of June 1, 2027.
The documented Defender for IoT micro agent retirement date changed from June 1, 2027, to August 15, 2027.
The documented retirement date changed from June 1, 2027, to August 15, 2027.
The planned micro agent retirement date changed from June 1, 2027, to August 15, 2027.
The planned Defender for IoT micro agent retirement date changed from June 1, 2027, to August 15, 2027.
The documented retirement date changed from June 1, 2027, to August 15, 2027.
The documented planned retirement date for the Defender for IoT micro agent changed from June 1, 2027, to August 15, 2027.
The documented planned retirement date changed from June 1, 2027, to August 15, 2027.
The planned Defender for IoT micro agent retirement date changed from June 1, 2027, to August 15, 2027.
The documented retirement date changed from June 1, 2027, to August 15, 2027.
The planned Defender for IoT micro agent retirement date changed from June 1, 2027, to August 15, 2027.
The documentation now states that Defender for IoT plans to retire the micro agent on August 15, 2027, instead of June 1, 2027.
The documentation updates the planned Defender for IoT micro agent retirement date from June 1, 2027, to August 15, 2027.
The planned micro agent retirement date changed from June 1, 2027, to August 15, 2027.
The documented retirement date changed from June 1, 2027, to August 15, 2027.
The planned micro agent retirement date changed from June 1, 2027, to August 15, 2027.
The planned Defender for IoT micro agent retirement date changed from June 1, 2027, to August 15, 2027.
The planned Defender for IoT micro agent retirement date changed from June 1, 2027, to August 15, 2027.
The planned Defender for IoT micro agent end date changed from June 1, 2027, to August 15, 2027.
The documented planned end date changed from June 1, 2027, to August 15, 2027.
The planned Defender for IoT micro agent retirement date changed from June 1, 2027, to August 15, 2027.
The planned Defender for IoT micro agent retirement date changed from June 1, 2027, to August 15, 2027.
The documented planned retirement date changed from June 1, 2027, to August 15, 2027.
The documentation now states that the Defender for IoT integration with Azure IoT Hub plans to retire on August 15, 2027. Two internal reference links were also updated.
The documented planned retirement date changed from June 1, 2027, to August 15, 2027.
The planned end date changed from June 1, 2027, to August 15, 2027.