Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
How to reestablish trust with the Windows Azure AD authentication system after the AD FS server stops responding
Article ID: 2521057 - View products that this article applies to.
Not sure what release of Office 365 you're using? Go to the following Microsoft website:
Am I using Office 365 after the service upgrade?
When a federated user tries to use Active Directory Federation Services (AD FS) to access an Office 365 resource, the user may get the following error message:
For Internet users, the error occurs after they're prompted for a user name and password.
There was a problem accessing the site. Try to browse to the site again.
If the problem persists, contact the administrator of this site and provide the reference number to identify the problem.
Reference number: <GUID>
When this error occurs, the web browser’s address bar points to the on-premises AD FS endpoint at the following address:
This issue may occur if the relying party trust is missing or corrupted in the AD FS 2.0 Management Console.
Important This section contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
To check whether the relying party trust is missing or corrupted in the AD FS 2.0 Management Console, follow these steps:
If the relying party trust is present or if it doesn't match the taxonomy that's listed, delete the entry, and then continue with one of the following methods.
Method 1: Re-add or update the federated domain relying party trust
Method 2: Remove the hardcoded federation metadata endpoint
For more info about how to troubleshoot the "There was a problem accessing the site." error message, see the following Microsoft Knowledge Base article:
(http://support.microsoft.com/kb/2383983 / )Error message from AD FS when a federated user signs in to Office 365: "There was a problem accessing the site.”
Still need help? Go to the Office 365 Community
Article ID: 2521057 - Last Review: May 22, 2013 - Revision: 27.0