Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
"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?
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:
Note This log is located at Admin_Applications\SSO_Diagnostic_Tests\ADFSDiagnostic.txt.
There is no valid Metadata Exchange (MEX) URL registered with the Microsoft Office 365 authentication system.
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.
This issue may occur if one of the following conditions is true:
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 configurationTo make sure that the AD FS service endpoints are set up to support SSO authentication, see the following Microsoft Knowledge Base article:
(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 ADTo 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:
(http://support.microsoft.com/kb/2647048/ )How to update or to repair the configuration of the Office 365 federated domain
Still need help? Go to the Office 365 Community
Article ID: 2707365 - Last Review: May 15, 2013 - Revision: 9.0