How to Plan and Run Better Company Town Halls in Microsoft Teams
Employee engagement in the United States sits at roughly 31 percent. Gallup’s figure explains why a company-wide update matters, and why so many still miss the mark.
The usual failure is simple. Teams gets treated like a bigger meeting, not a broadcast. A calendar link, a dense slide deck, and a loose agenda create dead air, shallow answers, and a recording nobody finishes.
Strong town halls follow a different model. They are planned like live productions, with clear roles, timed segments, rehearsed transitions, and a deliberate attendee experience.
That approach matters even more now. Teams Live Events retire by July 2026, and Microsoft is folding town hall and webinar into a single events experience by April 2026. Teams that build a repeatable playbook now will handle that shift with less friction.
The core work is not flashy. Choose the right event type, lock governance early, rehearse in full, and measure what changed after the broadcast.
Key Takeaways
These principles do most of the work in a strong town hall.
Choose the right format first. Meeting, webinar, and town hall serve different purposes. Town hall is the best fit for one-to-many updates with moderated Q&A and producer controls, and it supports 10,000 view-only attendees by default or 100,000 with Attendee Capacity Packs.
Lock governance before creative. Confirm who can schedule, set recording retention for U.S. compliance, assign co-organizers, and finalize Q&A moderation rules at least one week out.
Build a minute-by-minute run-of-show. A time-coded script prevents overrun, dead air, and awkward handoffs that weaken executive credibility.
Rehearse at full fidelity. Use the Green Room with every presenter, test RTMP-In, and simulate a presenter dropout so your backup plan is real.
Use Microsoft eCDN for office watch-parties. Microsoft eCDN, an enterprise content delivery network, reduces repeated video traffic across office networks during large internal broadcasts.
Measure questions answered and watch time, not just registrations. Tie each metric back to communication goals so leadership sees the town hall as a campaign with outcomes.
Choose the Right Event Type
The wrong format creates problems no producer can fix later.
A town hall in Teams is a broadcast-style event where the audience watches a controlled feed and engages through moderated Q&A and reactions. Attendees do not join with open microphones or cameras unless the event team deliberately brings them on screen.
Organizers, co-organizers, and presenters work inside a standard meeting space while attendees see a managed broadcast. The Manage what attendees see setting is on by default, so producers control which speaker, screen share, or video package reaches the audience. Raised hands are supported in town halls with up to 3,000 attendees when that option is enabled. For larger broadcasts, Attendee Capacity Packs scale the event to 100,000.
| Feature | Meeting | Webinar | Town Hall |
|---|---|---|---|
| Interactivity | Full two-way audio and video | Presenter-led with attendee chat | Broadcast with moderated Q&A |
| Default capacity | 1,000 | 1,000 | 10,000 view-only |
| Registration | Optional | Built-in | Built-in |
| Chat or Q&A | Open chat | Chat plus Q&A | Moderated Q&A, chat optional |
| Manage what attendees see | Off by default | Off by default | On by default |
| Recording and transcripts | Available | Available | Available with translate options |
Use a meeting for small workshops that need full discussion. Choose a webinar when you need registration and more interactivity for up to 1,000 people. Pick a town hall for company-wide briefings, executive updates, policy rollouts, and any event where moderated Q&A matters more than open discussion.
Tie the Event to Communication Goals
A town hall should reinforce one clear message and a short list of behaviors.
Without that anchor, the event turns into information theater. People hear updates, but they leave unsure what to do next, what changed, or why leadership called the meeting in the first place.
Set success metrics that match your communication plan. If you are rolling out a pricing change at a mid-market firm, useful goals might include a policy acknowledgment rate above 80 percent, a post-event survey score above 4 out of 5, and at least five high-priority questions answered live.
That framing also helps leadership. When the town hall is positioned as one step inside a broader communication effort, not a calendar obligation, budget and executive attention usually follow.
Lock Governance and Licensing Early
Early governance prevents last-minute production choices from colliding with policy.
Finish this checklist at least seven days before the event.
Confirm town hall scheduling is enabled for organizers in Teams admin center.
Assign co-organizers and presenters, and lock the list 48 hours before the event.
Verify default attendee capacity and assign Attendee Capacity Packs if you expect more than 10,000 viewers.
Ensure recording and transcript retention meets your U.S. compliance requirements.
Set Q&A to moderated, assign at least two moderators, and decide whether attendee chat is off or limited.
Validate RTMP-In policy if you plan to use an external encoder such as OBS or vMix.
Confirm Microsoft eCDN is active if offices will host group watch-parties.
Minimum-viable-risk configuration for a company-wide briefing: Manage what attendees see on, Q&A moderated, attendee chat off, captions on, recording on, transcript on, and the organizer list finalized 48 hours before the event.
Do not skip the people side of governance. Site leads need room links, office AV checks, and a named contact for support. Legal, HR, and internal communications should also know who will approve sensitive answers before they appear on screen.
Build a Time-Coded Run-of-Show
A run-of-show, the minute-by-minute production script, is the best defense against dead air.
Keep most internal town halls to 45 minutes or less. Longer sessions can work, but attention drops fast when speakers wander, transitions drag, or Q&A starts too late.
A simple 45-minute flow works well. Start with a cold open bumper at 00:00. Bring in the host at 00:10. Cover agenda and norms at 02:00. Run the CEO update from 05:00 to 13:00. Share a customer or business win at 13:00. Move to a product demo at 18:00, then people updates at 25:00, moderated Q&A at 30:00, and closing actions at 42:00.
Define each role with one clear job. The organizer owns scope and governance. The co-organizer handles backup start, stop, and production support. The producer switches layouts and monitors attendee view. The Q&A moderator sorts questions by topic, merges duplicates, and publishes the best ones. If you use RTMP-In, short for Real-Time Messaging Protocol input, assign one person to watch the external feed and failover plan. End with an executive debrief in the Green Room, the private prep space attendees cannot see.
Configure the Event with Intention
Most production failures start with a missed setting, not bad content.
Move slowly through setup and confirm each toggle with the event owner.
Open Calendar, select New, then Town Hall.
Add co-organizers and presenters by name.
Confirm Manage what attendees see is toggled on.
Enable Q&A and assign moderators.
Set attendee chat to off or limited based on your governance decision.
Choose caption languages that fit your workforce.
Once those scheduling basics are set, some teams benefit from a short primer that shows how presenter views, Q&A layout, producer controls, and rehearsal choices work together in a real event flow. For a concise walkthrough that new event staff can review before rehearsal, before go-live, and again during final checks, the resource at teams town hall offers neutral further reading that reinforces the setup and production options covered here.
After those core settings are in place, brand the event, review the automated invitation emails, and add alt text to the hero image. Enable recording and transcript. If you need intranet embedding, copy the event HTML. Before you publish, test the invite flow with one attendee account and confirm the join experience works on managed devices.
Keep content design simple. Use one idea per slide. Build consistent lower-thirds, the name bars at the bottom of the screen. Stay inside 16:9 safe zones, pre-render short video bumpers, and create a hold slate so the audience never stares at a frozen screen during a transition.
Rehearse the Broadcast and Moderate Live
Full-fidelity rehearsal exposes technical risk while there is still time to fix it.
Seven to ten days out, run a silent network test for eCDN, gather presenter headshots, and confirm RTMP-In if you plan to use it. If several offices will watch together, ask site leads to test room audio, projected captions, and local internet performance before the final rehearsal.
Forty-eight hours before air, hold a full rehearsal with every presenter. Verify upload bandwidth for remote speakers, test slide animations, and practice the exact handoffs you expect to use. If an executive says rehearsal is optional, remind them that twenty minutes of prep costs less than a public audio failure.
On live day, open the Green Room 30 minutes early. Check audio levels, slides, and the attendee preview pane. Start with the bumper, bring in the host, and follow the run-of-show closely. Keep hand signals inside the Green Room, use a visible countdown clock, and avoid switching layouts in the middle of a sentence.
Q&A moderation needs the same discipline. Publish the best questions, group duplicates, and route sensitive items to the right reviewer before they go live. When an executive answers, have them repeat the question aloud and end with a clear action, owner, or date. Log every unanswered question for the recap email.
Protect Accessibility, Security, and Continuity
Accessible design makes the event clearer for every viewer, not only for people using assistive tools.
Enable live captions in the right languages, and publish the transcript and recording after the event. Ask speakers to slow down, describe visuals aloud, and avoid internal jargon that new employees may not know. If the deck includes detailed charts, share the slides in advance so screen reader users and office watch-parties can follow more easily.
Security depends on restraint. Keep attendee microphones and cameras off by default. Use Manage what attendees see so nothing unplanned reaches the audience. Set retention rules for recordings and transcripts, and avoid reading personally identifiable information from live questions.
Continuity planning matters because simple failures are common. A presenter can lose power, a shared video can stall, or a network path can drop without warning. Keep a backup presenter, a backup deck, and a fallback meeting link ready in your internal messaging channel so the audience still gets the message if the main event fails.
Give New Producers a Clear Reference
A short reference guide helps rotating staff support the event with fewer mistakes.
That matters when executive assistants, internal communications leads, or backup moderators step into the producer role for the first time. They need a fast way to understand the producer view, speaker roles, Q&A flow, and the difference between what presenters see and what attendees see.
For teams that want a simple companion resource, this overview can help first-time event staff get oriented before rehearsal day. It is most useful as a primer, not a replacement for your own run-of-show and governance checklist.
Measure Outcomes and Reuse the Content
Registration totals do not tell you whether the message landed.
Track reach through unique attendees and average watch time. Measure engagement through Q&A volume, upvotes, and reaction activity. Check comprehension with a short post-event survey, then compare results with concrete follow-through such as policy acknowledgment completion or a drop in support tickets on the same topic.
Be careful with raw attendance counts. A single office watch-party may represent fifty viewers on one screen, while forwarded invites can inflate registrations without adding real engagement.
Reuse the content aggressively. Publish a chapterized recording on the intranet with timestamps. Send a written recap that covers answered and unanswered questions. Cut short clips for Teams channels or leadership updates. Turn the sanitized Q&A into a knowledge-base article so employees who missed the live event still get the same guidance.
Frequently Asked Questions
The practical details below answer the issues teams raise most before launch.
What Is the Default Capacity and How Do Attendee Capacity Packs Change It?
By default, town hall events in Teams support up to 3,000 interactive attendees and 10,000 view-only attendees. When you assign Attendee Capacity Packs through the Teams admin center, capacity scales up to 100,000 attendees for large enterprise broadcasts.
Can Attendees Speak on Mic During a Town Hall?
No. Attendees cannot use microphones or cameras unless the event team explicitly brings them on screen. Most audience participation happens through moderated Q&A, reactions, and hand raise when that option is enabled for smaller events.
When Should I Use a Webinar Instead of a Town Hall?
Use a webinar when you need registration, attendee chat, and more interactive demos for up to 1,000 people. Choose a town hall when the event is a one-to-many broadcast with moderated Q&A and a larger or mostly view-only audience.
Can I Bring an External Encoder Feed into a Town Hall?
Yes. RTMP-In is supported for town hall events in Teams. You can send a feed from external encoders such as OBS or vMix into the event, which is useful for branded graphics, multi-camera switching, and pre-rendered video segments.
Where Do Recordings and Transcripts Live After the Event?
Town hall recordings and transcripts can be managed and published after the event for attendees to review. Organizers control access and retention, and transcripts can be translated into additional languages for distributed teams.
How Do I Preview the Attendee View Before Going Live?
Open the Green Room before starting the event and use the attendee preview pane. That view shows exactly what the audience will see, including layout, lower-thirds, and shared content, so you can catch issues before they go public.
