Copilot in Outlook: Meeting Preparation Is About to Get Smarter

on
Currently, the “Prepare for meetings with Copilot” feature requires at least three participants. Starting mid-October, this is changing. Copilot will soon support all meetings, including 1:1s. The rollout will begin in mid-October and is expected to complete by November 2025 according to the message center. With this update, you’ll also see new real-time insights in the Outlook meeting event form, summarizing relevant context, tasks, documents, and other resources. Plus, you’ll be able to chat with Copilot to confirm action items or better understand meeting goals. The more context Copilot has, the better it works. Meeting series with related emails, shared documents, Teams chats, and previous Copilot transcriptions deliver the richest experience. If your organization limits Copilot to in-meeting use only and deletes content afterward, you’ll miss out on much of this value. Here is a relevant " how to " guide for users.

Meeting policies in Teams have been updated in the Teams Admin Center

on
Microsoft released a lot of cool features last week, an I am sure I will comment them as the get closer to General Availability. But in this post, I will focus on some of the features that has surfaced GA just recently, and discuss if there are things the organization could or should look into.

Meeting Policy Settings
Already back in May, the option to create meetings where "only me" could bypass the lobby became available. But the organization wide setting is still set to "allow all to bypass". This is still true, but now there is a meeting policy which organizations can deploy to control this for all. 
To control this, look for the "Automatically admit people" in the teams admin portal. Select what best matches your security policy, but make sure to communicate this to the users as they probably are used to the allow all.
You can also control who gets to be a presenter through the same policy now. This is nice if you want to avoid guests to take control unless explicitly granted. My suggestion is to allow user override in most cases.