Sign-in & Login Problems

How to Remove an Old Employer's Okta Login from Microsoft Teams

Tauseeq Magsi Oct 10, 2026 869 views

Question details

The user needs to remove a persistent Okta or Microsoft 365 sign-in prompt from a previous employer that continues to appear and block access to desktop applications.

How to Remove an Old Employer's Okta Login from Microsoft Teams

Product: Microsoft Teams and Microsoft 365
Device & OS: Mac OS and Windows 10 Pro
Scenario: Signing into Microsoft Teams and other Office desktop applications after changing employers.
Observed behavior: An old employer's Okta or Microsoft 365 sign-in prompt repeatedly appears and blocks the use of Microsoft Teams and other Microsoft 365 desktop apps.

Before you start

Ensure that you completely close and quit Microsoft Teams and any other open Microsoft 365 applications before attempting to clear your stored system credentials.

Solution 1Recommended

Delete the Identities Cache via Mac Keychain Access

Use this solution if you are on a Mac to manually delete the leftover authentication tokens that trigger the old employer's prompt.

Simply signing out or clearing the standard application cache is often not enough to remove Okta login tokens. The credentials remain stored in your macOS Keychain and must be deleted manually.

Quit Microsoft Teams

Right-click the Microsoft Teams icon in your dock and select 'Quit' to ensure the application is completely closed.

Open Keychain Access

Click on the Spotlight search icon (magnifying glass) in the top-right corner of your screen, type 'Keychain Access', and press Enter.

Search for the Cache

In the Keychain Access search bar, type 'Microsoft Teams Identities Cache'.

Delete the Entry

Right-click the 'Microsoft Teams Identities Cache' entry from the list and select 'Delete'. Confirm the deletion if prompted.

Restart Your Mac

Restart your Mac computer, then open Microsoft Teams to sign in with your new credentials.

Delete the Identities Cache via Mac Keychain Access

Action Successful: Once the identities cache is cleared, Teams will prompt you for a fresh sign-in without defaulting to the previous employer's Okta page.

Solution 2

Clear Stored Credentials in Windows 10 Pro

If you are experiencing this issue on a Windows 10 Pro machine, you must remove the old credentials using the Windows Credential Manager.

Solution 3

Contact the Tenant Administrator

Use this step if clearing local credentials fails and the old login prompt continues to block access to multiple Microsoft 365 applications.

Free Microsoft Office alternative

Avoid Complex Login Conflicts with WPS Office

If persistent enterprise login prompts and tenant account conflicts in Microsoft 365 are disrupting your productivity, consider switching to WPS Office. It provides a lightweight, hassle-free environment that lets you focus on your work without dealing with complex cloud identity issues.

1. Download the Installer: Visit the official WPS Office website and download the free installation package for your Mac or Windows PC.
2. Install the Application: Run the downloaded installer and follow the simple on-screen instructions to set up the software.
3. Open Your Existing Files: Launch WPS Office and directly open your existing .docx, .xlsx, or .pptx files with full formatting compatibility, completely bypassing old Microsoft 365 login prompts.

Free and lightweight office suite for everyday document tasksFully compatible with Microsoft Word, Excel, and PowerPoint formatsNo complex enterprise tenant login dependencies or cache issuesFamiliar user interface for quick and seamless migration

microsoft office alternative - wps office

Frequently Asked Questions

Why does my old employer's Okta login keep popping up in Teams?

When you sign into Microsoft Teams or Office 365, your operating system saves an authentication token locally. If this token isn't properly overwritten when you change accounts, the system continuously attempts to authenticate against your old employer's Okta portal.

Will simply uninstalling and reinstalling Microsoft Teams fix the login issue?

Reinstalling the application typically does not resolve this issue because the login tokens are stored in the system's credential manager (Keychain on Mac or Credential Manager on Windows), which remains intact even when the app is removed.

What if clearing the Teams cache doesn't work for other Office apps?

If applications like Word or Excel are still affected, you need to search your Keychain or Windows Credential Manager for broader 'MicrosoftOffice' generic credentials and delete them. If the issue persists, a Microsoft 365 admin may need to resolve an Azure AD device registration conflict.

Login & Account Issues