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

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

Coming soonUpdated 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 Business Chat (BizChat): Users will be ablein 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 CIQ to ground their Copilot prompts with third-party data from their Microsoft Graph Connectors.

Context IQ (CIQ) is a setthe voice and face profiles of AI capabilities from Microsoft that allows users to search for, select,train any models or for any other purposes other than providing the voice and insert relevant enterprise or personal data directly into their prompts or conversations. This capability helps users to “ground” or anchor their promptsface enrollment feature in specific, contextually relevant data, making responses more accurate, specific, and useful.Microsoft Teams.

This message is associated with Microsoft 365 Roadmap ID 413111413708.

When this will happen:

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

General Availability (Worldwide)(Worldwide, GCC): We will begin rolling out late 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 late mid-February) and expectis expected to completebe fully in effect by earlylate April 2025 (previously earlylate March).

How this will affect your organization:

No impact forBefore this rollout, the tenant admin. End userscurrent 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 see areplace the existing enrollment setting in csTeamsMeetingPolicy. The new Other tab in CIQ to add their third-party data from any MS Graph ConnectorscsTeamsAIPolicy has two settings, EnrollFace and EnrollVoice, that are enabled.

This change will be available set to Enabled by default.

What you need to do to prepare:

This rollout will happen automatically by the specified date with no admin action required before or after the rollout.date. Review your current configuration to determine the impact for your organization. You may want to notify your usersadmins 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: Using Context IQ to refer to specific files, people, and more in Microsoft 365 Copilot - Microsoft Support (willOverview 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 updated before rollout)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.