About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
When the Hybrid Configuration wizard stops with The request was aborted: Could not create SSL/TLS secure channel, Microsoft's troubleshooting page gives a single cause: firewall settings or proxy server settings are configured incorrectly. The fix it documents has three parts. Allow the proxy to reach the Exchange Online endpoints, make sure each Exchange server has its proxy set correctly, then run the wizard again. In practice, the change needs an administrator of the on-premises Exchange servers and of the firewall or proxy. Microsoft's "Applies to" line lists Exchange Online and Exchange Server 2013 Standard and Enterprise Editions, and it does not state later Exchange versions.
What the error means
The Hybrid Configuration wizard sets up a hybrid deployment between an on-premises Microsoft Exchange Server organisation (Microsoft's scope line names Exchange Server 2013) and Exchange Online in Microsoft 365. Midway through, the on-premises server has to reach services on the internet. When it cannot make that connection, the wizard stops and shows the message above.
The full text on Microsoft's page starts like this, and the parts that matter for diagnosis are quoted exactly:
ERROR:Updating hybrid configuration failed with error 'Subtask Configure execution failed: Creating Organization Relationships. Execution of the Set-FederatedOrganizationIdentifier cmdlet had thrown an exception.
Further along the same message are the phrases "An error occurred while attempting to provision Exchange to the Partner STS", "An error occurred accessing Windows Live" and "The request was aborted: Could not create SSL/TLS secure channel."
Read together, the message says the step called Creating Organization Relationships failed because the connection from the Exchange server to an outside service could not be made. The words "SSL/TLS secure channel" describe the connection that failed to start. Microsoft's page does not say which endpoint was unreachable, and it does not name a TLS protocol version or cipher as the cause. It names the firewall and the proxy.
That matters because a different fix suggests itself when you see "SSL/TLS": changing protocol settings on the server. Microsoft's page does not recommend that. A change to server protocol settings affects every application on the server, so it is not a step to take on a guess.
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| The firewall or proxy blocks the Exchange Online endpoints | The wizard fails at Creating Organization Relationships; other internet access from the server may work | Firewall or proxy logs show denied connections from the Exchange server to Microsoft 365 addresses |
| No proxy is set on the Exchange server, but the network requires one | The error appears on a server that can browse the internet only through a proxy | The Exchange server's proxy value is empty and the WinHTTP proxy shows direct access |
| The proxy is set in one place but not the others | The proxy works for some tools and not for the wizard | The Internet Explorer proxy, the WinHTTP proxy and the Exchange server's own proxy value disagree |
| A wrong proxy address or port | The wizard fails the same way after someone "fixed" the proxy | The recorded proxy value does not match the address the network team publishes |
Microsoft's page lists three places where the proxy must be set on an Exchange server: Internet Explorer, the netsh command-line tool, and the Set-ExchangeServer cmdlet.
Prove the cause before changing anything
Everything in this section only reads settings.
- Copy the full wizard error text, including the cmdlet name Set-FederatedOrganizationIdentifier. Keep it for later comparison.
- Ask the network team whether the Exchange servers reach the internet directly or through a proxy. If through a proxy, get the exact address and port.
- On the Exchange server, read the WinHTTP proxy setting:
netsh winhttp show proxy
Microsoft's netsh page says this command displays the current WinHTTP proxy setting. Write down what it shows.
- Read the properties of the Exchange server in Exchange Management Shell. Microsoft's Get-ExchangeServer page gives this form for one server:
Get-ExchangeServer -Identity Mailbox01 | Format-List
Replace Mailbox01 with your server name. Look for the InternetWebProxy value in the output (and InternetWebProxyBypassList on Exchange 2016 or later) and write it down. Microsoft's Set-ExchangeServer page names InternetWebProxy as the web proxy server the Exchange server uses to reach the internet. Microsoft's Get-ExchangeServer page does not list the properties it returns, so check that the result shows InternetWebProxy. If it does not show it, treat the current value as unknown and do not run Fix step 3 on that server until the Exchange administrator has found it. Note also that Microsoft's Get-ExchangeServer page cautions that a $null or non-existent value for -Identity returns all servers, so use a real name.
- Check the Internet Explorer proxy setting for the account that runs the wizard. Microsoft's wizard page says to set the proxy in Internet Explorer but gives no steps, so use Internet Options on the server and record what is there.
- Ask the network team to look in the firewall or proxy log for blocked or reset connections from the Exchange server at the time the wizard failed.
If every place shows the proxy you expect and the logs show nothing blocked, the cause on Microsoft's page does not match your case. Read the limits at the end before changing anything.
Fix
Do these in order and run the wizard only at the end.
1. Allow the Exchange Online endpoints on the proxy or firewall.
Save first: save the current rule set or take a configuration backup.
Disruptive step: adding or changing a rule on a firewall or proxy changes what traffic your whole network is allowed to send.
Microsoft's wizard page tells you to configure the proxy server to allow access to the endpoints used by the service, and points to the Exchange Online section of the Microsoft 365 URLs and IP addresses page. That section lists each endpoint set with its category, addresses and ports. For example, the first set lists outlook.office365.com, among other names, with TCP ports 443 and 80, and the page's tables also list UDP 443 for some sets. Make the change under your normal change process. To undo it: restore the saved configuration. Microsoft's page points only to the Exchange Online section; if the wizard still fails, ask the network team which host the log shows as blocked.
2. Set the WinHTTP proxy on each Exchange server.
Save first: record the output of netsh winhttp show proxy.
Disruptive step: the command below changes how every Windows service on that server that uses WinHTTP reaches the internet, including Windows services unrelated to Exchange.
Microsoft's Exchange EM service page (it applies to Exchange 2016, 2019 and Subscription Edition, not the Exchange 2013 named on the wizard page) uses this form for a server behind a proxy:
netsh winhttp set proxy proxy.contoso.com.au:8080
The netsh page says the optional bypass-list parameter lists sites that should be reached without the proxy, and that reset proxy resets the setting to DIRECT. The netsh page also describes netsh winhttp import proxy source=ie, which imports the Internet Explorer proxy settings. That page is written for Windows Server 2008 and is archived, so check the command on your own server version.
To undo it: if the recorded value was direct access, run netsh winhttp reset proxy; otherwise run netsh winhttp set proxy again with the recorded value.
3. Set the proxy on the Exchange server object.
Save first: record the value from the earlier Get-ExchangeServer step, and keep the saved Format-List output as the record of the server's earlier state.
Disruptive step: the command below writes the setting to Active Directory for that server, and the cmdlet works on one server at a time. Change one server first, and rerun the wizard before you change the next.
Microsoft's wizard page gives this example, where you replace the name, address and port:
Set-ExchangeServer NameOfServer -InternetWebProxy Http://proxyURL:Port
For one server called ex01 and a proxy at proxy.contoso.com.au on port 8080, the command is:
Set-ExchangeServer ex01 -InternetWebProxy http://proxy.contoso.com.au:8080 -WhatIf
The -WhatIf switch, documented on Microsoft's Set-ExchangeServer page, shows what the command would do without changing anything. Run it first, then run the same command without -WhatIf. In Exchange 2016 and later, -InternetWebProxyBypassList lists servers (FQDNs, up to 100) that go to the internet directly rather than through the proxy.
To undo it: if there was a recorded value, run the same command with that value. If the value was empty, Microsoft's Set-ExchangeServer page documents no command that returns it to empty, so this step has no documented way back.
4. Run the Hybrid Configuration wizard again. Microsoft's step three is to rerun it. If the issue persists, the page says to contact Microsoft Support and reference that page.
Example (illustrative): Contoso has three Exchange servers, ex01, ex02 and ex03, behind a proxy at proxy.contoso.com.au on port 8080, and the wizard fails on ex01 with the message above. The network team confirms that the proxy blocks Microsoft 365 hosts unless they are on its allow list. Each server needs the proxy in three places (Internet Explorer, WinHTTP and its own Exchange setting), so there are 3 servers x 3 places = 9 values to read and, where wrong, to correct. The administrator records all nine, finds that ex01 has the WinHTTP proxy set but no Exchange proxy value, adds the Exchange Online endpoints to the proxy allow list, runs the -WhatIf form of the command for ex01, then the real command, and reruns the wizard from ex01.
Confirm the fix
The proof is the wizard itself. Run it again and confirm it gets past Creating Organization Relationships and finishes without the message. Then re-read the three proxy values on each server with netsh winhttp show proxy and Get-ExchangeServer -Identity ex01 | Format-List, and confirm they match what you intended to set.
If the wizard now fails with a different message, treat that as a new fault with its own cause. Do not undo the proxy changes just because the message changed.
What to watch afterwards
Microsoft's URLs page says endpoint data is updated as needed at the beginning of each month, with new IP addresses and URLs published 30 days before they become active, and that a change log subscription is available. Subscribe the network team to it, or have them check the Exchange Online section when they renew proxy rules, so a rule that was correct today does not block a new address later.
Keep a written record of the proxy value for each Exchange server in the three places. When a server is rebuilt or added, the setting is easy to miss in one of them. Microsoft's Exchange EM service page, which applies to Exchange 2016 and later, asks for the same two proxy settings, InternetWebProxy and the WinHTTP proxy, on servers behind a proxy.
Read next
Related articles you may want next.
- TroubleshootingTLS handshake failure: no shared protocol or cipher, read the s_client error and the Schannel eventsslv3 alert handshake failure, no protocols available or Schannel 36874: prove which side lacks a shared TLS version or cipher, fix it and confirm.Read article
- Troubleshooting450 4.4.317 Cannot connect to remote server [Message=UntrustedRoot]: Microsoft 365 can't deliver to a mail serverNDR 450 4.4.317 [Message=UntrustedRoot]: why Exchange Online rejects a certificate chain and how the mail server owner fixes it.Read article
- TroubleshootingCan't see free/busy information after a mailbox is moved to Microsoft 365: the 'Could not be updated' errorFree/busy blank after a mailbox move to Microsoft 365? Check the calendar's Default permission first; the opposite direction is a different fault.Read article
Risks and limits
- These commands have not been run or lab-tested.
- Microsoft's wizard page is dated 2025-06-25 and gives one cause. It does not address TLS protocol versions, certificates or cipher suites, so a case outside the firewall and proxy cause needs its own diagnosis.
- Microsoft's wizard page gives no steps for the Internet Explorer proxy, and Microsoft's Get-ExchangeServer page does not list the proxy property; it is named on the Set-ExchangeServer page.
- The netsh page is for Windows Server 2008 and is archived. Microsoft's Exchange EM service page, which applies to Exchange 2016 and later, shows the same
netsh winhttp set proxyform for servers behind a proxy, so check it on your own Windows version. - A change to a shared proxy or firewall affects other systems. Use your normal change process and keep the saved configuration.
- If your proxy and firewall are correct and the error continues, Microsoft's page says to contact Microsoft Support and reference the page, which carries the original knowledge base number 3067292.
Sources
- Could not create SSL/TLS secure channel error - Exchange — Microsoft Learn, page dated 2025-06-25, accessed 20 November 2026
- Set-ExchangeServer — Microsoft Learn, date not shown, accessed 20 November 2026
- Get-ExchangeServer — Microsoft Learn, date not shown, accessed 20 November 2026
- Netsh Commands for Windows Hypertext Transfer Protocol (WINHTTP) — Microsoft Learn, page dated 2012-07-02, accessed 20 November 2026
- Microsoft 365 URLs and IP address ranges — Microsoft Learn, page dated 2026-08-14, accessed 20 November 2026
- Exchange Emergency Mitigation Service (Exchange EM Service) — Microsoft Learn, page dated 2026-07-14, accessed 20 November 2026
This article was originally published on .