Four Microsoft 365 Copilot Features That Will Make Your Workflow Easier

on
Microsoft has announced four Copilot updates, some already live or in preview, others rolling out soon, that are designed to simplify tasks, improve control, and boost productivity. These enhancements include smarter content referencing, flexible reasoning modes, customizable response scoping, and integrated meeting scheduling. Timelines may change, so keep an eye on official updates.  Copilot Chat Enhancements: Reference Files and Emails Easily Copilot Chat for users with a Microsoft 365 Copilot license is being enhanced by introducing quick access to emails directly in prompts. By typing “/” in the prompt box, users can search and reference relevant content without manual uploads, improving prompt quality and Copilot responses. Suggested prompts beneath the input box will also include relevant files or emails for faster starts. This capability will surely reduce friction and ensure responses are grounded in the right context (Also now known as ContextIQ). This update is associate...

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.