Defender for Identity on AD FS, AD CS and Entra Connect servers
Timelines and exceptionsTimeline
From the capture of 18 Oct 23:50 UTC- 6 undated sections
- 5 with conditions
Requirements, exceptions and scope
- Install and configure sensors on non-domain-controller serversRequirementException2 conditions2 passages
Deploying the Defender for Identity sensor v3.x on AD FS, AD CS, and Microsoft Entra Connect servers that aren't domain controllers is in preview. Use…
- Configure permissions for the Microsoft Entra Connect (ADSync) databaseRequirementExceptionRecommendation3 conditions2 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 18 Oct 23:50 UTC; extracted 18 Oct 23:51 UTC. Extractor: microsoft-1/9/fc65ebeb286710c0a830833db8a7e5de7e266b79981fe9c7c34479be9369ad3c.
Review priority. Extracted assertions require review · Applicability or exceptions require review
0 date changes and 0 condition changes across 1 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 · 3
Compact evidence remains available after full document bodies expire. Earlier extractions can have different vocabulary or capture limitations.
- 18 Oct 23:50 UTC · 14 candidates
- 12 Oct 23:53 UTC · 14 candidates
- 8 Oct 23:13 UTC · 15 candidates