Multitenant Intelligent Recap, Sharing with Copilot summary and talk to your Copilot

on
Here are three new features for Copilot, either already enabled in your tenant, or on it's way really soon. Intelligent Recap Access for Multi-tenant Organization Copilot will soon supports intelligent meeting recaps for B2B users in multi-tenant organizations, allowing access to summaries from the hosting tenant. This will make it much easier for meeting participants in large (multitenant) organizations. The update mentions multi tenant organizations and B2B organizations, but it is not clear on which scenarios will be supported. I'll keep an eye out for any information on this. The feature is Rolling out in July 2025 (Roadmap ID 488298 ). There is no configuration required, as the feature will be automatically enabled for all eligible users.  Sharing with Copilot summary We all know the flow of sharing documents from 365. The flow includes a popup box where we are asked to enter the address of the recipients and a big blank box to write "something" about the documen...

Copilot in Teams will be available for multitenant organizations (B2B)

on
Microsoft has announced that Copilot will be accessible to Business-to-Business (B2B) members within Multi-Tenant Organizations (MTO). This update allows users with B2B (shadow) identities to utilize Copilot during Teams meetings, provided they have a license in their host tenant. This will help organizations boost collaboration and productivity when working with different organizations.

There will be a new policy setting in the Teams Admin Center (TAC) enabling IT administrators to manage and control Copilot access specifically for B2B members.

According to the Roadmap ID 423474, we can expect this feature to be rolling to the first customers at the end of this month. Keep an eye out on the messeage center, and in the Teams Admin Center for these changes. 

I know a lot of users and customers are asking for this feature, but organizations should make sure such access is aligned with their own security and access policies. And users should be informed that when the feature is released, some organizations might not turn it on.