logo
search
Microsoft 365 Error Codes

How to Fix Microsoft Sign-In Error AADSTS50196 Client Request Loop

Maira MehtabMaira Mehtab Sep 21, 2026 869 views

Question details

Users are unable to log in to Microsoft services due to error AADSTS50196, which stops the authentication process after detecting a client request loop.

Product
Microsoft 365 / Microsoft Entra ID
Device & OS
not provided
Scenario
Attempting to sign in to a Microsoft application, third-party integration, or service using a work or school account.
Observed behavior
The sign-in operation is terminated by the server. An error message appears stating AADSTS50196 (client request loop) and advises the user to contact the application vendor or IT administrator.
Before you start

Before proceeding, check your network environment to see if you are actively connected to a corporate network or a company VPN, as these settings frequently impact authentication policies.

Solution 1Recommended

Gather Sign-In Context and Contact Your IT Administrator

Since this error is usually tied to backend organizational policies or app configurations, you need to collect specific connection details and escalate the issue to your IT admin.

Error AADSTS50196 generally means an application or service is stuck in an infinite loop, requesting authentication tokens too rapidly. Microsoft's servers block this to protect the system. End users typically cannot fix this without administrator intervention.

1
Identify Account and Service

Confirm the exact Microsoft service or third-party application you are trying to access, and note whether you are using a personal, work, or school account.

2
Copy the Error Details

On the error screen, look for the 'More details' or 'Troubleshooting details' section. Copy the entire error message, paying special attention to the 'Correlation ID' and 'Timestamp'.

3
Note Your Network Status

Document whether your device is currently connected to a corporate Wi-Fi network, a mobile hotspot, or a company VPN.

4
Escalate to the Administrator

Provide the copied error details and your network status to your organization's Microsoft administrator or IT helpdesk so they can investigate the application configuration and network routing.

For Application Developers: If you are the vendor or developer of the application causing this error, review your code to ensure your app is silently handling token acquisition properly and not getting trapped in a repetitive prompt loop.
Free Microsoft Office alternative

Use WPS Office as a Reliable Alternative to Microsoft 365

If persistent Microsoft login errors are preventing you from accessing your important documents, switch to WPS Office. It provides robust offline capabilities and a comprehensive suite for Word, Excel, and PowerPoint files without the hassle of continuous online authentication loops.

  1. 1. Download the Installer: Visit the official WPS Office website and click the free download button.
  2. 2. Install WPS Office: Run the downloaded file and follow the simple on-screen instructions to set up the software.
  3. 3. Open Your Documents: Launch WPS Office and open your existing files directly from your local drive without needing a Microsoft account.
Fully compatible with Microsoft Office formats, including .docx, .xlsx, and .pptx.Lightweight installation allows you to open documents instantly.Edit documents completely offline, bypassing complex cloud authentication errors like AADSTS50196.Familiar user interface ensures a seamless migration from Microsoft 365.
microsoft office alternative - wps office

Frequently Asked Questions

What does error AADSTS50196 actually mean?

It indicates a 'client request loop.' This happens when a Microsoft service or a third-party application repeatedly requests authentication tokens in a very short amount of time, prompting Microsoft Entra ID to terminate the connection to prevent system overload.

Can I fix the AADSTS50196 error on my own?

In most cases involving work or school accounts, you cannot fix this yourself. The issue is usually rooted in conditional access policies, network restrictions, or bad application code that requires an IT administrator or the software developer to resolve.

Will clearing my browser cache resolve this error?

Sometimes. If the authentication loop is being caused by a corrupted or expired session token cached in your browser, clearing your cookies and cache, or attempting to log in via an Incognito/Private window, may bypass the error temporarily.

Why does the error ask me to contact the application vendor?

If you are trying to log into a third-party application using your Microsoft credentials, the vendor's software might have a bug causing the infinite loop. The developers need to update their code to fix how the app requests access tokens from Microsoft.