← Back to blog
Microsoft 365

Teams splits the Copilot meeting policy: what it means for your PowerShell scripts and meeting governance

By Zarioh Digital Solutions4 min read
Share

Microsoft is splitting the Teams Copilot meeting policy into two separate settings, MeetingAI and TranscriptionWithMeetingAI, and the rollout has just been pushed back to December 2026 and January 2027. What changes in the admin center, what happens to existing PowerShell scripts, and which steps should you take now?

Until recently, a single setting in Microsoft Teams, the Copilot meeting policy, controlled both whether AI features were available in a meeting and whether transcription ran automatically alongside them. Microsoft is now splitting that one switch into two separate policies: MeetingAI and TranscriptionWithMeetingAI. For IT administrators who manage Teams meeting policies through PowerShell or their own automation, this is more than a name change.

This is a Dutch Microsoft 365 administration topic, relevant to any organisation running Teams, not a change specific to Dutch regulation. The update has been in the Microsoft 365 Message Center since early November and was recently revised: the rollout originally planned for mid November has moved to early December 2026 for the phased release and early January 2027 for worldwide availability. For organisations already updating scripts or documentation, that is extra time to prepare.

What exactly changes in the Teams admin center?

The existing Copilot meeting policy splits into two settings. MeetingAI determines whether Copilot, Facilitator, Intelligent Recap and other AI features are available in a meeting. TranscriptionWithMeetingAI determines whether transcription starts automatically once those AI features are turned on. The existing Transcription policy remains alongside these two and still governs whether transcription itself is allowed, independent of AI.

The meeting options themselves also change. The Allow Copilot and Facilitator toggle is replaced by Who can manage AI, with a new addition, Who can use AI, for more precise control over who can switch on AI features during the meeting. If you disable MeetingAI organisation wide, that setting automatically jumps to nobody, and transcription is switched off at the same time.

Why Microsoft is making this change now

The old, combined policy made it impossible to allow AI features without also enabling transcription, or the other way around. For organisations with strict rules around recorded conversations, think of performance reviews, customer contracts or works council meetings, that was an unnecessary limitation. With the two separate switches, you can, for example, allow Intelligent Recap in regular team meetings while excluding both transcription and AI for a specific group of sensitive meetings.

What happens to existing configurations?

Microsoft runs a one time automatic conversion itself, so your organisation's current, effective behaviour stays intact. You do not need to recreate policies to avoid breaking anything. What does change is the PowerShell syntax: where you currently reference the Copilot policy, you will use MeetingAI and TranscriptionWithMeetingAI going forward. Once the new controls are active, the old Copilot policy can no longer be updated directly.

Four steps to prepare now

Run through a short checklist before the December rollout. Search your scripts, Intune configurations and governance tools for references to the Copilot meeting policy and replace them with the new names ahead of time. Update internal documentation and runbooks that still point to the old setting. Inform the colleagues who manage Teams policy, so nobody is caught off guard by two switches where there used to be one. And after the migration, verify that the automatically converted settings actually match what your organisation intended.

If your organisation does not use PowerShell or custom scripts for Teams meeting policy, there is little to do right now. The conversion happens entirely in the background, and you will mainly notice the two new names in the admin center.

Default meeting templates: applying policy without the organiser having to know

Alongside this policy change, Microsoft is working on Default Meeting Templates, due to be marked generally available in late November. As an administrator, this lets you apply meeting settings, including security settings such as recording and copy restrictions, by default as soon as someone schedules a Teams meeting through Outlook or the calendar. The organiser no longer needs to know or manually enable those settings.

The feature is tied to a license, though: for now, only organisers with an assigned Teams Premium license can use default templates. For organisations considering a broader Teams Premium rollout, this is a reason to have that conversation now rather than after the feature goes live.

The point of this update is that Microsoft is adding more granularity to Teams governance right as AI in meetings becomes the norm rather than the exception. Preparing scripts and documentation now avoids surprises in December. Want help setting up Teams meeting policy, rolling out Teams Premium, or a broader Microsoft 365 governance approach? Contact Zarioh.

Z

Zarioh Digital Solutions

IT specialists from Utrecht, the Netherlands. We help businesses with Microsoft 365, AI agents, hosting and telephony, and share what we learn in practice. Follow us on LinkedIn

Related articles

← Back to all articles
Share