A new Defender portal page lets administrators enable or disable selected public preview features tenant-wide or by safe deployment channel. Features are off by default unless the tenant participated in the private preview.
Defender for Endpoint adds individual controls for public-preview features
This was a documentation-led period, but several updates carry direct administrator consequences. Defender for Endpoint now documents a portal page for enabling or disabling selected public-preview features tenant-wide or through a safe deployment channel. In Sentinel, Exchange Security Insights collector guidance requires migration to Azure Monitor and the Log Monitor API, while data lake retention is explicitly tied to supported workspace regions. Other notable guidance covers portal-key offboarding tools and more precise ASIM parser and unmapped-field handling.
- Selected public previews can be managed by tenant or safe deployment channel
Endpoint · Endpoint protection
A new Defender for Endpoint portal page lets administrators enable or disable selected public-preview features tenant-wide or by safe deployment channel. Features are off by default unless the tenant participated in the private preview, and the existing Preview features setting must be enabled first.
- Exchange Security Insights guidance requires Log Monitor API migration
Sentinel · Cloud and workloads
The on-premises and online Exchange Security Insights collectors are marked for migration to Azure Monitor, with the documented update changing from the Azure Log Analytics HTTP Data Collector API to the Log Monitor API. Administrators are advised to update the collector to version 8.0.0.0 or later.
- Offboarding deployment tools can carry a portal-generated key
Endpoint · Endpoint protection
The deployment-tool procedure supports a Defender portal offboarding key with configurable expiration and interactive or quiet command-line offboarding; the existing .offboarding-file method remains available. The key cannot be viewed again and works only with the tool that generated it.
- Sentinel data lake retention now requires a supported workspace region
Sentinel · Cloud and workloads
The retention guidance states that a workspace must be in a supported region to use data lake retention.
- ASIM references separate parser timing and clarify packed unmapped fields
Sentinel · Cloud and workloads
The ASIM reference now distinguishes query-time and ingestion-time parsers, links to parser definitions, and clarifies that pack=true retains unmapped fields in AdditionalFields. It also adds native normalized entries and additional data sources.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
9 updates
Microsoft Defender for Endpoint
2 updatesDefender Deployment Tool Windows
Private previewThe documentation describes generating a deployment tool with a Defender portal offboarding key, configurable expiration, and support for interactive or quiet command-line offboarding. The existing .offboarding-file method remains available.
Microsoft Sentinel
7 updatesData Connectors Reference
RetirementAction requiredThe documentation marks the on-premises and online Exchange Security Insights collectors for migration to Azure Monitor and requires updating from the Azure Log Analytics HTTP Data Collector API to the Log Monitor API.
List of Microsoft Sentinel Advanced Security Information Model (ASIM) parsers | Microsoft Learn
Doc updateThe documentation reorganizes the ASIM parser tables, adds links to parser definitions, distinguishes query-time and ingestion-time parsers, and clarifies that `pack=true` retains unmapped fields in `AdditionalFields`. It also adds native normalized entries and additional data sources.
Sentinel Tables Connectors Reference
RetirementThe connector reference now marks the older Exchange Security Insights entries as deprecated and adds Azure Monitor entries. It also adds Menlo, Miro, QCrypton, and RedRays mappings and changes Cisco SD-WAN support flags to Yes.
Geographical Availability Data Residency
Feature updateThe documentation now lists additional data lake-supported regions, including Canada East, Brazil, East Asia, Japan West, Korea, UAE Central, France South, Norway, Switzerland West, UK West, and more Australian regions.
Manage Table Tiers Retention
Feature updateThe documentation now states that workspaces must be in a supported region to use data lake retention.
Manage Data Overview
Doc updateThe data management overview now links to Data lake retention availability for supported-region information.
Normalization Schema Email
Feature updateThe normalized email schema now lists `EmailInteraction` alongside `EmailDelivery` and `EmailInspection` as allowed `EventType` values.
