Plan Defender for Identity operations around the unified portal and 30-day hunting retention

Frame this document as a source-led configuration and assurance check: Plan Defender for Identity operations around the unified portal and 30-day hunting retention. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official Microsoft Defender for Identity in the Microsoft Defender portal from Microsoft supports the following bounded statements:

• Microsoft moved classic Defender for Identity portal users to the unified Defender portal; the documentation says redirection is automatic and the legacy portal cannot be restored. The research record locates this support at Converged experiences in the Microsoft Defender portal > Note.
• The Microsoft Defender portal stores advanced-hunting data for 30 days; Microsoft directs customers needing longer retention to stream activities to Microsoft Sentinel or another partner SIEM. The research record locates this support at Configuration and posture > API > Tip.

Do not import neighboring assumptions into the source record. The supported task is a scoped comparison involving identity alerts, investigations, remediation roles, evidence retention, escalation, exclusions, and incident workflows and the conditions the source actually describes.

What the source does not establish

Portal convergence and hunting retention do not establish SIEM ingestion, schema continuity, report retention, licensing, or successful migration of legacy workflows. It does not establish a deployment’s current state, authorize a production change, prove compliance, or show that Active Directory, Windows DNS, time, cloud portals, endpoint data, network telemetry, privileged access, and response staffing are healthy. Documented options are review inputs, not universal mandates.

Applicability questions

• For source statement 1 at Converged experiences in the Microsoft Defender portal > Note, which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Configuration and posture > API > Tip, which observable configuration, record, or test can confirm applicability here?
• Which deployed instance of identity alerts, investigations, remediation roles, evidence retention, escalation, exclusions, and incident workflows will be compared with the source, and why that instance?
• How will the review distinguish a source mismatch from a failure in Active Directory, Windows DNS, time, cloud portals, endpoint data, network telemetry, privileged access, and response staffing?
• Who approves the conclusion, exception, test window, and rollback threshold?

DSE recommendation:

DSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. Record the source location, examined part of identity alerts, investigations, remediation roles, evidence retention, escalation, exclusions, and incident workflows, observed and expected states, owner, and reason for deviation.

Translate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include Active Directory, Windows DNS, time, cloud portals, endpoint data, network telemetry, privileged access, and response staffing, while excluding secrets and sensitive personal or topology data from ordinary tickets.

Verification and evidence

Build a reproducible chain from Converged experiences in the Microsoft Defender portal > Note; Configuration and posture > API > Tip to the observed environment. Useful domain evidence includes alert records, investigation timelines, analyst actions, tuning or exclusion approvals, remediation results, and case closure; label every item with scope, timestamp, collector, and stable identifier.

Close the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.

Official references

• Microsoft Defender for Identity in the Microsoft Defender portal — Microsoft