← Previous day

Next day →
Day in brief

Sentinel ISOC preview details tenant transition and analytics-rule migration paths

The period’s consequential Sentinel changes are new guidance for the preview Integrated Security Operations Center (ISOC): existing deployments can transition under an irreversible tenant-wide scope, and eligible analytics rules can be converted to Defender custom detections and validated before cutover. Other material updates cover promotional-mail handling in Defender for Office 365, Defender for Servers billing rules, and the deprecation of Defender for Endpoint support for Amazon Linux 2 ARM64. Much of the remaining update set is lower-impact Identity terminology and portal-navigation cleanup, including revised Sensor Management paths.

  • New Microsoft Sentinel guidance identifies ISOC as a preview capability and explains how existing deployments opt in. It calls for eligibility and permission checks, connection of all workspaces, and review of changed discounts, pricing, and data benefits; the transition is described as irreversible at tenant scope.

  • The new migration procedure explains how to convert eligible Microsoft Sentinel analytics rules into Microsoft Defender custom detections, validate the results, and complete migration. Original rules remain enabled during evaluation and should be disabled only after alert behavior and dependent automation have been checked.

  • A Microsoft 365 Message Center major update says promotional messages will be tagged as “promotions” and can be moved automatically to a Promotions folder, with the system learning from user actions. The notice lists public preview beginning in mid-April 2026 and general rollout beginning in late July 2026; administrators control the settings.

  • The updated Defender for Servers FAQ states that from November 1, 2026, machines are billed only when protected by Plan 1 or Plan 2 and in a billable power state. Plan 1 billing also distinguishes desktop devices from servers using operating-system and device information, with updated agent and classification rules.

  • The Linux 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.

This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.

150 updates

23

Investigate Users

Doc update

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.

Whats New

Feature update

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.

Defender Security For Ai

New feature

The page now describes detections that correlate communication, identity, authorization, and resource signals to identify identity compromise and delegated abuse involving trusted agents.

Whats New

New feature

The What's New page now describes security-for-AI coverage with detections and disruption for identity-compromise patterns that can weaponize trusted agents.

Security Copilot Agents Defender

Doc update

The documentation now directs administrators to **Content management > Security Store** instead of **Security Copilot > Security Store**. The page metadata date was also updated.

Extend Ueba

Doc update

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.

Siem Defender Case Management

Doc update

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.

Manage Cases

Doc update

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.

Case Sla Policies

Doc update

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.

Defender Copilot Workbooks

Doc update

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.

Defender Threat Intelligence

Doc update

The documentation now states that ISOC customers require an ISOC workspace to use threat intelligence capabilities, without limiting the requirement to preview capabilities.

Siem Defender Automation

Doc update

The article’s custom metadata was updated, and the statement that the feature is in preview was removed.

Okta Attack Disruption

Doc update

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.

Ai Agent Real Time Protection

Doc update

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.

Scoping

Doc update

The documentation adds separate navigation instructions for Microsoft Sentinel in the Defender portal and ISOC, including **Automation** in the ISOC main menu.

Data Privacy

Feature update

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.

Ai Agent Detection Protection

Doc update

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.

Audit Retain Case Data

Doc update

The page now links to the updated “How data tiers and retention work” section in Microsoft Sentinel documentation and includes updated authoring metadata.

8

Manage Incident Cases

Doc update

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.

Investigate Incident Cases

Doc update

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.

Manage Incident Case Merging

Doc update

The article now describes incident cases as the recommended experience and states that the legacy incident experience remains available, without mentioning a preview period.

Manage Incident Case Tasks

Doc update

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.

Merge Incident Cases Manually

Doc update

The article no longer describes incident cases or the legacy experience as being in preview. It also adds an authoring metadata tag.

Move Alert To Another Incident Case

Doc update

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.

Plan Incident Response

Doc update

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.

Prioritize Incident Cases

Doc update

The documentation now identifies incident cases as the recommended experience and says the legacy incident experience remains available, without labeling incident cases as preview.

7

Advanced Hunting Query Results

New feature

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.

Advanced Hunting Microsoft Defender

Feature update

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.

Custom Detection Manage

Doc update

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.

Api Advanced Hunting

Feature update

The page now says Advanced hunting examines event data without stating the previous “past 30 days” period. Documentation metadata and date were also updated.

3

Onboard Isoc Workspace

Doc update

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.

Pilot Deploy Investigate Respond

Doc update

The instructions now direct users through Investigation & response > Detection > Custom detection rules after selecting Create. Page metadata was also refreshed.

1
1

Isoc Overview

Feature update

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.

1
5

Mde Linux Prerequisites

RetirementAction required

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.

Configure Ai Agent Runtime Protection

Feature update

The documentation now describes the PromptEvidenceCollection setting, PowerShell commands to manage it, required Defender Antivirus platform and engine versions, and managed-policy precedence.

Ai Agent Runtime Protection Overview

Feature update

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.

Microsoft Defender Endpoint Releases

Feature updateAction required

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.

Aggregated Reporting

Doc update

The documentation now directs administrators to Investigation & response > Detection > Custom detection rules instead of the previous Hunting location.

29

Migrate To Sensor V3

Doc update

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.

Technical Faq

Doc update

The FAQ date was updated, and references to deployment health and domain-controller traffic now use “identity security” terminology in Microsoft Defender.

Identity Security Initiative

Doc update

Updated section headings and capitalization for “Identity Security” terminology throughout the page.

Prerequisites Sensor Version 2

Doc update

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.

Configure Event Collection

Doc update

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.

Configure Event Forwarding

Doc update

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.

Prerequisites Standalone

Doc update

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.

Configure Scoped Access

Doc update

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.

Configure Sensor Settings

Doc update

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.

Active Directory Federation Services

Doc update

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.

Activate Sensor

Doc update

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.

Capacity Planning

Feature update

The documented default capacity increased from 350 to 1,000 sensors. Low-memory health issues are now reported in the Microsoft Defender portal.

Directory Service Accounts

Doc update

The page date and wording were updated, including Microsoft Defender naming, grammar, and descriptions of the 30-credential default and Deleted Objects permissions.

Manage Action Accounts

Doc update

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.

Test Connectivity

Doc update

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.

Create Directory Service Account Gmsa

Doc update

The page now says that read-only permissions on the Deleted Objects container allow Microsoft Defender to detect user deletions in Active Directory.

Investigate Domain

Doc update

The licensing prerequisite now says “Microsoft Defender for Identity” instead of “Defender for Identity” when describing included licenses such as E5.

Password Protection

Doc update

The prerequisite now spells out “Microsoft Defender for Identity” instead of “Defender for Identity” in the license requirement.

2

Deploy Sensor V3

Doc update

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.

3

Protect Github

New feature

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.

Release Notes

Feature update

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.

Policies Cloud Discovery

Feature update

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.

4

Defender For Servers Overview

Doc update

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.

Faq Defender For Servers

Feature update

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.

Regional Availability

Feature update

The documentation updates supported and unsupported region lists, including changes involving Australia Central, Denmark East, India South Central, Malaysia West, and other regions.

Integration Defender For Endpoint

Feature updateAction required

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.

1

Plan Defender For Servers Select Plan

Feature updateAction required

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.

56

Migrate Playbooks To Automation Rules

Doc update

The instructions now direct administrators to Investigation & response > Detection > Analytics instead of Microsoft Sentinel > Configuration > Analytics in the Defender portal.

Transition MSSP-managed deployments to Microsoft Defender | Microsoft Learn

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.

Optimize Microsoft Defender XDR data ingestion | Microsoft Learn

Doc update

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.

Update UEBA to use Microsoft Defender XDR data | Microsoft Learn

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.

Manage Data Overview

Doc update

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.

Defender portal

New feature

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.

Microsoft Sentinel Defender Portal

Doc update

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.

Soc Optimization Reference

New feature

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.

Defender portal

Doc update

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.

Defender portal

New feature

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.

Bookmarks

Doc update

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.

Data Federation Setup

Doc update

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.

Define Playbook Access Restrictions

Doc update

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.

Create Basic Automation Rules Simple Flows

Doc update

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.

Defender portal

Doc update

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.

Use Playbook Templates

Doc update

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.

Defender portal

Doc update

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.

Tutorial Enrich Ip Information

Doc update

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.

Watchlists Create

Doc update

The watchlist creation steps now show separate navigation for Microsoft Sentinel and ISOC in Microsoft Defender.

Import Export Automation Rules

Doc update

The page now provides separate navigation paths for Microsoft Sentinel in the Defender portal, ISOC, and Microsoft Sentinel in the Azure portal.

Whats New

Feature update

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.

Defender portal

Doc update

The guide now lists separate navigation paths for Microsoft Sentinel in the Defender portal, the ISOC main navigation menu, and the Azure portal.

Defender portal

Doc update

The instructions now direct administrators to Investigation & response > Detection > Analytics instead of Microsoft Sentinel > Configuration > Analytics.

Defender portal

Doc update

The instructions now direct administrators to Investigation & response > Detection > Analytics instead of Microsoft Sentinel > Configuration > Analytics. Documentation metadata and links were also refreshed.

Generate Playbook

Doc update

The documentation now links to the Microsoft Defender portal and provides separate navigation paths for Microsoft Sentinel and the ISOC main navigation menu.

Integrations

Doc update

The documentation adds navigation paths for Microsoft Sentinel in the Defender portal and the ISOC main menu, alongside the existing Sentinel path.

Sap Applications Overview

Feature update

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.

Defender portal

Doc update

The Microsoft Sentinel documentation now directs users to Investigation & response > Detection > Analytics in the Defender portal. The Azure portal path remains unchanged.

Defender portal

Doc update

The documentation now directs administrators to Investigation & response > Detection > Analytics instead of Microsoft Sentinel > Configuration > Analytics.

Defender portal

Doc update

The documentation now directs users to Investigation & response > Detection > Analytics instead of Microsoft Sentinel > Configuration > Analytics. Metadata and reference links were also refreshed.

Hunts

Doc update

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.

Move To Defender

Doc update

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.

Defender portal

Doc update

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.

Sentinel Mcp Logic Apps

Doc update

The documentation now provides package-specific paths to the Automation page, including Microsoft Sentinel in the Defender portal and the ISOC main navigation menu.

Watchlists Manage

Doc update

The documentation adds the ISOC navigation path for Watchlists and updates related ontology links.

Hunts Custom Queries

Doc update

The instructions now list two Defender portal paths to Hunting: Microsoft Sentinel > Threat management > Hunting and Investigation & response > Hunts.

Microsoft Defender portal

Doc update

The instructions now direct administrators to Investigation & response > Detection > Analytics instead of Microsoft Sentinel > Configuration > Analytics. Page metadata and taxonomy links were also refreshed.

Public endpoint

Doc update

The documentation now directs Defender portal users to Investigation & response > Notebooks. The Azure portal path is unchanged.

Summary Rules

Doc update

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.

Watchlists Queries

Doc update

The documentation now includes Microsoft Defender ISOC menu paths for accessing Watchlists and Analytics, alongside the existing Sentinel portal paths.

Defender portal

Doc update

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.

Entity Behaviors Layer

Doc update

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.

Notebook Get Started

Doc update

The Microsoft Sentinel Notebooks location in the Defender portal is now **Investigation & response** > **Notebooks**. The Azure portal path remains under **Threat management**.

Sentinel Lake Connectors

Doc update

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.

Using Data Federation

Doc update

The documentation now directs administrators to Defender portal > Setup & configuration > Data management > Data & connectors, then the Tables tab.

3

Hunting

Doc update

The documentation now lists Microsoft Sentinel and ISOC navigation paths for opening hunting, and adds alternatives for preserving investigation context when using bookmarks.

1

Tutorial Extract Incident Entities

Doc update

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.

1
1

Codename Mdash Faq

Doc update

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.