Fix Teams Copilot Cannot Summarize a Meeting after a Policy Update

After an admin updates a Teams meeting policy, Copilot may stop summarizing meetings. You see an error like “Copilot is not available for this meeting” or the summary tab is missing. This happens because the policy change disabled Copilot or blocked transcription. This article explains the exact policy settings that control Copilot and how to verify and fix them.

You will learn where to check the effective policy for a user, how to enable transcription and Copilot, and what to do if the policy looks correct but Copilot still fails. The steps apply to Teams desktop, web, and mobile clients.

Why a Policy Update Breaks Copilot in Teams Meetings

Copilot in Teams relies on two separate features: transcription and the Copilot engine. When an admin changes a meeting policy, they may unintentionally disable one or both. The most common cause is setting the Transcription policy to Off. Without a transcript, Copilot has no data to summarize.

Another cause is the Copilot policy being set to Off or For meetings with transcription. The default is On, but an admin may have changed it. Also, the policy assignment order matters. A user can have a global policy, a group policy, or a per-user policy. The most specific one wins. If a user is in a group with a restrictive policy, the global policy settings are ignored.

Finally, the meeting organizer might have turned off transcription in the meeting options. Even if the policy allows it, the organizer can disable it for a specific meeting. This is a per-meeting override that blocks Copilot.

Steps to Diagnose and Fix Copilot After a Policy Change

Follow these steps in order. Each step verifies a different layer of the configuration.

1. Check the user’s effective meeting policy
   Sign in to the Teams admin center at admin.teams.microsoft.com. Go to Users > Manage users. Select the affected user. In the Policies tab, look at the Meeting policy assignment. Note the policy name. If it says Global (Org-wide default), the global policy applies. If it shows a custom policy, that policy takes precedence.
2. Open the meeting policy and verify Copilot settings
   In the Teams admin center, go to Meetings > Meeting policies. Select the policy that applies to the user. Scroll to the Copilot section. Set Copilot to On. Set Transcription to Allow. Click Save. Wait up to 24 hours for the change to propagate, though it usually takes effect within minutes.
3. Check the meeting options in the Teams client
   Open Teams and go to Calendar. Double-click the meeting where Copilot failed. In the meeting details, select Meeting options. Verify that Record and transcribe is set to Allow. Also confirm that Copilot is set to Allow. If either is off, turn it on and save.
4. Force a policy refresh on the client
   Sign out of Teams and sign back in. This forces the client to download the latest policy settings. Alternatively, restart the Teams app. On Windows, close Teams from the system tray, then reopen it.
5. Test with a new meeting
   Create a new meeting and start it. Turn on transcription manually if it is not already on. Check if Copilot appears in the meeting controls. If it does, the policy is now correct. The original meeting may still fail because the policy change does not retroactively enable Copilot for meetings that already ended.

If the Policy Is Already Correct But Copilot Still Fails

Sometimes the policy settings look correct, but Copilot still does not work. The next step is to check the license. Copilot for Microsoft 365 requires a specific license. Without it, the Copilot button is hidden even if the policy allows it.

Go to the Microsoft 365 admin center at admin.microsoft.com. Select Users > Active users. Find the user and check the Licenses and apps tab. Confirm that Microsoft Copilot for Microsoft 365 is assigned. If not, assign it and wait a few minutes.

If Teams Copilot Still Has Issues After the Main Fix

Copilot Shows a Message That Transcription Is Off

This message appears when the meeting organizer disabled transcription or the policy blocks it. Ask the organizer to open the meeting options and turn on transcription. If the organizer cannot change it, the admin must update the policy.

Copilot Is Grayed Out in the Meeting Controls

A grayed-out Copilot button means the policy or the license is blocking it. Recheck the effective policy and the license assignment. Also, Copilot is not available for channel meetings or for meetings that use end-to-end encryption.

Copilot Works for Some Users But Not Others

This indicates a per-user policy override. Compare the policy assignments of a working user and a non-working user. Use the Policy analysis tool in the Teams admin center to see which policy applies to each user.

New Teams Desktop vs Teams on the Web for Copilot

Item	Teams Desktop	Teams on the Web
Copilot availability	Full support	Full support
Transcription control	Available in meeting controls	Available in meeting controls
Policy refresh timing	Requires app restart	Requires page reload
Meeting options access	Opens in a dialog	Opens in a new browser tab
Known limitation	None major	Copilot may not load in private browsing mode

Conclusion

You can now diagnose and fix Copilot failures caused by a meeting policy update. The key is to verify the effective policy, enable transcription, and confirm the Copilot license. Always test with a new meeting after changing policies. For a quick check, use the Ctrl+Shift+P shortcut in Teams to open the policy diagnostics panel.

If you manage multiple users, consider creating a dedicated meeting policy for Copilot and assigning it to a security group. This gives you a consistent baseline and reduces the chance of accidental overrides.