Teams Copilot Meeting Controls: Organizer AI Access and Simpler Admin Policies Due November 2026

The entry lists the feature as In development, with general availability planned for November 2026. It covers Teams on Desktop and Mac, in the Worldwide (Standard Multi-Tenant) cloud, through the General Availability ring.

Microsoft's roadmap page carries its usual caveat. Dates and descriptions are estimates and subject to change, and entries can disappear when a feature ships, is cancelled, or is postponed. Read November as a target, not a promise.

What the roadmap entry says, and what it leaves out​

The description is short and broad. It confirms two things:

• Organizer-level control over who can enable and access AI in a meeting.
• A simpler admin policy model that covers both the live meeting and what happens after it.

It does not give:

• New policy names or values
• Default settings or which policy wins when two conflict
• Whether existing policy assignments will migrate automatically
• Licensing changes
• Changes to audit, retention, or Purview behavior
• Support for web or mobile clients
• Availability in GCC, GCC High, or DoD

Until Microsoft publishes Learn documentation or a Message Center post with details, anyone who claims to know the exact toggles is guessing.

Section summary: The direction is clear: more organizer control and simpler admin policy. The details aren't public yet.

Why "simpler" matters: today's policy model​

To see why Microsoft wants to simplify things, look at the current setup. Copilot behavior in Teams meetings is set in the meeting policy. Microsoft's Learn documentation says admins use the -Copilot parameter within the PowerShell CsTeamsMeetingPolicy cmdlet. That setting also depends on a separate one. Admins manage transcription through the Recording & Transcription section in the Teams admin center or the -AllowTranscription parameter, and Microsoft notes that this setting's value affects how, or if, Copilot works for your users.

Here is how the four current Copilot policy values map out, based on Microsoft's documentation:

The organizer's own options add another layer:

• During and after the meeting: once someone starts transcription, licensed users can use Copilot live and afterward.
• Only during the meeting: Copilot uses temporary speech-to-text data that isn't saved after the meeting ends.
• Off: Copilot is unavailable, and recording and transcription are turned off too.

The interactions can catch people out. Microsoft says that when transcription policy is on and the organizer picks "Only during the meeting," licensed users can select the Copilot button for use only during this meeting with temporary speech-to-text data, and to use Copilot during, and after the meeting, these users can start a transcript.

The documentation doesn't fully agree with itself either. The Learn page describes four values. The PowerShell reference for New-CsTeamsMeetingPolicy says the Copilot setting allows the admin to choose whether Copilot will be enabled with a persisted transcript or a non-persisted transcript, lists only Enabled and EnabledWithTranscript as possible values, and gives EnabledWithTranscript as the default. A Teams Rooms admin guide uses yet another label: Select On or On only with retained transcript from the dropdown for the Copilot setting. When three official pages describe one setting three different ways, a simpler model is overdue.

Section summary: Today, Copilot behavior comes from a policy value, a transcription policy, and an organizer choice, and the documentation doesn't use consistent terms. That's the problem roadmap 577399 says it will address.

Microsoft has changed these defaults before​

This isn't the first time Microsoft has changed Copilot meeting defaults, which is a good reason to plan carefully this time.

In September 2025, Office 365 for IT Pros reported that Microsoft would change the value of the Copilot setting in the Teams meeting policy from EnabledWithTranscript to Enabled. It explained the difference between the two transcript types: a persisted transcript is one that's saved to OneDrive for Business; a non-persisted transcript is one that Teams generates internally and deletes when the meeting ends.

Later coverage of Message Center post MC1139493 on Modern Workspace Pro said the affected tenants were those whose meeting policy was created or modified before the Copilot without transcription policy option was introduced (June 2024). In those tenants, Copilot and Facilitator will no longer automatically start transcription, and users must manually enable transcription to use post-meeting Copilot or Facilitator queries.

The lesson: a default change can quietly change what your users get after a meeting. Some organizations found out when people asked why their recap had no transcript. If November's "simpler policy model" consolidates or remaps values, expect a similar migration question.

Compliance: "only during" doesn't mean nothing is kept​

The roadmap mentions compliance and governance, so it's worth correcting one common assumption. The "Only during the meeting" mode doesn't save the speech-to-text data. But Microsoft's current documentation says that, depending on your Purview retention policies, Copilot prompts and responses during meetings might still be retained for compliance purposes, even with recording and transcription off. Microsoft says this applies to the Commercial cloud, not GCC or DoD.

There are other existing limits too. Copilot in Teams meetings isn't available in end-to-end encrypted meetings, and Microsoft says it isn't currently available in GCC High. In events optimized for large audiences, only organizers, co-organizers, and presenters can use Copilot. Any new organizer controls will sit on top of these existing rules about roles and licenses. The roadmap doesn't say whether any of them will change.

Post-meeting AI is a large area​

The roadmap explicitly covers "post-meeting experiences," which matters because that's where much of the AI output ends up. Intelligent recap currently provides AI meeting notes, recommended tasks, personalized and speaker timeline markers, chapters, and, in some cases, audio and video recaps. Microsoft's documentation says audio recaps are stored in the user's OneDrive for 60 days. Video recap data is stored with the original recording in OneDrive or SharePoint.

The roadmap doesn't say which of these features the new policy model will control. Still, a single policy covering both the live meeting and recap would be a real improvement over today's mix of transcription, recording, and Copilot settings. As general industry practice, admins should also review transcript access, sharing permissions, and sensitivity labels alongside any Copilot policy change.

Section summary: Governance needs to cover recaps, retained prompts, and stored transcripts, not just the Copilot button in the meeting.

What admins can do before November​

You don't need to wait for the feature to get ready. These steps use documented commands and settings only:

• List your current policies. Connect with Connect-MicrosoftTeams and run Get-CsTeamsMeetingPolicy to record each policy's Copilot and AllowTranscription values. Office 365 for IT Pros has published a one-line filter for finding policies set to Enabled.
• Record the intent behind each policy. For each one, decide whether it's meant to require transcripts (EnabledWithTranscript), allow live-only use (Enabled), default to saved transcripts (EnabledWithTranscriptDefaultOn), or default to off (Disabled). If values get remapped, you'll need that intent to check the results.
• Check meeting templates. Copilot can be added to Teams meeting templates. Look for templates that may conflict with a future organizer-level control.
• Review Purview retention. Confirm what your retention policies capture for Copilot interactions, especially if you rely on live-only mode for privacy.
• Check your clouds and clients. The roadmap entry lists only Worldwide multi-tenant and Desktop/Mac. If you're in a sovereign cloud or have many mobile and web users, don't plan around November.
• Watch Message Center. Implementation details, and any changes to defaults, will most likely appear there first.

Analysis​

As I see it, this roadmap item is Microsoft responding to admins who have had to manage Copilot through settings that depend on each other in non-obvious ways. Letting organizers decide who can enable AI fits how sensitive meetings really work. A board meeting, an HR investigation, and a product stand-up shouldn't share one tenant-wide default.

There's a reasonable counterpoint. Giving organizers more power also gives admins less central control. A compliance team that wants transcripts in every meeting, which is what EnabledWithTranscript enforces today, will want to know whether admin enforcement still overrides organizer choices. The roadmap's wording, "more predictable administration," suggests it will, but Microsoft hasn't confirmed it.

My view: this is likely good news, but you can't act on it yet. Do your policy inventory now and wait for Microsoft's documentation before changing anything.

Update: Additional details (October 23, 2026)​

Microsoft’s roadmap entry for ID 577399 now lists Android, iOS, and Web alongside Desktop and Mac as supported platforms. The feature remains marked “In development,” with general availability targeted for November 2026 in Worldwide Standard Multi-Tenant tenants.

That broadens the stated client scope beyond the desktop and Mac availability previously listed. Microsoft still has not published policy names, defaults, migration behavior, or sovereign-cloud availability.

Update: Teams AI meeting controls now targeted for December (November 4, 2026)​

Microsoft has revised roadmap ID 577399’s general-availability target from November 2026 to December 2026. The feature remains listed as “In development” for Worldwide Standard Multi-Tenant tenants, so the delay is a schedule change rather than confirmation that the controls have begun rolling out.

The roadmap entry also now lists both General Availability and Targeted Release rings. That suggests some tenants or users could receive the feature through Targeted Release before broader availability, although Microsoft has not provided eligibility criteria, a rollout sequence, or an exact start date.

The stated platform coverage remains Android, Desktop, iOS, Mac, and Web. Microsoft still has not documented the new policy names, how existing Copilot and transcription settings will map to the simpler model, or whether tenant-wide compliance settings can override an organizer’s choices. Admins planning around a November deployment should shift their readiness and validation plans to December, while continuing to watch Message Center for implementation details.