Exchange Connection Problems

Fix Exchange 2016 Federation Trust Error in Hybrid Configuration Wizard

John Wilson Sep 30, 2026 868 views

Question details

The user needs to resolve an error preventing the Hybrid Configuration Wizard from enabling Federation Trust.

Fix Exchange 2016 Federation Trust Error in Hybrid Configuration Wizard

Product: Exchange Server 2016
Device & OS: not provided
Scenario: Running the Hybrid Configuration Wizard to set up a hybrid Exchange environment.
Observed behavior: The wizard fails and reports it cannot access the federation metadata document because the connection was unexpectedly closed.

Before you start

Verify that your Exchange 2016 server can reach the internet and that outbound connections to Microsoft 365 endpoints are not blocked by a firewall or proxy.

Solution 1Recommended

Seek Specialist Assistance via Microsoft Q&A

Because hybrid configurations involve complex backend routing and identity federation, specialized support is highly recommended for diagnosing unexpected connection closures.

Exchange Hybrid Configuration failures often stem from specific environment variables, such as TLS misconfigurations, strict proxy rules, or transient endpoint outages.

Since the error explicitly states the connection to the federation metadata document was closed, getting official support will help pinpoint the network or server-side root cause.

Collect hybrid configuration logs

Gather your complete Hybrid Configuration Wizard (HCW) error logs, typically found in your server's AppData directory, along with details about your Exchange environment.

Navigate to Microsoft Q&A

Go to the official Microsoft Q&A website and locate the 'Microsoft Exchange Hybrid Management' section.

Post your detailed query

Create a new thread providing the exact error message, your HCW logs, and your Exchange 2016 version details so specialists can assist you with the federation trust failure.

Seek Specialist Assistance via Microsoft Q&A

Check TLS settings: Before posting, ensure TLS 1.2 is enabled and configured correctly on your Exchange 2016 server, as older TLS versions can cause connections to Microsoft endpoints to drop unexpectedly.

Free Microsoft Office alternative

Boost Your Productivity with WPS Office

While complex Exchange server issues require specialized Microsoft support, your daily document management shouldn't be complicated. WPS Office is a fast, lightweight, and highly compatible suite for all your document, spreadsheet, and presentation needs.

1. Download the installer: Visit the official WPS Office website and click the free download button for your operating system.
2. Run the installation: Open the downloaded setup file and follow the simple on-screen instructions to install the suite.
3. Start working: Launch WPS Office and instantly open your existing Microsoft Office files without any formatting loss.

Seamless compatibility with Microsoft Word, Excel, and PowerPoint file formats.Lightweight design that runs efficiently without consuming massive system resources.Integrated PDF tools to view, edit, and convert documents effortlessly.Familiar user interface for a smooth transition from Microsoft Office.

microsoft office alternative - wps office

Frequently Asked Questions

Why does the Federation Trust connection close unexpectedly in Exchange 2016?

This error is typically caused by network restrictions, a firewall blocking outbound connections to Microsoft 365 federation endpoints, or misconfigured TLS settings (such as TLS 1.2 not being strictly enforced) on the Exchange server.

Where can I find the Exchange Hybrid Configuration Wizard logs?

The HCW logs are usually saved on the Exchange Server under '%UserProfile%\AppData\Roaming\Microsoft\Exchange Hybrid Configuration'. Reviewing these text logs can provide deeper insight into why the metadata document connection failed.

Can I manually configure the Federation Trust without the wizard?

While it is technically possible using the New-FederationTrust cmdlet in the Exchange Management Shell, it is strongly recommended to resolve the underlying connectivity issue first. If the server cannot reach the metadata URL, manual configuration will also likely fail.

Outlook & Email Problems