Federated sign-in security requirements
Timelines and exceptionsTimeline
From the capture of 26 Aug 15:50 UTC · an earlier observationSource history: extracted from the page's source file at a commit; shared includes are not expanded
- 15 undated sections
- 12 with conditions
- 30 recorded changes
Requirements, exceptions and scope
- Does the policy apply only when a tenant has multiple federated domains?Exception3 conditions1 passage
- Can an administrator allow cross-domain sign-in?RequirementExceptionScopeRecommendation1 condition2 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.
How this timeline changed
Changes between ChangeIntel's readings of the page, between commits of its source file where Microsoft publishes it, in Internet Archive copies of pages that keep no other history, and entries from Microsoft's own change log (dated as Microsoft dates them). Edits between readings that neither records are unknown.
18 earlier changes
-
-
-
No longer on the page Can an administrator allow cross-domain sign-in?Microsoft's source, commit c520c42
-
-
-
-
-
-
-
-
Observed history and review priority
Captured 26 Aug 15:50 UTC; extracted 19 Oct 15:45 UTC. Extractor: microsoft-1/9/fc65ebeb286710c0a830833db8a7e5de7e266b79981fe9c7c34479be9369ad3c/source-commit.
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.
- 13 Oct 00:55 UTC · 27 candidates
- 5 Oct 23:18 UTC · 32 candidates
- 26 Aug 15:50 UTC · 27 candidates
- 20 Aug 02:27 UTC · 23 candidates