How to “Uninstall” Exchange Hybrid in Exchange Server 2019
A Practical, Lab‑Tested Reset Guide (HCW)
When
working with Exchange Server 2019 Hybrid, especially in a lab
environment, it’s very common to want to:
• Repeat
the Hybrid Configuration Wizard (HCW)
• Understand exactly what HCW changes
• Completely reset hybrid configuration
• Learn by re‑running the setup end‑to‑end
I
recently went through this exercise in a real Exchange 2019 + Edge + EOP lab,
and one thing became very clear:
Hybrid is
not something you uninstall. Hybrid is something you de‑program.
This post
explains how to cleanly remove (reset) Hybrid configuration in Exchange
Server 2019, using the modern and Microsoft‑accurate approach.
First: What HCW Actually Does (Important Context)
The
Hybrid Configuration Wizard:
• Does
NOT install software
• Does NOT add Windows services
• Does NOT add Exchange roles
Instead,
HCW writes configuration objects into: • On‑premises Exchange • Exchange
Online (EXO / EOP)
So when
we say “uninstall HCW”, what we really mean is:
Remove
the configuration objects created by HCW
A Common Misconception: Federation Trust Removal
Many
older blogs say:
“Remove
the Federation Trust to uninstall Hybrid”
This
advice is outdated for Exchange Server 2019.
Reality in Exchange 2019
•
Federation Trust is deprecated and hidden
• Cmdlets like Get‑FederationTrust / Remove‑FederationTrust do not exist
• Hybrid authentication now relies on OAuth, not legacy federation
If you
try to remove Federation Trust in Exchange 2019 and find: • The cmdlet doesn’t
exist
• No output is returned
👉 That is expected behaviour, not a problem.
There is nothing
missing and nothing to remove.
The Correct Way to Reset Hybrid in Exchange 2019
(Lab‑Safe)
Below is
the modern, supported method to reset Hybrid configuration.
Step 1: Remove the Hybrid Configuration Object
(Most Important Step)
On the
Exchange 2019 Mailbox server, open Exchange Management Shell and run:
Remove‑HybridConfiguration
Then
verify with: Get‑HybridConfiguration
If
nothing is returned, the Hybrid configuration object is removed.
Step 2: Remove HCW‑Created Send Connectors (On‑Prem)
List send
connectors: Get‑SendConnector
Remove
only the connectors created by HCW, typically named something like: Outbound to
Office 365
Use: Remove‑SendConnector
"Outbound to Office 365"
⚠️ Do not delete default or Edge send connectors.
Step 3: Remove HCW‑Created Receive Connectors (On‑Prem)
List
receive connectors: Get‑ReceiveConnector
Remove
Hybrid‑specific connectors such as: Inbound from Office 365
Use:
Remove‑ReceiveConnector "Inbound from Office 365"
Again, do
NOT touch default or Edge receive connectors.
Step 4: Remove Hybrid Connectors in Exchange Online
Connect
to Exchange Online PowerShell: Connect‑ExchangeOnline
Remove
the inbound connector created by HCW: Remove‑InboundConnector "Inbound
from On‑Premises"
Remove
the outbound connector created by HCW: Remove‑OutboundConnector "Outbound
to On‑Premises"
Only
remove connectors clearly created for Hybrid.
Step 5: Remove Migration Endpoint (Optional – Lab
Only)
If a
migration endpoint exists and you want a full reset:
Get‑MigrationEndpoint
Remove‑MigrationEndpoint "OnPrem‑EWS"
This step
is optional but useful for learning and repeat testing.
What You Should NOT Remove
Do NOT
remove or modify: • Edge Subscription
• Accepted Domains
• Certificates
• Azure AD Connect
• OAuth / AuthServer objects
These are
reused by HCW and are not part of the reset.
Result: Back to “Pre‑Hybrid” State
After
completing these steps:
✅ No HybridConfiguration object
✅ No hybrid send or receive connectors
✅ No hybrid connectors in Exchange Online
✅ No migration endpoint
You now
have a clean slate, without reinstalling Exchange.
Re‑Running HCW (Recommended Method on Server 2019)
On
Windows Server 2019, the most reliable way to launch HCW is:
rundll32
dfshim.dll,ShOpenVerbApplication https://aka.ms/hybridwizard
This
avoids ClickOnce issues and is fully Microsoft‑supported.
Key Lessons Learned
• Hybrid
is configuration, not software
• Federation Trust removal is obsolete in Exchange 2019
• Remove‑HybridConfiguration is the real “uninstall”
• HCW can be safely re‑run in labs
• Modern Hybrid relies on OAuth, not legacy federation
Final Thoughts
If you’re
learning Exchange Hybrid seriously, resetting and re‑running HCW in a lab is
one of the best exercises you can do.
It helps
you truly understand: • What HCW creates
• How mail flow and Edge/EOP integrate
• How modern Hybrid authentication works
And it
clears up a lot of outdated guidance still floating around online.
Comments
Post a Comment