Windows / Intune error

0X80072EE7

The server name or address could not be resolved.

Symbol / family
WININET_E_NAME_NOT_RESOLVED
Signed decimal
-2147012889
Unsigned decimal
2147954407

What it means here

A Windows networking component could not resolve the destination hostname.

Technical reference: Microsoft documentation or Microsoft-hosted support material

Resolution playbook

From symptom to verified fix

Start with evidence, change one variable at a time, and confirm the result before closing the incident.

1

Likely causes

  • DNS cannot resolve the service hostname.
  • A proxy, VPN, firewall, or TLS inspection path is interrupting the request.
  • The client is using an incorrect or retired endpoint.
2

Recommended fix

  1. Resolve the hostname with nslookup or Resolve-DnsName.
  2. Check proxy, VPN, DNS suffix, and filtering configuration.
  3. Confirm the endpoint name in the surrounding log is correct.
3

Verify

  1. Repeat the smallest operation that originally failed.
  2. Confirm the same HRESULT does not recur at the matching timestamp.
  3. Check the management console or service report for a fresh successful state, not only a client-side message.
4

Escalate when

  • The error persists after the relevant checks and a clean retry.
  • Multiple devices, users, or networks show the same failure, suggesting service or policy scope.
  • You can provide the exact UTC time, operation, device/build, correlation identifiers, and the relevant event or service logs.
Check DNS and the WinHTTP proxy
Resolve-DnsName <service-hostname>
netsh winhttp show proxy

Replace the placeholder with the hostname from the failing log. Both commands are read-only.

← Search another error

Browse Windows and Intune errors · Open Microsoft 365 Admin Decoder · Open Intune CSP Lookup