Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 272/272 feeds/APIs · 469/469 docs · 8/9 advisories · checked 15:44 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Defender XDR: Scoped access for Defender for Identity (preview)

Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Rollout

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

What the notice says

Microsoft’s text, with source markup removed
Coming soon in Microsoft Defender for Identity (MDI): The public preview of Active Directory domain-based scoping. This capability is a foundational step in extending role-based access control (RBAC) as part of the broader XDR unified role-based access control (URBAC) initiative. This new capability enables organizations to define and refine the scope of Microsoft Defender for Identity monitoring, providing more granular control over which entities and resources are included in security analysis. Many organizations using Defender for Identity operate across multiple Active Directory domains and need a way to delegate access based on responsibility or ownership. As organizations grow and manage complex identity environments, the ability to control who can access what (and where) is critical. Customers have this capability for Microsoft Defender for Endpoint with device groups and are expecting a similar capability for Defender for Identity. When this will happen: Public Preview: We will begin rolling out early June 2025 and expect to complete by late June 2025. General Availability (Worldwide): We will begin rolling out late July 2025 and expect to complete by late August 2025. How this will affect your organization: With AD domain-based scoping currently available for Microsoft Defender for Identity, organizations can limit visibility and investigation access based on Active Directory domains using XDR URBAC. This provides more control over who can access which alerts, activities, and identity data—supporting operational separation and minimizing unnecessary exposure across teams. What you need to do to prepare: This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your admins about this change and update your relevant documentation. This feature is available by default for admins to configure. No configuration is applied by default. To enable scoped access, go to Microsoft Defender XDR > Permissions and roles. On the Assignment page, select Microsoft Defender for Identity as the data source and define the relevant Active Directory domains for each role. Learn more: What's new - Microsoft Defender for Identity | Microsoft Learn

What changed

Between archive captures, newest first

The archive supplies one version of this notice.

Linked documentation

Microsoft pages the notice links to

The notice links to no Microsoft Learn or Support page that this installation reads.

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 26 Oct 15:44 UTC · 272 of 272 readable · 270 fully read · documentation 469/469 current