logo
search
Sign-in & Login Problems

How to Fix Office 365 Sign-In Errors When AD FS Fails

Maira MehtabMaira Mehtab Sep 28, 2026 870 views

Question details

Users need to resolve a sign-in failure when accessing Office 365 using a federated work or school account.

Product
Microsoft Office 365 / Microsoft Entra
Device & OS
not provided
Scenario
Attempting to sign in to Office 365 desktop or web applications through an enterprise federated work or school account.
Observed behavior
A "Something went wrong" error message appears on the screen before the user is given the opportunity to enter their password, completely blocking the login process.
Before you start

Verify that your internet connection is stable. Because this error typically indicates an enterprise identity or federation problem, end-users should consult their IT administrator before making any changes to device credentials or account settings.

Solution 1Recommended

Verify AD FS and Federation Configuration (For Administrators)

Since this is an identity federation issue, Microsoft 365 or Entra administrators must check the organization-level AD FS setup to resolve the root cause.

The authentication failure happening before password entry implies that the trust relationship or communication between Microsoft 365 and the organization's Active Directory Federation Services (AD FS) is broken.

1
Check AD FS Service Status

Access your server management tools to ensure that the Active Directory Federation Services are currently running and accessible on your primary servers.

2
Verify Federation Metadata and Certificates

Ensure the SSL and token-signing certificates are valid, have not expired, and are properly updated in both your local AD FS and Microsoft Entra ID.

3
Validate Network Access and DNS

Confirm that internal and external DNS records point to the correct federation service endpoints and that firewalls are not blocking authentication traffic.

4
Check Modern Authentication

Ensure that Modern Authentication is enabled for your Microsoft 365 tenant and properly configured in your AD FS environment.

Free Microsoft Office alternative

Switch to WPS Office for a Hassle-Free Experience

Complex AD FS configurations and enterprise sign-in errors can severely disrupt your workflow. WPS Office provides a free, lightweight alternative that allows you to create, edit, and manage your documents seamlessly without relying on complicated identity federation or forced cloud logins.

  1. 1. Download WPS Office: Visit the official WPS Office website and download the free installation package for your operating system.
  2. 2. Install the Software: Run the downloaded installer and follow the simple on-screen instructions to set up the software.
  3. 3. Open Your Files: Launch WPS Office and directly open your existing Microsoft Word, Excel, or PowerPoint files to start working offline.
Fully compatible with Microsoft Office formats (.docx, .xlsx, .pptx)No complex enterprise sign-in or AD FS dependencies requiredLightweight software with a fast, familiar user interface100% free core features for seamless offline document editing
microsoft office alternative - wps office

Frequently Asked Questions

Why do I get a 'Something went wrong' error before the password screen in Office 365?

This typically occurs when there is a breakdown in communication between Microsoft 365 and your organization's Active Directory Federation Services (AD FS). Because the Microsoft server cannot verify your identity provider's setup, the authentication process fails before it can ask for your password.

Can I fix the AD FS sign-in error myself?

In most cases, end-users cannot fix this independently. Because it involves enterprise-level identity federation, certificates, and networking, you will need your Microsoft 365 or Entra administrator to verify the server-side AD FS configurations.

How do I test if a local Office app issue is causing the sign-in failure?

You can try launching Microsoft Outlook or other Office applications in Safe Mode by holding the Ctrl key while clicking the app icon. If the application opens and signs in successfully, a local add-in might be interfering. Otherwise, use the Microsoft Support and Recovery Assistant for deeper diagnostics.