The registry path HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity is a core configuration key used by Microsoft Office 16.0 (Office 2016, 2019, and Microsoft 365) to manage user authentication, account sign-in states, and Modern Authentication settings. Core Functions and Features This key serves as the central hub for how Office applications identify the logged-in user and connect to cloud services like OneDrive and Outlook. Microsoft Learn Modern Authentication (ADAL/WAM): Controls whether Office uses Modern Authentication (Active Directory Authentication Library). Setting EnableADAL enables multi-factor authentication (MFA) and single sign-on (SSO), while forces older basic authentication. Identity Storage: Identities subkey stores specific account information, such as email addresses and unique identifiers for connected accounts, including Gmail and corporate Microsoft 365 accounts. Sign-In Troubleshooting: Deleting or renaming this key is a standard "fix" for persistent sign-in loops, password prompts, or "Account Error" messages. Removing it forces Office to clear cached credentials and re-authenticate the user. Web Account Manager (WAM) Overrides: Admins use values like DisableAADWAM DisableADALatopWAMOverride here to troubleshoot issues where the Windows Web Account Manager interferes with Office sign-ins. Microsoft Learn Common Registry Values
Deep Dive: Understanding the "HKEY-CURRENT-USER\Software\Microsoft\Office\16.0\Common\Identity" Registry Key Introduction: The Silent Overseer of Your Office Profile If you have ever opened Microsoft Word, signed into Excel, or allowed Teams to access your OneDrive, you have interacted—indirectly—with a critical but obscure part of the Windows Registry. Located deep within the hive of user-specific settings lies the path: HKEY-CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity . For the average user, this is just a cryptic string of characters. For system administrators and power users, it is the command center for Microsoft Office authentication, user identities, and sign-in states. In this long-form article, we will dissect what this key does, why it is important for Office 365 (Microsoft 365) and Office 2019/2021, common issues that arise from it, and how to safely manage it.
Part 1: Breaking Down the Path (What does it mean?) Before we discuss troubleshooting, let's parse the registry hierarchy:
HKEY_CURRENT_USER (HKCU): This root key contains configuration data specific to the currently logged-in Windows user. Anything changed here does not affect other users on the same machine. Software: The standard parent key for application settings. Microsoft: The vendor namespace. Office: The main suite container. 16.0: This denotes the version number. Crucially , 16.0 is not just for Office 2016. It is the version backbone for: Removing it forces Office to clear cached credentials
Office 2016 (Perpetual) Office 2019 (Perpetual) Office 2021 (Perpetual) Microsoft 365 Apps for Enterprise (formerly Office 365 ProPlus)
Common: Settings shared across multiple Office applications (Word, Excel, Outlook, PowerPoint). Identity: The focus of our article. This subkey manages how Office recognizes who you are.
The Purpose of the "Identity" Key The Identity key acts as a cache for the Microsoft Entra ID (formerly Azure AD) and Microsoft Account (MSA) authentication tokens. When you sign into Office, the application writes a "fingerprint" of your identity here so that it does not ask for your password every 10 minutes. Scenario A: The "
Part 2: Anatomy of the Identity Registry Key When you navigate to HKCU\Software\Microsoft\Office\16.0\Common\Identity using regedit.exe , you will typically see several subkeys and values. Subkeys to know:
Identities : This is the most important subfolder. Inside, you will find subkeys named with long GUIDs (Globally Unique Identifiers). Each GUID corresponds to a specific user account (e.g., user@company.com or a personal Outlook.com account). SignIn : Stores the global sign-in settings for the Office suite. LiveId : Legacy or supplemental tokens for Microsoft services. Cache : Temporary identity data used for faster re-authentication.
Critical Values inside the Identities\{GUID} folder: | Value Name | Data Type | Purpose | | :--- | :--- | :--- | | UniqueID | REG_SZ | The actual email address or UPN (User Principal Name) of the signed-in user. | | UniqueIDUnique | REG_SZ | A hashed version of the ID used for internal lookups. | | IsMicrosoftAccount | REG_DWORD | 1 = Microsoft Account (Outlook, Hotmail, Live). 0 = Work/School (Entra ID). | | FederationProvider | REG_SZ | Identifies the STS (Security Token Service), e.g., login.windows.net for corporate tenants. | | DisplayName | REG_SZ | The friendly name shown in the top-right corner of Office apps. | Live). 0 = Work/School (Entra ID).
Part 3: Why This Key Matters (Real-World Scenarios) Understanding the Identity key allows you to solve problems that standard troubleshooting cannot. Scenario A: The "Stuck Sign-In" Issue A user changes their domain password or enables MFA (Multi-Factor Authentication), but Word still shows the old account as "Signed in" even though authentication fails.
Why: The Identity key cached invalid or expired tokens. Solution: Clearing the Identities subkey forces Office to re-discover the user from scratch.