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.
Doc updateAction required 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.
Doc updateAction required 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.
Doc updateAction required 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.
Feature updateAction required 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.