Skip to content

Microsoft Entra hybrid join · Discover phase

Fix hybrid join error 0x801C003A (tenant not found)

0x801C003A · DSREG_DISCOVERY_TENANT_NOT_FOUND Checked against Microsoft Learn

Quick answer

0x801C003A means the device found your service connection point (SCP), but the tenant it points to wasn't found by the device registration service. Microsoft's guidance is to check that the SCP has the correct Microsoft Entra tenant ID and that the tenant has active subscriptions. During sync-join the same problem can show as a DirectoryError with AADSTS90002 (Tenant UUID not found).

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 the tenant ID in your service connection point match your Microsoft Entra tenant ID, and does that tenant have active subscriptions?

What 0x801C003A means

The service connection point object has the wrong tenant ID, or no active subscriptions were found in the tenant.

Common causes

  • The SCP object is configured with the wrong Microsoft Entra tenant ID.
  • The tenant has no active subscriptions.
  • For sync-join: the server returns DirectoryError 'AADSTS90002: Tenant UUID not found', which Microsoft attributes to an incorrect tenant ID in the SCP.

How to fix 0x801C003A

  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 discover-phase error is 0x801c003a (or a join-phase DirectoryError with AADSTS90002).
  3. Compare the tenant ID configured in the service connection point with your Microsoft Entra tenant ID.
  4. Correct the service connection point so it points to the right tenant (see the Configure a service connection point section of Microsoft's hybrid join tutorial).
  5. Check that the tenant has active subscriptions.
  6. Retry the join and check dsregcmd /status.

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.