Fix it now
Microsoft publishes CAA82EE2 as an internet access or network connectivity problem, and CAA70004 and CAA70007 as connection issues that usually show up in other Office applications too. Prove the device can reach the Microsoft 365 endpoints before you clear a single cache.
netsh winhttp show proxy
Test-NetConnection teams.microsoft.com -Port 443
Test-NetConnection login.microsoftonline.com -Port 443
- Check plain internet access first. Microsoft’s documented first step for CAA82EE2 is confirming the user actually has it, and on a laptop behind a captive portal that is the whole answer.
- Retest on a phone tether. Success there proves the corporate path is the problem and tells you where the ticket belongs.
- Inspect the certificate a browser is served for
teams.microsoft.com. If it was issued by your own firewall or internal authority, TLS inspection is in the path. - Check whether the same account fails in other Office applications. Microsoft says CAA70004 and CAA70007 usually do, which points at the machine’s connection settings rather than at Teams.
- Bypass the Microsoft 365 endpoints on the proxy and firewall, taking the list from Microsoft’s published endpoints service rather than a saved copy.
netsh winhttp show proxy reports what background processes are given, which is often not the proxy the browser uses.
If sign-in works you can stop here. If not, the next section covers what Teams needs from the network and which part of it your appliance is breaking.
Why it happens
These are network codes with an authentication label on them. Microsoft’s Teams sign-in troubleshooting page groups 0xCAA82EE2 with 0xCAA82EE7 under a single cause, internet access or network connectivity issues, and its remedy is to confirm the user has internet access and then check the network against the published Microsoft 365 endpoint list. It groups 0xCAA70004 with 0xCAA70007 under connection issues, adding the diagnostic hint that the same sign-in problem usually appears in other Office applications as well.
That hint is worth more than it looks. If Teams alone fails, you are looking at the Teams endpoints. If Word and Outlook fail to sign in too, you are looking at the authentication path shared by all of them, which is a different and usually simpler conversation with the network team.
What Teams needs from the network is not the same as what browsing needs. Microsoft’s published endpoint list puts Teams media in the Optimize category on UDP 3478, 3479, 3480 and 3481, and Teams signalling in the Allow category on TCP 443 and 80 with UDP 443. Long-lived connections and UDP media are exactly what a break-and-inspect proxy handles worst: it terminates the session, decrypts it, re-encrypts it with its own certificate and forwards it, which is invisible for ordinary browsing and destructive for this.
Microsoft is explicit about that in its network connectivity principles: bypass Microsoft 365 domains from TLS decryption, traffic interception, deep packet inspection and content filtering, and bypass traffic intermediation devices such as proxies and VPN services. This is not a workaround, it is the documented design.
The device has no working internet connection
You have this one if CAA82EE2 on one machine, and nothing else on it reaches the internet either – a captive portal, an expired guest session, a dropped wireless link.
- Open any external site in a browser and confirm it loads without a portal page.
- Retest Teams once real connectivity is confirmed.
- On a managed laptop, check whether an always-on VPN client has failed open and is blackholing traffic.
This is Microsoft’s own first step for the code, and it is the one most often skipped because the error looks like an authentication fault.
TLS inspection is breaking the session
You have this one if The certificate served for Microsoft 365 hosts is issued by your own appliance rather than by a public authority.
- Exempt the Microsoft 365 endpoints from decryption, starting with the Optimize category.
- Take the endpoint list from Microsoft’s published endpoints web service and automate the refresh, rather than maintaining it by hand.
- If the appliance must stay in the path for other traffic, confirm its issuing CA is trusted by the machine account as well as by the user.
- Retest immediately after the bypass, before any other change, so you know what fixed it.
The proxy demands authentication for every connection
You have this one if Interactive browsing works because the user authenticates to the proxy, while Teams background and media connections fail.
- Allow the Teams and Entra ID endpoints without proxy authentication, or bypass the proxy for them entirely.
- Confirm any PAC file returns a direct result for those hosts and is reachable from the machine.
- Compare
netsh winhttp show proxyagainst the browser’s proxy settings; background processes frequently get a different answer.
Required endpoints or ports are blocked
You have this one if Sign-in fails outright, or sign-in works and calls will not connect.
- Permit outbound TCP 443 and 80 to the Microsoft 365 endpoints for signalling, content and authentication.
- Permit outbound UDP 3478 to 3481 for Teams media. Without it calls fail or fall back to a worse path.
- Confirm DNS resolution for Microsoft hosts is not being redirected or filtered.
- Replace any hand-maintained allow list with the automated feed from Microsoft’s endpoints service.
A VPN is forcing everything through one break-out
You have this one if Only remote users fail, and the fault disappears the moment the VPN is disconnected.
- Configure split tunnelling for the Microsoft 365 Optimize endpoints, which is what Microsoft recommends.
- Base the split tunnel rules on the published ranges rather than on a handful of hostnames.
- Check whether the VPN client imposes inspection or filtering of its own.
- Retest calls as well as sign-in; media suffers most from a long path.
Full reference
What Teams needs open
| Category | Protocol and ports | What it carries |
|---|---|---|
| Optimize | UDP 3478, 3479, 3480, 3481 | Teams media – calls and meetings |
| Allow | TCP 443 and 80, UDP 443 | Teams signalling, content and sign-in |
Take those from Microsoft’s endpoints web service rather than from this or any other page. The addresses behind them change, and a list copied into a firewall two years ago is the most common reason a Teams problem appears months after anyone touched the network.
Reading the symptom back to the layer
| Observation | Likely cause |
|---|---|
| Fails on the corporate network, works on a tether | Proxy, firewall or inspection policy in the corporate path |
| Sign-in works, calls fail or drop | UDP media ports blocked, so media falls back or fails |
| Certificate for Microsoft hosts issued internally | TLS inspection is active and needs a bypass |
| Other Office apps also fail to sign in | The shared authentication path, not Teams – Microsoft’s own hint for CAA70004 and CAA70007 |
| Only remote workers fail | A VPN forcing all traffic through a central break-out |
| Only new machines fail | The inspection appliance’s CA is not in that machine’s trust store |
What Microsoft says about inspection
The network connectivity principles are unambiguous, and worth quoting to a security team that resists the change: bypass Microsoft 365 domains from TLS decryption, traffic interception, deep packet inspection and network packet and content filtering; prioritise direct internet access; avoid network hairpins; and bypass traffic intermediation devices such as proxies and VPN services. Microsoft adds that many of the outcomes people use inspection for can be achieved natively with Microsoft 365 security features.
When the network checks out
- Confirm which code you actually have. CAA82EE2 and CAA82EE7 share a cause; CAA70004 and CAA70007 share a different one.
- Test the same account on a different machine on the same network. If it works, the fault has moved from the network to the device.
- Check whether an endpoint security agent is filtering locally. Stop it for one test, retest, then re-enable it and raise a proper exclusion with the vendor rather than leaving protection off.
- For CAA70004 and CAA70007, Microsoft points at its guidance on connection issues after updating Office, which covers the same authentication path and lists the processes that need to be allowed.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
CAA70004 |
Connection issues, particularly where the sign-in problem also occurs in other Office applications | Microsoft Learn |
CAA70007 |
Documented in the same entry as CAA70004, with the same cause and the same remedy | Microsoft Learn |
CAA82EE2 |
Internet access or network connectivity issues. Documented together with CAA82EE7; confirm internet access, then check the path against the Microsoft 365 endpoint list | Microsoft Learn |
Confirm the fix worked
- The certificate served for Microsoft 365 hosts on an affected machine is issued by a public authority.
- Teams signs in on the corporate network without a prompt loop.
- A test call connects with media rather than failing or falling back.
- The proxy and firewall allow lists are fed from Microsoft’s published endpoints service.
- Other Office applications on the same device sign in cleanly, which is the check Microsoft’s own guidance points at.
Questions people ask about this
Is there anything to buy here?
No. These codes are about the network path, and every fix is a configuration change on equipment you already own. No Microsoft licence or subscription tier changes how a proxy handles the traffic.
Why does the browser work when the app does not?
Browsing is mostly short request-and-response over TCP. Teams keeps long-lived connections, uses UDP for media and is sensitive to latency, so it fails on paths that browsing tolerates.
Is bypassing inspection for Microsoft 365 a security risk?
It is Microsoft’s own documented recommendation, and the traffic stays encrypted and authenticated between client and service. Have the conversation with the endpoint list in front of you rather than treating it as all or nothing.
How do we keep the endpoint list current?
Use Microsoft’s published endpoints web service as the source and automate the refresh into your proxy and firewall configuration. Hand-maintained lists go stale quietly and surface months later as an intermittent Teams problem.
The error says CAA82EE2 but the user is at home on their own broadband. Now what?
Then start where Microsoft starts: confirm they have working internet at all. A captive portal, a failed VPN client or a dropped wireless link produces this code just as readily as a corporate proxy does.
