Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Free Fix CAA20003

Teams CAA20003 and CAA2000C: clock skew, Conditional Access and forced prompts

10 min read Updated October 5, 2026 Microsoft 365 & Entra ID

Fix it now

Microsoft publishes two causes for CAA20003: the device clock is wrong, or a Conditional Access policy is applying to the account. CAA2000C is different again – it means the request needs user interaction, usually multifactor authentication. Check the clock first, because it is the one nobody looks at.

Run these on the failing device, in an elevated Command Prompt, in order

w32tm /query /status
w32tm /resync
dsregcmd /status
  1. Read the w32tm /query /status output. A last successful sync hours or days old, or a source of Local CMOS Clock on a domain member, is your answer.
  2. If the clock was wrong, restart Teams and sign in again before changing anything else.
  3. If the clock is fine, check Conditional Access. In the Entra admin centre, run the What If tool against the affected user and this device to see which policies apply.
  4. If the code is CAA2000C, the broker had no silent path: sign in interactively and complete the MFA prompt rather than clearing caches.
  5. Only after those three, sign out of Teams properly, remove the Teams and Office entries from Credential Manager, and sign in fresh.

A device that loses time on every reboot has a flat CMOS battery. Resyncing fixes the symptom until the next power cycle.

If sign-in completes you can stop here. If not, the next section explains which of these codes Microsoft actually publishes and what the rest of them are worth.

Why it happens

Teams does not hold your password. It asks the Windows account broker for a token, and the broker either returns one it already holds or goes to Entra ID for a new one. The CAA codes are what the broker reports back when that fails, and they are much less uniform than they look: they are raised at different stages by different components, and only two of the five in this article have a published meaning.

Start with the one Microsoft does document. On its Teams sign-in troubleshooting page for Surface Hub, Microsoft gives CAA20003 two root causes: an incorrect time on the device, and a Conditional Access policy applying to the signing-in account. Both make sense once you know what a token is. A token carries validity windows, and both ends have to agree roughly what time it is; a device whose clock has drifted presents tokens that look expired or not yet valid. A Conditional Access policy, meanwhile, can refuse the sign-in outright before any token is issued.

CAA2000C is documented too, in an unrelated place. Microsoft’s guidance on Intune co-management enrolment failures shows it logged in the Microsoft Entra ID operational log as “0xCAA2000C The request requires user interaction”, with the code interaction_required and AADSTS50076 beneath it: multifactor authentication is needed and the silent path cannot provide it. That is not a corrupt cache. It is the broker telling you that somebody has to answer a prompt.

CAA2000B, CAA50021 and CAA90018 have no published meaning at all. They appear in the same family and clear with the same handling, but nothing on Microsoft’s documentation or support sites states what they point at, so treat any confident explanation of them – including one you have read before – with suspicion.

The device clock has drifted

You have this one if CAA20003 on one machine while others in the same office sign in normally, and w32tm /query /status shows an old last successful sync or a local CMOS source.

  1. Run w32tm /query /status and note the source and the last successful synchronisation.
  2. Run w32tm /resync. Note that /force is not a parameter of /resync; adding it makes the command print usage and do nothing.
  3. On a domain member, confirm it is syncing from the domain hierarchy rather than an internet source it cannot reach.
  4. Replace the CMOS battery on older hardware where time falls back after every reboot.

A Conditional Access policy is refusing the sign-in

You have this one if The same account fails on this device and works elsewhere, or a whole group started failing on the day a policy was enabled.

  1. In the Entra admin centre, open the Conditional Access What If tool and evaluate the user, the application and this device.
  2. Move a new policy to report-only mode and retest, so you can see its effect without leaving people locked out.
  3. Check the sign-in logs for the same user: a policy refusal is recorded there with the policy name.

On shared or unattended devices signing in with a device account, Microsoft states the account cannot have Conditional Access or MFA applied to it. Exclude it from those policies rather than working around them on the device.

The sign-in needs an interactive prompt

You have this one if CAA2000C, and the Entra ID operational log on the device shows interaction_required with AADSTS50076.

  1. Sign in interactively and complete the multifactor prompt. Silent token acquisition cannot satisfy an MFA requirement.
  2. If a background process or service account is hitting this, it needs a supported non-interactive authentication method, not a cache fix.
  3. Check whether MFA has recently moved from enabled to enforced for that user, which changes what the broker can do silently.

The device’s registration with Entra ID is broken

You have this one if Several Microsoft 365 applications prompt repeatedly on the same device, and dsregcmd /status shows no primary refresh token.

  1. Read the whole dsregcmd /status output and note the join type before changing anything.
  2. Remove and re-add the work account under Settings, Accounts, Access work or school, then restart.
  3. If the device is hybrid joined, confirm its computer object is still synchronising to Entra ID.

Rejoining a device is disruptive and belongs last, not first. Clear the clock and the policy questions before you touch device registration.

Cached credentials on the device are stale

You have this one if Teams in a browser works for the same account on the same network, the desktop app does not, and the clock and policies are both clean.

  1. Close Teams and every Office application.
  2. Open Credential Manager, Windows Credentials, and remove the generic entries belonging to Teams and to the Office identity store.
  3. Sign out of Windows and back in so the broker rebuilds, then start Teams.

Removing these entries forces a fresh sign-in. It deletes no mail, chat or files, and does not affect other users of the machine.

Full reference

Which codes are actually published

This matters more than it sounds. If you are working from a description that Microsoft never wrote, you are troubleshooting somebody’s guess. Only two of these five have a source.

Code Published meaning Where Microsoft says it
CAA20003 Incorrect time on the device, or a Conditional Access policy on the account Teams sign-in troubleshooting for Surface Hub
CAA2000C “The request requires user interaction” – interaction_required, with AADSTS50076 Intune co-management auto-enrolment troubleshooting
CAA2000B Nothing published –
CAA50021 Nothing published –
CAA90018 Nothing published. Microsoft documents CAA90014, which is not the same code –

Narrowing it down without guessing

Test What the result tells you
Teams in a browser works, the desktop app does not The device’s cached state or broker, not the account
A brand new Windows profile works The original profile’s cached state
The whole team fails at once Something tenant-side changed – very often a Conditional Access policy
Outlook and other Microsoft 365 apps fail too The device’s account registration, not Teams
w32tm /query /status shows a stale or local source Fix time before touching anything else

Where the evidence lives

  • Microsoft Entra ID operational log on the device, under Applications and Services Logs, Microsoft, Windows. This is where the interaction_required and AADSTS detail behind a CAA code appears.
  • The tenant sign-in logs in the Entra admin centre. A Conditional Access refusal is recorded there by policy name, which the client-side code never tells you.
  • dsregcmd /status on the device, for join type, tenant details and whether a primary refresh token exists.
  • w32tm /query /status for the time source and the last successful sync.

Doing this across many machines

Every step here is scriptable: a time resync, removal of the cached credential entries, and a reset of the Teams client through its app entry in Settings. What is not scriptable is the Conditional Access half, and that is the half that produces a whole-office outage. If more than a handful of users failed at once, look at what changed in the tenant before you push anything to devices.

One caution about resetting the Teams app: it clears local cache, so the first start afterwards is slower on a large tenant while the client downloads what it needs again. Chats, channels and files live in the service and are not affected.

Every code this article covers

Code What it points at Source
CAA20003 Microsoft gives two root causes: an incorrect time on the device, and a Conditional Access policy applying to the account Microsoft Learn
CAA2000B Seen alongside the other broker codes during Teams sign-in failures; no meaning is published, so diagnose it by the clock, policy and interaction checks in this article not published by the vendor
CAA2000C “The request requires user interaction” – the silent path failed and an interactive sign-in with multifactor authentication is needed Microsoft Learn
CAA50021 Reported by the account broker during sign-in; no vendor page states what it points at not published by the vendor
CAA90018 Reported by the account broker during sign-in; no vendor page states what it points at. Microsoft documents CAA90014 (device account password expired, wrong clock, or MFA on a device account), which is a different code not published by the vendor

Confirm the fix worked

  1. w32tm /query /status reports a recent successful synchronisation from the source you expect.
  2. Teams signs in without a repeated prompt.
  3. The Conditional Access What If tool shows no blocking policy for that user, application and device.
  4. Other Microsoft 365 applications on the same device sign in without prompting.
  5. Restart the machine and confirm Teams still signs in with no intervention.

Questions people ask about this

Is CAA20003 a licensing problem?

No, and it costs nothing to fix. A missing Teams licence produces a clear message about not having access to the service, not a broker code. Microsoft’s published causes for CAA20003 are the device clock and Conditional Access.

Will clearing the cache lose my chats or files?

No. Chats, channels and files live in the service. Clearing the local cache means the client downloads what it needs again at next sign-in, which makes the first start slower on a large tenant.

Why does the browser work when the app does not?

The browser holds its own session and does not go through the Windows account broker in the same way. When the browser works and the app does not, the account and the network are proven good and the fault is on the device.

What does CAA2000C actually want me to do?

Sign in interactively and complete the multifactor prompt. Microsoft logs it as “the request requires user interaction” with AADSTS50076 underneath, which is the code for multifactor authentication being required. No amount of cache clearing satisfies that.

Can I trust descriptions I find for CAA2000B, CAA50021 and CAA90018?

Be careful. Microsoft publishes no meaning for any of them. They respond to the same handling as the documented codes, but any page that tells you precisely what one of them means is telling you something the vendor has not.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

License Error 0x80043003 and 0x80cf0440: the subscription is deleted or suspended and enrolment stops License Error 0x80180022 and 0x800705b4: Windows edition and TPM block Intune enrolment License Error 550 5.1.90 and 550 5.7.232: Exchange Online sending limits have been hit License Error SharePoint Online is out of storage space: tenant and site quota errors
โ† Back to Knowledge Base