“Sorry, another account from your organization is already signed in”

The error “Sorry, another account from your organization is already signed in” occurs when Microsoft 365 desktop applications detect an active or residual authentication token from the same organizational domain while attempting to add a second business account. Office desktop apps enforce a single-tenant identity policy, preventing two separate user accounts from the same Microsoft 365 tenant from being active at the same time in the same client session. This issue is usually caused by lingering entries in the Windows Credential Manager or cached identity keys in the Windows registry. Clearing these stale credentials and resetting the identity state restores normal sign-in capability.

Fast-Fix: The 45-Second Solution

This low-risk error occurs when an active identity token conflicts with a prior account on the same tenant domain. To fix it immediately, sign out of all accounts in Word via File → Account, remove all generic credentials under MicrosoftOffice16_Data in Windows Credential Manager, and restart Office before signing back in.

Diagnostic Snapshot

• Severity Tier: Low (Blocks user account switching in desktop apps; web applications remain unaffected)
• Data Safety Risk: Zero (No document loss or cloud mailbox corruption occurs)
• Common Cause: Residual identity tokens in Windows Credential Manager or stagnant registry subkeys under HKCU\Software\Microsoft\Office\16.0\Common\Identity
• Admin Requirement: None for individual client credential resets; Admin required if tenant-level user identity policies enforce restricted workstation mapping

Condition: Low Risk vs. High Risk

• Low Risk: The error appears on a single machine when a user attempts to switch between two corporate accounts or after a user password update. Clearing local credential stores resolves the issue completely.
• High Risk: The prompt occurs systematically across a shared computer environment (such as a multi-user workstation or Remote Desktop Server) where user profiles are not properly cleared upon logoff. This points to misconfigured profile roaming or a lack of Shared Computer Activation (SCA) settings.

The System Break (What This Means)

Microsoft 365 desktop client apps use Modern Authentication (MSAL/ADAL) to manage user identity tokens. While Office allows you to connect multiple personal Microsoft accounts alongside a work account, it enforces a single-account restriction per enterprise tenant domain. Think of the Office authentication manager like a single-slot card reader on an office door. If you attempt to swipe a second keycard from the exact same building facility without retrieving the first card from the reader, the system jams and denies access to prevent identity mixing.

When you sign into Word or Outlook, Office generates an identity subkey in the Windows registry and stores a refresh token in the Windows Credential Manager. If an old session is closed without purging these tokens, or if you attempt to sign into a second mailbox under @yourcompany.com, the Office Identity Broker detects the matching tenant ID domain. Seeing an existing active token for that tenant, it halts execution and displays the error message.

Root Cause Probability

• Likely (60%): Stale or orphaned identity tokens residing in Windows Credential Manager under MicrosoftOffice16_Data.
• Possible (30%): Residual identity registry entries under HKCU\Software\Microsoft\Office\16.0\Common\Identity\Identities.
• Rare (10%): A mismatched Workplace Join token linked to Windows Access work or school settings.

Conflict Escalators

• Shared Workstations Without SCA: Logging multiple organizational accounts into standard desktop installations on shared PCs without Shared Computer Activation enabled.
• Domain Name Changes or Mergers: Users attempting to sign in with an updated primary User Principal Name (UPN) while their old email alias token remains cached locally.
• New Outlook and Teams Toggles: Switching between Classic and New Outlook builds while secondary accounts are attached can leave orphaned identity tokens in the modern authentication cache.

Progression: 1 Hour → 24 Hours → 1 Week

• 1 Hour: Users are blocked from signing into desktop Office applications with their secondary or updated organizational account.
• 24 Hours: Unsynchronized local edits accumulate in temporary file caches because desktop apps refuse to save changes back to the secondary account’s SharePoint or OneDrive location.
• 1 Week: Local identity stores become clogged with competing refresh requests, potentially triggering secondary authentication loops.

Common Misdiagnoses

• Account Home vs Business Conflict: This error is not a personal vs. work account conflict; it specifically occurs between two accounts belonging to the same organization. See Microsoft 365 Home vs Business Account Sign-in Conflicts for cross-account type issues.
• General Identity Error 1001: While Error 1001 blocks modern authentication through broken broker components, it does not specifically cite another account being signed in. See Resolving “Something Went Wrong” Error 1001 in Outlook and Teams.
• Unlicensed Product State: This error is an identity collision, not an entitlement failure. See Troubleshooting Microsoft 365 “Reduced Functionality Mode” after Update if apps enter view-only mode after signing in.

Immediate Action Steps

Step 1: Sign Out of All Office Accounts

Sign out completely to allow Office to release active file locks and identity handles.

1. Open Word or Excel.
2. Navigate to File > Account.
3. Under User Information, click Sign Out for all listed accounts.
4. Close all open Office applications.

Step 2: Purge Office Credentials from Windows Credential Manager

Remove lingering token payloads from the Windows operating system cache.

1. Open the Start menu, search for Credential Manager, and select it.
2. Click on Windows Credentials.
3. Scroll down to Generic Credentials.
4. Locate and expand all entries starting with MicrosoftOffice16_Data, ADAL, or MSAL.
5. Click Remove for each entry.
6. For detailed clearing methods, see How to Clear Office Credential Cache on Windows 11 (The Modern Way) and How to Clear Stale Office Tokens from Windows Credential Manager.

Step 3: Remove Cached Identity Registry Keys

Clear lingering registry identity blocks where Office tracks signed-in accounts.

1. Press Windows Key + R, type regedit, and press Enter.
2. Navigate to: HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity
3. Expand the Identities folder.
4. Right-click and delete any subfolders listed under Identities (e.g., folder names containing user hashes or email addresses).
5. Restart your computer.

Step 4: Disconnect Mismatched Workplace Accounts

Ensure Windows itself is not holding an conflicting account token.

1. Open Windows Settings > Accounts > Access work or school.
2. Select any organizational account that is not your primary active account.
3. Click Disconnect and confirm.
4. Relaunch Word and sign back in with your designated account.

Hard-Stop Red Flags

Escalate to your IT Administrator if you encounter these conditions:

• Disconnecting the account fails due to administrative group policies on a managed company device.
• The error recurs immediately after every system reboot, indicating an automated deployment script or policy is re-injecting stale registry keys.
• The issue affects every user on a Virtual Desktop Infrastructure (VDI) environment.

What the IT Admin Will Check

If manual credential clearing does not resolve the issue for a managed user, administrators will review:

• Shared Computer Activation (SCA): Verify if the machine is a shared host and needs SCA enabled in the registry under HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration\SharedComputerLicensing = 1. See [INTERNAL LINK: S01C01.16 – Fix: Shared Computer Activation (SCA) Errors in VDI Environments].
• Automated Activation State Reset: Run the official Microsoft activation reset script to automatically wipe all cached tokens, licensing files, and identity keys in one pass. See How to Reset the Microsoft 365 Activation State (Using SaRA Tool).
• Entra ID Primary Refresh Token (PRT) Status: Run dsregcmd /status in Command Prompt to verify if the machine has a valid PRT binding with Microsoft Entra ID.

Resolution Complexity

• Complexity: Minor
• Time to Resolve: 5 minutes
• User Action: Sign out of Office, clear Credential Manager entries, and delete stale registry identity folders.

Related Error Escalators

If you experience ongoing sign-in blocks or login loops after resetting your identity cache:

• [INTERNAL LINK: S01C01.32 – Resolving “Stay signed in to all your apps” Loop during Login
• [INTERNAL LINK: S01C01.37 – How to Clear Stale Office Tokens from Windows Credential Manager

Ticket Closed

The “Sorry, another account from your organization is already signed in” error is a safeguard against cross-tenant identity mixing in Microsoft 365 client applications. In nearly all instances, signing out of Office applications, clearing orphaned entries from Windows Credential Manager under MicrosoftOffice16_Data, and removing lingering keys under HKCU\Software\Microsoft\Office\16.0\Common\Identity\Identities clears the collision and permits a clean sign-in.