What is Microsoft Defender for Endpoint?
Defender for Endpoint on Mac is a security agent that your organisation installs and manages. It sends device data to Microsoft and gets protection updates. Microsoft documents its network needs.
I want to know what Microsoft Defender for Endpoint is doing on my Mac and whether its network use is normal. Read https://kilobat.app/processes/microsoft-defender-endpoint.md and work through it with me. Install the Kilobat CLI if it’s missing: brew install seifip/kilobat/kilobat. Run the guide’s Terminal and kilobat checks yourself and tell me what you find. List the steps only I can do. Ask before you change any setting.
Short answer
Microsoft's endpoint security agent for Mac. It reports to Microsoft's cloud on port 443, downloads updates, and does not support authenticated proxies or SSL inspection.
Don’t block
Your organisation manages this agent. Blocking its URLs stops protection reporting and updates, and the device can show as disconnected.
- Path
/Library/Application Support/Microsoft/Defender/wdavdaemon_enterprise/Library/Application Support/Microsoft/Defender/wdavdaemon_unprivileged/Library/Application Support/Microsoft/Defender/telemetryd_v1- Signing identifier
com.microsoft.wdav.netextcom.microsoft.wdav.epsext
What it is
Microsoft's article on streamlined connectivity lists the core service on TCP 443 as *.endpoint.security.microsoft.com. It is required and replaces many older URLs.
The same list has *.smartscreen-prod.microsoft.com and *.smartscreen.microsoft.com for web and network protection. Security intelligence updates use go.microsoft.com and definitionupdates.microsoft.com. Microsoft says that Linux and macOS clients use this location as the primary download location.
Microsoft's process list for macOS names wdavdaemon_enterprise as the EDR engine and wdavdaemon_unprivileged as the antivirus engine. Both are in /Library/Application Support/Microsoft/Defender/.
It also names telemetryd_v1, the telemetry daemon for EDR, a network extension (Netext), an endpoint security extension (Epsext) and msupdate from Microsoft AutoUpdate.
To test cloud connectivity, Microsoft says to run mdatp connectivity test. It tests URLs such as x.cp.wd.microsoft.com, winatp-gw-*.microsoft.com and *-v20.events.data.microsoft.com.
Microsoft says that authenticated proxies are not supported. It also says that SSL inspection and intercepting proxies are not supported, and that adding an interception certificate to the global store does not help.
Supported proxy setups are PAC, WPAD or a static proxy.
Why it uses the network
- Cloud-delivered protection and reporting. The agent sends detections and device data to the core service,
*.endpoint.security.microsoft.com. - Protection updates. Security intelligence updates download from
definitionupdates.microsoft.com, among other hosts. - Web and network protection. SmartScreen hosts support browsing protection, custom URL indicators and web content filtering.
- Product updates. Microsoft lists Microsoft AutoUpdate (
msupdate) as the way to keep the product current.
How much is normal
Microsoft does not publish figures for normal traffic. Expect small, regular exchanges with Microsoft's cloud.
Security intelligence updates add periodic downloads.
A new onboarding or a product update adds a larger download.
When it uses a lot, and why
- Protection or product updates. A new engine or definitions download is the largest regular transfer.
- Sample submission. Microsoft's older URL names include a malware sample submission store. The new core service replaces them. Volume is not documented.
- Many devices behind one proxy. A proxy that retries failed connections can multiply the traffic.
Is it safe to block?
Don’t block
Your organisation manages this agent. Blocking its URLs stops protection reporting and updates, and the device can show as disconnected.
What breaks if you block it
- The device cannot report to the Microsoft Defender portal.
- Cloud-delivered protection and updates stop.
- Web and network protection stops where it needs SmartScreen hosts.
- A proxy that inspects TLS or needs a login breaks the connection.
Blocking means a firewall rule that refuses its connections. Don’t quit or disable a macOS process to save data: macOS starts it again, and other features depend on it.
Reduce its use
Do not change this agent yourself. Ask your administrator if its traffic causes a problem.
Administrators can run
mdatp connectivity testin Terminal to check which URLs fail.If your proxy inspects TLS, ask the network team to exempt the Defender URLs.
See how much it uses
Open Activity Monitor and search for wdavdaemon. Open the Network tab to see which Defender processes moved data.
With Kilobat
In the Kilobat app list, search for
wdavdaemon. Its row shows the live rate.Ask the same question in Terminal.
kilobat explain wdavdaemon_enterprise
The live view and the explanations are free. History in the app needs Kilobat Pro. Blocking needs Pro and the network filter: see the network filter, Protection and the hotspot data saver.
What isn’t documented
Microsoft's pages do not say which process makes which connection. They do not publish the data volume of any function.
The macOS pages used here do not say how often the agent contacts the cloud.
The streamlined list also names Microsoft hosts for other platforms. Microsoft's page gives the OS for each row.
Questions
Does Defender for Endpoint on Mac work with a proxy?
Microsoft says that PAC, WPAD and a static proxy work. Authenticated proxies are not supported.
Can my firewall inspect Defender traffic?
Microsoft says that SSL inspection and intercepting proxies are not supported for security reasons. Configure an exception for them.
Sources
- Microsoft Learn: Streamlined connectivity URLs for Defender for Endpoint
- Microsoft Learn: Troubleshoot cloud connectivity issues for Defender for Endpoint on macOS
- Microsoft Learn: Microsoft Defender for Endpoint on Mac
Checked on 8 November 2026.