Microsoft 365 Copilot in Teams Ignores Meeting Recording: Fix

You ask Copilot in Microsoft Teams a question about a meeting you just attended, but it gives a vague response or says it cannot find the information. This often happens because Copilot cannot access the meeting recording or transcript. The root cause is usually a missing meeting recording policy, a disabled transcription setting, or a permissions gap. This article explains why Copilot ignores meeting recordings and provides the exact steps to fix the issue.

Why Copilot Cannot Access Meeting Recordings

Copilot in Teams relies on two data sources to answer questions about meetings: the live transcript and the recorded transcript. When either is missing, Copilot has no content to analyze. The most common reason is that transcription is not enabled for the meeting. Without a transcript, Copilot cannot index the spoken words.

Another cause is that cloud recording is disabled at the tenant level or on the specific meeting policy. Even if the meeting was recorded locally, Copilot needs the cloud recording file stored in Microsoft 365 to process it. If the recording is stored on a local device, Copilot cannot access it.

A third cause is a permissions issue. The user asking the question must have at least read access to the recording file in OneDrive or SharePoint. If the recording is stored in a location the user cannot access, Copilot will return an empty response.

Finally, Copilot data source settings in the Microsoft 365 admin center control whether Copilot can read Microsoft Graph data. If a tenant admin has restricted the data sources, Copilot may ignore meeting recordings entirely.

Steps to Re-enable Copilot Access to Meeting Recordings

Follow these steps in order. Each step addresses a specific cause. Test Copilot after each step to see if the issue is resolved.

1. Enable transcription on the meeting policy
   Sign in to the Teams admin center at admin.teams.microsoft.com. Go to Meetings > Meeting policies. Select the policy applied to your users. Under Audio & video, set Allow transcription to On. Click Save. This setting generates a live transcript for every meeting under this policy. Copilot reads the transcript to answer questions.
2. Enable cloud recording on the meeting policy
   In the same policy, under Audio & video, set Allow cloud recording to On. Click Save. This ensures that recordings are stored in Microsoft 365 and accessible to Copilot. Recordings saved to a local drive are ignored by Copilot.
3. Verify the user has access to the recording file
   Open the meeting in the Teams Calendar and select Recap. Under Recording, check if the recording file is listed. Click the file name to open it in OneDrive or SharePoint. If you see a permissions error, ask the meeting organizer to share the file with you. Without at least View access, Copilot cannot read the recording.
4. Check Copilot data source settings
   Sign in to the Microsoft 365 admin center at admin.microsoft.com. Go to Settings > Org settings > Copilot. Under Data sources, verify that Microsoft Graph is selected. If it is unchecked, Copilot cannot read any meeting data. Click Save if you made changes.
5. Confirm recording and transcription for a specific meeting
   During a meeting, select More actions in the meeting controls and choose Start transcription. Also select Record and transcribe to start both. After the meeting, wait a few minutes for processing. Then open the Recap tab and ask Copilot a question about the meeting. If the steps above are correct, Copilot should respond with specific meeting content.

If Copilot Still Has Issues After the Main Fix

Copilot responds with “I can’t find information about that meeting”

This error usually means the meeting recording or transcript was not generated. Check the meeting policy again to confirm both transcription and cloud recording are enabled. Also verify that the meeting organizer did not manually disable recording during the meeting. If the meeting was a channel meeting, the recording is stored in the SharePoint site of the channel. Ensure you have access to that site.

Copilot returns generic output instead of meeting-specific data

If Copilot gives a broad answer like “Meetings are important for collaboration” instead of quoting the discussion, it is not reading the recording. This often happens when the recording is still processing. Wait at least 5 minutes after the meeting ends. If the problem persists, check the Copilot data source setting again. A tenant admin may have restricted Copilot to only public data sources.

Recording file exists but Copilot still ignores it

The recording file may be in a format Copilot cannot process. Microsoft Teams recordings are stored as MP4 files with a companion VTT transcript file. If the VTT file is missing, Copilot cannot index the content. Open the recording in OneDrive and look for the .vtt file. If it is missing, re-record the meeting. Also confirm that the recording is stored in the user’s OneDrive or the team’s SharePoint library, not in an external location.

Copilot in Teams vs Copilot in Other Microsoft 365 Apps: Meeting Data Access

Item	Copilot in Teams	Copilot in Word or Excel
Data source for meetings	Meeting transcript and cloud recording	Document content only
Requires transcription	Yes, must be enabled per meeting policy	Not applicable
Requires cloud recording	Yes, stored in OneDrive or SharePoint	Not applicable
Permission needed	View access to recording file	Edit access to document
Delay after meeting	Up to 5 minutes for processing	None
Works with live meetings	Yes, during the meeting if transcription is on	Not applicable

Copilot in Teams is unique because it depends on real-time and recorded meeting data. Other Copilot apps work with static files. This means Teams Copilot has more dependencies on admin policies and user permissions. If you fix meeting access in Teams, the same settings do not affect Copilot in other apps.

Now you can resolve the issue where Copilot ignores meeting recordings. Start by enabling transcription and cloud recording in the Teams admin center. Then verify user permissions and Copilot data source settings. As a next step, test Copilot in a channel meeting to see if the behavior changes. For best results, always start transcription at the beginning of every meeting so Copilot has full context.