One or more AD FS proxy servers are unable to contact the AD FS service. As a result, user sign-in requests processed by these servers will fail.To fix this problem, be sure that the AD FS Configuration Database Service is available and reachable and that the AD FS service account has access to the configuration database. If you're using SQL Configuration Store, be sure that the network connection between the federation server and the SQL server is reliable.To verify that the configuration database is currently available, run one of the AD FS PowerShell commands from the server (for example, Get-ADFSProperties). The command will run successfully only if the configuration database is reachable and accessible from the federation server.
One of your on-premises Federation Service certificates is expiring. Failure to renew the certificate and update trust properties ...
One of your subscriptions is about to expire in the next few days. Follow the link and take appropriate action. Subscription ...
One of your subscriptions is in grace period and is about to expire in the next few days. This subscription has active users ...
One or both of the synchronization services aren't running. Make sure that the Windows Azure Active Directory Sync Service ...
One or more AD FS proxy servers are unable to contact the AD FS service. As a result, user sign-in requests processed by ...
One or more Exchange Configuration objects were found to be corrupt and in an inconsistent state. Please see the log for ...
One or more of the licenses could not be modified because they are inherited from a group membership. To view or modify group ...
One or more of your users are still using the old OneDrive sync client, which could be causing sync problems. We highly recommend ...
One or more Redirect URIs in your current project settings do not exist in your app's Azure Active Directory entry. Would ...