MC973519 - Microsoft Teams: Enable transcription policy by default

Coming soon for Microsoft Teams: We are updating our default policy settings for transcription for new tenants. Before this rollout, the setting was off by default. After this rollout, the setting will be on by default. This change applies to new global policies created for new tenants. Existing policies in the Teams admin center will not be changed; however, tenants that have not customized any part of their Teams meeting policy will be impacted.

• Tenants without customized policies: The new default settings will apply, and these tenants will be impacted by this change.
• Tenants with customized policies: Policies for user-level assignments or group-level assignments will remain unchanged and unaffected.

This change is designed to streamline the adoption of transcription and enhance the use of all AI features. This change will align transcription with the default policy for recording, which is also enabled by default in Teams admin center. This message applies to Teams for Windows desktop and Teams for Mac desktop.

This message is associated with Microsoft 365 Roadmap ID 468282.

When this will happen:

General Availability (Worldwide): We will begin rolling out early February 2025 and expect to complete by mid-February 2025.

How this will affect your organization:

After this rollout, transcription services will be more accessible to users, allowing them to turn on and use transcription as needed during meetings. Transcription will not be automatically activated for every meeting.

For new tenants, transcription will be enabled by default when admins set up their global policies. New tenants will automatically have the transcription policy turned on when they start. Existing tenants without a global policy will also have the policy turned on by default.

Transcription policy on by default in Teams admin center. Admins can turn off the policy if needed:

What you need to do to prepare:

This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation.

Before rollout, we will update this post with revised documentation.