How to solve this error in Microsoft Teams

Question

Dears,

I wanted to log in to the Teams account (lease) but I get this problem. Suddenly, the Teams application stopped working by itself. How to fix it?

"Request Id: 53c30856-3526-49ef-a062-e24103c42300

Correlation Id: 2db3c7b4-7179-4312-aca9-0175e648e768

Timestamp: 2025-03-14T11:21:00Z

Message: AADSTS900144: The request body must contain the following parameter: 'login_hint'. "

Sincerely
Tomasz

Answer 1

Your issue seems to be related to Azure Active Directory (AAD) authentication when logging into Microsoft Teams. The error message "AADSTS900144: The request body must contain the following parameter: 'login_hint'" indicates that the login request is missing required authentication details.

Possible Solutions:

1. Restart Teams and Clear Cache

• Close Teams completely.
• Delete cache files:

    - Press "Win + R" key, type "%appdata%\Microsoft\Teams", and press Enter.
    
    
    - Delete all files inside the Teams folder.
  

  • Restart Teams and try logging in again.

1. Try Logging in via the Web App

• Open Microsoft Teams Web and attempt to sign in.
  • If successful, reset the desktop app by signing out and back in.

1. Check Your Account and Credentials

• Ensure you’re using the correct email and credentials for the lease account.
  • If you have multiple Microsoft accounts, try switching accounts.

1. Reinstall Teams

• Uninstall Microsoft Teams from Control Panel > Programs & Features.
  • Download and install the latest version from Microsoft Teams website.

1. Check Organisational IT Policies
   • If your Teams account is managed by an organisation, contact your IT admin to check if there are policy restrictions or authentication issues.

If the issue persists, please share more details, such as whether this problem occurs on a personal or work account, and if you're using Windows, Mac, or mobile.

Answer 2

Dear Tomasz,

Since you can log in with your personal account but not the organisation leased one, the issue likely lies on the administrator's side, possibly due to:

1. Conditional Access Policies – Your organisation may have login restrictions based on device, location, or security settings.
2. Multi-Factor Authentication (MFA) – If required, ensure you’re completing the authentication steps (e.g., approval via Microsoft Authenticator).
3. Account License Issues – Your Microsoft Teams license may not be properly assigned or active.
4. SSO/Authentication Configurations – If your organisation uses Single Sign-On (SSO), there might be a misconfiguration preventing access.

Next Steps:

🔹 Contact Your IT Administrator

• Ask them to verify if there are any login restrictions or account issues on their end.
• Request them to check if your Microsoft Teams license is active.

🔹 Try Logging in via InPrivate/Incognito Mode

• Open Teams Web in an Incognito (Private) Browser session and attempt to sign in.

🔹 Try Logging in on Another Device/Network

• If possible, try signing in on a different PC or mobile device.
• Switch to a different internet connection (e.g., mobile hotspot) to rule out network-related blocks.

Let me know if the issue persists after contacting IT.

Best regards,
Muhammad Samiullah

Answer 3

A bit of a convolute procedure, but have a look at Alessandro Caputo post in this thread (towards the end): https://answers.microsoft.com/en-us/msteams/forum/all/error-loginhint/85d47ad0-5f43-4ebe-8756-c78226203be5 worked quite well for me (not perfect but it's the best workaround I've found so far)

A more professional solution (yet it needs to install outdated version): https://answers.microsoft.com/en-us/msteams/forum/all/problem-with-teams-when-changing-tenants-message/bd7f73d6-4d90-45cf-ae9d-f64a75960ee1

Answer 4

Hi @Tomasz Noszczyk

Please try clearing the Teams desktop cache and logging in to your work account again:

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

---

Answer 5

I believe this problem is in the last Teams app version published. The workaround is to downgrade to older version. Microsoft is aware of this situation.