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 NewsNew Microsoft Sentinel guidance describes moving existing deployments into the preview Integrated Security Operations Center (ISOC), alongside a tool for converting eligible analytics rules into Microsoft Defender custom detections. The period also records the planned retirement of two classic Defender for Identity alerts, deprecated Amazon Linux 2 ARM64 support for Defender for Endpoint, and a new Teams message-content hunting table in Defender for Office 365. Defender for IoT guidance moves the planned micro-agent retirement from June 1 to August 15, 2027; much of the remaining material is terminology, navigation, metadata, or documentation maintenance.
New Microsoft Sentinel guidance explains how an existing deployment can transition to Integrated Security Operations Center (ISOC), which remains in preview. It covers eligibility and permissions, connecting all workspaces, the irreversible tenant-wide transition scope, and changed discounts, pricing, and data benefits.
The documented Microsoft Defender migration tool converts eligible Microsoft Sentinel analytics rules into custom detections. Original rules remain enabled during evaluation, so administrators can validate alert behavior and dependent automation before completing the migration and disabling the originals.
The new MessageContents table provides authorized security analysts with Teams message snippets and metadata for threat investigations. Rollout runs from late September through late November 2026, with access controlled by specific permissions.
The updated guidance names Suspected identity theft (pass-the-hash) and Remote code execution attempt as retiring at the end of November 2026. It points administrators to Defender for Endpoint behavioral blocking and containment and to custom detections in Advanced hunting as monitoring alternatives.
The prerequisites guidance states that Defender for Endpoint support for Amazon Linux 2 on ARM64 was deprecated on October 31, 2026, and removes the previous last-version and support-end details.
Before opting into ISOC, verify eligibility, permissions, workspace connections, the irreversible tenant-wide scope, and billing implications. Keep original analytics rules enabled through migration validation and check dependent automation. Identity teams should review alternatives before the end-of-November alert retirement, while Amazon Linux 2 ARM64 operators should migrate to a supported distribution. IoT owners should update lifecycle plans to August 15, 2027, and Teams-hunting access remains permission-gated.
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 article now refers to identity security capabilities in Microsoft Defender instead of specifically Microsoft Defender for Identity, updates wording and terminology, and removes “(Preview)” from the Identity Explorer heading.
The documentation now covers discovering, installing, and managing workspace-level and tenant-level security content, including supported Defender content. It adds installation targets, status views, deployment requirements, and workspace and tenant installation procedures.
The November 2026 update documents reorganized navigation for organizations using Integrated Security Operations Center (ISOC). Microsoft Sentinel pages move into areas such as Investigation & response, Content management, and Threat intelligence.
The page now describes detections that correlate communication, identity, authorization, and resource signals to identify identity compromise and delegated abuse involving trusted agents.
The What's New page now describes security-for-AI coverage with detections and disruption for identity-compromise patterns that can weaponize trusted agents.
The documentation now directs administrators to **Content management > Security Store** instead of **Security Copilot > Security Store**. The page metadata date was also updated.
Adds instructions for creating integration profiles used by generated playbooks, including prerequisites, supported authentication methods, and Microsoft Graph setup.
The page removes preview qualifiers, states availability for new and existing UEBA deployments, ties Defender XDR source availability to Microsoft 365 E5 eligibility, and retains limitations.
The article removed the Preview labels and preview-scope wording for incident cases. It continues to recommend incident cases while stating that the legacy incident experience remains available.
The article’s metadata was updated, and two notes now state that available fields can vary by tenant configuration, removing the reference to preview scope.
The page now states that SLA policies are supported only in the single-tenant Microsoft Defender portal and not in multitenant environments, without the previous “During this preview” wording. An authoring metadata tag was also added.
The page no longer describes Copilot for Workbooks as being in preview. It continues to document Advanced Hunting tables as the supported data source and Log Analytics as unsupported.
The documentation now states that ISOC customers require an ISOC workspace to use threat intelligence capabilities, without limiting the requirement to preview capabilities.
The article’s custom metadata was updated, and the statement that the feature is in preview was removed.
The page adds authoring metadata and removes two ontology links plus the statement that the feature is in preview.
The page metadata was updated, and the statement that the feature is in preview was removed.
Documentation changes the included retention guidance from 30 to up to 90 days for supported Microsoft Defender data starting November 15, 2026. It also documents retention by supported table, extension up to 180 days for additional charges, and separate billing for additional Microsoft and non-Microsoft data.
The page now provides separate paths to open Automation in the Microsoft Defender portal: Microsoft Sentinel > Configuration > Automation, or Automation from the ISOC main navigation menu.
The page now states that the device-level setting enables or disables prompt evidence collection when AI agent runtime protection is configured, with a link to configuration guidance.
The documentation adds separate navigation instructions for Microsoft Sentinel in the Defender portal and ISOC, including **Automation** in the ISOC main menu.
The documentation now states that Microsoft 365 E5 customers can query supported Microsoft Defender XDR data in Advanced hunting for up to 90 days, replacing the previous 30-day period.
The documentation now directs administrators to configure prompt evidence collection for AI agent alerts and links local Windows agents to a device-level setting. Author metadata was also updated.
The page now links to the updated “How data tiers and retention work” section in Microsoft Sentinel documentation and includes updated authoring metadata.
A new Similar cases tab in the Microsoft Defender portal lists up to 20 related incidents by alert titles or entities, aiding analysts in identifying patterns. The Associated incidents card is renamed Recommended correlations. Public preview is available now; full rollout completes by early December 2026. No action required.
Microsoft added guidance on preparing query results and mapping entities, identifiers, labels, relationships, and enrichment in Defender XDR graph visualizations.
The documentation adds guidance for using **Visualize as graph** to map query-result columns to nodes and edges through Builder or JSON. It covers ontology suggestions, entity enrichment, validation, node limits, and graph exploration controls.
The documentation now explains that workbooks can use Advanced Hunting without ingesting the same data into a workspace. It also adds guidance for updating existing workbooks and clarifies that queries enforce the user's underlying data permissions.
Starting November 15, 2026, Microsoft 365 E5 customers can query supported Microsoft Defender XDR data for up to 90 days. The documentation also explains the query details shown for lookbacks over 30 days and updates Sentinel role and hunting navigation references.
The documented default remains 30 days for native Defender data, while eligible ISOC customers with supported licenses can query supported data for up to 90 days when retention is enabled and available.
The documentation now directs administrators to Investigation & response > Detection > Custom detection rules instead of Hunting > Custom detection rules for viewing rules, triggered alerts, and triggered actions.
The page now says Advanced hunting examines event data without stating the previous “past 30 days” period. Documentation metadata and date were also updated.
Microsoft Defender for Office 365 introduces a new MessageContents table in Advanced Hunting for Teams messages, enabling authorized security analysts to access Teams message snippets and metadata for improved threat investigations. Rollout is from late September to late November 2026, with access controlled by specific permissions.
The documentation no longer describes incident cases or their fields as being limited by preview scope. It continues to recommend incident cases and states that the legacy experience remains available; fields can vary by tenant configuration.
The documentation no longer describes incident cases and the legacy experience as being tied to a preview. It states that incident cases are recommended, while the legacy experience remains available.
The article now describes incident cases as the recommended experience and states that the legacy incident experience remains available, without mentioning a preview period.
The page now describes incident cases as the recommended experience without labeling them as in preview. It also confirms that the legacy incident experience remains available.
The article no longer describes incident cases or the legacy experience as being in preview. It also adds an authoring metadata tag.
The documentation now describes incident cases as the recommended experience and says the legacy incident experience remains available, without labeling incident cases as in preview.
The article now describes incident cases as the recommended experience without the previous preview wording. It confirms that the legacy incident experience remains available and that guidance applies to both.
The documentation now identifies incident cases as the recommended experience and says the legacy incident experience remains available, without labeling incident cases as preview.
The documentation now describes repository connections that deploy content to ISOC or Microsoft Sentinel workspaces, or supported Defender content to Microsoft Defender XDR at tenant scope. Tenant targets support Defender workbooks and custom detections, and don't require a workspace.
The setup step now refers to **Subscriptions** instead of **Subscription**, and the accompanying screenshot description and lightbox link were refreshed. Documentation metadata was also updated.
The instructions now direct users through Investigation & response > Detection > Custom detection rules after selecting Create. Page metadata was also refreshed.
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 article explains how Microsoft Defender detects and disrupts device-code phishing against GitHub Copilot CLI before downstream resource abuse. It documents required licensing, connector, Safe Links, and GitHub EMU prerequisites.
Microsoft Defender for Office 365 will tag promotional emails as “promotions” and can auto-move them to a Promotions folder, learning from user actions. Public preview starts mid-April 2026; general rollout begins late July 2026. Admins control settings; users can train the system by moving messages.
Eligible customers with existing Microsoft Sentinel deployments can choose to transition to ISOC, while customers without Sentinel can use ISOC directly. Supported Defender-level Content hub and CI/CD content can be deployed at tenant scope without an ISOC workspace; SOC optimization also no longer requires one.
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 documentation now states that Defender for Endpoint support for Amazon Linux 2 on ARM64 was deprecated on October 31, 2026, and removes the previous last-version and support-end details.
The documentation now describes the PromptEvidenceCollection setting, PowerShell commands to manage it, required Defender Antivirus platform and engine versions, and managed-policy precedence.
The documentation adds prompt evidence collection for AI agent runtime protection, including its Audit/Block prerequisites, alert behavior, upcoming default enablement, privacy considerations, and PowerShell or policy-template configuration.
Starting with version 101.26091.0003, Defender for Endpoint on Linux requires `iptables`; RPM packages also require `libacl`. The installer script and Defender deployment tool install these dependencies automatically.
The documentation now directs administrators to Investigation & response > Detection > Custom detection rules instead of the previous Hunting location.
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 article title, description, and affected passages now use Microsoft Defender and identity security terminology. Wording about NNR correlation, alert evidence, sensor health, unresolved entities, and optional NNR methods was refreshed, and metadata was updated.
The page title, headings, descriptions, and access guidance now refer to “identity security posture assessments” instead of “Defender for Identity security posture assessments.” The licensing requirement is specified as a Microsoft Defender for Identity license.
The page title, description, and body now refer to identity security health issues and deployments in Microsoft Defender instead of Microsoft Defender for Identity. The existing sensor and domain-related alert guidance remains, with the page metadata date updated.
The Defender for Identity sensor v2.x-to-v3.x migration article now refers to the Sensor Management tab instead of the Sensors page, including updated navigation and status instructions.
The article title and wording were revised to use “Certificate security posture assessments” and “Microsoft Defender.” Internal authoring links were removed, and the ESC4 section was renamed as an Identity Security assessment.
The page title and introductory text now refer to Microsoft Defender instead of Microsoft Defender for Identity. The content continues to cover cloud identity assessments for Okta, CyberArk Identity, and SailPoint Identity Security Cloud, including security risks and remediation recommendations. Related metadata links were also updated.
The page now uses Microsoft Defender and identity security terminology in its introduction, health-alert text, and automatic event-collection heading. The documented servers, settings, automatic configuration behavior, and sensor v3.x known issue remain described.
The page title, description, heading, and introductory text were shortened, and two internal authoring links were removed.
The FAQ date was updated, and references to deployment health and domain-controller traffic now use “identity security” terminology in Microsoft Defender.
The page title, description, and heading now use “Account security posture assessments” and refer to “Identity Security posture assessments.”
The page title, heading, and introductory text now refer to “Group Policy security posture assessments” instead of “Group policy security assessments.”
Updated section headings and capitalization for “Identity Security” terminology throughout the page.
The page now refers to identity security detections in Microsoft Defender instead of Defender for Identity detections and updates the related event-auditing guidance. The page date was also updated.
The documentation now states that Microsoft Defender identity security detections require millisecond data and updates the page date. The QRadar agentless Windows event collection prerequisite and reference link remain.
The page now describes creating a subscription for identity security event collection in Microsoft Defender. Its publication date was also updated to November 11, 2026.
The page now describes identity security detection in Microsoft Defender instead of Defender for Identity detection, and its metadata date was updated to November 11, 2026.
The page now lists AccountInfo among available hunting tables, separates sensor management from health issue notifications, and documents availability for areas such as Domain page, Alert tuning, Identity Explorer, and Identity reports. It also explains visibility and device-onboarding behavior for AD domain-scoped users.
The page now directs administrators to Settings > Identities > On-premises > Sensor Management. It also updates the steps to use the v2.x sensor row actions menu and Settings option, and refreshes related labels and screenshot text.
The procedure now directs administrators to Settings > Identities > On-premises > Sensor Management in the Microsoft Defender portal, then to open the sensor row actions menu and select Settings.
The page now uses updated Microsoft Defender and Microsoft Defender for Endpoint naming and refers to activating sensor v3.x. The publication date was also updated.
The page now describes monitoring, profiling, and forest mapping with Microsoft Defender rather than Defender for Identity. Its metadata was also updated.
The documented default capacity increased from 350 to 1,000 sensors. Low-memory health issues are now reported in the Microsoft Defender portal.
The article’s wording was updated to clarify that port mirroring applies to Microsoft Defender for Identity standalone sensors and is required for them to see network traffic. The support-table heading and publication date were also updated.
The page date and wording were updated, including Microsoft Defender naming, grammar, and descriptions of the 30-credential default and Deleted Objects permissions.
The page date and wording were updated to advise avoiding the same managed-action gMSA account on servers other than domain controllers. The text explains that a compromised server could expose the password and enable password changes or account disabling.
The page’s date was updated, and the workspace-details instruction now refers to the Microsoft Defender portal instead of the Microsoft Defender XDR portal.
The page now says that read-only permissions on the Deleted Objects container allow Microsoft Defender to detect user deletions in Active Directory.
The licensing prerequisite now says “Microsoft Defender for Identity” instead of “Defender for Identity” when describing included licenses such as E5.
The prerequisite now spells out “Microsoft Defender for Identity” instead of “Defender for Identity” in the license requirement.
The page updates the Microsoft Defender portal navigation to Settings > Identities > Manage action accounts and revises terminology for identity security and automatic auditing guidance. The page date was also updated.
The page updates its date, replaces some references to Defender for Identity with Microsoft Defender, and clarifies the mixed sensor v3.x/v2.x workspace example.
The documentation adds Enterprise-level onboarding alongside Organization-level connections. Enterprise connections cover all organizations through one connector and automatically disable existing organization-level connectors in that enterprise.
The GitHub connector now supports Organization-level and Enterprise-level connections. An Enterprise connection covers all organizations in the enterprise and improves visibility and protection against identity-driven attacks, including device code phishing targeting GitHub Copilot CLI.
The documentation now states that an alert is generated once for each new app not discovered in the last 180 days, replacing the previous 90-day window.
The comparison table now spells out “Yes” indicators and adds entries for attack surface reduction, next-generation protection, centralized configuration and administration, and APIs and integration. Page metadata was also refreshed.
Starting November 1, 2026, machines are billed only when protected by Plan 1 or Plan 2 and in a billable power state. Plan 1 billing now distinguishes desktop devices from servers by operating-system and device information, with updated agent and classification rules.
The documentation updates supported and unsupported region lists, including changes involving Australia Central, Denmark East, India South Central, Malaysia West, and other regions.
The documentation now states that the Microsoft Defender for Endpoint agent is required for Plan 1 capabilities on Linux and other non-Windows servers, and is needed to access the full Plan 1 capability set.
The documentation now states that the Microsoft Defender for Endpoint agent is required for the full set of Plan 1 capabilities, including on Linux and other non-Windows servers.
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.
New guidance explains how to review SOC optimization recommendations and use the preview migration tool to convert eligible analytics rules into custom detections, validate them, and complete migration.
New documentation explains how to opt an existing Microsoft Sentinel deployment into Integrated Security Operations Center (ISOC), including prerequisites, workspace connection requirements, permanent transition limits, and billing changes. ISOC is identified as being in preview.
A new page explains how to use the Microsoft Defender SOC optimization migration tool to convert eligible Microsoft Sentinel analytics rules into custom detections, validate results, and complete migration.
Adds instructions for creating a temporary Microsoft Defender alert-tuning rule that auto-resolves evaluation alerts containing `#EVAL`, including prerequisites, configuration, and validation steps.
The documentation now states that the recommendations API returns “Lower Defender data costs” recommendations with the recommendationTypeId `Precision_XdrIngestion_TableMigration`.
The instructions now direct administrators to Investigation & response > Detection > Analytics instead of Microsoft Sentinel > Configuration > Analytics in the Defender portal.
A new article outlines prerequisites and operational steps for moving MSSP-managed Microsoft Sentinel deployments to ISOC in Microsoft Defender, including updating content profiles, CI/CD pipelines, detections, workbooks, automation, delegated access, and permissions. It also notes that ISOC is in preview.
A new Microsoft Learn page explains ISOC data handling, supported Microsoft and non-Microsoft sources, table retention and tier settings, and up to 90 days of included retention for eligible customers beginning November 15, 2026.
The article now covers managing tables, tiers, and retention, including supported table types, XDR and Basic Logs management limitations, retention tiers, regional availability, ISOC guidance, and updated permissions links.
A new article explains how to manually convert Microsoft Sentinel analytics rules to Microsoft Defender custom detections, including differences, limitations, and validation guidance.
The new guidance explains how to update Sentinel queries, rules, workbooks, and playbooks to use Advanced Hunting data before stopping duplicate ingestion for supported Defender XDR tables. Tables with analytics retention of 180 days or more remain ingested.
A new article explains how to update playbooks that query Log Analytics or Azure Monitor Logs to use Microsoft Defender XDR Advanced Hunting through Microsoft Graph, including query, table, timestamp, and response-format changes.
The documentation explains how to import supported Microsoft Sentinel roles and assignments into Defender RBAC, activate required Defender workloads, and validate permissions before transitioning to ISOC.
The guidance explains that existing Microsoft Sentinel deployments can have UEBA process supported Microsoft Defender XDR data directly while continuing to store outputs in Sentinel. It covers workspace and DCR behavior, with DeviceLogonEvents currently supported.
The page now links separately to Sentinel and ISOC guidance for managing tables, tiers, and retention. Detailed table-type, tier, retention, and XDR cost information is consolidated under the table settings article, with a new link for ISOC eligibility and included retention.
The documentation now describes duplicating an existing automation rule, creating 1–10 copies, and optionally creating them inactive. It also updates portal navigation and a related link.
The documentation now reflects revised Microsoft Defender portal locations for Sentinel capabilities, including hunting, workbooks, threat intelligence, content management, connectors, analytics, watchlists, automation, and settings.
The documentation now describes recommendations for Microsoft Defender XDR tables ingested into Sentinel when the same data is available in Defender for 90 days. Recommendations identify dependent analytics rules, workbooks, and playbooks, and explain the effects of stopping ingestion.
The guide now reflects the current Defender portal path for Microsoft Sentinel connectors and updates retention steps to use the table details Overview and Retention tabs. Screenshots and portal labels were also refreshed.
The page now describes a Lower Defender data costs banner, progress panel, recommendation filter, and guidance for Microsoft Defender XDR tables also ingested into Sentinel. These recommendations must be marked Completed manually after the related content is updated.
The page now lists two navigation paths to Microsoft Sentinel hunting and notes incident tags, saved queries, and custom hunting tables as alternatives for preserving investigation context. It also clarifies that bookmarks remain unavailable in Advanced hunting.
The instructions now use the Defender portal’s Setup & configuration > Data management > Data & connectors path, with connector discovery on the Connectors tab. They also update the Azure Data Lake Storage connector name to Azure Data Lake Storage Gen2 and clarify how to view and manage instances.
The documentation now lists separate navigation paths for Microsoft Sentinel in the Defender portal and the ISOC main navigation menu, while retaining the Azure portal path.
Updated DevRel links and clarified how to open Automation in the Microsoft Defender portal: Microsoft Sentinel > Configuration > Automation for Microsoft Sentinel, or Automation from the ISOC main navigation. The creation steps now omit redundant navigation.
The article now documents access through Microsoft Defender integrated SOC (ISOC) using Threat intelligence > MITRE ATT&CK, retains the Microsoft Sentinel and Azure portal paths, and adds a navigation screenshot. The wording and update date were also revised.
The documentation now provides separate paths to the Automation page in the Microsoft Defender portal, ISOC main navigation, and Azure portal before selecting the Playbook templates tab.
The article now lists separate paths for Microsoft Sentinel in the Defender portal, ISOC, and the Azure portal.
The instructions now direct ISOC customers to select Dashboards & Reports > Workbooks before opening workbook templates. The remaining steps were renumbered, and related reference links were updated.
The tutorial now provides separate paths to the Automation page in the Microsoft Defender portal, including Microsoft Sentinel and ISOC navigation, while retaining the Azure portal path. Related DevRel links were also updated.
The watchlist creation steps now show separate navigation for Microsoft Sentinel and ISOC in Microsoft Defender.
The page now provides separate navigation paths for Microsoft Sentinel in the Defender portal, ISOC, and Microsoft Sentinel in the Azure portal.
The documentation states that the SAP solution for Sentinel is now included at no additional cost for active SAP production SIDs, covering development, test, and QA systems.
The guide now lists separate navigation paths for Microsoft Sentinel in the Defender portal, the ISOC main navigation menu, and the Azure portal.
The instructions now direct administrators to Investigation & response > Detection > Analytics instead of Microsoft Sentinel > Configuration > Analytics.
The instructions now direct administrators to Investigation & response > Detection > Analytics instead of Microsoft Sentinel > Configuration > Analytics. Documentation metadata and links were also refreshed.
The documentation now links to the Microsoft Defender portal and provides separate navigation paths for Microsoft Sentinel and the ISOC main navigation menu.
The documentation adds navigation paths for Microsoft Sentinel in the Defender portal and the ISOC main menu, alongside the existing Sentinel path.
The documentation specifies a $2/hour fee outside ISOC for each connected, active production SAP system identified by SID. Nonproduction and inactive systems are not charged, while systems with unknown status are billed as production. It also notes that the per-system fee is removed under the announced ISOC pricing change.
The Microsoft Sentinel documentation now directs users to Investigation & response > Detection > Analytics in the Defender portal. The Azure portal path remains unchanged.
The documentation now directs administrators to Investigation & response > Detection > Analytics instead of Microsoft Sentinel > Configuration > Analytics.
The documentation now directs users to Investigation & response > Detection > Analytics instead of Microsoft Sentinel > Configuration > Analytics. Metadata and reference links were also refreshed.
The documentation now lists two Microsoft Defender portal paths to Hunting: the existing Microsoft Sentinel > Threat management > Hunting path and Investigation & response > Hunts in the ISOC main navigation.
The documentation now lists the Microsoft Sentinel and ISOC navigation paths where bookmarks remain available and suggests incident tags, saved queries, and custom hunting tables as alternatives.
The overview now shows updated screenshots for the content hub, MITRE ATT&CK coverage, and incident Attack story. It also documents the path to Microsoft Sentinel connectors: Setup & configuration > Data management > Data & connectors > Connectors > Classic connectors - Microsoft Sentinel.
The documentation now provides package-specific paths to the Automation page, including Microsoft Sentinel in the Defender portal and the ISOC main navigation menu.
The documentation adds the ISOC navigation path for Watchlists and updates related ontology links.
The instructions now list two Defender portal paths to Hunting: Microsoft Sentinel > Threat management > Hunting and Investigation & response > Hunts.
The instructions now direct administrators to Investigation & response > Detection > Analytics instead of Microsoft Sentinel > Configuration > Analytics. Page metadata and taxonomy links were also refreshed.
The documentation now directs Defender portal users to Investigation & response > Notebooks. The Azure portal path is unchanged.
The article now directs administrators to **Investigation & response > Summary rules** instead of **Microsoft Sentinel > Configuration > Summary rules**. It also updates metadata and adds two ontology links.
The documentation now includes Microsoft Defender ISOC menu paths for accessing Watchlists and Analytics, alongside the existing Sentinel portal paths.
The documentation now directs administrators to Setup & configuration > Data management > Data & connectors, the Connectors tab, and Classic connectors - Microsoft Sentinel to view installed or in-use connectors. The accompanying screenshot was updated.
The prerequisite text remains unchanged: the UEBA behaviors layer generates behaviors only when supported data sources are connected and actively sending logs to the Analytics tier. The linked data-tier and retention guidance was updated.
The Microsoft Sentinel Notebooks location in the Defender portal is now **Investigation & response** > **Notebooks**. The Azure portal path remains under **Threat management**.
The documentation wording about the default 30-day Analytics-tier retention, data availability, and ingestion of XDR tables into Analytics and data lake tiers was updated.
The documentation now directs administrators to Defender portal > Setup & configuration > Data management > Data & connectors, then the Tables tab.
The guidance identifies affected Defender XDR tables, column and data-type differences, and required updates for queries, detections, workbooks, and automation when transitioning Microsoft Sentinel content.
Adds guidance for creating or updating workbooks to query Microsoft Defender XDR data through Advanced Hunting, including prerequisites, permissions, schema differences, and cross-workspace behavior.
The documentation now lists Microsoft Sentinel and ISOC navigation paths for opening hunting, and adds alternatives for preserving investigation context when using bookmarks.
The documentation now lists separate paths to the Automation page in the Defender portal, including the ISOC main navigation route. The Azure portal path remains documented separately.
Microsoft added guidance for using migration reports, matching blocker codes, safely editing and validating Microsoft Sentinel analytics rules, and reassessing migration eligibility.
The FAQ no longer includes the bullet explaining that Codename MDASH dynamically executes triggering inputs to validate vulnerability preconditions. Its model-agnostic architecture paragraph remains documented.