Fix it now
Office keeps asking you to sign in because it cannot hold on to what it was given. Microsoft publishes no meaning for 0xCAA20003, so diagnose the loop rather than the code: clear the cached identity, then check whether a Conditional Access policy is refusing the request, which is what Microsoft does document for the neighbouring 0xCAA20004.
dsregcmd /status
- Sign out of Office from File, then Account, then Sign out, and close every Office application.
- Open Credential Manager from Control Panel, select Windows Credentials, and remove any entries for
MicrosoftOffice16. - Open Start, then Settings, then Accounts, then Access work or school. If the account you use for Office is listed there but is not the account you sign in to Windows with, select it and choose Disconnect.
- Restart the device. Microsoft’s own procedure has a restart at this point, and the token broker holds state that a sign-out does not clear.
- Sign in again from inside an Office application rather than from Settings, and complete any multi-factor prompt fully instead of dismissing it.
- If the loop returns, run Microsoft’s Microsoft 365 sign-in troubleshooter from the Get Help app before doing anything by hand.
If the same account signs in cleanly in a browser on the same machine, the account is fine and the fault is in the client’s identity cache, the token broker or a policy that treats the Office client differently from the browser.
If Office holds the sign-in through a restart you are done. If it loops again, the next section covers how the token is obtained and which of the four causes you are looking at.
Why it happens
Modern Office does not store your password. It asks Windows for a token scoped to the service it needs, and Windows either produces one from what it already holds or sends you to Microsoft Entra ID to sign in interactively. Once a token arrives it is cached in the user’s profile, refreshed quietly in the background, and shared across the Office applications. A loop forms when part of that chain works and part does not: the interactive sign-in completes, so the dialog closes, but nothing usable is cached, so the next component to ask starts the whole thing again.
Be careful with what the code itself tells you, because the honest answer is very little. Microsoft publishes no meaning for 0xCAA20003, and none for 0xCAA20001 or 0xCAA1000E either. It does publish one for the code right next to it: 0xCAA20004 occurs if an issue affects Conditional Access. That is a real, useful data point, and it is the reason Conditional Access belongs high on the list here – but it is published for 0xCAA20004, not for 0xCAA20003, and anyone who tells you otherwise has filled in the gap themselves.
So diagnose the pattern instead. Who fails, on how many machines, and since when. One user on one machine is cached state. One user on every machine is the account or a policy that targets it. Every user on one machine is device registration or the broker. Everybody at once, starting on a date, is something that changed in the tenant.
The cached identity on this profile is stale
You have this one if One user loops, other users on the same machine sign in normally, and it started after a password reset or an account change.
- Sign out of Office and close every Office application.
- Remove the
MicrosoftOffice16entries from Windows Credential Manager, under Windows Credentials. - If that is not enough, use Microsoft’s published cleanup rather than editing keys by hand: OLicenseCleanup.vbs removes the licence state and signoutofwamaccounts.ps1 clears cached Web Account Manager accounts. Both are downloadable from Microsoft and are run elevated.
- Sign back in from inside an Office application and let the cache rebuild.
Microsoft’s manual equivalent removes the whole HKCU\Software\Microsoft\Office\16.0\Common\Identity key and the Licensing key beside it, not a single subkey under Identity. If you are going to do it by hand, do the documented set.
Conditional Access is refusing the request
You have this one if The account signs in fine in a browser on the same machine, or on a different device, and nothing you change on the client alters the behaviour.
- Have whoever administers the tenant open the user’s sign-in logs in the Microsoft Entra admin centre and find the failed request. The policy that blocked it is named there.
- The usual triggers are a device compliance requirement the machine does not meet, a location or network condition, and a requirement for an approved or managed client application.
- Fix the condition rather than the client: enrol the device, bring it into compliance, or scope the policy correctly.
This is the cause most often missed, because every symptom is on the client and every fix is in the tenant. Microsoft documents Conditional Access as the cause of 0xCAA20004, which is why it is worth ruling out early even though the code you have is a different one.
Device registration is inconsistent
You have this one if Every user on the machine loops, and dsregcmd /status shows a state that contradicts itself.
- Read the device state and token sections of
dsregcmd /statusin full before deciding anything. - For a device that is registered rather than joined, remove the work account under Settings, Accounts, Access work or school, restart, and add it back.
- For a device joined to the tenant, involve whoever manages the tenant before leaving and rejoining, because that affects far more than Office.
The account itself changed
You have this one if The loop began on a specific date across all of that user’s devices, and nobody touched the machines.
- In the Microsoft 365 admin centre, open Users, then Active users, select the user, and open Licenses and Apps.
- Confirm a licence is assigned and that the desktop applications are enabled within it.
- Check whether sign-in for the account has been blocked, which presents as a loop rather than a clear message in some builds.
- Restore the licence or unblock the account, then sign in again on the client.
Full reference
What Microsoft actually publishes about these codes
| Code | Published meaning | Source |
|---|---|---|
0xCAA20004 |
This error occurs if an issue affects Conditional Access | Microsoft Learn, Teams sign-in errors |
0xCAA20003 |
Nothing published | – |
0xCAA20001 |
Nothing published | – |
0xCAA1000E |
Nothing published | – |
The 0xCAA codes are raised by the identity stack that Office, Teams and the Windows token broker share, which is why Microsoft’s own documentation for them sits under Teams sign-in troubleshooting rather than under Office. That is a legitimate source for the code, and it is the only one that publishes anything for this family.
Microsoft’s documented reset, in order
- Run the Microsoft 365 activation or sign-in troubleshooter from the Get Help app. It scripts most of what follows.
- For estates, use the enterprise, command-line build of the Microsoft Support and Recovery Assistant, which can be run across many devices.
- Run OLicenseCleanup.vbs elevated to remove Office licence state.
- Run signoutofwamaccounts.ps1 elevated to clear cached Web Account Manager accounts. It needs Windows 10 version 1803 or later.
- If the device is Workplace Joined, run WPJCleanUp.cmd, or disconnect the account under Settings, Accounts, Access work or school.
- Restart, then sign in once from inside an Office application.
The locations Microsoft names, if you are doing it by hand
| Location | What it holds |
|---|---|
HKCU\Software\Microsoft\Office\16.0\Common\Identity |
Cached Office account identities |
HKCU\Software\Microsoft\Office\16.0\Common\Licensing |
Cached Office licence state |
%localappdata%\Microsoft\Office\Licenses |
Subscription licence files. The licence ID begins EWW |
| Credential Manager, Windows Credentials | Stored Office credentials, named MicrosoftOffice16 |
%LOCALAPPDATA%\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\AC\TokenBroker\Accounts |
Broker account state |
Export any registry key before you delete it, and expect the user to sign in from scratch afterwards, including any multi-factor step. Prefer Microsoft’s published scripts over hand edits: they remove the whole documented set in the right order, which hand editing frequently does not.
When the browser works and Office does not
This is a diagnostic, not a contradiction. The browser signs in directly and uses the current user’s settings. Office goes through the Windows token broker and its own cache, and background components use the machine-level proxy configuration rather than the user’s. So a working browser rules out the account, the password and the tenant being down, and points at the broker, the cache, or a policy that distinguishes between client applications – which Conditional Access can be configured to do.
What to check when all four causes are ruled out
- Update Office fully from File, Account, Update Options, Update Now, and install outstanding Windows updates. The broker is serviced with Windows, not with Office.
- Run an Online Repair: right-click Start, select Apps and Features, select the Office product, select Modify, then Online Repair and Repair.
- Test with a newly created local profile on the same machine. Success there confirms the original profile rather than the machine.
- Check the sign-in logs in the Entra admin centre even if you are confident it is not policy. A failed silent token request recorded there ends the argument in a minute.
- Confirm the machine’s clock and time zone are right. Token validation is time-sensitive and a badly wrong clock produces failures that look like anything but a clock.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0xCAA20003 |
Seen during Office and Teams sign-in. Microsoft does not publish a meaning for it; diagnose the loop, not the code | not published by the vendor |
0xCAA20004 |
Microsoft publishes this as occurring if an issue affects Conditional Access | Microsoft Learn |
0xCAA20001 |
Another code from the same identity stack, seen in the same exchange. No published meaning | not published by the vendor |
0xCAA1000E |
Raised by the identity library during sign-in. No published meaning | not published by the vendor |
Confirm the fix worked
- Open Word, go to File then Account, and confirm the correct work account is shown as signed in.
- Close every Office application, reopen one, and confirm no sign-in prompt appears.
- Run
dsregcmd /statusand confirm the device state and token sections are consistent. - Restart the machine and open Office again, to prove the token survived rather than being rebuilt each session.
- Check the user’s Entra sign-in logs and confirm the successful interactive sign-in is recorded with no policy failure after it.
Questions people ask about this
What does 0xCAA20003 actually mean?
Microsoft does not publish a meaning for it. It comes from the identity stack that Office, Teams and the Windows token broker share, and it appears when sign-in cannot complete. The neighbouring 0xCAA20004 is published as a Conditional Access problem, which is a hint worth acting on, but it is not the same code and should not be presented as one.
Why does the browser work when Office does not?
They take different paths to the same identity service. The browser signs in directly with the current user’s settings; Office goes through the Windows token broker and its own cache, and its background components use the machine-level proxy. A fault in either breaks Office while leaving the browser untouched.
Does this mean my subscription has a problem?
Usually not. A missing entitlement produces a licensing message that says so. Check the licence assignment anyway, because a removed seat can present as a loop rather than as a clear notice.
Will removing the work account delete anything?
Not your documents. It removes the device’s connection to the account, so anything relying on that connection, including single sign-on to other applications, will prompt again afterwards. On a device joined to the tenant, do not do it without talking to whoever manages it.
Is there anything to buy to fix this?
No. This is cached credential state, device registration or a tenant policy, and all three are configuration. If the licence has genuinely been removed, reassigning a seat you already own costs nothing.
