We have an Office 365 Single Sign on environment where users were having issues starting outlook. The application would hang on loading profile. Users could not launch outlook, nor create a new profile. Users COULD log in to OWA (Office 365) and authenticate against the ADFS.
No changes were made to the network on the on-prem nor the Office 365 environment.
We tried the Microsoft Support and Recovery Assistant for Office 365 but this tool is not supported for Single Sign on environments.
We ran the following tests on https://testconnectivity.microsoft.com:
Single Sign on - Passed
DNS Tests - Passed
Outlook Connectivity Tests - Failed due to Autodiscover failure
Autodiscover - Failed with the following code:
A Web exception occurred because an HTTP 503 - ServiceUnavailable response was received from Unknown.
HTTP Response Headers:
X-AutoDiscovery-Error: LiveIdBasicAuth:FederatedStsUnreachable:<X-forwarded-for:220.127.116.11><ADFS-Business-682ms>failed logon error - STSFailure - '<s:Fault xmlns:s="http://www.w3.org/2003/05/soap-envelope"><s:Code><s:Value>s:Sender</s:Value><s:Subcode><s:Value xmlns:a="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">a:InvalidSecurity</s:Value></s:Subcode></s:Code><s:Reason><s:Text xml:lang="en-GB">An error occurred when verifying security for the message.</s:Text></s:Reason></s:Fault>'<FEDERATED><UserType:Federated>Logon failed "firstname.lastname@example.org".;
We confirmed connectivity to ADFS with:
We were a little stuck at this point so we contacted Microsoft for assistance.
After several hours the problem was part resolved by enabling the Modern Authentication Process.
We still have the Autodiscover errors, but this got the users working.
The fix was to connect to Microsoft Exchange Online via PowerShell and run the follwoing:
Issue has now been fully resolved. After much messing around and hours of Microsoft Sernior technicians, I spotted that the TIME on the ADFS server and the time on the ADFS Proxy server were out by 7 minutes. Each machine was on a different physical host.
I configured a tursted time source on each physical host, re-tested the testconnectivity.microsoft.com and the problem was resoved!
The difference in time (+5 minutes) was the cause.