If Teams keeps signing you out on a company-managed Windows device, you lose access to chats, files, and meetings at the worst moments. This usually happens because of a conflict between the Teams app cache, a Windows credential issue, or a conditional access policy that your device fails to satisfy. In this article, you will learn the exact causes of repeated sign-outs and the step-by-step fixes that work on managed devices. You will also see how to check the Teams admin center for policy settings that force sign-outs.
Key Takeaways: Fix Teams Sign-Out Loops on Managed Windows
- Teams cache folder (AppData\Roaming\Microsoft\Teams): Corrupted cache files cause frequent sign-outs; clearing them forces a fresh sign-in.
- Windows Credential Manager: Stale Teams credentials in the Windows Credential Manager break token refresh; removing them restores a clean sign-in.
- Teams admin center > Conditional access policies: Device compliance requirements can block or terminate Teams sessions; verify your device meets policy conditions.
Why Teams Signs Out Automatically on a Managed Device
Teams relies on a background service called the Teams Update Service and a set of local cache files to keep you signed in. When the cache becomes corrupted or the Windows token that Teams uses expires, the app cannot refresh your session and forces a sign-out. On managed devices, group policies or conditional access rules from your IT department can also terminate sessions if the device fails a compliance check.
A second common cause is the Teams app itself. The new Teams desktop client uses a separate cache location and may conflict with the classic Teams app if both are installed. Additionally, Windows Credential Manager stores sign-in tokens for Teams; if those credentials are outdated or blocked by a security policy, Teams logs you out to avoid using an invalid token.
How Conditional Access Policies Affect Teams Sign-In
Conditional access policies in Microsoft Entra ID can require that your device be marked as compliant before Teams allows a session. If your device does not report compliance, the policy blocks the sign-in or forces a sign-out after a short period. Managed devices often have Intune or Configuration Manager settings that must be updated to meet compliance rules.
Steps to Stop Teams from Signing You Out
Follow these steps in order. Each step addresses a different cause, so test after each one to see if the sign-out stops.
Step 1: Clear the Teams Cache
- Close Teams completely
Right-click the Teams icon in the system tray and select Exit. Then open Task Manager with Ctrl+Shift+Escape and end any process named Teams or ms-teams. - Open the cache folder
Press Win+R, type %appdata%\Microsoft\Teams, and press Enter. This opens the Teams cache directory. - Delete the cache contents
Select all files and folders inside the Teams folder and delete them. Do not delete the Teams folder itself. - Restart Teams
Launch Teams from the Start menu. You will need to sign in again. This clears any corrupted token files that forced the sign-out.
Step 2: Remove Stale Credentials from Windows Credential Manager
- Open Credential Manager
Press Win+S, type Credential Manager, and select the app from the search results. - Go to Windows Credentials
Click the Windows Credentials tab. Look for entries that start with MicrosoftTeams or contain teams.microsoft.com. - Remove the Teams credentials
Click the arrow next to each Teams-related entry, then click Remove. Confirm the deletion. - Restart Teams
Sign out of Teams if it is open, then close it. Reopen Teams and sign in with your work account. This forces Windows to create a fresh token for Teams.
Step 3: Check for Conflicting Teams App Versions
- Open Settings
Press Win+I to open Windows Settings, then go to Apps > Installed apps. - Look for both Teams versions
Search the list for Microsoft Teams and Microsoft Teams (work or school). If both appear, the classic Teams app may be interfering with the new Teams client. - Uninstall the classic Teams app
Select Microsoft Teams (classic) and click Uninstall. Keep the new Teams app installed. After uninstalling, restart your device and sign in to Teams.
Step 4: Verify Conditional Access and Compliance Policies
- Check device compliance
Open the Microsoft Intune Company Portal app on your device. If the device shows as non-compliant, click Check Access to refresh the status and follow any prompts to update policies. - Contact your IT administrator
If the device remains non-compliant, your IT team must adjust the conditional access policy or the device configuration. Ask them to verify that the policy allows Teams sign-in on your device. - Review Teams admin center policies
If you have admin rights, go to Teams admin center > Users > Manage users, select your account, and check the assigned policies. Look for a session timeout policy that may force sign-outs.
If Teams Still Signs Out After the Main Fix
Sometimes the sign-out loop continues even after clearing cache and credentials. The following issues are common on managed devices.
Teams Signs Out After Every PC Restart
This often happens when the Teams app is set to run as administrator or when the user profile is corrupted. Right-click the Teams shortcut, select Properties, and clear the Run this program as an administrator check box. Then sign out and sign back in.
Teams Signs Out Only When Using a VPN
VPN connections can change your IP address, which triggers a conditional access policy that requires a new sign-in. Check with your IT team to see if the VPN is configured to allow Teams traffic without re-authentication. You can also try disconnecting the VPN, signing in to Teams, then reconnecting the VPN.
Teams Signs Out During Meetings
A token refresh failure during a meeting causes an abrupt sign-out. This is usually due to a network proxy that blocks the refresh token endpoint. Ask your IT team to allow the URLs listed in the Microsoft 365 network endpoints documentation, especially login.microsoftonline.com and teams.microsoft.com.
New Teams Desktop vs Classic Teams on Managed Devices
| Item | New Teams Desktop | Classic Teams Desktop |
|---|---|---|
| Cache location | %appdata%\Microsoft\Teams | %appdata%\Microsoft\Teams (same path, but separate subfolders) |
| Sign-out behavior | More stable with token refresh | Known to drop sessions when cache is corrupted |
| Conditional access support | Full support for device compliance | Limited support in some environments |
| Recommended for managed devices | Yes, use the new Teams | No, migrate to new Teams |
If you are still on classic Teams, plan to switch to the new Teams. Your IT administrator can enable the new Teams toggle in Teams admin center > Teams apps > Manage apps.
After completing the steps, you should be able to keep Teams signed in for days without interruption. Start by clearing the cache and credentials, then verify your device compliance. If the problem persists, check the Teams admin center for session policies and ask your IT team to review conditional access rules. Use the new Teams desktop app to avoid the sign-out loop entirely.