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:
The Metadata Exchange (MEX) address for AD FS could not be accessed.
This log is located at Admin_Applications\SSO_Diagnostic_Tests\ADFSDiagnostic.txt.
Additionally, after you sign in to your Microsoft cloud service such as Office 365, Microsoft Azure, or Windows Intune by using a federated account, 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 Azure Active Directory (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, see the following Microsoft Knowledge Base article:
How to troubleshoot non-browser apps that can’t sign in to Office 365, Azure, or Windows Intune
Method 2: Make sure that the AD FS service endpoint configuration is updated to the Azure AD authentication system
To make sure that the AD FS service endpoint configuration metadata is updated to the 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:
How to update or repair the settings of a federated domain in Office 365, Azure, or Windows Intune
Still need help? Go to the Office 365 Community
website or the Azure Active Directory Forums