Microsoft 365 VPN split tunnelling
Retained observation
Source metadata changed; retained article content is unchanged.
Read the current Microsoft source · Link to this observation · Compare any two versions
Observation details · observed 24 Oct 00:57 UTC
- Observed by ChangeIntel
- 24 Oct 00:57 UTC
- Source update metadata
- 20 Aug 06:14 UTC
- First observed on this installation
- 8 Oct 23:29 UTC
- Last successful check
- today 01:07 UTC
- Next check due
- 27 Oct 01:07 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.
Watch this page to review its changes in My radar.
Timeline
From the capture of 24 Oct 00:57 UTC- 6 undated sections
- 9 with conditions
- 33 recorded changes
Requirements, exceptions and scope
Enterprises have traditionally used VPNs to support secure remote experiences for their users. While core workloads remained on-premises, a VPN from the remote client routed…
- How do I apply DLP and protect my sensitive data when the traffic no longer flows through my on-premises solution?Requirement2 conditions1 passage
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.
-
No longer on the page Overview: VPN split tunneling for Microsoft 365Microsoft's source, commit afe1c3b
-
No longer on the page Why is port 80 required? Is traffic sent in the clear?Microsoft's source, commit afe1c3b
-
No longer on the page Overview: VPN split tunneling for Microsoft 365Microsoft's source, commit afe1c3b
-
No longer on the page Overview: VPN split tunneling for Microsoft 365Microsoft's source, commit afe1c3b
-
Recommendation added Overview: VPN split tunneling for Microsoft 365Microsoft's source, commit afe1c3b
-
No longer on the page Overview: VPN split tunneling for Microsoft 365Microsoft's source, commit afe1c3b
-
Recommendation added Overview: VPN split tunneling for Microsoft 365Microsoft's source, commit afe1c3b
-
21 earlier changes
-
-
-
-
-
-
Recommendation added Overview: VPN split tunneling for Microsoft 365Microsoft's source, commit 932afe3
-
No longer on the page Overview: VPN split tunneling for Microsoft 365Microsoft's source, commit 932afe3
-
-
-
-
-
-
-
No longer on the page Overview: VPN split tunneling for Microsoft 365Microsoft's source, commit 41365be
-
-
Observed history and review priority
Captured 24 Oct 00:57 UTC; extracted 24 Oct 00:57 UTC. Extractor: microsoft-1/9/d9863eb412f92fa5ec3a8ca32e2dd7cfe8095530f456ecb1866608d1166a435d.
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 · 18
Compact evidence remains available after full document bodies expire. Earlier extractions can have different vocabulary or capture limitations.
- 24 Oct 00:57 UTC · 24 candidates
- 13 Oct 00:24 UTC · 24 candidates
- 8 Oct 23:29 UTC · 24 candidates
- 29 Apr 20:52 UTC · 20 candidates
- 25 Mar 18:00 UTC · 20 candidates
- 10 Mar 08:20 UTC · 20 candidates
- 9 Mar 19:08 UTC · 20 candidates
- 2 Mar 23:13 UTC · 21 candidates
- 16 Dec 2025 23:22 UTC · 21 candidates
- 7 Aug 2025 21:00 UTC · 21 candidates
- 25 Jul 2025 17:35 UTC · 22 candidates
- 2 May 2024 21:48 UTC · 21 candidates
- 20 Dec 2023 20:54 UTC · 21 candidates
- 20 Dec 2023 03:21 UTC · 21 candidates
- 19 Oct 2023 14:41 UTC · 21 candidates
- 27 Jul 2023 03:09 UTC · 21 candidates
- 30 Nov 2022 01:04 UTC · 21 candidates
- 30 Nov 2022 00:58 UTC · 21 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 today 00:51 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
- 24 Oct 00:57 UTC · shown above
- 13 Oct 00:24 UTC
The page title or its body outside the tracked passages changed. Review the source for its effect.
- 8 Oct 23:29 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.