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

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

Message ID: MC1387573 (Updated)

Updated June 22, 2026: We have updated the timeline. 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]

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

[Impact on Your Organization]

Who is affected

  • Microsoft 365 tenant admins managing Teams apps and experiences

Platforms/Services

  • Teams admin center (web)
  • Microsoft Teams

What will happen

  • A new admin experience will be available at: Teams admin center > Teams apps > Built-in Teams agents

    43a41bb56b3ecf0d9d56418bca308209f23606de 

  • Built-in agents will be managed separately from traditional apps and agents.
  • Admins will be able to:
    • Allow or block individual built-in agents
    • Assign access to specific users or groups
    • Configure agent-specific settings
  • Built-in Teams agents will no longer be governed by the Org-wide app setting for Microsoft apps.
  • Existing agent-level configurations will remain unchanged after rollout.
  • For users who already have the app installed, we will carry those installs forward and make the app available to those same users.
  • 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.
  • 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:

  • Review your current org-wide app settings for Microsoft apps, as they will no longer apply to built-in Teams agents.
  • Review and update agent-level permissions and configurations as needed in the new admin experience.
  • Review install settings and audience for this change.
  • Inform your admins and helpdesk teams about the new management surface and controls in the Teams admin center.
  • Update internal documentation that references Teams app governance.

Learn more:

[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

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

Latest Posts

Pass It On
Leave a Comment

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply