Managing Microsoft 365 endpoints
No content change seen yet. Watched since 8 Oct 23:29 UTC, last read today 00:13 UTC, next check 21 Oct 00:13 UTC. Microsoft's own edits are listed below.
Read the Microsoft source · Link to this observation · My radar
Timeline
From the capture of 8 Oct 23:29 UTC · an earlier observationLegacy capture: table structure or oversized sections are unavailable for extraction
Microsoft's revision log on this page · 18 entries
Dates from the page's own change log or history section. They describe earlier edits, not upcoming policy.
SD-WANGet-PacFileClientRequestId- Change management for Microsoft 365 IP addresses and URLsRequirementExceptionRecommendationTentative3 conditions
- Am I peering appropriately with Microsoft?Recommendation
- I see network requests to IP addresses not on the published list, do I need to provide access to them?ExceptionRecommendation3 conditions
- I have to have the minimum connectivity possible for Microsoft 365RequirementExceptionRecommendationTentative3 conditions
- My firewall requires IP Addresses and can't process URLs. How do I configure it for Microsoft 365?RequirementExceptionRecommendation3 conditions
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.
14 earlier changes
Observed history and review priority
Captured 8 Oct 23:29 UTC; extracted 16 Oct 16:11 UTC. Extractor: microsoft-1/9/fc65ebeb286710c0a830833db8a7e5de7e266b79981fe9c7c34479be9369ad3c/legacy.
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 · 15
Compact evidence remains available after full document bodies expire. Earlier extractions can have different vocabulary or capture limitations.
- 13 Oct 00:24 UTC · 25 candidates
- 8 Oct 23:29 UTC · 27 candidates
- 29 Apr 20:52 UTC · 25 candidates
- 28 Apr 19:48 UTC · 25 candidates
- 10 Mar 05:56 UTC · 25 candidates
- 9 Mar 18:18 UTC · 25 candidates
- 16 Dec 2025 23:22 UTC · 25 candidates
- 10 Sep 2025 21:26 UTC · 25 candidates
- 16 Nov 2024 01:33 UTC · 25 candidates
- 20 Jun 2024 22:29 UTC · 25 candidates
- 20 Jun 2024 22:22 UTC · 25 candidates
- 30 Oct 2023 13:32 UTC · 25 candidates
- 19 Oct 2023 14:41 UTC · 25 candidates
- 5 Dec 2022 21:29 UTC · 25 candidates
- 5 Dec 2022 19:40 UTC · 25 candidates
Microsoft's edits
History on GitHubCommits to the page's source in MicrosoftDocs/microsoft-365-docs, with Microsoft's own messages. Commit dates can be hours or days before Learn publishes the change. ChangeIntel keeps a copy of each diff, so an edit stays readable here if GitHub stops serving it. Read 19 Oct 23:56 UTC.
The page Learn serves was built from a commit that is not in this list: the public copy may lag the repository Microsoft publishes from, or the change came through a shared include.
Related public evidence
No related evidence found in this installation's recent collection. This does not establish that no announcement exists.
Retained observations
- 13 Oct 00:24 UTC
8 removed passages (about 50 words). The changed wording mentions prerequisites. Review the source to confirm the effect.
- 8 Oct 23:29 UTC · shown above
What changed
First observed 18 Oct 2026No field changes in the recorded history.
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.