'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix Microsoft 365 Sign-In Redirects to Unreachable ADFS Server
Question details
Users are unable to sign into Microsoft 365, Azure, or email because the federated domain redirects to an offline or unavailable ADFS server.
- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- Attempting to log into Microsoft 365 or Azure services using an account tied to a federated domain.
- Observed behavior
- The login process redirects to an Active Directory Federation Services server that is unreachable, preventing users from authenticating and accessing their accounts.
Ensure you have access to a cloud-only global administrator account (typically ending in .onmicrosoft.com) or are prepared to verify your tenant and DNS ownership with Microsoft Support.
Contact Microsoft Support for Federation Administration
Since the primary ADFS server is down, reaching out to Microsoft Support is the safest method to restore access if you lack a fallback admin account.
When an ADFS server fails completely, the domain must be converted from federated to managed authentication to bypass the broken redirection.
Microsoft Support can assist in unlinking the failed server after verifying your domain ownership.
If you have a fallback admin account, go to the Microsoft 365 admin center and navigate to 'Support' > 'Help & support' to open a service request.
Alternatively, post your issue in the Active Directory Federation Services section of Microsoft Q&A to get guidance from support engineers.
Be prepared to add a TXT record to your domain's DNS settings to prove ownership to the Microsoft support agent.
Ask the administrator or support agent to convert your domain to managed authentication or update your federation configuration.
Convert Federated Domain to Managed via PowerShell
If you have access to a cloud-only global administrator account, you can manually disable federation using the MSOnline PowerShell module.
Switch to WPS Office for a Hassle-Free Experience
Tired of dealing with complex server configurations, ADFS outages, and login failures? WPS Office provides a robust, lightweight, and offline-capable alternative to Microsoft 365. Keep your productivity high without relying on complex enterprise identity servers.
- 1. Visit the WPS Office Website: Go to the official WPS Office website on your computer.
- 2. Download the Installer: Click the 'Free Download' button to obtain the lightweight installation package.
- 3. Install and Launch: Run the installer, follow the on-screen setup prompts, and open WPS Office to start working immediately.
Frequently Asked Questions
Why does my Microsoft 365 login redirect to an ADFS server?
When a domain is set up for federation, Microsoft 365 delegates user authentication to your organization's on-premises Active Directory Federation Services (ADFS) server. If this server goes offline, the redirect fails, blocking access.
Can I bypass the broken ADFS server to access my admin account?
Yes, you can bypass the ADFS redirection by logging in with a cloud-only global administrator account, which typically uses the default '.onmicrosoft.com' domain instead of your custom federated domain.
How long does it take to convert a domain from federated to managed?
Once the PowerShell command is executed or Microsoft Support initiates the change, it can take anywhere from a few minutes to up to 2 hours for the authentication update to fully propagate across all Azure and Microsoft 365 services.
