Teams Troubleshooting IT Guide (2026)

Why Your Helpdesk Needs a Dedicated Teams Troubleshooting Playbook

Microsoft Teams has become the backbone of workplace communication for millions of organizations. And when it breaks? The helpdesk phone doesn't just ring — it doesn't stop ringing. Audio dropping mid-call, the new Teams client refusing to launch, screen sharing going dark during a board meeting. These are the tickets that pile up fastest, and they're the ones where frustrated users expect answers now.

Here's the thing, though: most troubleshooting guides online are written for end users. They'll tell someone to "restart the app" or "check your internet." That's fine for a basic user, but as an IT helpdesk pro, you need admin-level diagnostics, PowerShell commands, registry fixes, and clear escalation paths.

So, let's dive into exactly that — a complete troubleshooting reference for the new Teams client in 2026, covering everything from clearing the cache to digging into call quality data in CQD.

Step One: Rule Out a Microsoft Service Outage

Before you spend 30 minutes troubleshooting a user's machine, check whether Microsoft itself is having a bad day. Seriously — this single step can save your team hours of wasted effort.

Visit the Microsoft 365 Service Health dashboard at https://admin.microsoft.com → Health → Service health
Check the @MSFT365Status account on X (formerly Twitter) for real-time incident reports
Use the Microsoft 365 Status page at https://status.office.com for a public-facing view (no admin login required — handy when your admin account is also affected)

If Teams is listed as degraded or experiencing an incident, document the incident ID, communicate the status to affected users, and monitor for resolution. No amount of local troubleshooting will fix a server-side problem.

Understanding the New Teams Client Architecture

Microsoft completed the migration from classic Teams to the new Teams client (built on Edge WebView2) in 2024–2025. If you haven't updated your internal docs and scripts for the new architecture, now's the time — a lot has changed under the hood.

Key Processes in Task Manager

The new Teams client runs as two main processes:

ms-teams.exe — the main application process
ms-teams_modulehost.exe — a dedicated process for calling features, introduced for better performance and stability

If your endpoint security or firewall rules were configured for classic Teams (Teams.exe), you must update them to allowlist both ms-teams.exe and ms-teams_modulehost.exe. I can't stress this enough — failure to do this is one of the most common causes of calling failures we see with the new client.

New Cache Location

The new Teams client stores its cache at a completely different path than classic Teams:

%LocalAppData%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams

Classic Teams used %AppData%\Microsoft\Teams. If your documentation or scripts still reference the old path, update them now — you'll save yourself a lot of confusion.

Critical Registry Keys

Several registry settings affect how the new Teams client installs and runs:

; Allow sideloaded MSIX apps (required for new Teams)
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModelUnlock
  AllowAllTrustedApps = 1 (DWORD)

; Also check Group Policy override
HKLM\SOFTWARE\Policies\Microsoft\Windows\Appx
  AllowAllTrustedApps = 1 (DWORD)

; Disable auto-update (VDI environments only)
HKLM\SOFTWARE\Microsoft\Teams
  disableAutoUpdate = 1 (DWORD)

If AllowAllTrustedApps is set to 0, the new Teams MSIX package can't install or launch. This is the single most common root cause behind those "Due to org policy, you can't install the new Teams" errors. Check it first.

The Top 10 Teams Helpdesk Tickets (and How to Fix Them)

1. Teams Won't Launch or Shows a Blank Window

When a user opens Teams and sees a blank window that immediately closes, here's the escalation path that actually works:

Clear the Teams cache — Close Teams completely (make sure it's really closed, not just minimized to the system tray), then delete all contents of the cache directory:
```
%LocalAppData%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams
```
Check WebView2 Runtime — Teams requires the Edge WebView2 Runtime. Verify it's installed:
```
Get-ItemProperty "HKLM:\SOFTWARE\WOW6432Node\Microsoft\EdgeUpdate\Clients\{F3017226-FE2A-4295-8BDF-00C3A9A7E4C5}" -ErrorAction SilentlyContinue | Select-Object pv
```
If it's absent, download and install it from the Microsoft Edge WebView2 page.
Check SYSTEM account permissions — The SYSTEM account and Administrators group need Full Control of the Teams installation directories. Run:
```
Get-AppxPackage MSTeams
```
to verify the MSIX package is properly provisioned.
Check for reparse points — This is an easy one to overlook. If the Cookies or Cache shell folders point to reparse points, open Registry Editor and go to:
```
HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders
```
Update any entries that point to reparse points to standard folder paths.
Run the pre-installation check script — Microsoft provides TeamsLaunchCheck.ps1, which automates all these checks. Download it from the Microsoft Learn documentation and run it on the affected machine. Honestly, this script should be your go-to before manually checking each step.

2. Audio Problems: No Sound, One-Way Audio, or Echo

Audio issues generate the highest volume of frustrated tickets. (Pun intended.) Here's a systematic approach that'll get you to the root cause faster:

Test the device in Teams settings — Navigate to Settings → Devices and click "Make a test call." This creates a test call to Echo Bot and plays back audio, confirming mic, speaker, and network path all in one shot.
Check device permissions — Go to Windows Settings → Privacy & Security → Microphone and confirm Teams has access. Do the same for Camera while you're there.
Update audio drivers — Outdated audio drivers are a leading cause of one-way audio. Update through Device Manager or your manufacturer's driver portal.
Check for Bluetooth interference — If a user has multiple Bluetooth audio devices paired, Teams may route audio to a device that isn't actually on the user's head. It happens more often than you'd think. Unpair unused devices.
Network assessment — Poor audio usually traces back to the network. Run the Microsoft Teams Network Assessment Tool to measure jitter, packet loss, and latency to Microsoft's media relay servers:
```
# Install the tool from Microsoft, then run:
NetworkAssessmentTool.exe
# Results are logged to:
# %LocalAppData%\Microsoft Teams Network Assessment Tool\results.tsv
```

3. Camera Not Detected in Video Calls

When a user reports their camera isn't working, run through this checklist:

Verify camera permissions in Windows Settings → Privacy & Security → Camera
Check if another application (Zoom, WebEx, etc.) is holding the camera exclusively — close all other video apps first
Test the camera in the Windows Camera app to isolate whether it's a Teams issue or a system-level problem
For USB cameras, try a different USB port (preferably USB 3.0)
Update camera firmware and drivers from the manufacturer's website

4. Screen Sharing Not Working

Screen sharing failures often have an admin-level root cause that users can't fix on their own:

Meeting policy restriction — The meeting organizer or tenant admin may have disabled screen sharing. Check the Teams admin center under Meetings → Meeting policies and verify that Screen sharing mode is set to "Entire screen" or "Single application."
GPU hardware acceleration — Disable GPU hardware acceleration in Teams settings if screen sharing shows a black screen. Go to Settings → General and toggle it off.
Corrupted cache — Corrupted cache files can cause screen sharing to silently fail. Clear the cache directory (you'll notice this fix comes up a lot — it's the "turn it off and on again" of Teams troubleshooting).

5. Sign-In Failures and Authentication Loops

Few things are more annoying for a user than getting stuck in a login loop. Here's how to break the cycle:

Clear all Teams credentials from Windows Credential Manager — open Credential Manager from Control Panel, go to Windows Credentials, and remove any entries containing "Microsoft" or "Teams"
Clear the Teams cache directory
Check if the user's account is locked out or if Conditional Access policies are blocking the sign-in (check Entra ID Sign-in logs for failure codes — these are usually very descriptive)
For hybrid environments, verify time synchronization. A clock skew of more than 5 minutes can cause authentication token failures, and this one catches people off guard
Run the built-in Teams Sign-in diagnostic in the Microsoft 365 Admin Center (more on admin diagnostics below)

6. Chat Messages Not Sending or Appearing Delayed

Message delivery issues typically point to network problems:

Check the user's network connection — run ping outlook.office365.com and Test-NetConnection -ComputerName teams.microsoft.com -Port 443 from PowerShell
Verify that your proxy or firewall isn't blocking Teams endpoints. Microsoft publishes the required URLs and IP ranges at https://learn.microsoft.com/en-us/microsoft-365/enterprise/urls-and-ip-address-ranges
Check WebSocket connectivity — Teams chat relies on WebSocket connections, which some legacy proxies don't handle properly. This is one of those issues that seems random but has a very specific cause

7. File Sharing and Upload Failures

When users can't upload or share files in channels or chats:

Check file size — Teams enforces a 250 GB maximum file size for uploads (generous, but people do hit it with video files)
Verify SharePoint Online storage quotas — Teams channel files are stored in SharePoint behind the scenes, so if the associated SharePoint site has hit its storage limit, uploads will fail
Check permissions — ensure the user has at least Contribute permissions on the underlying SharePoint document library
For unsupported file types, rename the extension or ZIP the file before uploading

8. Notifications Not Working

Missing notifications cause users to miss important messages — and then blame IT for it. Run through these checks:

Check Teams notification settings: Settings → Notifications and activity
Verify Windows notification settings: Settings → System → Notifications — ensure Teams is allowed to send notifications and Focus Assist / Do Not Disturb is turned off
Check the user's Teams status — if it's set to "Do Not Disturb," notifications are suppressed by design (you'd be surprised how often this is the culprit)
For persistent issues, reset notification settings by clearing the Teams cache

9. Teams Running Slowly or Consuming Excessive RAM

Teams can be a resource hog. When users report sluggish performance:

Check system resources — Teams requires at minimum 4 GB RAM (8 GB recommended). If the system is maxed out, close unnecessary applications
Disable GPU hardware acceleration if the machine has an older or integrated GPU
Clear the Teams cache — accumulated cache data slows down the client over time
Check for conflicting background processes — VPN clients, endpoint protection, and backup agents can all compete for resources
On machines with limited resources, consider pointing the user to Teams for Web (https://teams.microsoft.com) in a browser as a lighter alternative

10. New Teams Installation Blocked by Group Policy

This is an admin-specific issue that end users simply can't resolve themselves:

Check Group Policy: Computer Configuration → Administrative Templates → Windows Components → App Package Deployment
Ensure "Prevent non-admin users from installing packaged Windows apps" is set to Not Configured or Disabled
Verify the AllowAllTrustedApps registry key at HKLM\SOFTWARE\Policies\Microsoft\Windows\Appx is set to 1
Run gpresult /h gpresult.html on the affected machine to identify which policy is actually blocking the installation

PowerShell Diagnostics for Teams Admins

PowerShell is honestly your most powerful tool for investigating Teams issues at scale. Once you get comfortable with the MicrosoftTeams module, you'll wonder how you ever managed without it.

Installing and Connecting

# Install the MicrosoftTeams module (requires PowerShell 5.1+ or PowerShell 7+)
Install-Module MicrosoftTeams -Force -AllowClobber

# Connect to your tenant
Connect-MicrosoftTeams

# If using service account with stored credentials:
$cred = Get-Credential
Connect-MicrosoftTeams -Credential $cred

# Verify connection and list available commands
Get-Command -Module MicrosoftTeams | Measure-Object
# Expected: 100+ cmdlets available

Common Diagnostic Commands

# Check a user's Teams policies
Get-CsOnlineUser -Identity "[email protected]" | Select-Object DisplayName, TeamsUpgradePolicy, TeamsMeetingPolicy, TeamsCallingPolicy, TeamsMessagingPolicy

# Check Teams meeting policy details
Get-CsTeamsMeetingPolicy -Identity "Tag:RestrictedUser" | Format-List

# Verify phone number assignment (for calling issues)
Get-CsPhoneNumberAssignment -AssignedPstnTargetId "[email protected]"

# Fix a phone number assignment
Set-CsPhoneNumberAssignment -Identity "[email protected]" -PhoneNumber "+14255551234" -PhoneNumberType DirectRouting

# Check Teams client configuration
Get-CsTeamsClientConfiguration

# List all Teams a user belongs to
Get-Team -User "[email protected]" | Select-Object DisplayName, GroupId, Visibility

Troubleshooting Module Installation Issues

If Connect-MicrosoftTeams fails with "not recognized as a cmdlet," don't panic — it's usually a simple fix:

# Completely remove and reinstall
Uninstall-Module -Name MicrosoftTeams -AllVersions -Force
Install-Module MicrosoftTeams -Force

# If NuGet provider prompt appears, type Y and press Enter
# Close and re-open your PowerShell session after installation

Using the Microsoft 365 Admin Center Self-Help Diagnostics

Microsoft provides built-in diagnostic scenarios specifically for Teams issues. These are genuinely useful — they run automated checks against your tenant configuration and give you step-by-step fix instructions. I'd recommend getting familiar with them if you haven't already.

How to Access

Sign in to https://admin.microsoft.com as a Teams admin or Global admin
Navigate to Support → New service request
Describe your issue (e.g., "user can't sign into Teams") — the system will suggest a diagnostic
Enter the affected user's email address and click "Run tests"

You can also type diagnostic shortcuts directly into the search bar — this is the faster route:

Diag: Teams Sign-in — diagnoses user sign-in failures
Diag: Teams Dial Pad Missing — checks why a user doesn't see the dial pad
Diag: Teams Direct Routing — validates Direct Routing configuration
Diag: Teams Call Queue — verifies Call Queue can receive calls
Diag: Unable to Schedule Teams Meeting on behalf of Delegate — checks delegate permissions

These diagnostics are read-only — they can't make changes to your tenant. They're available in commercial tenants but not in GCC High or DoD environments.

Remote Diagnostic Log Collection

One of the most useful features added to the Teams Admin Center is the ability to remotely collect diagnostic logs from a user's Windows or Mac device — without needing the user to do anything. If you haven't tried this yet, it's a game-changer for remote support.

How to Collect Logs Remotely

Open the Teams Admin Center at https://admin.teams.microsoft.com
Navigate to Users and select the affected user
Click "Request client logs"
Select which client (if the user has multiple devices) to collect from
Wait up to 8 hours for the logs to be collected and uploaded — grab a coffee, or ten
Download the logs from the same user page once they're available

What Gets Collected

Web logs — diagnostics, calling, central data layer, and Web Media logs
Desktop logs — Shell Diagnostics and Slimcore logs (including the media stack)

Procmon traces and OS Event Logs are not collected since they require elevated privileges. For those, you'll still need to collect manually or use endpoint management tools like Intune.

Call Quality Troubleshooting with CQD and Call Analytics

When users report poor call quality, you need data — not guesswork. Microsoft gives you three tools that work together, and understanding when to use each one makes a real difference.

Call Analytics (Per-User Investigation)

Call Analytics is your first stop for investigating an individual user's call problems:

Open the Teams Admin Center → Users
Select the affected user and click the Meetings & calls tab
Click on the specific call or meeting that had issues
Review the Audio, Video, and Screen Sharing tabs for quality metrics

Key metrics to watch:

Jitter — should be under 30ms. Values above this cause choppy audio
Packet loss — should be under 5%. Higher values cause audio dropouts
Round-trip time — should be under 100ms. Higher values cause that annoying conversation lag where people keep talking over each other

Helpdesk agents with the Teams Communications Support Specialist role can access Call Analytics for basic investigation. The Teams Communications Support Engineer role provides additional detail.

Call Quality Dashboard (CQD) — Org-Wide Trends

CQD (https://cqd.teams.microsoft.com) gives you an org-wide view of call quality trends. Use it when you start noticing patterns — maybe multiple users in the same building are reporting poor quality, or quality dropped right after a network change.

CQD data is available within 30 minutes of a call ending, which is pretty close to real-time
Upload your building and subnet data to CQD to enable location-based analysis — this is crucial for pinpointing whether issues are site-specific
Use the Power BI CQD templates for deeper analysis with visualizations and drill-downs

Real-Time Analytics (In-Progress Meetings)

For VIP meetings or live events where quality issues are reported in real time, use Real-Time Analytics in the Teams Admin Center. This shows live telemetry for in-progress scheduled meetings, including per-participant audio quality, network metrics, and device information. It's particularly valuable when the CEO's town hall is glitching out and you need answers fast.

Implementing Quality of Service (QoS) for Teams

QoS marks Teams traffic with DSCP (Differentiated Services Code Point) values so your network hardware can prioritize real-time audio and video over less time-sensitive traffic like file downloads. If your org hasn't set this up yet, it's worth the effort.

Recommended QoS Port Ranges and DSCP Values

Media Type	Source Port Range	DSCP Value	DSCP Class
Audio	50000–50019	46	Expedited Forwarding (EF)
Video	50020–50039	34	Assured Forwarding (AF41)
Screen Sharing	50040–50059	18	Assured Forwarding (AF21)

Deploying QoS via Group Policy

; Create a GPO and navigate to:
; Computer Configuration → Policies → Windows Settings → Policy-based QoS

; Create three rules:
; Rule 1: Teams Audio
;   Application: ms-teams.exe
;   DSCP Value: 46
;   Source port range: 50000-50019

; Rule 2: Teams Video
;   Application: ms-teams.exe
;   DSCP Value: 34
;   Source port range: 50020-50039

; Rule 3: Teams Screen Sharing
;   Application: ms-teams.exe
;   DSCP Value: 18
;   Source port range: 50040-50059

; IMPORTANT: Also create matching rules for ms-teams_modulehost.exe

One thing people forget: QoS only works end-to-end if every device in the path respects the priority markings. Make sure your network switches and routers are configured to honor DSCP markings, or all this effort won't make a difference.

Escalation Path: When to Escalate Beyond the Helpdesk

Not every Teams issue can (or should) be resolved at the helpdesk tier. Knowing when to escalate is just as important as knowing how to troubleshoot. Here's a practical guide:

Escalate to network engineering — When CQD shows quality degradation affecting specific subnets or buildings, or when packet loss and jitter exceed thresholds across multiple users
Escalate to identity/security team — When sign-in failures trace back to Conditional Access policy blocks or Entra ID configuration issues
Open a Microsoft support case — When the issue affects multiple users, you've exhausted local troubleshooting, and the admin diagnostics don't identify a root cause. Include remote diagnostic logs and Call Analytics data in the support ticket — it'll speed up resolution considerably

Quick-Reference: Teams Troubleshooting Cheat Sheet

Symptom	First Check	PowerShell Command / Tool
Can't sign in	Entra ID sign-in logs	`Diag: Teams Sign-in`
No dial pad	Calling policy assigned?	`Get-CsOnlineUser -Identity [email protected] \| Select TeamsCallingPolicy`
Poor call quality	Call Analytics in TAC	`CQD → cqd.teams.microsoft.com`
App crashes	Clear cache	Delete `%LocalAppData%\Packages\MSTeams_8wekyb3d8bbwe\...`
Won't install	AllowAllTrustedApps registry	`Get-AppxPackage MSTeams`
No audio	Device settings test call	Network Assessment Tool
File upload fails	SharePoint storage quota	SharePoint admin center → Active sites

Frequently Asked Questions

How do I clear the Microsoft Teams cache on the new client?

Close Teams completely — right-click the system tray icon and select Quit, or end the ms-teams.exe process in Task Manager to be sure. Then navigate to %LocalAppData%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams and delete everything in this folder. Restart Teams. Note that this path is different from the classic Teams cache path — the old %AppData%\Microsoft\Teams location no longer applies.

Why does Microsoft Teams keep crashing after a Windows update?

Windows cumulative updates can occasionally break the Edge WebView2 Runtime that the new Teams client depends on. After a major update, verify that WebView2 is still installed and up to date. Also check that ms-teams_modulehost.exe is allowed through your endpoint protection — security software sometimes re-evaluates trust after OS updates. If crashes persist, clear the Teams cache and run TeamsLaunchCheck.ps1 to identify the root cause.

How can I check a user's Teams call quality as a helpdesk agent?

You'll need the Teams Communications Support Specialist role (at minimum) assigned in the Microsoft 365 Admin Center. Once that's set up, open the Teams Admin Center, go to Users, select the user, and click the Meetings & calls tab. You can review quality metrics for any recent call, including jitter, packet loss, and round-trip time. For org-wide analysis, you'll need the Teams Administrator role and access to CQD.

What ports and URLs must be open for Microsoft Teams to work?

Teams requires outbound HTTPS (port 443) to multiple Microsoft endpoints, plus UDP ports 3478–3481 for media traffic (STUN/TURN). The complete list of required URLs and IP ranges is published by Microsoft and updated regularly. At a minimum, ensure *.teams.microsoft.com, *.skype.com, *.lync.com, and *.sfbassets.com are accessible. Blocking UDP ports is the number one cause of poor audio and video quality — if you take away just one thing from this guide, let it be this.

Can I collect Teams diagnostic logs remotely without the user's help?

Yes, and it's a real time-saver. The Teams Admin Center supports remote diagnostic log collection for Windows and Mac clients. Navigate to the user's profile in the Teams Admin Center and click "Request client logs." The logs are collected silently in the background and typically available within 8 hours. This captures web diagnostics, calling logs, and Slimcore media stack logs. It doesn't collect procmon traces or OS event logs — for those, you'll still need manual collection or Intune.