Migrating users from one Microsoft 365 tenant to another is a common task for IT administrators, but it often comes with challenges. One of the most frequent issues users face after migration is the “Another account already signed in” error when trying to activate Microsoft Office. This error occurs because the Office installation on the user’s device is still associated with their old tenant account.
In this blog, we’ll walk you through the steps to resolve this issue on both Windows and Mac devices, based on Microsoft’s official guidance from this article.
For Mac Devices
If your users are on Mac devices, follow these steps to resolve the activation issue:
- Close All Microsoft 365 Apps:
- Ensure all Microsoft 365 applications (Word, Excel, Outlook, etc.) are closed.
- Run a Terminal Command:
- Open Terminal on the Mac.
- Run the following command to reset the authentication credentials:
- defaults write com.microsoft.Word ResetOneAuthCreds -bool YES
- Open Microsoft Word and Activate:
- Launch the Microsoft Word app and follow the activation steps using the new tenant account.
- If the Issue Persists:
- Refer to Microsoft’s guide for additional troubleshooting steps: Can’t sign in to an Office 2016 for Mac app.
For Windows Devices
For users on Windows devices, follow these steps to resolve the activation issue:
- Sign Out of All Microsoft 365 Apps:
- Open any Microsoft 365 app (e.g., Word, Excel).
- Go to File > Account and click Sign Out.
- Repeat this for all Microsoft 365 apps.
- Modify the OneAuth Account Store:
- Navigate to the following folder:
- %localappdata%\Microsoft\OneAuth\accounts
- Navigate to the following folder:
- You’ll see one or more
<GUID>
files. These files correspond to the accounts associated with the device. - Open each file using Notepad and examine the
account_hints
value to identify files not associated with the account you want to use. - In each identified file, locate the
association_status
entry and change the status ofcom.microsoft.Office
todisassociated
. For example:- “association_status”: “{\”com.microsoft.Office\”:\”disassociated\”,\”com.microsoft.Outlook\”:\”associated\”}“
- Save the file after making the changes.
- Try Signing In Again:
- Open any Microsoft 365 app and sign in with the new tenant account.
- If the Issue Persists:
- Sign out of all Microsoft 365 apps again.
- Delete all folders in the following locations:
- %localappdata%/Microsoft/OneAuth
- %localappdata%/Microsoft/IdentityCache
Why Does This Happen?
During a tenant migration, the Office installation on a user’s device may still be linked to their old tenant account. This causes a conflict when the user tries to activate Office with their new account. The steps above help clear the old credentials and reset the activation process.
Preventative Measures for Future Migrations
To avoid activation issues during future migrations, consider the following best practices:
- Communicate with Users:
- Inform users about the migration process and provide clear instructions for re-activating Office.
- Use Shared Computer Activation:
- For shared devices, enable Shared Computer Activation to simplify licensing.
- Monitor Activation Status:
- Use the Microsoft 365 Admin Center to monitor Office activation status across your organization.
- Test with a Pilot Group:
- Before migrating all users, test the process with a small group to identify and resolve potential issues.
Conclusion
The “Another account already signed in” error is a common but fixable issue during user migrations. By following the steps outlined above, you can ensure that your users can activate Office seamlessly in the new tenant. Proper planning, communication, and the use of Microsoft’s official troubleshooting guides can make the migration process smoother for both IT administrators and end-users.
!!! THANKS FOR READING !!!
Regards,
HARISH KUMAR
Knowledge is not a finite resource to hoard; it’s a boundless treasure that grows when shared