Defender for Endpoint network connectivity and service URLs
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:08 UTC
- Observed by ChangeIntel
- 24 Oct 00:08 UTC
- Source update metadata
- 22 Sep 07:34 UTC
- First observed on this installation
- 6 Oct 16:26 UTC
- Last successful check
- today 00:18 UTC
- Next check due
- 27 Oct 00:18 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:08 UTC- 3 dates
- 6 undated sections
- 8 with conditions
- 10 years agomonth window
- 8 years agomonth window
- 2 years agostarting
Requirements, exceptions and scope
Before you onboard devices to Microsoft Defender for Endpoint, configure firewall or proxy access to the required service URLs. Allow outbound connections, and bypass HTTPS…
- Enable access to Microsoft Defender for Endpoint service URLs in the proxy serverRequirementScope1 condition2 passages
- Connect devices without direct internet accessRequirementExceptionRecommendation1 condition3 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 24 Oct 00:08 UTC; extracted 24 Oct 00:08 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 · 3
Compact evidence remains available after full document bodies expire. Earlier extractions can have different vocabulary or capture limitations.
- 24 Oct 00:08 UTC · 18 candidates
- 18 Oct 23:18 UTC · 18 candidates
- 6 Oct 16:26 UTC · 18 candidates
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:08 UTC · shown above
- 18 Oct 23:18 UTC
1 removed passage (14 words). The changed wording mentions network endpoints. Review the source to confirm the effect.
- 6 Oct 16:26 UTC
Baseline for retained history; no earlier retained text to compare.
What changed
First observed 18 Oct 2026- 18 Oct 2026 · 23:20:08 UTC Guidance8 May 2024, conditional
- 18 Oct 2026 · 23:20:08 UTC Streamlined connectivity URL lists (2)April 2018, conditional
- 18 Oct 2026 · 23:20:08 UTC Streamlined connectivity URL listsAugust 2016, conditional
- 18 Oct 2026 · 23:20:08 UTC SummaryGuidance extraction is incomplete. Legacy capture: table structure or oversized sections are unavailable for extraction Earlier recorded facts remain historical evidence; omitted statements have unknown status. → Microsoft's guidance publishes 3 dates, from August 2016 to 8 May 2024 (Guidance).
The most recent 100 field changes are listed. Complete recorded revisions are kept separately.
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.