Skip to content

Microsoft Entra hybrid join · Join phase

Fix hybrid join error 0x801C03F2 (DirectoryError)

0x801C03F2 · DSREG_E_DIRECTORY_FAILURE Checked against Microsoft Learn

Quick answer

0x801C03F2 means the device registration service answered the join with a DirectoryError, and the server message tells you which one. The most common one in a sync-join, 'The device object by the given ID isn't found', is expected: the computer object hasn't synced from Active Directory to Microsoft Entra ID yet. Wait for Microsoft Entra Connect sync, and the next join attempt should succeed.

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

Read the Server Message under Previous Registration in dsregcmd /status. 'device object ... isn't found' with Registration Type: sync just means you need to wait for sync.

What 0x801C03F2 means

The device registration service (DRS) returned ErrorCode DirectoryError during the join phase.

Common causes

  • Sync-join: the device object hasn't been synced from AD to Microsoft Entra ID yet (Microsoft calls this expected).
  • Federated join: 'Your request is throttled temporarily. Please try after 300 seconds', caused by several registration requests in quick succession.
  • Sync-join: 'AADSTS90002: Tenant UUID not found', caused by a wrong tenant ID in the service connection point.

How to fix 0x801C03F2

  1. Run dsregcmd /status (Windows 10 1803 or later) and read Previous Registration: Registration Type, Error Phase (join), Client ErrorCode 0x801c03f2, and the Server Message.
  2. If the message says the device object isn't found, wait for Microsoft Entra Connect sync to finish. The next join attempt after sync should succeed.
  3. If the message says the request is throttled, wait at least 300 seconds before you retry.
  4. If the message is AADSTS90002, fix the tenant ID in the service connection point (see 0x801C003A).
  5. On earlier Windows 10 versions, find the same details in the User Device Registration event log, event ID 204.

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.