How to reestablish trust with the Office 365 authentication platform after the AD FS 2.0 server stops responding

When a federated user tries to use Active Directory Federation Services (AD FS) 2.0 to authenticate access to a Microsoft Office 365 resource, the user may receive the following error message:For Internet users, the error occurs after they are prompted for valid credentials.

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 Trusting Party entry 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:�

To verify that the Trusting Party entry is missing or corrupted in the AD FS 2.0 Management console, follow these steps:

1. Sign in to the core AD FS server.
2. Click Start, point to All Programs, click Administrative Tools, and then click AD FS 2.0 Management.
3. In the management console, expand AD FS 2.0, expand Trust Relationships, and then expand Relying Party Trusts.
4. Verify that the Microsoft Office365 Identity Platform entry is present and that it matches the following taxonomy:
   1. On the Monitoring tab, verify the following settings:
   2. • Metadata URL: https://nexus.microsoftonline-p-int.com/federationmetadata/2007-06/federationmetadata.xml
      • Monitor Relying Party: selected
      • Automatically update relying party: not selected
   3. On the Identifiers tab, verify the following settings:
   4. • Display Name: Microsoft Office 365 Identity Platform
      • Relying party identifiers:
        � https://login.microsoftonline-int.com/extSTS.srf
        urn:federation:MicrosoftOnlineINT
   5. On the Endpoints�tab, verify the following settings for the�WS-Federation Passive Endpoints:
   6. • URL: https://login.microsoftonline-int.com/login.srf
      • Index: 0
      • Binding: POST
      • Default: Yes
      • ResponseURL: <blank>
   7. On the Advanced tab, verify the following setting:
      
      Secure hash algorithm: SHA-1

Note All other tabs and fields are intentionally left blank.

If the entry is present, but the entry does not match the taxonomy that is listed, update the entry manually to resolve the issue. Or, delete the entry, and then continue with one of the following methods. If the entry is missing, continue with one of the following methods.

Method One: Re-add /update the Federated Domain Relying Party Trust

1. Click Start, point to All Programs, click Microsoft Online Services, right-click Microsoft Online Services Module for Windows PowerShell, and then click Run As Administrator.
2. At the command line, type the following commands, and press ENTER after each command:
3. • connect-MSOLService
     Note�Log on by using Office 365-managed administrator account credentials in this command.
   • If you run these commands on a server that is not�in the AD FS 2.0 Federation Server farm, type�Set-MsolADFSContext -Computer:<AD FS Servername>
   • Update-MSOLFederatedDomain -DomainName<Identity_Federated_(AD FS)_Domain_Name>�

Method Two: Remove hardcoded federation metadata endpoint

1. Open�Registry Editor, and then locate the following registry entry:
   
   HKEY_LOCAL_MACHINE\Software\Microsoft\MOCHA\IdentityFederation
2. If the string value FederationMetadataURL�exists, delete the string value. This will restore the normal functionality of�using the metadata endpoint from the Relying Party Trust entry in AD FS 2.0.

For more information about how to troubleshoot the "There was a problem accessing the site." error message, click the following article number to view the article in the Microsoft Knowledge Base: �