If Microsoft Teams will not connect while the internet works, check Teams cache, Microsoft account sign-in, VPN, proxy, firewall, DNS, system time, service status and work/school policies.
Start by comparing what still works: browser versus app, Wi-Fi versus mobile data, Ethernet link versus DNS, or restart versus smaller network refresh. That comparison tells you where the fix belongs.
Start with the exact layer that still works
Teams can refuse to connect while your browser and other apps keep working because it depends on more than general internet access. It needs Microsoft sign-in, Teams services, cached tokens, correct system time, DNS, WebSocket access, notifications, firewall permissions and sometimes work or school device policy. A normal website loading in Chrome does not prove all of that is healthy. This is why Teams may sit on reconnecting, show a sign-in loop or say you are offline during an otherwise normal connection.
The best order is to check whether Teams web works, then clear cache, sign out and back in, test without VPN, check proxy/firewall and confirm Microsoft service status. If Teams web works but desktop Teams fails, focus on the app cache and local profile. If both fail, the issue is account, Microsoft service access, DNS or network policy.
Quick diagnosis table
Try these fixes in order
Use this order so you prove the failure point before changing broad settings.
- 01
Try Teams on the web
Open Teams in the browser. If web Teams works, your account and basic internet are fine and the desktop app is the narrow issue.
- 02
Check Microsoft service status
A Teams outage or Microsoft 365 issue can make local fixes useless. Check status before reinstalling.
- 03
Sign out and back in
A stale token can trap Teams in reconnecting or offline mode. Sign out fully, close Teams and sign in again.
- 04
Clear Teams cache
Teams cache can become stale after updates, account changes or crashes. Clearing it often fixes reconnecting loops.
- 05
Turn off VPN and proxy for a test
VPNs and proxies can block Teams traffic even while web browsing works. Test without them before changing router settings.
- 06
Check firewall permissions
Teams needs permission for calls, messages and background connections. Security tools may block the desktop app specifically.
- 07
Check date and time
Wrong system time can break Microsoft sign-in and secure connections. Set time automatically.
- 08
Reinstall Teams only after cache tests
Reinstalling can help, but cache, sign-in and VPN checks are faster and more targeted.
- 09
Retest after a restart or reconnect
After the fix appears to work, restart the app, reconnect the adapter or reboot the device once. A fix that survives the next restart is much more reliable than one lucky successful load.
Detailed checks
Teams desktop and Teams web are useful comparisons
The browser version gives you a clean comparison. If it works, the account and Microsoft service are reachable.
- That points to desktop cache, local app permissions or profile state.
Teams uses more than simple HTTPS pages
Meetings, chat, presence and calls use multiple Microsoft services and connection types. A network can allow normal websites while blocking part of Teams.
- This is common on strict work, school, hotel or filtered networks.
Cached tokens cause strange loops
Teams can keep old sign-in tokens after password changes, tenant changes or account switching.
- Signing out and clearing cache refreshes the identity layer without wiping Windows.
The repeat pattern matters
If Teams fails only on VPN, only at work or only after sleep, the trigger is the clue.
- Do not reinstall the app repeatedly when the pattern points to network policy or VPN.
Why repeat testing matters
A single successful load can be a cached page, a lucky route or a temporary service recovery. Repeat testing shows whether the fix changed the actual broken layer.
- Use the exact same app, website or connection state that failed before. That keeps the confirmation honest.
Mistakes to avoid
Do not assume one working browser proves every app has clean internet.
Do not blame the router when the pattern follows one device, app, VPN or adapter.
Do not change DNS, VPN, firewall and drivers all at once. Test one layer at a time.
FAQ
Why won't Teams connect if internet works?
Because Teams needs Microsoft sign-in, cached tokens, service access, DNS, firewall permissions and sometimes WebSocket traffic. Browsing only proves basic web access.
Compare Teams web and desktop first.
Can Teams cache cause reconnecting?
Yes. Damaged or stale cache can keep Teams stuck offline or looping sign-in.
Clear cache after signing out and closing Teams.
Can VPN block Teams?
Yes. VPNs and proxies can block or slow Teams services while browsers still work.
Test without VPN and ask IT if it is a work-managed connection.
Why does Teams web work but desktop fail?
That points to the desktop app, cache, local permissions or profile state.
Clear cache, update Teams and sign in again.
Why do calls fail but chat works?
Calls can use different traffic and stricter network requirements than chat.
Firewall, proxy or network policy may be blocking media traffic.
Can wrong time break Teams?
Yes. Microsoft sign-in depends on secure time and certificates.
Set time and time zone automatically.
Should I reinstall Teams?
Only after cache, sign-in, VPN, proxy and firewall checks.
Reinstalling is useful, but not the fastest first step.
When should I contact IT?
Contact IT if Teams fails only on a work device, work network or VPN.
They may need to allow Teams services or fix policy.
Is this a router problem?
Usually not if other devices and services work. It is more likely Teams cache, Microsoft access, VPN or firewall.
Router checks matter if Teams fails on every device on the same network.
Outside references
- Microsoft Teams Help
Official Teams support reference.
- Microsoft Service Health
Official Microsoft service status reference.