New Copilot Updates for Outlook Scheduling, Word Agent Mode, and PowerPoint Agent Mode

Microsoft has announced Copilot enhancements across Outlook, Word, and PowerPoint that improve scheduling, document creation, and presentation building. Here is a summary of some of the features I think can come in handy. Be aware that timelines may change as deployments progress, some of these have already been pushed back a couple of months. All of the following features requires a Microsoft 365 Copilot license, and will be enabled by default for users with such a license. Automatic rescheduling of 1:1 meetings Automatic rescheduling of flexible 1:1 meetings and personal events in Outlook with Copilot, helping users resolve conflicts with minimal manual effort is coming soon. This will be in addition to the already released auto rescheduling of meeting rooms. Originally this feature was planned for mid‑November 2025 to mid‑January 2026, but is now hopefully coming between to mid‑February 2026 and the end of February 2026. A Microsoft Copilot license is required to use the capability....

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

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.