Skip to content

Microsoft Entra hybrid join · Discover phase

Fix hybrid join error 0x8007000D (proxy returns HTML)

0x8007000D · E_INVALIDDATA Checked against Microsoft Learn

Quick answer

In Microsoft Entra hybrid join, 0x8007000D (E_INVALIDDATA) means the device got a response it couldn't parse as JSON. Microsoft says this usually happens because an outbound proxy answered with HTTP 200 and an HTML sign-in page instead of passing the request through. Make sure the device's system context can authenticate to the proxy silently, or that registration traffic bypasses it.

Waitlist · launches Dec 1, 2026

The Autopilot + Device Prep Deployment Doctor

Checks your tenant, read-only, for the config that breaks ESP and Device Preparation, and tells you why a stuck device is stuck. Join the waitlist and we'll email you at launch.

Join the Kit 1 waitlist for the Autopilot + Device Prep Deployment Doctor

Check this first

Does your proxy require authentication that the computer account (system context) can't do silently? That is Microsoft's stated cause.

What 0x8007000D means

During hybrid join, the device couldn't parse the server's JSON response, most likely because a proxy returned HTTP 200 with an HTML authorization page.

Common causes

  • An outbound proxy returns HTTP 200 with an HTML authorization page instead of the registration service's JSON.
  • The system context can't discover the proxy or authenticate to it silently.

How to fix 0x8007000D

  1. On Windows 10 1803 or later, run dsregcmd /status on the affected device and read the Diagnostic Data section (it appears only on a domain-joined device that hasn't completed hybrid join).
  2. Confirm the DRS Discovery Test or Previous Registration shows 0x8007000d.
  3. Make sure the device's system context can discover the outbound proxy and authenticate to it silently.
  4. Make sure the proxy passes the registration service's response through unchanged instead of returning its own HTML page.
  5. Retry the join and confirm dsregcmd /status no longer reports the error.

Free PDF

Top 10 Intune and Autopilot Enrollment Errors: Causes and Fixes

A free cheat sheet covering ten enrollment errors, each with the symptom, the most likely cause, the fix, and a link to the full guide.

  • Ten real error codes and failures, including 0x80180014, 0x8018002b, 0x801c03f3, 0x800705b4, the ODJConnector logon failure, and the Win32 detection error 0x87d1041c.
  • Every cause and fix checked against Microsoft's own documentation.
  • A link from each entry to the full zakitpro.com article.

You get the free PDF. By subscribing you also agree to receive occasional emails from zakitpro about Intune and Autopilot troubleshooting. Emails are sent through MailerLite. You can unsubscribe anytime with the link in every email. See the privacy page for how your email is handled.

Related guides and tools

Other Microsoft Entra hybrid join codes

Sources

This page is a paraphrase of Microsoft's documentation. Check the source before you change production settings.