Teams Keeps Asking You to Sign In (and Family Calls Fail)
In plain English
Teams keeps asking you to sign in when the app cannot match the Microsoft account it expects, and that got more common after Skype retired in May 2025. Start with the account, not the cache, and use the cluster guide, Microsoft 365, Store and Edge Problems: Activation, Install and Sign-In Errors, if you want the broader sign-in path in one place.
First safe step
Before you clear anything, open Teams, select your profile picture, and read which Microsoft account it shows. The family account and a work or school account look identical in this app, and the wrong one loops the sign-in forever.
Stop when Teams stays signed in and a test call connects.
Teams keeps asking you to sign in when the app cannot match the Microsoft account it expects, and that got more common after Skype retired in May 2025. Start with the account, not the cache, and use the cluster guide, Microsoft 365, Store and Edge Problems: Activation, Install and Sign-In Errors, if you want the broader sign-in path in one place.
That order matters for families. If the same Microsoft account still holds group chats, call history, or shared contacts, clearing the wrong session first can split the setup and make the next sign-in harder to trace.
This page starts with the safest check, then moves to the lightest cache cleanup. If the account itself is fine, you can keep the family chat thread intact while you fix the loop, and if the account is the real problem, you will spot that before you touch more app data.
1 What Teams Free is doing and why the loop starts after Skype retirement
This page is for Teams Free sign-in loops, not paid Teams admin problems. If you used Skype before it retired in May 2025, old account links can leave family users bouncing between the wrong Microsoft sign-in screens.
The safest first move is to confirm which Microsoft account owns the family chats and call history before you clear anything. That way you do not split the group into two accounts or lose the thread while chasing the loop.
If you are seeing the same prompt over and over, the issue is usually the account connection, the app cache, or both. The first check belongs to the account, then the app, in that order, so the family chat stays attached to the right login.
This guide sits in the broader Microsoft 365, Store and Edge Problems: Activation, Install and Sign-In Errors cluster, because the same Microsoft account can drive more than one sign-in path. That is why the loop can look like a Teams problem when the account link is the real snag.
2 Check the Microsoft account first, before you clear anything Free
- Start by checking the email address shown in Teams Free, then compare it with the Microsoft account that owns your family chats and call history. If the app shows a different address, or a work alias you do not use for family, you may be signed into the wrong account.
- Look for a second account, an old Skype-connected login, or a saved alias that can make the family group look missing. That group is often still there, but it is tied to the other account, so signing out of the wrong one can hide the chat thread and the call setup until you switch back.
- If you are unsure which account is the family one, open the Microsoft account page in a browser and match the email there with what Teams shows on screen. This is the same kind of account check that also matters in the broader Microsoft 365, Store and Edge Problems: Activation, Install and Sign-In Errors cluster, and it is worth doing before any cache cleanup.
- If the account details do not match, stop and sign back in with the account that was used for the family group, before you try any app fixes. That keeps the chat history and call setup attached to the right profile and avoids splitting the family into two sign-ins.
3 Clear Teams cache in the safest order for family chat preservation Free
- Close Teams completely first. On Windows, open
Task Manager, end everyTeamsorms-teams.exeprocess, then reopenFile Explorerand clear only the cache files tied to the sign-in loop. If you already checked the right Microsoft account, keep that part alone and do not sign out of the family group again. - The safest pattern is to remove the app cache, not the account record. That means deleting the Teams cache folders and temporary files that store old sign-in state, while leaving the Microsoft account itself in place so the family chat thread and call setup stay attached to the same login.
- After that, start Teams again and give it a little time. The first launch can take longer because it rebuilds local data, and you may see a fresh sign-in prompt before the app settles. If the loop was only stale cache, this is the point where the sign-in path usually opens normally.
If you also use the same Microsoft account for billing or another Microsoft app, keep those checks separate for now. The account and billing checks that can block Microsoft sign-in belong in the next step only if the loop comes back after the cache reset.
✓ Signed in? You can stop here.
4 If the loop continues, repair the sign-in path without breaking the family group Free
If Teams still keeps asking you to sign in, check the parts that can break Microsoft auth before you remove the app again. A bad clock, a stale network session, or a browser sign-in problem can make the app loop even when the account itself is fine.
- Start with the device clock. Open Settings, confirm the time, date, and time zone are correct, then turn on automatic time if it is off. After that, reconnect to a trusted network and try the sign-in again, because captive portals and flaky Wi-Fi can block the handoff to Microsoft.
- Next, test the same account in a clean browser window. Sign out of other Microsoft tabs, open a private window, and go to the Microsoft sign-in page for the account that owns the family group. If the browser sign-in works, the account is probably fine and the problem is inside Teams, not the login itself.
- Only after that should you remove and re-add Teams on the device. That keeps the family chat identity tied to the right Microsoft account while you refresh the app install. If the browser sign-in fails too, the fix may be closer to the account side, which is where the Microsoft 365, Store and Edge Problems: Activation, Install and Sign-In Errors cluster starts to overlap with the rest of the sign-in path.
5 When family calls still fail, test the device and app settings that affect calling
- If Teams Free signs in but family calls still fail, start with the device side. Check the microphone and camera, then open the app’s permissions so Teams can use them, and make sure the right speaker, mic, and camera are selected before you change anything deeper.
- If the call still drops or the other person cannot hear you, compare the same setup on another device that uses the same Microsoft account. If calling works there, the problem is usually local to this device or app install, not the family group itself.
- Only after that should you try the app update and reinstall path, and only if the calling problem shows up on more than one device. That keeps you from chasing a one-device settings issue when the account and family chat are already in place.
6 When to stop and use account recovery instead of more app fixes
If the loop still comes back after the account check and cache cleanup, stop treating it like a Teams app problem. A locked, blocked, or security-challenged Microsoft account can keep throwing you back to sign-in, and the fix belongs on the account side, not in Teams.
Use account recovery when you see signs like a password reset prompt you did not ask for, a message that the account is blocked, or a security code that never arrives. If Windows keeps asking for the wrong sign-in method, check Forgot Your Windows PIN? PIN vs Password, and Getting Back In before you keep retrying the app.
If the account page says the account is locked or needs more proof, go to the Microsoft recovery or verification flow and finish that first. That is the safer next step than more app resets, and it fits the same pattern as Microsoft Account Blocked or Locked: The Recovery Form, Done Properly or Verification Code Not Arriving: Email, Text and Authenticator Fixes when the code never shows up.
If you still cannot sign in after that, stop cycling through Teams and use the account reset path from a browser on a trusted device. Once the account is open again, sign back in and let Teams reconnect to the same family login.
Frequently asked questions
Will clearing the Teams cache delete our family group chat?
No, if you sign back in with the same Microsoft account. The chat is tied to that account, not to the cache files on the device. Signing in with a different account can make the chat look missing.
Why does Teams work on my phone but keep asking to sign in on the PC?
That split usually points to the PC sign-in or its cached Teams data, not to the family account. Use the same account on both devices to compare, then clear the cache on the PC only.
The short version
A sign-in loop that survives the account check and a clean cache is rarely solved by signing in one more time. At that point the loop is telling you the problem sits outside the family chat itself, either in the sign-in path on that device or in the account behind it.
Work from that split. Keep the confirmed family account, stop clearing data, and if the sign-in loop is really an account recovery problem, finish recovery in a browser before you open Teams again. When Teams opens without asking, make one short test call before the next family call.
Neighbouring cases in this cluster: 'Product Deactivated' or 'Unlicensed Product' in Word and Excel.
Different number on screen?
Type it exactly as it appears and get the plain-English answer.
Pop-up telling you to call?
That is a scam. Microsoft never asks you to phone a number.