Teams streaming for events

What it does

An event in Customer Insights - Journeys can create and own the Microsoft Teams meeting behind it, so registration, the join link and attendance data all hang off the same record. You pick a streaming provider on the event, and the platform provisions the Teams object through the Graph API when you save.

Key facts

Streaming is switched on per event with the Do you want to stream this event toggle, then a provider from the dropdown.
Three current options, all generally available: Teams meeting v2, Teams webinar v2 and Teams town hall. All three are built on Graph APIs rather than the older integration.
Three legacy options are on the way out: Teams meeting, Teams webinar and Teams live event. Treat them as end-of-life for new builds.
Teams live events are being retired by Microsoft effective 30 June 2026, with events already scheduled honoured through 28 February 2027. Town hall is the documented replacement.
Teams webinar capacity is up to 1,000 attendees, on both the legacy and v2 versions. Town hall is the option for large-scale audiences beyond that.
A Microsoft 365 licence including the Teams service is mandatory. Without it, the Teams options simply don't appear in the streaming provider list — there's no error message explaining why.
Tenant setup is an admin job: Teams authentication configured in Customer Insights - Journeys, the right permissions, and application access policies. For engagement data sync where the organisation manages Teams user policies, the OnlineMeetingArtifact.Read.All API permission is needed.
Saving the event creates the Teams meeting and makes the saving user its owner. That owner is set at creation and cannot be changed, and it is a different thing from the owner of the event record.
Presenters come from speakers. Add a speaker at event or session level with an email address populated and they appear in the Teams webinar with the Presenter role.
Co-organizers are a two-step: add the person to the Team Members table on the Additional information tab, then set them via the lookup on the General tab. They need access to both Customer Insights - Journeys and the Teams instance. Co-organizers can manage the lobby, start and stop recording, and manage attendee roles.
Teams webinars require event registrations, and registrations created in Customer Insights - Journeys sync to the Teams webinar automatically.
Attendance flows back through the Join in Teams button in the email designer, which issues per-attendee URLs. Engagement data — check-in, checkout, duration — populates roughly ten minutes after the webinar ends.
Microsoft's documentation still lists co-organizer definition from within Customer Insights - Journeys and improved attendance reporting as coming in February 2026. Check whether that has landed in the tenant you're working in rather than assuming either way.

When to use / skip

If the client is a Microsoft 365 shop running webinars, use the native integration rather than Zoom or ON24. The registration sync and automatic attendance are the payoff, and you'd otherwise be building both.

Pick by shape of event, not by size alone. Meeting v2 for interactive sessions where everyone might talk. Webinar v2 for presenter-to-audience up to a thousand. Town hall for broadcast-style events to a large internal or external audience, and for anything currently on live events.

Skip the native integration when the client's webinar practice is already built on a specialist platform with polls, breakouts and reporting their marketing team lives in. The integration will feel like a downgrade and you'll spend the project defending it. In that case, keep the event record for registration and treat the streaming platform as an external system.

Configuration decisions

Which provider per event type, and whether the client gets a free choice or a rule. Left open, marketers pick meeting when they mean webinar.
The migration plan off Teams live events, given the 2026 retirement date and the 2027 grace period for already-scheduled ones.
Who saves the event first, because that person becomes the permanent Teams meeting owner. This deserves an actual process, not chance.
Whether speakers are modelled properly with email addresses, since that's what drives presenter roles in Teams.
Whether the tenant admin will grant OnlineMeetingArtifact.Read.All, which some security teams will query, and what the attendance story is if they refuse.
How guest presenters from outside the organisation are handled, since they need to exist in the Teams instance first.

Gotchas

The Teams meeting owner is fixed at creation. If a contractor builds the events and leaves, the client owns a set of meetings they can't fully control, and the only fix is recreating them.
Missing Teams licence produces an empty dropdown, not a message. Consultants lose an afternoon to this.
Changes made in the Teams calendar do not flow back to the event record. Reschedule in Teams and the event record — and everything driven off it — is silently wrong.
On-premises mailboxes can't have calendar items created for organisers or speakers. In a hybrid Exchange estate, some staff get calendar invitations and others need an email instead.
Guest presenters won't see the event in their calendar at all. Send them the link by hand and tell the client that's expected.
Registration is mandatory for webinars, so a client wanting an open-link webinar with no sign-up has picked the wrong provider.

Consultant notes

Establish the owner-at-creation rule on day one and put a named service or shared account behind it if the client's events team has turnover.
Get the Teams authentication and application access policy work into the admin's backlog early. It involves a tenant admin who does not report to your sponsor.
If the client is still on Teams live events, raise the retirement date as a delivery item with a date, not a footnote. The grace period runs out in February 2027.
Demo the join-link-to-attendance loop, since that's the argument for using native Teams over an external webinar platform, and it's the thing marketers actually care about.
Before go-live, test with a guest presenter and, if the estate is hybrid, with an on-premises mailbox. Both fail in ways the happy-path test won't show.

Worth another look as the Teams live events retirement date passes, and to confirm whether the co-organizer and attendance reporting improvements shipped.