Two Major Admin Control Updates for Copilot and Agent Management

At Ignite Microsoft showcased and talked about two new admin controls for Copilot and Agents. These controls drew a significant amount of attention for their potential to simplify management and strengthen governance across Copilot experiences and AI agents. These capabilities are now emerging in preview, offering administrators early access to improved insights, expanded control surfaces, and more secure operational foundations. Copilot Overview Page Refresh in Microsoft 365 Admin Center First off is the redesigned landing page for Copilot in the Microsoft 365 Admin Center (MAC), giving admins an at-a-glance view of the Copilot journey across Chat, Agents, and M365 Copilot. This update  centralizes critical insights and success metrics, helping organizations accelerate adoption and maintain security posture. The refreshed page introduces success metrics such as Chat active users, assisted hours for licensed users, and satisfaction rate. Each Copilot pillar now includes multi‑...

Sensitivity labels in Teams

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.