#TEST TLS 1.2 EXCHANGE 2010 VERIFICATION#

To resolve this issue, make sure that your on-premises environment supports TLS 1.2. You can verify this by looking at the HCW logs.

#TEST TLS 1.2 EXCHANGE 2010 VERIFICATION#

If you are using the HCW to configure a hybrid environment between Microsoft Exchange Server 2010 and Exchange Online, and the wizard is stuck at the domain verification stage, this situation might be caused by the same issue. 'The underlying connection was closed: An unexpected error occurred on a send.'.' 'An error occurred accessing Windows Live'. DelegationFederationTrust 'Microsoft Federation Gateway'Īn error occurred while attempting to provision Exchange to the Partner STS. When you create a federation trust manually, you may experience the following issue when you run the Set-FederatedOrganizationIdentifier cmdlet: TLS deprecation will also affect users when they create a federation trust manually or by using the Hybrid Configuration Wizard (HCW) if TLS 1.2 is not configured. Inability to access cloud archives by users whose primary mailbox is on-premises Inability to access free/busy information of Exchange Online mailboxes If TLS 1.2 is not enabled on your servers that are running Exchange Online, and you are still using a hybrid Exchange Server environment, you will experience the following issues: We have deprecated the use of legacy TLS for all Exchange Online endpoints.

Effect of legacy TLS deprecation for Exchange Online on Exchange hybrid users

Test tls 1.2 exchange 2010