Moving Sentinel to the Defender portal
Timelines and exceptionsTimeline
From the capture of 12 Oct 23:53 UTC- 12 undated sections
- 24 with conditions
Requirements, exceptions and scope
This article explains how to transition your Microsoft Sentinel experience from the Azure portal to the Defender portal. If you use Microsoft Sentinel in the…
- Onboarding to the Defender portal with customer-managed keys (CMK)RequirementScope1 condition2 passages
- Configure automation rules and playbooksRequirementExceptionScopeRecommendationTentative14 conditions10 passages
- Understand how alerts are correlated and incidents are merged in the Defender portalRequirementExceptionScope2 conditions3 passages
Extracted automatically from Microsoft's wording. Confirm dates, conditions and whether they apply to you in the source before acting; a month or quarter is a window, not a day.
Observed history and review priority
Captured 12 Oct 23:53 UTC; extracted 16 Oct 16:10 UTC. Extractor: microsoft-1/9/fc65ebeb286710c0a830833db8a7e5de7e266b79981fe9c7c34479be9369ad3c.
Review priority. Extracted assertions require review · Publisher marks guidance tentative · Applicability or exceptions require review
0 date changes and 0 condition changes across 0 compared revisions. Suggested check interval: 24 hours.
Earlier unavailable versions and edits between checks are unknown. A missing statement requires review; it does not mean the policy was cancelled. Recovered historical statements are not original revision snapshots.
Retained observations · 2
Compact evidence remains available after full document bodies expire. Earlier extractions can have different vocabulary or capture limitations.
- 12 Oct 23:53 UTC · 41 candidates
- 8 Oct 23:13 UTC · 29 candidates