To resolve this issue, use one of the following methods, as appropriate for your situation.
Method 1: Troubleshoot AD FS connectivity
Troubleshoot AD FS service problems that might limit connectivity by using the following Microsoft Knowledge Base article: �
2419389�Internet browser cannot display the AD FS webpage when a federated user tries to sign in to Office 365 web resources �
Method 2: Troubleshoot AD FS Proxy server functionality
If the sign-in problems that are described earlier only occur when you are connected to AD FS from outside the on-premises network, use the following Microsoft Knowledge Base article to troubleshoot AD FS Proxy service problems that might limit connectivity: �
2712961�How to troubleshoot the AD FS connection
Method 3: Update the AD FS service metadata to Windows Azure AD
If the sign-in problems that are described earlier begin to occur after the service name of the AD FS Federation service farm is changed, the new MEX endpoint address must be updated in Windows Azure AD. To do this, use the "How to update the configuration of the Office 365 federated domain" of the following Microsoft Knowledge Base article: �
2647048 How to update or to repair the configuration of the Office 365 federated domain
Method 4: Troubleshoot AD FS SSL certificate problems
If a sign-in attempt to Office 365 web services results in a certificate warning from the AD FS server, use the following Microsoft Knowledge Base article to troubleshoot SSL certificate problems:
2523494� You receive a certificate warning from AD FS when you access Office 365 web resources by using a federated account
Method 5: Troubleshoot split-brain DNS problems for AD FS service name resolution
To troubleshoot split-brain DNS configuration problems with the on-premises network, use the following Microsoft Knowledge Base article:
2715326 Split-brain DNS misconfiguration prevents seamless SSO sign-in experience