The roadmap lists the feature as In development, with general availability estimated for November 2026. That date is a target, not a promise.
What Microsoft is promising
The roadmap entry makes these points:
- What it does: Admins can set default meeting templates so the organization's preferred settings are applied automatically when users schedule Teams meetings.
- Where it applies: Meetings scheduled through Outlook or the Teams calendar.
- Why: To apply meeting settings, including protection settings, at scale, and to cut down on organizers configuring meeting options by hand.
- Licensing: Only organizers with an assigned Teams Premium license can use default meeting templates.
- Platforms: Desktop, Mac and Web.
- Cloud: Worldwide (Standard Multi-Tenant) only.
- Release ring: General Availability, with an estimated date of November 2026.
Microsoft's roadmap page warns that all information on it is subject to change. Entries are also removed once a feature ships, or if it is cancelled or postponed. Plan around the November estimate, but don't promise it to your CISO in writing.
Section summary: This is a roadmap item, not a shipped feature. It promises automatic, organization-wide meeting defaults in Teams and Outlook scheduling, but only for organizers with Teams Premium licenses in the commercial worldwide cloud.
Why this is different from the templates you already have
Teams has had meeting templates for a while, and the word "default" is already in use, which could confuse people. Microsoft's documentation already calls the Virtual appointment template a default meeting template in Microsoft Teams that your users can use to schedule virtual appointments with external guests. Microsoft's documentation lists the built-in templates that are read-only and can't be updated, including the Controlled-content meeting, Virtual appointment and Webinar templates.
Today's system is opt-in. Templates sit in a picker, and an organizer has to choose one. A Microsoft Q&A thread describes what Teams Premium users should see: a drop-down next to "New Event" in the calendar showing default templates (Webinar, Town hall, Virtual appointment) and custom templates made available via policy. If nobody opens that drop-down, the template does nothing.
Roadmap item 576609 targets that gap. The template would be applied when the meeting is scheduled, so organizers don't have to remember to pick it. It's a bit like the difference between leaving a seatbelt in the car and having the car buckle you in.
Current admin controls in Microsoft Learn:
| Capability | What Microsoft documents today |
|---|---|
| Custom templates | Teams Premium admins can create up to 50 custom templates in Teams admin center > Meetings > Meeting templates |
| Per-option control | Each option has a default value, a visibility setting and a lock status. Locked options can't be changed by organizers |
| Template visibility | By default, the Global policy allows users to see and use all meeting templates, including the Virtual appointment template and any custom templates that you created. |
| Targeting | To assign specific custom meeting templates to specific users, you must create a separate meeting template policy |
| Propagation | Microsoft says a new template can take up to 24 hours to appear for users |
Section summary: Today's templates have to be picked by the organizer. The new feature would apply organizational defaults automatically at scheduling time.
What settings could be covered
The roadmap entry mentions "protection settings" but doesn't list which settings default templates will support. The existing custom template system gives a good idea of what's possible. Microsoft's admin documentation lists template options in five groups:
- Security: sensitivity label, lobby bypass rules, dial-in lobby bypass, end-to-end encryption, watermarks for screen share and video, sensitive content detection during screen sharing, and restrictions on copying or forwarding chat, captions and transcripts.
- Audio & video: whether attendees can use their microphones and cameras.
- Recording & transcription: automatic recording, who can record, and Copilot availability.
- Roles: announcements when dial-in callers join or leave.
- Meeting engagement: meeting chat, reactions, Q&A, and "Manage what attendees see."
Microsoft Learn training material shows how admins might use these controls, for example using a stricter default for who can bypass the lobby, but allowing the meeting organizer to change the setting if needed. That kind of policy suits an automatic default well: secure out of the box, but not so strict that people find workarounds.
Treat this as a guide, not a confirmed feature list. Microsoft hasn't said that every existing template option will work in a default template.
Interactions to watch
Some existing behaviors will probably matter once default templates arrive. These points come from current documentation. How the new feature handles them is still unknown.
- Sensitivity labels win. Microsoft's training material says labels can control end-to-end encryption, meeting chat, automatic recording, lobby bypass, who can present, who can record and watermarks, and if any of these settings are configured in the label, they will override these settings in the template. A default template won't overrule your Purview labeling strategy.
- Encryption has trade-offs. Microsoft says recording and transcription don't work when end-to-end encryption is on. If your default turns on E2EE, you've also turned off recaps for meetings that use it.
- Template edits apply to existing meetings. Under current behavior, changing an existing template affects new meetings and meetings already scheduled with it. If that carries over to default templates, one edit could change a lot of calendars at once.
- Licensing gaps. Because only Teams Premium-licensed organizers can use default templates, meetings scheduled by unlicensed colleagues won't get your defaults. In a partly licensed tenant, coverage will be uneven.
Open questions Microsoft hasn't answered
The roadmap description leaves several gaps that admins will want filled before November:
- Can organizers override the defaults, or do locks apply the same way they do in custom templates?
- Can admins target different defaults to different groups, or is it one default per tenant?
- How do default templates interact with existing meeting template policies and meeting policies?
- Which Outlook builds are supported? The roadmap lists Desktop, Mac and Web but no minimum versions, and mobile isn't mentioned.
- When will GCC and sovereign clouds get it? Only the worldwide multi-tenant cloud is listed.
Until Microsoft publishes documentation, assume none of these are settled.
How to prepare now
You can't configure default templates yet, but you can get ready:
- Audit your Teams Premium licensing. Find out which organizers actually have a license assigned. They are the only ones who will get the new defaults.
- Build and test a candidate template today. In the Teams admin center, go to Meetings > Meeting templates, select Add, set your options, lock or hide what you need, and save. Allow up to 24 hours for it to appear for users.
- Review meeting template policies. Under Meetings > Meeting templates policies, check which templates each group can see. The Global (Org-wide default) policy shows everything unless you've changed it.
- Check your sensitivity labels. Labels override template settings, so make sure your label design and your planned defaults don't conflict.
- Think through the E2EE versus recording trade-off before you make encryption a default.
- Watch roadmap ID 576609 and Message Center for changes to timing or scope.
The bottom line
Default meeting templates fix the main weakness of today's Teams meeting templates: they only work when an organizer remembers to pick one. If organizational defaults are applied automatically when meetings are scheduled in Teams or Outlook, Teams Premium tenants could get consistent protection settings without relying on users to change them every time.
The Teams Premium requirement narrows who benefits, and the main implementation details are still unpublished: overrides, targeting, how it fits with policies, and client versions. November 2026 is the estimate. Until Microsoft publishes the documentation, prepare your licensing, labels and candidate templates, but hold off on announcing it to users.
Correction (October 20, 2026): the built-in meeting template list previously named "protected meeting" and "large meeting," which do not exist as built-in templates in Microsoft's documentation. Microsoft's built-in templates are the Controlled-content meeting template included with Teams, the Virtual appointment template included with Teams Premium, and the Class, Lecture and Webinar templates for Teams for Education.