How to Prepare Large-Scale Events in Microsoft Teams and Town Hall

Large-scale Microsoft Teams and Town Hall events raise the stakes on technical readiness. A stalled stream reads very differently in front of 5,000 employees than in a team meeting of ten. Microsoft's April 2026 licensing update also changed who can host at that scale, and how. This guide covers every technical piece that has to be in place, from capacity and network testing through event-day operations, using Microsoft's current limits and settings.

How Do You Prepare for a Large-Scale Microsoft Teams or Town Hall Event?

Preparing a large-scale Microsoft Teams or Town Hall event means confirming six things are in place: the right format and capacity, a validated network, locked Teams settings, ready presenters, a full rehearsal, and an event-day production plan. Under Teams Enterprise, Town Halls support 3,000 interactive or 10,000 view-only attendees. Attendee Capacity Packs extend that to 100,000.

The Technical Readiness Checklist at a Glance

Use this table as the master list. Each row maps to a section below.

Format and Capacity

Format and license set the ceiling for every other decision, so settle both first. For large broadcasts, Town Hall is the default. Under Teams Enterprise it includes producer controls, moderated Q&A, Microsoft eCDN, Ultra-Low Latency streaming, and 1080p video. Webinars suit registration-driven sessions where attendees may need cameras and microphones. For the full side-by-side, see our Microsoft Teams meeting types comparison and the pillar guide, Mastering Large Virtual Events on Teams.

Capacity After the April 2026 Licensing Update

Microsoft's April 2026 licensing update for Teams events moved many advanced event features from Teams Premium into Teams Enterprise. Capacity above Teams Enterprise limits now comes from Attendee Capacity Packs.

The pack rules that catch planners off guard:

• Packs belong to organizers - Each organizer holds one pack. Your organization can buy several, and an admin reassigns a pack by removing it from one organizer first.
• Capacity doesn't update itself - Assigning a larger pack after scheduling leaves existing events at their old limit. The organizer has to edit capacity in the scheduling form.
• Format locks at scheduling - Interactive or view-only is chosen when the event is created. Switching means building a new event.
• Premium grandfathering has an end date - Teams Premium licenses bought before April 1, 2026 keep 100,000 until the term ends. After renewal, events above 3,000 attendees need a pack. Check that renewal date against your event calendar.

Packs count concurrent attendees only, so organizers, co-organizers, and presenters don't use up seats. They're also available in GCC, GCC High, and DoD environments.

Teams Live Events retired on June 30, 2026.  Events scheduled before that date are supported through February 28, 2027. Any recurring broadcast still running on Live Events needs a Town Hall replacement before then.

Network Readiness

IT teams prepare the network for a global Town Hall in four moves. Confirm Microsoft eCDN is active and peering, clear two browser policies that block peering, run a Silent Test across representative office subnets, and route remote attendees' stream traffic around the VPN. Start two to three weeks out, so there's time to fix what the test finds.

Know the Bandwidth Math

Without an eCDN, every viewer pulls a separate stream across your internet link. Microsoft estimates 2 Mbps per viewer at each location,  or 3 Mbps for 1080p. That means 500 viewers in one office need about 1,000 Mbps (500 x 2 Mbps), or 1,500 Mbps at 1080p. Microsoft eCDN cuts that load by letting viewers on the same network share the stream with each other. It's included with Teams Enterprise and on by default for Town Hall organizers.

Validate eCDN Before You Test

Run Microsoft's eCDN validation check  in a browser before any load test:

1. Open a Town Hall stream in Edge or Chrome. Microsoft recommends a browser over the Teams app for validation.
2. Press Alt+Shift+P to open the eCDN stats overlay. Confirm the viewer IP shows and the group ID matches your subnet mapping.
3. Open the same stream in a second tab. Peer-to-peer traffic appears in orange on the graph.
4. Check that the session data appears in the eCDN Analytics dashboard.

Two browser policies quietly block peering when they're missing. Chrome and Edge 146 extend Local Network Access enforcement to the WebRTC connections eCDN uses, so admins must allow the eCDN and Teams domains through the Local Network Access policy. If the viewer IP doesn't appear in the overlay, disable mDNS IP masking for those same domains. The Teams desktop app isn't affected by the Local Network Access change.

Run a Silent Test on Real Subnets

The Teams Silent Test for Town Halls  simulates a large event in the background on Teams desktop clients in the subnets you target. It's included with Teams Enterprise, runs for up to 180 minutes, and needs a Global Admin or Teams Admin to schedule it. Users see no notifications or visible changes. Results appear in the eCDN Analytics dashboards shortly after the test starts.

A test doesn't need to match your audience size. It needs to represent the offices and networks your audience will use. For sample size, Microsoft's eCDN silent test guidance  recommends 20 to 100 devices, with 5 as the minimum. Two results matter most:

• Peer-to-peer ratio - The share of video viewers received from each other. At 90%, only 10% of traffic crossed the internet link. A low ratio points to too few concurrent viewers or a network that needs tuning.
• Rebuffering - Microsoft says it "should ideally be below 1%." Spikes point to congestion or misconfiguration.

Start at 480p, raise quality in later tests, and avoid end-of-day windows when devices drop off.

Plan for Remote and VPN Viewers

Microsoft's guidance for Teams events in VPN environments  sends Town Hall attendee traffic straight to the internet instead of through the VPN. Traffic goes direct only when both the hostname and the resolved IP match Microsoft's published list. Microsoft supplies a PowerShell script that builds the PAC file, with versions for Worldwide, GCC, GCC High, and DoD tenants. Three details matter:

• It covers attendees only. Presenter traffic isn't included.
• Ultra-Low Latency streams still need it, because an event can fall back to standard streaming.
• Microsoft asks you to weigh the security risk of bypassing the VPN against the performance gain.

In eCDN, you can also exclude VPN subnets from peering,  so office and VPN viewers don't peer with each other. Viewers outside your subnet mapping don't peer at all by default.

Choosing an eCDN Provider

Microsoft eCDN is the default, and it comes with Teams Enterprise. Town Halls also support certified partner eCDNs, including Hive, Kollective, and Ramp. Organizations already running one of these providers can keep it. Confirm the provider is selected in the Teams admin center before you run your Silent Test.

Configure Teams Before Invitations Go Out

Settings changed after invitations go out cause the most avoidable live-day problems. Lock these before anyone receives a join link:

• Event type and capacity: interactive or view-only, sized to the organizer's license or pack. This can't change later.
• Roles and permissions: assigned and communicated (see below).
• Q&A: decide who moderates questions and how they'll be answered.
• Captions, recording, and accessibility settings: turned on and tested.
• RTMP-In: confirmed if you're producing from an external encoder. Admins control whether organizers can use it.
• Registration: configured for webinars. See our Teams Event Registration Guide.
• Branding: intro slides, lobby messages, and lower thirds ready. Custom backgrounds and meeting themes inside Teams still require Teams Premium. See our Microsoft Teams Event Branding Guide for more.

Assign Roles and Permissions Early

Roles decide who can start the stream, manage Q&A, and present. Unclear permissions create avoidable chaos during the live event.

• Organizer - Owns setup, scheduling, and follow-up. For Town Halls above Teams Enterprise limits, the organizer also holds the Attendee Capacity Pack.
• Co-organizers - Manage presenter permissions, Q&A, and reporting.
• Presenters - Deliver content and appear on screen.
• Attendees - Watch and engage through Q&A, polls, and reactions.

Prepare Presenters and Their Setups

Different devices, internet speeds, and camera setups produce different audio and video quality. Individual tech checks with each presenter remove most of those surprises. Walk presenters through joining as a presenter, sharing their screen, and checking their audio levels. Assume nothing about their comfort with the platform.

• Wired internet where possible.
• A quality microphone and camera.
• A dual-screen setup for moderators and organizers, so slides and Q&A stay visible at once.
• Teams Rooms confirmed for compatibility and permissions, with links validated at least 24 hours ahead.

Rehearse at Full Fidelity

At this scale, rehearsals aren't optional. Run a full mock event with the same settings, format, and capacity as the live one. Presenters should join from their actual locations and run every transition and Q&A segment. IT should monitor call quality in Teams' Call Quality Dashboard (CQD) while the rehearsal runs, so problems surface a week early instead of on air.

Run Event Day with a Production Plan

• Assign a technical lead to own real-time troubleshooting.
• Keep production chatter in a dedicated channel, separate from the attendee experience.
• Keep backup content files ready in case of playback failure. For high-risk segments, consider pre-recording. See: How to Run a Simulated Live Webinar in Teams.
• Confirm presenter readiness and platform settings before going live.
• Agree on an escalation path, so the team knows who decides when something breaks.

Technical Readiness Timeline

Work backward from the event date. Microsoft sets the two-week notice for Teams Event Services. The other lead times are working buffers that leave room to fix what testing finds.

When to Bring in a Production Partner

Teams provides the platform. Running it for 10,000 or 100,000 attendees takes production capacity most internal teams don't keep on staff. Bring in a partner when:

• The event is business-critical, and a failed stream carries real consequences.
• Attendance will cross Teams Enterprise license limits, and no one owns pack assignment and capacity settings.
• Your audience spans offices, home networks, and VPNs, and IT needs another set of hands during testing.
• You need registration, branding, and/or reporting beyond native Teams features.
• You operate in GCC High or another regulated environment.

As a Microsoft Preferred Supplier, EventBuilder has delivered more than 75,000 of Microsoft's own events. Our team handles platform setup, professional moderation, presenter preparation, and custom communications, with 24/5 technical support for organizers and attendees. EventBuilder holds ISO 27001 (Data Security) and ISO 27701 (Privacy) certifications and is GCC High-eligible.

FAQ: Large-Scale Microsoft Teams Events

1. What roles do I need to assign for a large Teams or Town Hall event?

Four roles matter: organizer (owns setup, scheduling, and follow-up), co-organizer (manages presenter permissions, Q&A, and reporting), presenters (deliver content on screen), and attendees (engage through Q&A, polls, and reactions). Assign these early and communicate each role's permissions before the event.

2. How many attendees can a Microsoft Teams Town Hall support in 2026?

Under Teams Enterprise, a Town Hall supports up to 3,000 attendees with engagement features like reactions, polls, and Q&A, or up to 10,000 in view-only mode with Q&A. An Attendee Capacity Pack assigned to the organizer extends that to 100,000. Microsoft recommends Teams Events Services for events above 20,000 attendees.

3. Do I need Teams Premium to host a large Town Hall?

No. Since April 1, 2026, Teams Enterprise includes Microsoft eCDN, Ultra-Low Latency streaming, 1080p video, and attendance reports for Town Halls. Capacity above Teams Enterprise limits comes from an Attendee Capacity Pack. Teams Premium now covers branding, advanced meeting protection, and intelligence features such as intelligent recap.

4. Can I switch a Town Hall from interactive to view-only after scheduling?

No. Organizers choose interactive or view-only when they schedule the event, and Microsoft doesn't allow switching afterward. Changing formats means creating a new event, so lock the format before invitations go out.

5. What is an eCDN and do I need one for a Teams event?

An eCDN (enterprise content delivery network) lets viewers on the same network share a video stream instead of each pulling a separate copy over the internet. Without one, Microsoft estimates 2 Mbps per viewer at each location. Microsoft eCDN is included with Teams Enterprise and on by default for Town Halls.

6. How do you stress-test an eCDN before a large Town Hall?

Validate eCDN in a browser first, using the Alt+Shift+P stats overlay. Then schedule a Teams Silent Test for Town Halls from the Teams admin center. It runs silently on Teams desktop clients in the subnets you target, for up to 180 minutes. Review the peer-to-peer ratio and aim for rebuffering below 1%.

7. How should IT handle VPN users during a Town Hall?

Follow Microsoft's guidance for Teams events in VPN environments, which routes Town Hall attendee traffic directly to the internet when both the hostname and the IP match Microsoft's published list. It applies to attendee traffic only. In eCDN, you can also exclude VPN subnets from peering.

8. How far in advance should I start technical preparation for a large Teams event?

Start at least four weeks out to confirm format, licensing, and capacity. Run network validation and a Silent Test two to three weeks out, rehearse about a week out, and validate permissions and links 24 hours before. Events above 20,000 attendees need at least two weeks' notice to Teams Events Services.

9. What happens if something goes wrong during a live Town Hall?

Keep backup content ready in case of playback failure, use a dedicated communication channel for production staff, and assign a technical lead to oversee real-time troubleshooting. Confirm presenter readiness and platform settings immediately before going live. 

Plan Your Next Large-Scale Event with Confidence

Large-scale Microsoft Teams and Town Hall events succeed when preparation meets precision. With the right format, the right capacity, thorough rehearsals, clear documentation, and prepared presenters, you build a reliable event and a confident, connected audience.

Our team helps design, test, and run large-scale Microsoft Teams events, from capacity and licensing planning through live-day production. We hand the behind-the-scenes complexities so you can focus on delivering value. Connect with us to create your fully-customized technical readiness plan!

Download Your Free Resource:

The Ultimate Toolkit for Large-Scale Virtual and Hybrid Events on Microsoft Teams

Get our whitepaper that walks you through every stage from technical setup and presenter prep to post event analytics and engagement tracking. 

---

Disclaimer: This article was created with some help from AI, but thoroughly edited, revised, reviewed, and fact-checked by a living, breathing, coffee-drinking human writer.