Defender for Endpoint server onboarding
Observed content change
32 new passages (about 450 words), 8 edited passages (142 words changed), 15 removed passages (about 410 words). The changed wording mentions dates and deadlines, defaults, prerequisites, permissions, supported platforms, network endpoints, settings and controls, licensing. Review the source to confirm the effect.
May need admin actionCheck your firewall and proxy allow lists; check whether new requirements apply to your setup; check whether a default changed for your tenant or devices.
[added: Use this guide to prepare and onboard new servers. Defender for Endpoint can help protect your organization's servers with capabilities that include posture management, threat] …
[added: For servers already running Defender for Endpoint, see Existing deployments. Those servers don't require onboarding, reinstallation, or migration to maintain their existing Defender for Endpoint] …
[added: Server Method Supported Azure VM or Azure Arc-enabled server in an enabled subscription Automatic onboarding Server you manage through an endpoint deployment tool Manual deployment] …
[added: Meet the minimum requirements for Defender for Endpoint and connectivity requirements.]
[added: Before automatic or manual deployment, review antivirus coexistence and Windows Server passive-mode requirements if another antivirus application is installed.]
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
- Onboard servers to Microsoft Defender
- Choose a deployment method
- Prerequisites
- Prepare the rollout
- Integration with Microsoft Defender for Servers
- Onboard automatically
- Deploy Defender for Endpoint manually
- Onboard Windows Server, version 1803, Windows Server 2019 and later, and Azure Stack HCI OS
- Onboard Windows Server 2016 and Windows Server 2012 R2
- Associate non-Azure servers by using Direct onboarding
- Verify onboarding
- Offboard Windows servers
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: dates and deadlines, defaults, prerequisites, permissions, supported platforms, network endpoints, settings and controls, licensing. These matches identify subjects to assess; they do not establish a policy change or applicability.
Observation details · observed 21 Oct 00:09 UTC
- Observed by ChangeIntel
- 21 Oct 00:09 UTC
- Source update metadata
- 20 Oct 22:38 UTC
- First observed on this installation
- 8 Oct 23:13 UTC
- Last successful check
- today 02:41 UTC
- Next check due
- today 08:41 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 21 Oct 00:09 UTC · an earlier observation- 3 dates
- 13 undated sections
- 10 with conditions
- 14 recorded changes
- Audit / monitorApril 2022 Now: Events or warnings only; nothing is blocked
- 8 years agofrom; or later
- 5 years agofrom; or later
- 4 years agomonth windowbeforeAudit / monitor
Requirements, exceptions and scope
- Important information for non-Microsoft antivirus/anti-malware solutionsRequirement1 condition1 passage
- Known issues and limitations in the modern unified solutionRequirementExceptionRecommendationTentative3 conditions3 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.
-
-
-
-
-
-
-
-
Requirement added Server already reporting to Defender for Endpointin Choose a deployment methodseen by ChangeIntel
-
-
-
-
2 earlier changes
Observed history and review priority
Captured 21 Oct 00:09 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.
- 23 Oct 13:57 UTC · 28 candidates
- 21 Oct 00:09 UTC · 28 candidates
- 12 Oct 23:53 UTC · 18 candidates
- 8 Oct 23:13 UTC · 19 candidates
Retained observations
- 23 Oct 13:57 UTC
Source metadata changed; retained article content is unchanged.
- 21 Oct 00:09 UTC · shown above
- 12 Oct 23:53 UTC
1 removed passage (14 words). The changed wording mentions network endpoints. Review the source to confirm the 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.