(this post has been re-published on the Microsoft TechCommunity Blog here)
You probably know by now that Microsoft Teams Premium creates informative Recap notes from your recorded meetings (known as Intelligent Recap). Here's an example:
When I demo this feature, I like to use the fictitious information in my demo tenant. However, often the best examples of these kinds of meetings come from our actual real-life meetings, since there's multiple people speaking about real topics, which in turn makes for a much better summary.
So am I forced to use my real-world meetings for all my demos? No. #CopilotCanDoIt :)
- Ask Copilot to create for you a fictitious script of two people talking about a project. Tell it how many minutes long you want it to be. In my case, it created my 3-minute long script with no problem, and I was able to paste it into Microsoft Word:
- Schedule a new meeting in your demo tenant. Invite a 2nd user that you have access to.
- Use a device to join the meeting as the demo user. Use another device to join the meeting as the 2nd user. This could be a laptop and cell phone [with Teams Mobile installed].
- Make sure both devices can hear your 3rd device that will be reading the script - use the Read Aloud feature in Microsoft Word (Copilot can also read it aloud if you prefer).
- Create a meeting recording of the auto-reading of the script using the microphones of each device. The tricky part - hitting the correct mute & unmute buttons at the right time on each device for each speaking user.
When you're done, you've got a nice Recap like the one shown above.
If you're also licensed for Copilot for Microsoft 365 (which is integrated into Teams and other M365 apps), you can also ask additional questions about the meeting. For instance, I was interested in the tone or sentiment of the meeting:
I knew Copilot would find it, because I purposely added some worried verbiage to the script. :)
Now I've got a completely fictitious meeting with recap ready to demo, without any worry that I might be showing content from a real-world meeting that might not be appropriate for sharing!
No comments:
Post a Comment