Microsoft Teams Events to Support 20,000 Registrations With Attendee Packs

It's a short roadmap line, but it touches licensing, event design and admin planning. The higher number comes with conditions, and not everyone will get it.

What Microsoft is actually promising​

Here is what roadmap item 574110 states:

• The change: Teams Events will support up to 20,000 registrations.
• The condition: The organizer must have a valid Attendee pack.
• Status: In development. The feature is not shipping yet.
• Target: General availability in November 2026.
• Scope: Microsoft Teams, Web, Worldwide (Standard Multi-Tenant).

Microsoft's roadmap says its estimated dates and descriptions are subject to change. Treat November as a target. If your big product launch is booked for mid-November, keep a fallback plan.

Section summary: This is a planned change, it depends on a license, and it is scoped to the commercial worldwide cloud. Nothing has rolled out yet.

The "valid Attendee pack" condition​

The Attendee pack is the add-on that came out of Microsoft's April 2026 Teams licensing overhaul. Microsoft describes Attendee Capacity Packs as add-on licenses for Teams Enterprise that let event organizers host events for up to 100,000 attendees. They can be purchased to support 5,000, 10,000, 20,000, 35,000, 50,000, 75,000, and 100,000 event attendees.

The 20,000 figure in the roadmap item matches one of those published tiers exactly. Microsoft's April 2026 customer licensing FAQ uses that tier as its example: if an organizer is assigned a 20k Attendee Pack, the organizer can host any number of events with a capacity of 20k attendees per event for as long as the pack remains assigned to them and active under the contract.

Without a pack, Teams Enterprise organizers have these defaults:

• Host events with capabilities to engage with audiences (including reactions, raise hand, polls, and Q&A) for up to 3,000 attendees.
• Host events for up to 10,000 attendees in view-only mode (with Q&A).

Microsoft's licensing overview also breaks limits down by event type. Organizers with advanced event features get a ceiling of 3,000 attendees for "events with registration and engagement capabilities." The view-only 10,000-attendee tier is listed as an event "without registration." That's why the registration wording in this roadmap item matters. Registration-based events are the kind with sign-up forms, waitlists and approval steps, and they have been capped well below the view-only tier.

Analysis: Microsoft hasn't said what the registration limit for pack holders is today. Our reading is that the roadmap item makes registration-backed events scale further for organizations that have paid for the capacity. Until Microsoft updates its documentation, don't assume more than that.

Section summary: The 20,000 number matches the existing 20K Attendee Capacity Pack tier. You'll need the add-on. Free Teams licenses don't get this increase.

Registrations vs. attendees: two different numbers​

This is the distinction organizers most need to get right. The roadmap counts registrations. Microsoft's capacity pack documentation counts concurrent attendees.

Microsoft explains that the attendee limit is based on the number of attendees currently in the event at the same time. If attendees leave, other attendees can join until that limit is reached. Also, organisers, co-organisers and presenters do not count against the attendee cap.

Microsoft's capacity pack page gives an example. With a 20,000 pack, once 20,000 attendees are in the event, nobody else can join. If attendance drops to 19,800, up to 200 more people can get in.

The two numbers can come apart in practice. Many people who register for a webinar never show up, so 20,000 registrations usually means fewer than 20,000 people in the room at once. Microsoft hasn't said exactly how the new registration limit will relate to the concurrent attendee limit. Read the documentation that ships with the feature before you plan around either number.

Microsoft's licensing overview also documents a related feature for organizers with advanced event features: when registration reaches capacity, a waitlist collects overflow requests. Organizers can also set registration start and end times and approve registrants manually.

Section summary: Registrations are sign-ups and capacity is how many people are in the event at once. Plan for both and don't assume they're the same.

Reaching 20,000 people doesn't mean 20,000 open microphones​

A 20,000-person Teams event is a broadcast, and Microsoft's own feature table makes that clear. The company states that Teams events support up to 1,000 fully interactive attendees (with cameras and microphones on, as well as event registration), similar to the previous webinar experience.

Microsoft's "event features at scale" support page shows what attendees can do at each tier today:

The 20,000 mark is also where polls, chat, raised hands and reactions stop being available. The new registration ceiling therefore lines up with the largest tier that still has those engagement features. That alignment is our observation. Microsoft hasn't stated it.

Microsoft's support documentation describes several more conditions for events above 1,000 seats:

• Events above 1,000 capacity are optimized for scale automatically. Attendee microphones and cameras are off, and attendees watch on a slight delay, with the ability to pause and rewind.
• Between 1,000 and 20,000 attendees, chat is a streaming experience that only works during the event. Attendees can send and read messages but can't reply or react, and chat history isn't available after the event ends.
• Regular interactive chat, breakout rooms and PowerPoint Live aren't supported in events optimized for scale.

Microsoft's capacity pack FAQ also says the packs determine the maximum capacity an organizer can set for a Teams event, and that they increase capacity without unlocking any other features. This table reflects current behavior. Microsoft hasn't said whether item 574110 will change any of it.

Section summary: At 20,000, attendees get polls, reactions and streaming chat, but no cameras, no microphones and no breakout rooms.

Admin checklist: getting ready before November​

Microsoft's Teams admin documentation describes how pack management works today:

1. Check your inventory. Sign in to the Teams admin center and go to Add-on Licenses > Teams Events. If there are no active attendee packs in your organization, you see this page with a redirect to purchase attendee packs in the Microsoft 365 admin center.
2. Check your role. Microsoft's management page says you need the Global Administrator role to manage license assignments. Teams Administrators get read-only access to the License Management section.
3. Assign the right tier. On the Licenses tab, select Assign to new users, search for the organizer, pick a pack size in the Attendee pack column, then select Apply and confirm.
4. Remember the one-pack rule. Each organizer can hold only one pack at a time, and assigning a new one replaces the old one. Microsoft licensing commentator Topedia notes that assigning multiple packs to a single account does not increase the total capacity.
5. Update scheduled events by hand. Microsoft says event capacity doesn't update automatically when an organizer gets a larger pack. The organizer has to change it in the event scheduling form.
6. Be careful removing packs. If you remove a pack after events are scheduled, those events may no longer run at their planned capacity. Microsoft says Teams warns the admin and emails the organizer a list of affected events.
7. Watch the tenant-wide limit. Microsoft's documentation caps an organization at 50 concurrent events across all organizers.

There's also a network benefit at this tier. Microsoft's eCDN purchasing documentation says pack holders get Microsoft eCDN included, and that an organizer with a 20,000 Attendee Pack license can host multiple concurrent Town Halls with up to 20,000 attendees each.

Section summary: Buy the pack, assign it as a Global Admin, update existing events manually, and keep the 50-concurrent-event limit in mind.

Who should care, and who can skip it​

Customers still on legacy Teams Premium: You may not notice this right away. Organizers with an active Teams Premium license purchased before April 1, 2026, can continue to host events for up to 100,000 attendees until their current Teams Premium term ends. Once that term ends, events with capabilities to engage with audiences that have more than 3,000 attendees require an attendee pack sized to the desired attendee capacity. If your renewal comes before a big event, budget for the pack.

Government and sovereign cloud tenants: Microsoft's capacity pack page lists packs as available in commercial, EDU, GCC, GCC High, DoD and nonprofit environments. This roadmap item only lists Worldwide (Standard Multi-Tenant). Don't expect the 20,000-registration change in your tenant until Microsoft confirms it for your cloud.

Small businesses on Business Basic, Standard or Premium: Microsoft's licensing overview puts these SKUs in the "foundational" event tier, so this change is unlikely to affect you.

The bigger picture​

This item continues the large-event overhaul Microsoft started in April 2026, when it moved features out of Teams Premium and started selling capacity in tiers. Teams live events have also gone away. Third-party analyst Virto Software reports that they retired on 30 June 2026 and that new large events run as town halls in the Events app. Lifting registration limits to match a paid capacity tier is a sensible next step in that plan.

One caveat: Microsoft's marketing calls this a way to "engage larger audiences at scale," but engagement at 20,000 means polls and streaming chat. A two-way conversation isn't on offer at that size. If you need actual participation from that many people, design the event around Q&A and polls, and keep the open microphones for the speakers on stage.

Bottom line: If your organization runs big webinars or town halls, check your pack inventory now, confirm your renewal dates, and check Microsoft's documentation again in November to see how registration counts and attendance limits work together once the feature ships.