Accessing Microsoft Teams using organizational or personal credentials
Hi @Cathal Moss,
Good day to you.
Thank you for reaching out, I truly appreciate you taking the time to share the details and the troubleshooting steps you’ve already tried.
Based on what you described. This behavior typically points to an issue with the sign-in components Teams relies on such as cached credentials/tokens, local app data, or the embedded web sign-in experience rather than the installer itself. That’s why uninstalling/reinstalling doesn’t always resolve it.
Please try the steps below in order:
Step 1: Fully quit Teams and clear Teams cache/local data (Windows)
- Close Teams completely (right-click the Teams icon in the system tray > Quit).
- Press Windows + R, paste the following, then press Enter:
- %userprofile%\appdata\local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams
- Delete all files and folders in the directory.
- Restart your computer then open Teams and try signing in again.
Additional guidance (Including MacOS environment): Clear the Teams client cache - Microsoft Teams | Microsoft Learn
Step 2: Remove saved work credentials
- Open Control Panel > Credential Manager > Windows Credentials.
- Remove any entries related to Microsoft/Teams/Office/ADAL/Azure (examples: MicrosoftOffice…, Teams…, ADAL…, Azure…).
-
- Restart the computer and attempt Teams sign-in again.
Step 3: Disconnect and re-add your Work/School account (if applicable)
- Go to Settings > Accounts > Access work or school.
- If your work account is listed, select it and click Disconnect.
-
- Restart your computer.
- Add the work account back on the same page, then open Teams and try again.
Step 4: Check the embedded sign-in component
Teams uses a web-based sign-in flow in the background. If the embedded sign-in component is outdated or corrupted, it can cause loops/crashes.
- Ensure Microsoft Edge is up to date.
- If your organization manages devices, please ask IT to confirm Microsoft Edge WebView2 Runtime is installed and updated.
- Restart after updates and test Teams again.
Step 5: Contact your IT
If the issue still continues after these checks, I recommend reaching out to your IT Admin and ask them to verify your organization’s Conditional Access/MFA settings, Intune/MDM device compliance requirements, Entra ID sign-in logs (to confirm whether sign-ins are being blocked or token issuance is failing), and any proxy/SSL inspection configurations that could be interrupting the sign-in flow.
IT admins can refer to this article: Troubleshooting sign-in problems with Conditional Access - Microsoft Entra ID | Microsoft Learn
In case the issue becomes more complex or your IT admins unable to access the necessary information, your admin can open a Microsoft Support ticket through the Microsoft Admin Center so Microsoft can review the detailed authentication traces and logs. They have access to system-level diagnostics and can investigate the problem more thoroughly. At the very least, they can provide the most effective workaround to ensure your experience remains smooth and secure.
As community moderators, we appreciate your understanding that we do not have access to the administrative tools or permissions required to investigate or modify these configurations. We also do not have the capability to initiate remote sessions for direct assistance. Our role is to guide users to the appropriate resources and support channels.
I hope this information is helpful. Should you have any further questions or need additional assistance, feel free to reach out.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have any extra questions about this answer, please click "Comment".
Note: Follow the steps in our documentation to enable email notifications if you want to receive email notifications related to this topic.