Smarter AI Workflows in Microsoft 365 Copilot has been announced on the roadmap: Tools, Source Control, and Agents

on
Tool Selection in Copilot Chat: Making AI Features More Discoverable One of the most helpful updates in my opinion, is the introduction of the new “Tools” button in Copilot Chat. Users will soon see this button directly in the chat prompt box, offering quick access to a curated set of Copilot features such as Researcher, Analyst, Pages, and image generation.  This will hopefully help users with an easier path to the different tools at their disposal. The feature is turned on by default, with no admin configuration required. This feature is associated with Roadmap ID 497298 , and is expected to roll out in the last weeks of August. Source Control in Copilot Chat: Scoped Responses for Greater Relevance Another user-friendly enhancement coming up, is the ability to scope Copilot Chat responses to specific content sources. This feature will allow users to define exactly which documents, folders, or repositories Copilot should reference when generating responses. It’s a subtle but power...

Sensitivity labels in Teams

on
A new feature for Sensitivity labels in Azure AD will soon be available to Teams, and can really ensure guests are not invited accidentally into a team with internal or sensitive information.

The feature behind this is currently in preview and can be found described on this page. After the preview has been enabled, a new option appears when labels are created (I have not discovered a way to update existing labels, but I'm hoping this will be a possibility once the feature goes into GA).

By not selecting the highlighted option, it suddenly becomes "impossible" to invite guests to the Team, the site or the group in question.

Please note the current defaults on the image was to not to allow any guests, and the section on managed devices was to block all non-compliant. Be careful not to set policies that could possibly block users from doing their job.

Once the label has been created, it can must be published before group creators have the labels available to them. Existing groups and teams can also have this label added once it is available.

This addition, described as road-map item 57275, is a most welcomed one for my customers who are concerned about the accidental addition of guests into groups or teams where they have sensitive information stored.

The feature requires Azure AD P1 licenses. It is already rolling out, and should be completed by the end of this year according to a message in the O365 admin portal last week.