Defender for Identity on AD FS, AD CS and Entra Connect servers
Observed content change
1 new passage (17 words), 2 edited passages (4 words changed). The changed wording mentions prerequisites. Review the source to confirm the effect.
May need admin actionCheck whether new requirements apply to your setup.
[added: Use these procedures for Defender for Identity v2.x sensors. For v3.x sensors, follow v3.x deployment and configuration.]
… The following additional requirements apply to [added: v2.x sensors on] AD FS, AD CS, and Microsoft …
A [added: v2.x] sensor installed on an AD FS, …
Short quotes of Microsoft's changed wording from Microsoft source, © Microsoft Corporation. Read the page for the full text.
Read the current Microsoft source · Link to this observation · Compare any two versions
Sections to inspect
- Configure sensors for AD FS, AD CS, and Microsoft Entra Connect
- Prerequisites
Up to 12 section headings from retained before/after evidence. The current source may have changed again.
Why this was flagged
The changed words, with a few words around them, matched these rule categories: prerequisites. These matches identify subjects to assess; they do not establish a policy change or applicability.
Observation details · observed 18 Oct 23:50 UTC
- Observed by ChangeIntel
- 18 Oct 23:50 UTC
- Source update metadata
- 18 Oct 17:35 UTC
- First observed on this installation
- 8 Oct 23:13 UTC
- Last successful check
- 25 Oct 00:48 UTC
- Next check due
- today 00:48 UTC
Observation time is not publication time, and a comparison does not establish an effective date. Full source bodies are not published; this page holds generated summaries, section headings and, as the page's license allows, Microsoft's changed wording. A documentation edit does not confirm feature availability in an environment.
This is an earlier observation; review the latest in My radar.
Timeline
From the capture of 18 Oct 23:50 UTC · an earlier observation- 6 undated sections
- 5 with conditions
Requirements, exceptions and scope
- Install and configure sensors on non-domain-controller serversRequirementException2 conditions2 passages
- 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 22 Oct 18:57 UTC. Extractor: microsoft-1/9/d9863eb412f92fa5ec3a8ca32e2dd7cfe8095530f456ecb1866608d1166a435d.
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 · 4
Compact evidence remains available after full document bodies expire. Earlier extractions can have different vocabulary or capture limitations.
- 24 Oct 00:41 UTC · 14 candidates
- 18 Oct 23:50 UTC · 14 candidates
- 12 Oct 23:53 UTC · 14 candidates
- 8 Oct 23:13 UTC · 13 candidates
Retained observations
- 24 Oct 00:41 UTC
Source metadata changed; retained article content is unchanged.
- 18 Oct 23:50 UTC · shown above
- 12 Oct 23:53 UTC
The page title or its body outside the tracked passages changed. Review the source for its effect.
- 8 Oct 23:13 UTC
Baseline for retained history; no earlier retained text to compare.
What changed
First observed 18 Oct 2026No field changes are shown for this selection.
Cite this recorded revision to keep the same title, summary, facts and links when the page changes.
A day selects the latest observation by the end of that UTC day; today's selection can change until midnight. History starts when this installation records it.