Copilot in Teams: Get control of your meeting data with Microsoft 365 Copilot

One of the most valuable experiences in Copilot for Microsoft 365 (Microsoft 365 Copilot) is using it with your Teams recordings and meeting data. But now we have AI assistants in our, do we, and do our colleagues, understand exactly how Copilot is using our data and tracking what we say to do its job?

In this video we explore what data Copilot uses, where it gets that data in different scenarios, the different approaches you can take to capturing meeting data to allow Copilot to work, and the steps you can take if you don't want Copilot interacting with the content of your meetings.

This is essential information to be able to ensure everyone feels safe when using Microsoft Teams with Copilot for Microsoft 365.

Links:

Chapters:
0:00 Introduction
1:12 Background on meeting recording
3:03 Using Copilot for Microsoft 365 with Teams meeting recordings
6:18 Using Copilot for Microsoft 365 in Teams meetings
12:48 Avoiding Copilot in your Teams meetings
15:29 A vital aspect of AI adoption

Apart from publicly accessible information, all user data or other related information shared in this video is created for demonstration purposes only. User accounts, passwords, or other data used as part of any demonstrations shown in this video have been created specifically for that purpose and are not any individual or company's private information or data.

[miamizeusofmontreal]

Great explanation. Thank you. Sharing with my collegauges.

[thomashohm]

Some things changed since the recording of this video: the meeting options of copilot changed (e.g. transcript + copilot). Also the requirement of transcription and recording in order to use copilot does not exist any more. Copilot was automatically available and processing the content once I started copilot. Seems like a dedicated "copilot recording layer" was implemented independent from the recording and transcription features without copilot. At least those are my experiences in our environment, maybe that is different in other environments.