Announcement ID | MC912707 | Published Date | 10-17-2024 | |
Service | Microsoft Teams | Last Updated | 12-20-2024 | |
Category | Plan for change | Expiration Date | 03-24-2025 | |
Roadmap ID | 413708 | Action Required by Date | ||
Tags | Major update, Admin impact, Feature update, User impact |
Summary |
---|
The new Microsoft Teams policy, effective mid-February 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. |
More Information |
---|
A new 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. 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-February 2025 (previously early February) and is expected to be fully in effect by late February 2025 (previously mid-February). How this will affect your organization:Before this rollout, the current policy After this rollout, the new 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-January 2025. To help you get started, review:
If your organization prefers to disable voice and face enrollments, review and update your settings before mid-February 2025. 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.
|