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

Message Center

This announcement expired on Jun 16, 2025 and is no longer active in Message Center.

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.

Last Updated

Apr 4, 2025

Published Oct 17, 2024

View version history

Service

Microsoft Teams

Tag

Major change
Updated message
Feature update
User impact
Admin impact

Platforms

Desktop
Mac

More information

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:

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.

Version history

13 versions tracked

Updated 12 times since Oct 17, 2024. Microsoft Message Center only ever shows the current version; this archive preserves the history.

Compare any two versions

From
To
  1. Apr 4, 2025 · 09:01 PMLatest · v13

    Changed: No tracked field changed

  2. Apr 4, 2025 · 09:01 PMv12

    Changed: No tracked field changed

  3. Apr 4, 2025 · 09:01 PMv11

    Changed: Body, End date

  4. Feb 6, 2025 · 08:16 PMv10

    Changed: Body

  5. Feb 6, 2025 · 08:05 PMv9

    Changed: Body

  6. Feb 4, 2025 · 10:56 PMv8

    Changed: Body

  7. Jan 31, 2025 · 06:11 PMv7

    Changed: End date

  8. Jan 31, 2025 · 04:51 PMv6

    Changed: Body

  9. Dec 20, 2024 · 11:19 PMv5

    Changed: Body

  10. Nov 28, 2024 · 12:37 AMv4

    Changed: Body, End date

  11. Oct 25, 2024 · 09:40 PMv3

    Changed: Body, Tags

  12. Oct 21, 2024 · 06:58 PMv2

    Changed: No tracked field changed

  13. Oct 17, 2024 · 11:34 PMOriginal · v1

    Changed: Initial version