Another Account From Your Organization Is Already Signed In

Clear saved sign-in data, switch to the right profile, then sign in with one work account to stop this “already signed in” message.

If you’re seeing the “already signed in” message on your screen today, you’re not alone. It pops up when Microsoft 365 apps, Windows, or your browser thinks a work account is still active in the background. You can be staring at a clean sign-in screen and still get blocked.

This page walks you through the fixes that usually work on the first try, plus the deeper cleanups that remove stubborn cached tokens. You’ll end up with one clear path: one device, one active work account, no mystery leftovers.

Why This Message Shows Up

Most of the time, the message is about stored identity data, not a person secretly logged in. Microsoft 365 apps use sign-in caches so you don’t have to enter a password every time. When that cache holds two accounts from the same organization, or it holds an old account that no longer matches your current sign-in, the apps can refuse the new session.

Microsoft notes that the error can be expected when a different Microsoft 365 account from the same tenant is already signed in. Older Office builds can also block a second user in the same organization during a single session.

Common Triggers People Miss

You switched accounts in a browser — Your browser profile kept cookies for a work portal, then the desktop app tried to reuse them.
You signed in once on this Windows profile — The login token stayed in a local cache even after you removed the account from an app.
You changed your work email — The old UPN, alias, or domain is still stored in a sign-in file.
You use two organizations on one PC — OneDrive, Teams, Outlook, and Office can each keep their own account state.

Fast Checks That Fix Most Cases

Quick check — Do these in order. Stop when the message disappears.

Sign out of every Microsoft 365 app — In Word or Excel, go to File, then Account, then Sign out. Close every Office window after that.
Quit Teams and OneDrive fully — Use the tray icons, choose Quit, then confirm the processes are gone in Task Manager.
Restart your device — A restart clears in-memory tokens that survive app close.
Sign in once, with one work account — Open one Office app, sign in, and keep it to a single organization account on that Windows profile.

If you’re using the web and the desktop app together, try a clean browser profile for work. A separate profile keeps work cookies from colliding with personal sign-ins.

Browser Reset When The Wrong Account Keeps Auto-Picking

If the desktop app opens a browser sign-in and it keeps jumping to the wrong user, test with a clean session. You’re trying to break the link between saved cookies and the account chooser.

Use a private window — Open an InPrivate or Incognito window and sign in from scratch to see if the error disappears.
Clear Microsoft sign-in site data — In your browser settings, clear cookies for login.microsoftonline.com and office.com, then retry the sign-in flow.
Remove saved passwords for work sites — Saved entries can auto-fill the wrong user and push you into a loop.

After you confirm a clean browser session works, repeat the sign-in using your normal profile, then remove the extra work account from that profile’s cookie store.

Use This Table To Pick The Right Cleanup

Where The Conflict Lives	What To Clear	When To Try It
Office apps	Sign out, close apps, reopen, sign in once	First attempt on any device
Windows account links	Disconnect work account in Settings	When Office keeps pulling the wrong user
Local identity cache	Delete OneAuth and IdentityCache folders	When the error survives sign-out and restart

Fixing The Organization Account Already Signed In Error On Windows

When the fast steps don’t clear the block, treat it like a cache problem. You’ll remove saved identities, then let Office rebuild fresh sign-in files the next time you log in.

Before you start — Close Word, Excel, Outlook, Teams, OneDrive, and any browser tabs open to Microsoft 365 portals.

Save your work, then close apps; open files can hold a token longer than you expect.

Step 1: Disconnect Work Or School Accounts

Open Windows Settings — Go to Accounts, then Access work or school.
Disconnect stale entries — If you see an account you no longer use for office.com, select it, then choose Disconnect.
Restart, then test Office activation — Open Word and try signing in with the account you want.

Step 2: Clear OneAuth Account Files

Microsoft’s activation troubleshooting points to the OneAuth account store. The folder can contain one or more GUID-named files that keep account hints and app association data.

Open the OneAuth accounts folder — In File Manager, paste %localappdata%\\Microsoft\\OneAuth\\accounts into the location bar.
Open the GUID files in Notepad — Look for an account_hints value that matches the user you want to keep.
Mark Office as disassociated — In files tied to old users, change the Office entry in association_status from “associated” to “disassociated,” then save.
Try signing in again — Open Word and sign in with only your chosen work account.

Step 3: Remove Cached Identity Folders

If the file edits feel too fiddly, Microsoft lists a simpler reset: sign out, remove cache folders, then sign in again. This wipes saved tokens so Office can rebuild clean state.

Sign out of all Microsoft 365 apps — Make sure every Office app shows “Sign in” next to your profile area.
Delete local cache folders — Remove all folders inside these paths: %localappdata%\\Microsoft\\OneAuth and %localappdata%\\Microsoft\\IdentityCache.
Restart and sign in — Open Word and sign in to activate again.

Step 4: Run The Microsoft Sign-In Troubleshooter

If your sign-in keeps looping, try Microsoft’s sign-in troubleshooter through the Get Help app. It can reset stuck activation and identity pieces without you hunting through folders.

Open Get Help — Use the Start menu search for Get Help.
Run the Microsoft 365 sign-in troubleshooter — Follow the prompts, then reboot if it asks.
Test activation again — Open one Office app and sign in once.

Another Account From Your Organization Is Already Signed In When You Use Office Apps

This message can show up inside Word, Excel, or Outlook when you try to switch users. With Office 2013, Microsoft explains that one Microsoft 365 sign-in per tenant per session is normal behavior. Newer builds handle switching better, but an older cached identity can still force the same error.

Try this path — Sign out inside the Office app, close it, restart your PC, then sign back in with the one account you want active. If the account picker still shows the wrong user, remove connected services and stored credentials on that Windows profile.

Clean Office Credentials Without Digging Into Files

Remove connected services — In the Office app, go to File, then Account, then remove services tied to the wrong user.
Clear Windows Credential Manager entries — Search for Credential Manager, open Windows Credentials, then remove entries that mention Office, ADAL, or your old work email.
Sign in using “This app only” if prompted — When Office asks if it can manage the device, pick the option that keeps your sign-in limited to the app unless your org requires device management.

Mac Fix If The Error Appears During Activation

On macOS, Microsoft points to a OneAuth reset flag you can set from Terminal, then reopen Word and continue activation. It’s a quick way to clear stale credentials tied to Office sign-in.

Close all Microsoft 365 apps — Quit Word, Excel, Outlook, and OneDrive.
Run the reset command — Open Terminal and run defaults write com.microsoft.Word ResetOneAuthCreds -bool YES.
Reopen Word and sign in — Complete activation with the account you want.

If the Mac steps don’t work, try signing out of the app, deleting local Office sign-in data, then signing in again. The aim is the same: remove cached identities so the app stops trying the wrong one.

Admin-Side Checks When Users Keep Getting Blocked

If you manage Microsoft 365 for a team, the user’s device state can matter as much as the app state. Microsoft lists admin checks like user license assignment and device status in Microsoft Entra ID.

Quick Admin Checklist

Confirm the license is assigned — In Microsoft 365 admin center, open the user and verify the right license box is ticked.
Toggle the license once — If it looks correct, uncheck, save, then recheck and save again.
Check device status — In Entra admin center, look for the device under Devices and enable it if it’s disabled.

Some network tools can interfere with activation. If your user is behind a proxy, firewall, or VPN, test once with that layer off to rule out blocked sign-in traffic.

Stop The Error From Coming Back

Once you fix the sign-in state, a few habits keep it from returning. The goal is to keep your work identity clean and separate, so cached cookies and tokens don’t cross wires.

Simple Habits That Help

Use one Windows profile per work identity — Separate Windows logins prevent cross-account cache collisions.
Use separate browser profiles — Keep work portals in one profile and personal browsing in another.
Pick one sign-in method and stick with it — If you sign in with a work account in Teams, use the same account in OneDrive and Office on that device.
Update Windows and Microsoft 365 — Updates can fix sign-in bugs and token handling issues.

If you see the message again after a clean setup, don’t keep hammering the Sign in button. Sign out everywhere, reboot, then repeat the cleanup steps. That’s faster than guessing.

Official References

If you’re still stuck after the full cleanup, create a new Windows user account and try activation there. A fresh profile starts with empty identity caches, which often ends the loop.

When the message reads another account from your organization is already signed in and you’re sure you’re using the right user, the fix is nearly always the same: clear the cached sign-in traces, then sign in once with the account you want.

Use that same approach if you see another account from your organization is already signed in during Office activation after a password change. Clear the cached data, restart, then sign in fresh.