Fix it now
The wizard stops while writing hybrid organisation configuration, and two of the codes in this family have published one-line fixes. HCW8039 means extra namespaces have been added to the hybrid Send connector; HCW8014 means stale Client Access servers are still listed on the hybrid configuration object. Clear each with a single command and rerun.
Get-SendConnector -Name "Outbound to Microsoft 365"
Set-SendConnector -Name "Outbound to Microsoft 365" -AddressSpace "smtp:contoso.mail.onmicrosoft.com;1"
Set-HybridConfiguration -ClientAccessServers $Null
Get-HybridConfiguration | Set-HybridConfiguration -ExternalIPAddresses $null
- Read the wizard’s log for the failed run and note which code it stopped on, because the fixes are different and running all of them is unnecessary.
- For HCW8039, check the address space on the send connector the wizard created. It should be either an asterisk or your tenant routing domain with a cost, and nothing else.
- For HCW8014, clear the Client Access servers from the hybrid configuration object. Microsoft’s fix is the single Set-HybridConfiguration line above.
- For HCW8018 in the same family, clear the external IP addresses from the same object with the last line.
- Rerun the Hybrid Configuration Wizard after whichever change you made, and let it complete before judging the result.
HCW8054 and HCW8092 have no published meaning. If the run stops on one of those, work from the log line’s own text and from the checks in the last section rather than from the number.
If the wizard completes, stop here. If it stops on the same step again, the next section covers what it is trying to write and what gets in the way.
Why it happens
The wizard writes hybrid configuration into both organisations: organisation relationships, accepted and shared domains, the send and receive connectors that carry mail between you and the service, and a hybrid configuration object in Active Directory that records what the last successful run decided. A run that fails part way has already made some of those changes, and the next run has to work around what it finds.
That is why several of the errors in this family are about stale state rather than about anything being wrong with your design. HCW8014 is published as “The Client Access servers specified by the Hybrid Configuration Active Directory object were not properly cleared during the upgrade of the hybrid configuration”, with incorrect or removed servers still listed on the object as the cause. HCW8018 is its sibling for external IP addresses. Both are cleared with one command each.
HCW8039 is a different shape. It is published as “The hybrid Send connector must only contain the single address space”, and the cause is that other namespaces have been added to the Send connector the wizard created. Microsoft’s own check is to look at the address space on the connector named Outbound to Microsoft 365 and confirm it is either an asterisk or the tenant routing domain with a cost, then set it back.
HCW8054 and HCW8092 are the two in this article with no published meaning at all. A search of Microsoft’s documentation for HCW8054 returns nothing; HCW8092 appears only in community threads, reported against the Configure Mail Flow task. Use them to correlate lines in your own log, and be sceptical of any source that tells you precisely what either one means.
Extra namespaces on the hybrid send connector
You have this one if The run stops with HCW8039, or the send connector the wizard created has grown address spaces somebody added later.
- Read the connector:
Get-SendConnector -Name "Outbound to Microsoft 365". - Look at the AddressSpace value. It should show either an asterisk, or your tenant routing domain with a cost, such as contoso.mail.onmicrosoft.com;1.
- Set it back:
Set-SendConnector -Name "Outbound to Microsoft 365" -AddressSpace "smtp:contoso.mail.onmicrosoft.com;1". - Rerun the wizard.
If somebody added a namespace to that connector deliberately, find out why before removing it. It is usually a shortcut that should have been a separate connector.
Stale servers or addresses on the hybrid configuration object
You have this one if HCW8014 or HCW8018, typically on an organisation where servers have been decommissioned or an earlier hybrid configuration was upgraded.
- For HCW8014, clear the server list:
Set-HybridConfiguration -ClientAccessServers $Null. - For HCW8018, clear the addresses:
Get-HybridConfiguration | Set-HybridConfiguration -ExternalIPAddresses $null. - Rerun the wizard, which repopulates whichever of those it needs.
- Check
Get-HybridConfigurationafterwards so you know what the successful run recorded.
A domain is not verified in the tenant or not accepted on premises
You have this one if The run fails while writing domain or address space configuration, and the domain list includes something one side does not recognise.
- Confirm each domain is verified in Microsoft 365 admin centre under Settings, then Domains.
- Confirm the matching accepted domain exists on premises:
Get-AcceptedDomain. - Remove any domain from the wizard’s selection that you do not actually intend to share between the two organisations.
- Rerun with the corrected list rather than with everything selected.
The account running the wizard lacks the rights it needs
You have this one if The failure is immediate and identical every time, and the log records an authorisation problem rather than an object or a network one.
- Use an account with Organization Management on premises for the on-premises half.
- Sign in to the tenant with an account holding a role that can change Exchange Online organisation settings and register applications.
- Check for a conditional access policy blocking the sign-in the wizard performs, and arrange an exclusion for the run.
- Rerun and confirm the step now proceeds before changing anything else.
The Exchange build is not one the wizard will work with
You have this one if The wizard stops early, before doing anything useful, on a server running an older Exchange version.
- Check the build:
Get-Command Exsetup.exe | ForEach-Object {$_.FileVersionInfo}. - If another Exchange server in the organisation runs a current build, run the wizard from that one instead.
- Check the coexistence rules before you plan anything: Exchange Server SE RTM setup prevents coexistence with Exchange 2013, and from SE CU2 setup prohibits coexistence with any Exchange version out of support at that release.
- If no server in the organisation is on a supported build, that has to be fixed before hybrid can be configured; object cleanup will not help.
An unsupported Exchange server keeps working, which is why they linger. It stops receiving security updates, which is why they should not.
Full reference
What is published, and what is not
| Code | Published meaning | Fix |
|---|---|---|
HCW8039 |
The hybrid Send connector must only contain the single address space | Set-SendConnector -Name "Outbound to Microsoft 365" -AddressSpace "smtp:<tenant routing domain>;1" |
HCW8014 |
The Client Access servers specified by the Hybrid Configuration Active Directory object were not properly cleared during the upgrade | Set-HybridConfiguration -ClientAccessServers $Null |
HCW8054 |
Nothing published | Read the log line’s own text |
HCW8092 |
Nothing published; community reports place it on the Configure Mail Flow task | Read the log line’s own text |
Before you clean anything up
Removing hybrid objects on a system that is partly working interrupts cross-premises mail flow and free/busy while you rebuild. Do the cleanup in a planned window, record what exists before you start, and remove objects one at a time rather than in a single sweep.
- Record the current state on both sides:
Get-HybridConfiguration,Get-OrganizationRelationship,Get-IntraOrganizationConnector, and the send and receive connectors the wizard created. - Make the one change the error calls for, and rerun. Most of these are single-command fixes and do not need a cleanup at all.
- Only where the configuration is genuinely tangled, consider
Remove-HybridConfiguration, which clears the on-premises hybrid configuration object so the wizard starts from a known state. - Note that removing the configuration object does not remove the organisation relationships or the connectors. Those are separate objects and have to be dealt with separately.
- Rerun the wizard rather than hand-building the remainder, so both organisations end up describing the same arrangement.
The checks that make a rerun likely to succeed
- Every domain you intend to share is verified in the tenant and present as an accepted domain on premises.
- The account you are using holds Organization Management on premises and a sufficient administrative role in the tenant.
- The Hybrid Configuration Wizard itself is the current version. An out-of-date wizard produces its own documented failure that no amount of object cleanup will fix.
- The on-premises server you run it from is on a build that is currently supported, and coexists legally with what else is in the organisation.
- The send connector the wizard created has not acquired extra address spaces since the last successful run.
Where the hybrid configuration object fits
Get-HybridConfiguration returns the object the wizard maintains in Active Directory, recording what the last successful run decided: the servers, the domains, the external addresses and the features selected. It is a record rather than a live configuration, and its value is that a failed run can be diagnosed by comparing what it holds with what the current run is trying to do. Two of the errors in this family are literally about stale entries in it.
Rerunning without making it worse
- Run the wizard from the same server and the same accounts each time, so that a difference between runs is a change you made rather than a variable you did not control.
- Do not run the wizard concurrently from two servers. It writes to both organisations and the second run will be working against the first.
- Keep the wizard log for each run. The codes are stable within your own logs even where Microsoft publishes nothing for them, and comparing two runs is often more informative than either one alone.
- Give the run time to complete. A wizard that appears stuck at a step is frequently waiting on the service rather than failing.
- Test the outcome rather than trusting the summary: a free/busy lookup and a test message in each direction tell you more than the wizard’s final page.
When a licence is the actual fix
Most of what is on this page is free to fix. Verifying a domain, clearing a stale server list, correcting a send connector address space and sorting out permissions cost nothing, and the Hybrid Configuration Wizard is free. The exception is the last cause on the list: if the on-premises server you need to run the wizard from is on an Exchange version that is no longer supported, cleanup will not help and the honest answer is a supported server. That points at Exchange Server Subscription Edition, licensed with a server licence for each running instance – Standard supporting 1 to 5 mailbox databases, Enterprise 1 to 100 – plus a Client Access Licence for each user or device, where the Enterprise CAL is an add-on to a Standard CAL. Which route you take matters as much as the licence: from Exchange Server 2019 CU14 or CU15 this is an in-place upgrade, and from Exchange 2016 or earlier it is a new server and a mailbox move. Arco supplies Exchange Server SE Standard and the matching CALs, and can tell you which of those two situations you are in before you order.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
HCW8054 |
Reported when the wizard stops while writing hybrid organisation configuration. Microsoft publishes nothing for this code; read the log line it appears on | not published by the vendor |
HCW8092 |
Reported around the Configure Mail Flow task. Microsoft publishes nothing for this code | not published by the vendor |
HCW8039 |
The hybrid Send connector must only contain the single address space. Caused by other namespaces having been added to the connector the wizard created | Microsoft Learn |
HCW8014 |
The Client Access servers specified by the Hybrid Configuration Active Directory object were not properly cleared during the upgrade of the hybrid configuration | Microsoft Learn |
Confirm the fix worked
Get-SendConnector -Name "Outbound to Microsoft 365"shows a single address space: an asterisk, or the tenant routing domain with a cost.Get-HybridConfigurationshows the servers and addresses the successful run recorded, with nothing stale left over.- The Hybrid Configuration Wizard completes without stopping on a code.
- A test message flows in each direction between the two organisations.
- A free/busy lookup across the hybrid boundary returns real availability.
Questions people ask about this
Is any of this fixed by buying something?
Only the last cause. Domain verification, object cleanup, connector settings and permissions are all free changes. A licence matters only if the on-premises server you need is on an Exchange version that is no longer supported.
What does HCW8054 mean?
Microsoft does not publish a meaning for it. A search of Microsoft’s documentation returns nothing at all for the string. Read your own wizard log’s text for that line, and work from the checks in this article rather than from the number.
Is Remove-HybridConfiguration safe?
It clears the on-premises hybrid configuration object so the wizard starts from a known state, which is sometimes exactly what you want. It does not remove the organisation relationships or the connectors, so it is not a full reset, and it should be done in a planned window with a record of what existed first.
Why did the send connector grow an address space?
Almost always because somebody needed to route mail for another domain and used the connector that was already there. It is a reasonable-looking shortcut that breaks the wizard, and the right answer is a separate send connector for that traffic.
Can I run the wizard from any Exchange server?
From one on a currently supported build. Check the version before you start, and check the coexistence rules too: Exchange Server SE RTM setup prevents coexistence with Exchange 2013, and from SE CU2 it prohibits coexistence with any version out of support at that release.
