Skip to main content
🦉
Message CenterMicrosoft 365 Updates
HomePermissionsTenant FinderPortfolio
🦉
M365 Message Centerby Cengiz YILMAZ

Track the latest updates, features, and announcements for Microsoft 365 services. Comprehensive archive of service updates and important changes.

Quick Links

HomePermissionsTenant FinderPortfolio

Connect

© 2026 M365 Message Center. Created with ❤️ by Cengiz YILMAZ

Data sourced from Microsoft 365 Message Center • Not affiliated with Microsoft

  1. Home
  2. /
  3. MC912707

Microsoft Teams: New policy for voice and face enrollment will default to "On" (configure now)

Plan for Change
Major Change

Message ID

MC912707
View in Admin Center

Roadmap ID

413708
View in Roadmap

Services

Microsoft Teams

Affected Platforms

DesktopMac

Summary

The new Microsoft Teams policy, effective mid-March 2025, will enable voice and face enrollment by default, offering enhanced meeting features. Admins should configure settings now using new PowerShell cmdlets and inform users of changes. Microsoft 365 Copilot license is required for full functionality.

Details

Updated April 4, 2025: We have updated the rollout timeline below. Thank you for your patience.

Updated February 6, 2025: Please verify that all previously set values remain unchanged and as intended.

A new csTeamsAIPolicy policy for Microsoft Teams (available now via Microsoft PowerShell and taking effect in mid-March 2025 (previously mid-February) will give IT admins more control over voice and face enrollment settings, allowing organizations to manage these features based on their needs. After rollout, voice and face profile enrollment will be enabled by default, and users can benefit from voice isolation, speaker recognition, and attribution in meeting rooms, resulting in smarter meeting recaps and enhanced functionality for Microsoft 365 Copilot in meetings. To access Copilot features, a Microsoft 365 Copilot license is required. This message applies to Teams for Windows desktop and Mac desktop.

NOTE: Microsoft doesn't use the voice and face profiles of users to train any models or for any other purposes other than providing the voice and face enrollment feature in Microsoft Teams.

This message is associated with Microsoft 365 Roadmap ID 413708.

When this will happen:

The new Microsoft PowerShell cmdlets are available now for admins to configure, to ensure a smooth transition.

General Availability (Worldwide, GCC): The new Microsoft PowerShell cmdlets are available now for preparation and to ensure a smooth transition. The policy takes effect starting in mid-March 2025 (previously mid-February) and is expected to be fully in effect by late April 2025 (previously late March).

How this will affect your organization:

Before this rollout, the current policy csTeamsMeetingPolicy has a single setting, EnrollUserOverride, that allows the administrator to enable or disable the enrollment of both face and voice profile of users.

After this rollout, the new csTeamsAIPolicy will replace the existing enrollment setting in csTeamsMeetingPolicy. The new csTeamsAIPolicy has two settings, EnrollFace and EnrollVoice, that will be set to Enabled by default.

What you need to do to prepare:

This rollout will happen automatically by the specified date. Review your current configuration to determine the impact for your organization. You may want to notify your admins about this change and update any relevant documentation.

If your organization prefers to disable voice and face enrollments, review and update your settings before mid-March 2025 (previously mid-January). To help you get started, review:

  • Set-CsTeamsAIPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn
  • Get-CsTeamsAIPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn

Learn more: Overview of voice and face enrollment - Microsoft Teams | Microsoft Learn

If your organization prefers to disable voice and face enrollments, review and update your settings before mid-March 2025 (previously mid-February).

Important: The EnrollUserOverride setting can be assigned globally, directly to users, or to groups in PowerShell.

Admins must ensure that changes are applied consistently across all these locations to avoid unintended configurations.

Timeline

📅
Published
Oct 17, 2024
Message published to Message Center
✏️
Updated
Apr 4, 2025
Message content updated
🏁
End Date
Jun 16, 2025
Message timeline ends

Tags

#Updated message#Feature update#User impact#Admin impact

Category

📋Plan for Change

Related Messages

Similar updates

MC912178

Microsoft Teams: Download Transcription and View RTMP-In 708 Captions for Town hall and Webinar

Oct 16, 2024
MC937925

Microsoft Teams: Additional report fields in the time clock export for improved reporting in the Shifts app

Nov 19, 2024
MC952889

Microsoft Teams admin center: Non-disruptive device operations for Microsoft Teams devices

Dec 10, 2024
MC1120871●

Important Update: Teams Meeting Join URL Validation

Jul 24, 2025
MC1069555●

Microsoft Teams: Send messages to attendees in the meeting lobby with Lobby chat

May 7, 2025