Posted inMicrosoft Teams

MC1387573: Microsoft Teams Adds Centralized Governance for Built-In Agents in Teams Admin Center

4 minutesPosted inMicrosoft Teams
MWPRO IMPACT SCORE
OPERATIONAL IMPACT
52
0 25 50 75 100
HIGH IMPACT • REVIEW RECOMMENDED
Recommended Action:
Review the update and plan any required actions before rollout.
▶ What is MWPro Impact Score? Watch our 60‑second explainer

Primary Audience

Microsoft 365 AdminsTeams AdminsSecurity TeamsCompliance TeamsIT ManagersService Owners
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
The update introduces a dedicated governance interface in Teams admin centre for built-in agents like Copilot, requiring admins to review and adjust agent-level permissions and update documentation. Current org-wide Microsoft app settings may no longer apply, so configuration checks and communication to admin teams are needed. User impact is minor as availability and UI remain largely unchanged, but governance changes and compliance controls require planning and possible policy updates.
65
🛡️ Admin Impact
HIGH
20
👥 User Impact
LOW
55
⚡ Urgency
HIGH
50
🔧 Effort
HIGH
ℹ️ WHAT YOU NEED TO KNOW
📌

AT A GLANCE

Teams admin centre now has a dedicated section to manage built-in Teams agents like Copilot and Facilitator. Org-wide app settings no longer cover these agents.
👥

END USERS

No major end-user change expected.
🛡️

IT ADMINS

Review agent-level settings and permissions, update internal documentation, and inform support teams about new governance controls.
📅

ROLLOUT TIMELINE

Available:
Now

📢 Official Microsoft Message Center Announcement

(Updated) Microsoft Teams: Governance for built-in agents in the Teams admin center
Message ID: MC1387573 (Updated)

Updated July 20, 2026: We have updated the content. Thank you for your patience.

[What and Why]

We are introducing a new governance experience in the Teams admin center that enables admins to manage built-in Teams agents in a dedicated, centralized location. These built-in agents, including Channel Agent, Facilitator and Copilot Agent in Teams are integrated directly into core Teams experiences and do not require installation from the app store.

This update improves administrative clarity and control by separating governance for built-in agents from traditional apps and bringing them into a single, dedicated management surface. This enables more precise policy management and supports enterprise-ready AI governance at scale.

This message is associated with Microsoft 365 Roadmap ID 564766.

[Rollout Schedule]

  1. General Availability (Worldwide, GCC): Early July 2026 through mid-July 2026

[Impact on Your Organization]

Who is affected

  1. Microsoft 365 tenant admins managing Teams apps and experiences

Platforms/Services

  1. Teams admin center (web)
  2. Microsoft Teams

What will happen

  1. A new admin experience will be available at: Teams admin center > Teams apps > Built-in Teams agents
  2. 43a41bb56b3ecf0d9d56418bca308209f23606de
  3. Built-in agents will be managed separately from traditional apps and agents.
  4. Admins will be able to:
  5. Allow or block individual built-in agents
  6. Assign access to specific users or groups
  7. Configure agent-specific settings
  8. Built-in Teams agents will no longer be governed by the Org-wide app setting for Microsoft apps.
  9. Existing agent-level configurations will remain unchanged after rollout. However, if no agent-level configuration is set and availability is currently controlled by the org-wide Microsoft apps setting, that org-wide setting will no longer apply to built-in Teams agents.
  10. For users who already have the app installed, we will carry those installs forward and make the app available to those same users.
  11. Going forward, install action will no longer be available in the admin center UX for these built-in agents, as they do not require separate installation.
  12. The feature will be available by default as part of the updated admin experience.

[Action Required / Recommendations]

No action is required before rollout.

We recommend that you:

  1. Review your current org-wide app settings for Microsoft apps. If the org-wide Microsoft apps setting is turned off and no agent-level configuration exists for these agents, their availability will change to allowed after rollout.
  2. Review and update agent-level permissions and configurations as needed in the new admin experience.
  3. Review install settings and audience for this change.
  4. Inform your admins and helpdesk teams about the new management surface and controls in the Teams admin center.
  5. Update internal documentation that references Teams app governance.

Learn more:

  1. Facilitator in Microsoft Teams meetings | Microsoft Support
  2. Get started with Channel Agent for Teams channels | Microsoft Support
  3. How to use Microsoft 365 Copilot in Teams group chats | Microsoft Support

[Compliance considerations]

QuestionAnswer
Does the change alter how admins can monitor, report on, or demonstrate compliance activities?Yes. Admins gain a new, dedicated governance surface for built-in Teams agents, improving visibility and management granularity.
Does the change include an admin control and can it be controlled through Entra ID group membership?Yes. Admins can assign access to specific users or groups, implying Entra ID group-based control.
Does the change allow a user to enable and disable the feature themselves?Yes. Admins can allow or block individual agents, effectively enabling/disabling availability.

Source: Microsoft Message Center • Analysed by MWPro

<<< [MC1387573] Archive
Tooltip: View earlier revisions of this post

Share This Update
Tags: