"Sorry, another account from your organization is already signed in on this computer" in Office 2013
When you try to sign in to an Office 2013 app by using your Office 365 user ID and password, you receive the following error message:
Sorry, another account from your organization is already signed in on this computer.
This behavior is expected. It occurs if another account is already signed in to Office 2013 by using a different Office 365 user account within the same organization.
Sign out of the first account that signed in, then restart that computer. If this solution does not resolve the issue, try the workaround below.
The method in this section contains steps that explain how to modify the registry. However, serious problems may occur if the registry is modified incorrectly. Follow these steps carefully. For added protection, back up the registry before you begin so that the registry can be restored it if a problem occurs. For more information about how to back up and restore the registry, see the following Microsoft Knowledge Base article: 322756 How to back up and restore the registry in Windows.
This workaround may cause some account settings to be lost.
To work around this behavior, remove the existing user account and all connected services from your Office 2013 profile, and then clear cached credentials that may be on the computer:
Step 1: Remove the user account from your Office 2013 profile
In the upper-right corner of an Office 2013 app (Word, Excel, PowerPoint), select your name, and then select Switch Account.
On the Accounts screen, click Sign out.
Locate the account that you want to remove, and then click Sign out.
Step 2: Remove connected services from your Office 2013 profile
Go to File, and then click Account.
Under Connected Services, remove all the services for the existing account.
Step 3: Clear cached credentials on the computer
Edit the registry to remove cached credentials:
Select Start, click Run, type regedit, and then click OK.
In Registry Editor, locate the following registry subkey:
Select the Office account that you want to delete, and then click Delete.
In the Identity subkey, locate Profiles, right-click the same Office account that you located in Step 1 of this procedure, and then click Delete.
Select File and then Exit Registry Editor.
Remove the cached credentials in Credentials Manager:
Select Start, then Windows System, then open the Control Panel and select Credential Manager.
You may have to use the search field in the Control Panel to find the Credential Manager.
Under the Windows Credentials tab, locate the account that you want to remove and then click Remove.
In Windows 7, this is listed as Generic Credentials.
Log off, and then log back in to the computer.
In Office 2013 apps, you can access Office 365 content in SharePoint Online by providing your Office 365 user ID and password. If you have multiple Office 365 user IDs from different organizations, you can access content from the SharePoint Online deployments of each organization.
However, Office 2013 only supports one Office 365 user sign-in from each tenant or organization per session.
Office 2013 makes a best effort to prevent a second user from signing in when another user from the same organization is already signed in. However, there may be cases in which this scenario is not detected and the Office 2013 user interface may show that another user is successfully signed in. In this case, the second user cannot access his or her own content. All Office 365 content that he or she tries to open will be performed by using the first user’s credentials.
Be aware that Office 2013 respects the permissions of all documents and SharePoint Online libraries. That is, if the first user doesn’t have access to a document that the second user has access to, and the second user (who believes they are signed in) attempts to open that document, the document will not open because Office tries to open the document as the first user.
To fix this scenario, the signed-in user should sign out of Office 2013, and then restart his or her computer. Doing this makes sure that a clean state is present when the other user tries to sign in again.
If restarting the computer does not resolve the issue, then adjusting the registry is the recommended solution.
Still need help? Go to Microsoft Community.