HCW8001 with Hybrid config, tried all the known fixes, nothing is working

M Dwight Snow 5

I have run into this error with the HCW8001 and tried all known fixes, the tenant.mail.onmicrosoft.com domain is not being created in O365 admin center or exchange, it is however in Entra.

Melvin Snow

M Dwight Snow 5 Reputation points

2024-12-03T12:26:03.6433333+00:00

Hey Alex, tried that, no difference, same error.
Alex Zhang-MSFT 3,155 Reputation points Microsoft Vendor

2024-12-13T01:51:49.5266667+00:00

Hello, @M Dwight Snow,

Just checking in to see if the information below was helpful.

If the issue has been resolved, please mark the helpful replies as answers.

Best Wishes,

Alex Zhang
Alex Zhang-MSFT 3,155 Reputation points Microsoft Vendor

2024-12-17T01:15:52.11+00:00

Hello, @M Dwight Snow,

Is there any update on this thread? If the issue has been resolved, please mark the helpful replies as answers, this will make answer searching in the forum easier and be beneficial to other community members as well. Thanks for your understanding.

Best Wishes,

Alex Zhang

1 answer

Alex Zhang-MSFT 3,155 Reputation points Microsoft Vendor

2024-12-03T05:15:38.21+00:00
Hello, @M Dwight Snow,

Welcome to the Microsoft Q&A platform!

The HCW8001 error often indicates a problem with the tenant routing domain not being properly recognized or created. Here are a few steps you can try to resolve this:

1.Verify Directory Synchronization: Ensure that directory synchronization is enabled and functioning correctly. You can use the following PowerShell command to enable it if it's not already:

Set-MsolDirSyncEnabled -EnableDirsync $true

2.Check Accepted Domains: Make sure that the domain is listed as an accepted domain in both your on-premises Exchange server and Office 365 tenant.

3.Manually Add Routing Address: You can try manually adding the routing address for a user and then re-running the Hybrid Configuration Wizard (HCW). Use the following command:

Set-AdUser username -Add @{ProxyAddresses=('smtp:username@contoso.mail.onmicrosoft.com')}

4.Re-run HCW and check DNS Records: Re-run HCW and ensure that the necessary DNS records especially the TXT records for domain verification, are correctly set up and propagated.

Hope the solutions above can help you with your issue. Let me know if you need more detailed information on any of these steps or if there's anything else I can assist you with!

If the answer is helpful, please click on ACCEPT ANSWER as it could help other members of the Microsoft Q&A community who have similar questions and are looking for solutions.

Thank you for your support and understanding.

Best Wishes,

Alex Zhang
Please sign in to rate this answer.
Alex Zhang-MSFT 3,155 Reputation points Microsoft Vendor

2024-12-06T06:03:44.4433333+00:00

Hello, @M Dwight Snow,

I'm sorry to hear the issue persists. Please reconfirm the following points.

1.Ensure domain ownership is verified in Office 365.

2.Check for duplicate UPNs in your on-premises Active Directory.

3.Update to the latest version of Azure AD Connect.

4.Manually add the domain in the Office 365 admin center.

5.Review the Hybrid Configuration Wizard logs located at %appdata%\Microsoft\Exchange Hybrid Configuration.

If you need detailed instructions, please say your requirements.

If this answer helps you please mark "Accept Answer" so other users can reference it.

Thank you for your support and understanding.

Best Wishes,

Alex Zhang

Alex Zhang-MSFT 3,155 Reputation points Microsoft Vendor

2024-12-10T00:54:38.0133333+00:00

Hello, @M Dwight Snow,

Is there any update on this thread?

If the answer is helpful please click on ACCEPT ANSWER as it could help other members of the Microsoft Q&A community who have similar questions and are looking for solutions.

Thank you for helping to improve Microsoft Q&A!

Best Wishes,

Alex Zhang

Alex Zhang-MSFT 3,155 Reputation points Microsoft Vendor

2024-12-20T04:07:48.53+00:00

Hello, @M Dwight Snow,

Is there any update on this thread? Just checking in to see if above information was helpful. If the issue has been resolved, please mark the helpful replies as answers.

Best Wishes,

Alex Zhang

M Dwight Snow 5 Reputation points

2024-12-20T12:04:35.74+00:00

None of these worked. MS support on prem exchange team had to do a few things on the on prem server

Scoped and sent a scoping email.

Checked the basics such as the certificate on IIS and SAN entries on the certificate.

Verified the Exchange topology, Client Access URI, EWS URL, and authentication settings.

Ran the health checker.

Confirmed that the MRS proxy was set to true.

Noted that Extended Protection was enabled.

Found that SCH crypto values were not defined and set them to 1.

Disabled Extended Protection for EWS front end and backend.

Uninstalled HCW from the control panel and downloaded the HCW wizard.

Ran the HCW wizard, which completed successfully.

From on-premises, we were unable to create a migration endpoint using Autodiscover and EWS.

Created a migration endpoint from EXO and tested mailbox migration, which completed successfully.

Informed you to create an allow rule for all Office 365 IP ranges and try creating the endpoint from the on-premises server.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

HCW8001 with Hybrid config, tried all the known fixes, nothing is working

1 answer

Your answer