"No valid Metadata Exchange (MEX) URL registered with the Microsoft Office 365 authentication system" error after you run the MOSDAL Support Toolkit

Article ID: 2707365 - 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?
(http://office.microsoft.com/redir/HA103982331.aspx)
Expand all | Collapse all

PROBLEM

After you run the Microsoft Online Services Diagnostics and Logging (MOSDAL) Support Toolkit, the Active Directory Federation Services (AD FS) diagnostics log shows the following error:
There is no valid Metadata Exchange (MEX) URL registered with the Microsoft Office 365 authentication system.
Note This log is located at Admin_Applications\SSO_Diagnostic_Tests\ADFSDiagnostic.txt.

Additionally, after you sign in to Office 365 resources by using single sign-on (SSO)-enabled user ID credentials, rich client application authentication may fail when you try to access services.
Back to the top | Give Feedback

CAUSE

This issue may occur if one of the following conditions is true:

  • The MEX service endpoint is disabled in the on-premises AD FS 2.0 Federation service.
  • The MEX service endpoint is enabled in the on-premises AD FS 2.0 Federation service, but it was disabled the last time that the update-MSOLFederatedDomain cmdlet was run to update Office 365 with AD FS 2.0 configuration data. To determine whether AD FS 2.0 metadata isn't updated correctly, see the "Cause" section of following Microsoft Knowledge Base article:
    2647020
    (http://support.microsoft.com/kb/2647020/ )
    "Your organization could not sign you in to this service" error and "80041317" or "80043431" error code when a federated user tries to sign in to Office 365
Back to the top | Give Feedback

SOLUTION

To resolve this issue, use one of the following methods, as appropriate for your situation.

Method 1: Reset the AD FS 2.0 service endpoints to the default configuration

To make sure that the AD FS service endpoints are set up to support SSO authentication, see the following Microsoft Knowledge Base article:
2712957
(http://support.microsoft.com/kb/2712957/ )
SSO authentication to Office 365 fails after you change AD FS 2.0 service endpoint settings in the AD FS 2.0 Management


Method 2: Make sure that the AD FS 2.0 service endpoint configuration is updated to Windows Azure AD

To make sure that the AD FS 2.0 service endpoint configuration metadata is updated to the Windows Azure Active Directory (Windows Azure AD) authentication system, see the "How to update the configuration of the Office 365 federated domain" section of the following Microsoft Knowledge Base article:
2647048
(http://support.microsoft.com/kb/2647048/ )
How to update or to repair the configuration of the Office 365 federated domain

Back to the top | Give Feedback

MORE INFORMATION

Still need help? Go to the Office 365 Community
(http://community.office365.com/en-us/default.aspx)
website.
Back to the top | Give Feedback

Properties

Article ID: 2707365 - Last Review: May 15, 2013 - Revision: 9.0
Applies to
  • Microsoft Office 365 for enterprises (pre-upgrade)
  • Microsoft Office 365 for education  (pre-upgrade)
  • Windows Azure Active Directory
Keywords: 
o365 o365a mosdal4.5 o365022013 o365062011 o365e o365m pre-upgrade after upgrade KB2707365
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top