Teams town hall vs live events vs Stream

Anyone who ran a company all-hands on Teams Live Events remembers the producer view, the twenty-second delay, and the moment the Q&A panel filled up with "can you hear me?" Live Events is gone — retired in 2024 — and its replacement is town hall. Meanwhile Stream kept its name but changed completely, and the phrase "Stream live event" now refers to something that no longer exists. This guide untangles the three, sets out what a town hall actually gives you at each licence level, and says plainly when a big ordinary meeting is the better choice.

The short history

• Teams Live Events (2018–2024): a one-to-many broadcast, produced from Teams or an external encoder, with attendees watching a delayed stream and interacting only through moderated Q&A. It could be scheduled from Teams, Yammer, or classic Stream.
• Stream (Classic): the old video portal, which also hosted live events. Retired; content migrated to Stream (on SharePoint), which is not a portal but a set of video capabilities inside SharePoint and OneDrive.
• Town hall (2023 onward): the successor to Live Events, built on the modern meeting infrastructure. Same one-to-many shape, lower latency, a producer experience inside the regular Teams client, and a standard tier included in most enterprise plans plus a Teams Premium tier.

If a runbook, an integration, or a colleague still says "Live Events" or "Stream live," they mean town hall.

Town hall versus a large meeting

A Teams meeting scales into the hundreds and, with view-only overflow, beyond — so why a town hall?

Attendee experience. Town hall attendees are strictly view-only: they can't unmute, share, or see each other. There's no roster of a thousand names, no accidental cameras, no "you're on mute" chaos. Interaction is through Q&A (moderated) and reactions. If your event is a broadcast, that's what you want; if it's a discussion, it's what you don't.

Production. Town hall has a presenter/organiser view with a queue of what's going live next, a green room for presenters to prepare off-air, control of what attendees see, and — at Premium — RTMP-in so a professional production setup can push a produced feed into the event. Live meetings have none of that.

Scale. Standard town hall supports large audiences (Microsoft's published ceiling is in the low tens of thousands; check the current number for your plan). Premium raises it substantially, and very large events beyond that go through Microsoft's assisted programme. A regular meeting tops out far lower.

Latency. Town hall is a broadcast, so there's a delay between presenter and attendee — much shorter than Live Events but present. Meetings are real time. Anyone running a live poll or a "raise your hand" moment across the whole audience will notice.

Recording and post-event. Town hall recordings are automatic and published for on-demand viewing via the event page; that's where Stream comes back in.

Where Stream fits now

Stream (on SharePoint) is the video layer for Microsoft 365: playback with chapters, transcripts, captions, analytics, and sharing controls, all on top of files that live in SharePoint or OneDrive. Town hall recordings, meeting recordings, and uploaded videos are all "Stream" in this sense.

What Stream is not: a live streaming service, a portal with channels, or a broadcast tool. The post-event workflow is: town hall records → recording lands in the organiser's OneDrive (or a SharePoint location if you configure it) → you share it, or embed it on a SharePoint page or in Viva Engage, with Stream providing the player and analytics. For a curated on-demand library, build a SharePoint site with the Stream web parts and a video library; that's the modern "video portal."

Standard versus Premium town hall

Broadly, and worth checking against the current comparison table before promising anything:

| | Standard (in most enterprise plans) | Teams Premium | |---|---|---| | Attendee capacity | Large; a fixed standard ceiling | Higher ceiling | | Concurrent town halls per tenant | Limited | More | | Green room, Q&A, reactions, recording | Yes | Yes | | RTMP-in (external encoder) | No | Yes | | Live translated captions | Limited languages | More languages | | Attendee-facing email customisation | Basic | Branded, customisable | | Post-event attendance and engagement reports | Basic | Detailed | | eCDN for on-premises network relief | Microsoft eCDN included | Yes, with more configuration | | Branded event pages and themes | No | Yes | | External presenters | Yes | Yes |

The honest read: standard town hall is enough for most internal all-hands. Premium earns its cost when you need RTMP-in for a produced show, larger audiences, multilingual captions across many languages, or the reporting comms teams want. Buying Premium only for town hall is expensive; most organisations that justify it also use it for meeting protection, advanced webinars, or intelligent recap.

eCDN and the network

A town hall to five thousand office-based staff is five thousand video streams hitting the internet edge. Microsoft eCDN — included for town halls — uses peer-to-peer distribution between attendees on the same network to cut that. It needs a bit of enablement and works best when the network team has confirmed WebRTC between clients isn't blocked. Skipping this is the number-one cause of "the town hall was fine at home and terrible in the office."

Choosing

• Discussion among up to a few hundred people → meeting.
• Broadcast to the company with moderated Q&A → town hall, standard.
• Produced show with external encoder, big audience, or multilingual → town hall, Premium.
• Interactive session with registration and marketing → webinar (a different format, covered separately).
• On-demand library afterwards → Stream on SharePoint, via a SharePoint site.

And a governance note: who may create town halls is a meeting-policy setting. Most organisations restrict it to comms and events teams, both to keep the concurrent-event limits free and to avoid every team lead broadcasting a "town hall" to twelve people.