Microsoft Copilot Not Working? 8 Common Issues & Fixes
Microsoft Copilot in Teams is a powerful AI assistant — until it stops responding, fails to load, or shows up greyed out. You might see the Copilot button missing from the ribbon, or errors like “Couldn’t update license… Error code: 29” or “Something went wrong. Let’s try again.” Most of these trace back to a handful of causes: licensing, the wrong account, a stale cache, an unsupported update channel, or privacy and policy settings. With Microsoft reporting that more than 90% of the Fortune 500 now use Microsoft 365 Copilot (FY26 Q1 earnings call, October 2025), a Copilot that won’t load is a real productivity blocker — so here’s how to fix it, fastest checks first.
Quick fix: Confirm you’re online, fully quit and reopen Teams, and sign out and back in with the same account that holds your Copilot license. That clears the majority of “Copilot not working” cases in under five minutes. If it persists, work through the eight fixes below in order.
How to fix Microsoft Copilot when it’s not working
1. Check your internet connection and network access
Copilot is a cloud service, so it needs stable connectivity that meets Microsoft’s network requirements. Quick checks:
- Restart your router and reconnect after 2–3 minutes; use an ethernet cable to rule out Wi‑Fi instability.
- If you’re on a corporate network, confirm a firewall, VPN, or antivirus isn’t blocking Copilot — temporarily disable security software to test, then re-enable it and add Teams and Copilot to the allowlist rather than leaving protection off.
2. Clear the Teams cache
A corrupted cache is one of the most common reasons Copilot fails to load or appear. The location depends on which client you run:
- New Teams (the default since 2024): quit Teams, then delete the contents of
%LocalAppData%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache. - Classic Teams: quit Teams, then delete the files in
%appdata%\Microsoft\Teams.
Restart Teams afterwards. Many users find this alone resolves Copilot not loading [2].
3. Make sure you actually have a Copilot license
This is the single most common cause — and the easiest to get wrong. Teams Premium does not include Microsoft 365 Copilot. They’re separate products: Copilot in Teams requires the Microsoft 365 Copilot add‑on license assigned on top of your Microsoft 365 or Office 365 subscription.
- Ask your admin to confirm a Microsoft 365 Copilot license is assigned to your account specifically — not just Teams Premium.
- A newly assigned license takes time to propagate. Allow 30–60 minutes, and in some cases up to 24 hours, before Copilot appears.
- To force a refresh in desktop Office apps, go to File > Account > Update License, then close and reopen all Microsoft 365 apps.
- Note: Copilot requires a user-based license — it isn’t available with device-based licensing for Microsoft 365 Apps.
4. Sign in with the correct account
If Teams is signed in with a different account than the one holding your Copilot license, the Copilot entry point won’t show. A common trap: being signed in with both a personal Microsoft account and a work or school account at once, which stops Copilot from validating correctly. Sign out of the personal account, then sign back in with the work account tied to the subscription.
5. Update your apps — and check your update channel
Microsoft ships frequent Copilot fixes, so an outdated app is a common culprit. There’s also a less obvious requirement: Copilot only works on the Current Channel or Monthly Enterprise Channel. If your organization is on the Semi‑Annual Enterprise Channel, Copilot won’t appear until the channel is changed (an admin task). Microsoft is explicit about this:
“If you’re using the Semi-Annual Enterprise Channel of Microsoft 365, you’ll find that Microsoft 365 Copilot features aren’t available in your apps.” — Microsoft Support
| Component | Check for updates | Why it matters |
|---|---|---|
| Microsoft Teams | Weekly | Core Copilot features and access |
| Windows | Monthly | System-level compatibility |
| Microsoft 365 Apps | Monthly | Integration with Copilot (use a supported channel) |
6. Check your privacy / connected-experiences setting
Copilot can be blocked by Office privacy settings. In the Office apps, the optional connected experience “Experiences that analyze your content” must be turned on (File > Account > Account Privacy > Manage Settings) for Copilot to function. If your admin disabled it org-wide, Copilot won’t appear.
7. Enable Copilot for Teams meetings
If Copilot works elsewhere but is greyed out in meetings, it’s almost always policy. In the Teams admin center > Meetings > Meeting policies, the Copilot setting must be On (or “On only with retained transcript”). Because meeting Copilot relies on the transcript, transcription or cloud recording must also be allowed — if both are off, Copilot can’t activate in calls or meetings [5].
8. Check service health, then use Microsoft’s built-in tools
Rule out a problem on Microsoft’s side: the Microsoft 365 Service Health Dashboard lists active incidents affecting Teams and Copilot with estimated resolution times. If there’s no outage, let Microsoft’s diagnostics do the work:
- The Get Help app in Teams (includes a Copilot connectivity troubleshooter), and the official find and enable the missing Copilot button guide.
- The Microsoft Support and Recovery Assistant.
- Teams logs at
%appdata%\Microsoft\Teams\logs.txtfor error details [1].
Still stuck? Gather your logs and the exact error message, then have your admin contact Microsoft Support.
How to prevent Copilot issues from coming back
Most recurring Copilot problems are setup problems. Three habits keep it stable:
- Keep software current on a supported channel. Update Teams, Windows, and Microsoft 365 Apps regularly, and stay on the Current or Monthly Enterprise Channel so fixes land automatically.
- Monitor service status. Watch the Microsoft 365 Service Health Dashboard for incidents that affect Teams and Copilot before they derail your day.
- Align with IT governance. In the Microsoft 365 Admin Center, admins can manage licenses, privacy controls, meeting policies, and update channels so Copilot behaves consistently across the organization.
For larger teams, consistent Teams setups also matter: when every workspace is provisioned the same way, there are fewer misconfigurations for Copilot to trip over. That’s where nBold helps — it standardizes team creation with governed templates and naming, so collaboration environments stay predictable as you scale. Cleaner structure means Copilot has cleaner content to work with, and team productivity holds up.
FAQs
Why isn’t my Microsoft Copilot working?
Copilot usually fails for one of a few reasons: no Microsoft 365 Copilot license assigned (Teams Premium isn’t enough), a recently assigned license that hasn’t propagated, the wrong account, an unsupported Office update channel, an outdated app, or a service outage. Work through the eight fixes above in order.
Does Teams Premium include Microsoft 365 Copilot?
No — they’re separate products. Teams Premium adds advanced meeting features; Copilot in Teams requires the Microsoft 365 Copilot add-on license assigned on top of your Microsoft 365 or Office 365 subscription. If Copilot is missing, confirm the Copilot license specifically.
How long does it take for Copilot to appear after a license is assigned?
Allow 30–60 minutes, and in some cases up to 24 hours, for a new license to propagate. To speed it up in desktop Office apps, use File > Account > Update License, then restart all Microsoft 365 apps.
Why is Copilot greyed out or missing in Teams meetings?
Meeting Copilot depends on an admin meeting policy set to On (or “On only with retained transcript”) and on transcription or cloud recording being allowed. If those are off, Copilot stays greyed out in meetings.
How do I clear the cache in new Teams?
Quit Teams completely, delete the contents of %LocalAppData%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache, and restart. Classic Teams uses %appdata%\Microsoft\Teams instead.
“Ensuring you’re signed in to Teams with the same Microsoft account used to purchase the M365 subscription can resolve licensing discrepancies. Signing out and signing back in can help refresh the account settings.” [2]