Microsoft Teams Not Working, Audio, Login, and Chat Fixes
Why Microsoft Teams Not Working Is Such a Common Problem
I've seen this exact situation play out hundreds of times. You sit down for a 9 AM standup, click the Teams icon, and, nothing. The app spins forever, throws a cryptic error code, drops your audio mid-sentence, or refuses to let you into a meeting at all. Meanwhile everyone else is waiting. It's one of the most professionally embarrassing tech problems out there because it happens in public, right when it matters most.
Here's the honest truth about why Microsoft Teams not working is so hard to diagnose: there isn't one problem. There are dozens of failure points that produce nearly identical symptoms. Your audio cutting out could be a corrupted cache, a Windows audio driver conflict, or a Group Policy locking your microphone. Your login failing could mean your SIP domain isn't enabled, your license expired at midnight, or Microsoft's own servers hit an incident. The error message Teams shows you, if it shows one at all, rarely points at the actual cause.
The most common root causes I see across enterprise and personal setups:
- Corrupted local cache files. Teams aggressively caches everything locally. When those files get corrupted, after an update, a hard shutdown, or a Windows profile issue, Teams breaks in weird, unpredictable ways.
- SIP domain not enabled in your tenant. This is purely an admin-side issue, completely invisible to end users, and it produces the
FAILED_TO_AUTO_DISCOVER_DOMAINerror that baffles IT teams the first time they see it. - Licensing gaps and sync delays. Microsoft 365 license changes don't take effect instantly. A license assigned at 4 PM might not propagate until the next morning. Teams Premium features have their own additional provisioning layer that adds another 24-hour window on top of that.
- Entra ID permission misconfigurations. The "We couldn't add member" error is a perfect example, it's caused by a single boolean flag deep in Microsoft Entra ID that most admins don't know exists until they hit this wall.
- Network-level blocks. If your org's firewall or proxy isn't whitelisting the required Microsoft IPs and URLs, Teams will partially work at best, meetings may connect but screen sharing fails, or chat loads but files don't.
- Service incidents on Microsoft's side. Sometimes it genuinely isn't your fault. Microsoft runs a health dashboard for a reason.
The good news is that the vast majority of Microsoft Teams not working issues are fixable without opening a support ticket. This guide walks you through every fix in order, from the simple to the complex, so you can get back online fast. Browse all Microsoft fix guides →
The Quick Fix, Try This First
Before you do anything else, before you reinstall, before you call IT, before you open a ticket, clear your Teams cache. I cannot overstate how many "Microsoft Teams not working" calls I've resolved in under five minutes just by doing this. Corrupted cache files are the single most common cause of Teams behaving strangely, and clearing them is completely safe. You won't lose your messages, your contacts, or your meeting history. All of that lives in the cloud.
Here's exactly what to do on Windows, depending on which version of Teams you have:
If you're on the new Microsoft Teams (2023 or later):
The cleanest method is using the built-in reset option. Open your Windows search bar, type Settings, and open the Settings app. Navigate to Apps > Installed apps. In the search box, type Microsoft Teams. Find the entry labeled "Microsoft Teams" (not the classic version), click the three-dot menu on the right, and select Advanced options. Scroll down to the Reset section. Click Reset. Confirm when prompted. Then restart Teams from scratch.
If you'd rather delete the files directly: first, right-click the Teams icon in your taskbar and choose Quit. Press Win + R to open the Run dialog. Paste this path exactly:
%userprofile%\appdata\local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeamsHit OK, then select everything in that folder and delete it all. Restart Teams.
If you're on classic Teams:
Quit Teams completely via the taskbar. Press Win + R, type:
%appdata%\Microsoft\TeamsDelete everything in that directory. Restart Teams. The first launch will take longer than usual, that's normal, Teams is rebuilding its cache from scratch.
After the restart, test the specific thing that was broken. Audio issues, login loops, missing contacts, broken file tabs, clearing the cache fixes a surprising number of these on the first try.
If you're on a Mac and Microsoft Teams not working is your situation, the cache clear process is slightly different and a lot of Teams guides forget to cover it. The good news: the logic is identical, just the file paths change.
Start by fully quitting Teams. Right-click the Teams icon in your Dock and select Quit, or press Command (⌘) + Q with Teams in focus. Don't just close the window, make sure the app is fully terminated.
Open Finder. In the top menu bar, click Go, then hold down the Option key to reveal the hidden Library option. Click Library.
For classic Teams on macOS, navigate to:
~/Library/Application Support/Microsoft/TeamsDelete the contents of that folder, not the folder itself, just everything inside it.
For new Teams on macOS, the cache location is under:
~/Library/Containers/com.microsoft.teams2/Data/Library/Application Support/Microsoft/MSTeamsSame approach: clear the contents, leave the folder.
After deleting, restart Teams. On macOS you may also want to open System Preferences > Security & Privacy > Microphone and confirm Teams still has permission listed, sometimes a cache reset can prompt macOS to re-evaluate app permissions, and you'll see a permission dialog on next launch. Just click Allow.
If Teams launches clean and your audio, chat, and file tabs are all loading normally, you're done. If not, keep going through the steps below, there's a deeper issue at play.
This one shows up specifically when someone tries to connect to the Microsoft Teams admin center and sees a hard stop: FAILED_TO_AUTO_DISCOVER_DOMAIN. It's not a client-side error, it's entirely tenant-level, which means individual users can't fix it themselves. You need admin access.
There are four distinct scenarios that trigger this error, and you need to rule each one out in order.
Scenario A, SIP domain not enabled. This is the most common cause. Connect to Skype for Business Online via PowerShell. Then run:
Get-CsOnlineSipDomainIf your domain shows as disabled, enable it with:
Enable-CsOnlineSipDomain -Domain yourdomain.comReplace yourdomain.com with your actual tenant domain. Important: this fix isn't instant. It can take anywhere from 15 minutes to a full hour to propagate across Microsoft's infrastructure. Don't panic if it doesn't work immediately, set a timer and check back.
Scenario B, No user licensed for Teams or Skype for Business. Your tenant needs at least one user with a valid Teams or Skype for Business license assigned. If everyone's license lapsed or was removed, this error appears. See Step 5 for exact instructions on assigning licenses through the Microsoft 365 admin center.
Scenario C, IPs and URLs are blocked. Your firewall or proxy may be preventing Teams from reaching the required Microsoft endpoints. You'll need to whitelist the IPs and URLs specified in Microsoft's official network requirements for Teams. Work with your network team on this one, it's not something that can be done from within Teams itself.
Scenario D, Active service incident. Before spending two hours troubleshooting, check the Microsoft 365 Service Health Dashboard. If there's a live incident affecting Teams federation or admin center connectivity, the fix is to wait it out. No amount of PowerShell will resolve an incident on Microsoft's side.
This is one of those errors that makes you feel like you're going crazy. You try to add a colleague, internal or external, to a Team, and you get: "We couldn't add member. We ran into an issue. Please try again later." You retry. Same thing. You try a different member. Same thing. But here's the strange part: if you go directly to the Microsoft 365 Groups admin panel, you can add people just fine. So Teams is clearly broken in a way that Groups isn't.
The cause is a single setting in Microsoft Entra ID (formerly Azure Active Directory). There's a tenant-level permission called UsersPermissionToReadOtherUsersEnabled, and when it's set to False, Teams loses the ability to look up other users in the directory, which breaks the "add member" flow entirely.
To fix it, you need Global Administrator access to Microsoft Entra ID. Here's how to change the setting:
# Connect to Microsoft Graph or Azure AD PowerShell
# Then update the setting:
Set-MsolCompanySettings -UsersPermissionToReadOtherUsersEnabled $TrueAlternatively, you can change this through the Entra ID portal UI: navigate to Microsoft Entra ID > User settings and look for the option governing whether users can read other user profiles. Toggle it to enabled.
Once the setting is changed, the fix takes effect relatively quickly, usually within minutes, though in larger tenants it can take up to an hour to sync across all services. Try adding the member again after a 10-minute wait. In most cases, this completely resolves the issue without any other changes needed.
Worth noting: this setting also affects other Microsoft 365 apps that depend on directory lookups, so if you've had mysterious "can't find user" problems in SharePoint or Outlook's people picker, fixing this one setting may quietly resolve those too.
Microsoft Teams Premium features disappearing, or never appearing in the first place, is one of the most confusing experiences in the Microsoft 365 ecosystem. You purchase a license, assign it to a user, they log out and back in, and... nothing. The features aren't there. I know how infuriating this is.
The first thing to understand is timing. Teams Premium license provisioning has a built-in delay of up to 24 hours. This isn't a bug, it's by design. So if you just assigned the license an hour ago, wait it out. Check back tomorrow morning before you start deeper troubleshooting.
If it's been more than 24 hours and Teams Premium features still aren't showing up, use Microsoft's own diagnostic tool: the Microsoft Remote Connectivity Analyzer. This is the most underused tool in Microsoft's support arsenal, and it directly checks whether a user account meets all the requirements for Teams Premium. Here's how to run it:
- Open a browser and go to the Teams Premium Details test on the Microsoft Remote Connectivity Analyzer site.
- Sign in using the credentials of the affected user account, not an admin account, the actual affected user.
- Enter the verification code shown on screen and click Verify.
- Check the terms of agreement box, then click Perform Test.
The tool will then run through a checklist that answers three critical questions: Does this account have a valid Teams license? Does it have a valid Teams Premium license? Were the necessary backend services enabled for Teams Premium after the license was assigned? That third check is the one most admins miss, there's a service enablement step that doesn't happen automatically in all tenant configurations.
If the test surfaces warnings or failures, it provides direct links explaining exactly what's wrong and how to fix each item. Follow those links. They're far more specific than anything you'll find by guessing.
One more thing: if users were assigned trial licenses for Teams Premium, those trials are only valid for 30 days from the purchase date. If the trial expired, the features disappear without warning. There's no grace period. The only path forward is purchasing full Teams Premium licenses.
Note: the Microsoft Remote Connectivity Analyzer isn't available in GCC or GCC High government environments. If your org operates in those environments, you'll need to work directly with Microsoft support for Teams Premium provisioning issues.
A lot of Microsoft Teams not working scenarios trace back to a licensing issue that nobody noticed. A license expired. Someone's account was moved to a different department and lost its Teams assignment. An IT admin removed a duplicate license and accidentally removed the wrong one. These things happen constantly in larger organizations, and Teams is often the first app to break when they do.
Here's how to check and fix licensing directly through the Microsoft 365 admin center, no PowerShell required for this one:
- Sign in to admin.microsoft.com with your admin account.
- In the left navigation, go to Users > Active Users.
- Search for the affected user and click their name to open their profile.
- In the panel that slides out on the right, click the Licenses and Apps tab.
- Expand the Licenses section. You'll see a list of available licenses with checkboxes.
- Make sure either Microsoft Teams or a license bundle that includes Teams (like Microsoft 365 Business Standard or E3) is checked.
- Click Save changes.
After saving, the license assignment begins propagating, but it can take up to 24 hours for Teams to fully recognize the change. This is a hard Microsoft system limitation, not something you can speed up. If the user needs access urgently and you're in a larger enterprise environment, occasionally signing the user out of all Microsoft 365 apps and signing back in can sometimes accelerate the recognition, though it's not guaranteed.
For teams admins dealing with the FAILED_TO_AUTO_DISCOVER_DOMAIN error, remember that at least one user in the tenant must have a valid Skype for Business or Teams license, not just any Microsoft 365 license. If everyone on the tenant has, say, only Exchange Online licenses, that error will persist until a proper Teams-capable license is assigned to at least one account with a Teams admin role.
Advanced Troubleshooting for Microsoft Teams Not Working
If you've made it here, the standard fixes didn't fully resolve your Microsoft Teams not working situation. That usually means there's something environmental, network policy, Group Policy, a domain-join issue, or a deeper service configuration problem. Let's dig in.
Check the Windows Event Viewer. When Teams crashes or fails silently, Windows Event Viewer often captures the real error. Press Win + X and select Event Viewer. Go to Windows Logs > Application. Filter by source "MSTeams" or just scroll through recent errors around the time Teams failed. Look for Event IDs in the 1000–1002 range, these typically indicate application faults with a module name that tells you exactly what failed (a DLL, an audio component, a network module). This information is invaluable when escalating to Microsoft support.
Check for hybrid configuration conflicts. If your organization runs Skype for Business on-premises alongside Microsoft Teams, you need a properly configured hybrid connection between the two. Without this, Teams and Skype for Business can't interoperate correctly, and you may see presence failures, missed calls, and federation errors. This is especially common in organizations that are mid-migration, they've deployed Teams but haven't fully decommissioned Skype for Business. The fix requires configuring a Skype for Business hybrid model, which is an admin-level task that needs to be coordinated with your on-premises Skype team.
Verify Group Policy isn't blocking Teams. In domain-joined environments, Group Policy Objects can block Teams from running, prevent it from updating, or restrict audio device access. Open gpedit.msc on the affected machine and check under Computer Configuration > Administrative Templates > Windows Components > App Privacy for any policies blocking microphone or camera access. Also check User Configuration > Administrative Templates > Microsoft Teams if your org has deployed Teams-specific ADMX templates.
Network-level diagnosis. Microsoft Teams requires access to a specific set of IPs and URLs to function. If your org uses a proxy, firewall, or content filtering system, it may be silently dropping Teams traffic, particularly for meetings, file sharing, and the admin portal. The full list of required endpoints is maintained in Microsoft's official network planning documentation. The most important ones to verify are the Teams calling and meeting IPs, the SharePoint Online endpoints (required for file sharing in Teams), and the Azure CDN URLs that Teams uses for media. Your network team can run a packet capture to confirm whether these requests are making it through.
Presence status issues in Outlook. If Teams presence isn't showing correctly in Outlook, contacts appearing as "Unknown" or presence not updating, this is often a separate issue from Teams itself. It can relate to how the Outlook add-in is configured, whether the user's Teams account is properly linked to their Outlook profile, or service-side delays in presence propagation. Restarting the Outlook client and signing out and back into Teams simultaneously often resolves this. If it persists, check whether the Teams Outlook add-in is enabled under File > Options > Add-ins in Outlook.
If you've run through every step in this guide and Teams is still broken, it's time to escalate. Specifically, call Microsoft if: your service health dashboard shows no active incident but the problem is tenant-wide; you've correctly configured SIP domains and licensing but the FAILED_TO_AUTO_DISCOVER_DOMAIN error persists beyond two hours; or Teams Premium provisioning fails even after the Remote Connectivity Analyzer shows all checks passed. When you contact Microsoft Support, bring your tenant ID, the Event Viewer logs from affected machines, and the output of your Remote Connectivity Analyzer test. That package cuts escalation time dramatically.
Prevention & Best Practices to Keep Microsoft Teams Running Smoothly
Fixing Microsoft Teams not working is satisfying, but avoiding it in the first place is better. After years of managing Teams deployments across organizations of all sizes, here's what actually makes the difference between a Teams environment that runs reliably and one that breaks every other week.
Keep Teams updated, and let it update itself. A significant portion of Teams problems I see are on clients that are two, three, sometimes six versions behind. Microsoft pushes fixes and improvements constantly, and old clients hit bugs that were resolved months ago. In most personal setups, Teams updates automatically. In enterprise environments, verify your update policy isn't accidentally blocking Teams updates. The Teams admin center has an update policy section, check it.
Monitor your license expiration dates. Set a calendar reminder 30 days before any Teams or Teams Premium trial license expires. Trial licenses go from fully functional to completely dark the moment they expire, there's no graceful degradation, just an abrupt cutoff. Full commercial licenses also need to be tracked. In the Microsoft 365 admin center, you can see upcoming expirations on the Billing > Your products page.
Test network connectivity proactively. The Microsoft Remote Connectivity Analyzer isn't just a break-fix tool, you can run it proactively on user accounts after any major network change (new firewall rules, proxy updates, VPN configuration changes) to confirm Teams connectivity is intact before anyone starts complaining that it's broken.
Document your tenant configuration. Keep a living document that records your SIP domain status, your hybrid Skype configuration (if applicable), and your key Entra ID settings. The UsersPermissionToReadOtherUsersEnabled flag we covered earlier is a perfect example, it's something that could be accidentally toggled during a security hardening review. If you don't know it was enabled intentionally, you won't know to check it when "add member" starts breaking again.
- Schedule a monthly cache clear on all employee machines using a simple startup script, it takes 30 seconds and prevents a whole category of random Teams weirdness
- Set up Microsoft 365 Service Health alerts so you get emailed when there's a Teams incident, this alone saves hours of unnecessary troubleshooting
- After any major Microsoft 365 license change, wait the full 24 hours before concluding there's a problem, provisioning delays are normal and not a reason to open a ticket
- For orgs in hybrid Skype/Teams environments, schedule a quarterly review of your hybrid configuration to ensure it stays correctly set up as Microsoft rolls out changes
Frequently Asked Questions
Why does Microsoft Teams keep showing "You're missing out" when I try to sign in?
This sign-in error usually means Teams can't connect to your organization's tenant, either because your account isn't set up correctly in Microsoft Entra ID, or because the SIP domain for your organization hasn't been enabled. If you're an end user hitting this, hand it to your IT admin and ask them to check whether SIPDomain is enabled for your tenant by running Get-CsOnlineSipDomain in PowerShell. If SIPDomain is disabled, they can enable it with Enable-CsOnlineSipDomain -Domain yourdomain.com, though be aware it can take up to an hour to take effect. In the meantime, try clearing your Teams cache and signing in fresh, the steps for that are in the Quick Fix section above.
How do I know if my account has a valid Teams license?
The fastest way to check your own license status is to ask your Microsoft 365 admin to look you up in the Microsoft 365 admin center at Users > Active Users, your license assignments show up on the Licenses and Apps tab of your user profile. If you have admin access yourself, you can check it directly. You're looking for either a standalone Microsoft Teams license or a bundle license (like Microsoft 365 Business Standard, E3, or E5) that includes Teams. If Teams is checked and saved, but you're still getting blocked, run the Teams Premium Details connectivity test through the Microsoft Remote Connectivity Analyzer, it directly verifies whether the services are actually provisioned for your account, not just whether the license is assigned.
Does my account need a valid Teams Premium license separately from a regular Teams license?
Yes, Teams Premium is a separate add-on license that sits on top of your standard Teams license. Having a regular Microsoft 365 or Teams license does not grant access to Teams Premium features like intelligent meeting recaps, advanced meeting protection, or custom meeting branding. You need both: a base Teams license AND a Teams Premium license assigned to your account. After both are assigned, allow up to 24 hours for provisioning to complete, and if the features still don't appear after that window, use the Microsoft Remote Connectivity Analyzer's Teams Premium Details test to diagnose exactly which part of the provisioning chain is incomplete.
Were the appropriate services enabled after my Teams Premium license was assigned?
This is actually one of the most overlooked causes of Teams Premium features not showing up, and it's something the Microsoft Remote Connectivity Analyzer specifically checks for you. Assigning the license is step one; but certain Teams Premium capabilities require corresponding backend services to be switched on in your tenant's configuration, and this doesn't always happen automatically. When you run the connectivity test in the Remote Connectivity Analyzer, one of its explicit checks is whether those services were properly enabled after license assignment. If that check comes back failed, the tool gives you a direct link to the resolution steps, follow those exactly, because the fix varies depending on which services weren't enabled.
Why can't I open files in a Teams chat window even though SharePoint works fine?
This is almost always a cache or permissions issue rather than a file storage problem. First, try the cache clear described in the Quick Fix section, corrupted Teams cache files commonly break the Files tab and in-chat file preview while leaving SharePoint itself unaffected. If the cache clear doesn't fix it, check whether your firewall or proxy is blocking the Azure CDN URLs that Teams uses to serve file previews and the SharePoint connector within Teams, these are different endpoints than what direct SharePoint access uses. A network admin can verify this with a packet capture. If you're seeing an explicit error when clicking the Files tab (rather than just a spinning loader), note the exact error text and check the Teams service health dashboard for any active file-related incidents.
My Teams presence status shows wrong in Outlook, how do I fix it?
Presence sync between Teams and Outlook is handled through the Teams Outlook add-in, and it breaks more often than it should. Start by confirming the add-in is active: open Outlook, go to File > Options > Add-ins, and make sure "Microsoft Teams Meeting Add-in for Microsoft Office" is listed as an active add-in and not in the disabled section. If it's disabled, select it and click Enable. Next, sign out of Teams completely, then sign out of Outlook, then sign back into both, doing this in sequence forces a fresh presence sync. If the issue persists, it may be related to how your organization's hybrid Skype for Business configuration is set up, particularly if you're in a mixed Skype/Teams environment where presence routing between the two systems gets confused. Your admin can check the hybrid configuration settings to ensure presence is being correctly federated between Skype and Teams.