Home › Microsoft Teams › 0xCAA70007

Microsoft Teams · 0xCAA70007 · Windows 10 / Windows 11

Microsoft Teams Error 0xCAA70007: Failed Token Acquisition on Windows 10/11

The error occurs due to a failed authentication token acquisition from Azure AD. Clearing the token cache and fixing network configurations resolves the issue.

Error Details

FactValueSourceNote
Exact error string0xCAA70007 (ADAL_CLIENT_ERROR_NO_TOKEN)Teams logs.txt and Entra sign-in logsIndicates token acquisition failure
Affected OS buildsWindows 10 / Windows 11Microsoft Teams documentation
Relevant log pathC:\Users\%USERNAME%\AppData\Roaming\Microsoft\Teams\logs.txtLocal file systemSearch for 'CAA70007' or 'tokenAcquisitionFailed'
Identity cache locationC:\Users\%USERNAME%\AppData\Local\Microsoft\IdentityCacheLocal file systemMay contain corrupted files
Conditional Access policiesReview in Microsoft Entra admin centerEntra Monitoring > Sign-in logsCheck for blocking policies

Log Files to Check

What This Error Actually Means

The error code 0xCAA70007 (ADAL_CLIENT_ERROR_NO_TOKEN) indicates that Microsoft Teams failed to acquire an authentication token from Azure Active Directory (Azure AD). This typically occurs when the Teams client cannot refresh or retrieve a valid token for user authentication. The error is raised by the Azure Active Directory Authentication Library (ADAL) or its successor, the Microsoft Authentication Library (MSAL), which are responsible for handling token acquisition in modern Microsoft applications.

Affected Versions and Scope

This issue primarily affects users running Microsoft Teams on Windows 10 or Windows 11 operating systems. It is not limited to specific tenant configurations but can occur across various Azure AD environments, particularly those with Conditional Access policies enforced. The error does not affect users on macOS or mobile platforms, as the authentication flow differs significantly on these platforms.

Where To Look First: Logs and Event IDs

To diagnose this issue, examine the following log files:

Relevant Event IDs in the Windows Event Viewer include:

Root Causes

Stale or Corrupted Token Cache Entries

This is the most common cause. After a password change, Multi-Factor Authentication (MFA) method update, or token expiration, stale entries in the Windows Credential Manager or IdentityCache folder prevent Teams from refreshing tokens. Use Get-StoredCredential | Where-Object {$_.Target -match 'Teams|MicrosoftOffice'} to identify problematic entries.

Conditional Access Policy Block

Azure AD Conditional Access policies may block token issuance if the user's device is non-compliant, their location is restricted, or specific authentication methods are enforced. Check Microsoft Entra admin center > Monitoring > Sign-in logs for failed attempts with AADSTS codes alongside 0xCAA70007.

Network or Proxy Interference

Firewalls, proxies, or TLS-inspection appliances may block or alter traffic to login.microsoftonline.com on port 443. Use Test-NetConnection -ComputerName login.microsoftonline.com -Port 443 to verify connectivity.

Corrupted Microsoft.AAD.BrokerPlugin

The AAD BrokerPlugin is critical for token acquisition in Windows applications. If missing or damaged, Teams cannot authenticate. Verify its presence with Get-AppxPackage -AllUsers | Where-Object {$_.Name -match 'BrokerPlugin'}.

Fix Procedure

  1. Clear ADAL/MSAL Token Cache:
    Warning: Clearing credentials may affect other applications using the same token cache.

    1. Quit Teams.
    2. Open Control Panel > Credential Manager > Windows Credentials.
    3. Remove all entries starting with 'MicrosoftOffice16_Data', 'Teams', or 'msteams'.
    4. In PowerShell (elevated):

    Remove-Item 'C:\Users\%USERNAME%\AppData\Roaming\Microsoft\Teams\Local Storage' -Recurse -Force
    Remove-Item 'C:\Users\%USERNAME%\AppData\Local\Microsoft\IdentityCache' -Recurse -Force
  2. Repair Microsoft.AAD.BrokerPlugin:

    In PowerShell (elevated):

    Get-AppxPackage -AllUsers | Where-Object {$_.Name -match 'BrokerPlugin'} | Select-Object Name, Version
    If missing or damaged, restore with:
    Add-AppxPackage -Register 'C:\Windows\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\AppxManifest.xml' -DisableDevelopmentMode
  3. Fix Proxy/TLS Inspection Issues:

    Add login.microsoftonline.com and login.windows.net to your proxy's TLS inspection bypass list. Alternatively, import the proxy CA certificate into the Windows trusted root store via Group Policy:
    Computer Configuration > Windows Settings > Security Settings > Public Key Policies > Trusted Root Certification Authorities.

  4. Force Teams Reinstall:

    1. Remove Microsoft Teams (work or school) and Teams Machine-Wide Installer from Settings > Apps.
    2. Delete the following directories:
    C:\Users\%USERNAME%\AppData\Roaming\Microsoft\Teams
    C:\Users\%USERNAME%\AppData\Local\Microsoft\Teams
    3. Reinstall Teams from teams.microsoft.com.

Error Code Variants

Error Code Description Distinguishing Features
0xCAA70008 (ADAL_CLIENT_ERROR_TOKEN_EXPIRED) Token has expired and cannot be refreshed. Log entries mention token expiration or renewal failure.
0xCAA70009 (ADAL_CLIENT_ERROR_NO_SESSION) No active authentication session exists. Occurs after extended periods of inactivity without reauthentication.

Verification

After applying fixes, verify by:

Prevention

To avoid recurrence:

TIP: Use the Teams client's built-in help tools by pressing Ctrl + Shift + I to open the developer console and inspect real-time authentication attempts.

Sources & References

Related Guides

Get new error code fixes by email

Product-specific solutions for Intune, Autopilot, SCCM and Entra ID — straight to your inbox. No spam.