"Metadata Exchange (MEX) address for AD FS could not be accessed" error after you run the MOSDAL Support Toolkit

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.

Additionally, after you use single sign-on (SSO)-enabled user ID credentials to sign in to Office 365 resources, you may receive a "Page not found" when you try to connect to AD FS.

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

• DNS can't resolve the AD FS service name.
• The AD FS MEX address was changed, but AD FS configuration metadata wasn't updated to the Windows Azure Active Directory (Windows Azure AD) authentication system.

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

Method 1: Troubleshoot client connectivity problems

To identify and resolve issues that cause client computer network connectivity problems, click the following article number to view the article in the Microsoft Knowledge Base:

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

To make sure that the AD FS service endpoint configuration metadata is updated to the 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: �

Still need help? Go to the Office 365 Community�website or�the�Windows Azure Active Directory Forums website.