Additional team and channel-related features and issues within Microsoft Teams for business
Teams webinars v2 in Customer Insights - Journeys are intended for large-audience events where a few presenters speak and attendees can react, chat, or answer polls, but attendees can’t share audio, video, or content. They support registrations and up to 1,000 attendees.
If the goal is a friendlier registration experience, the documented pattern in Customer Insights - Journeys is:
- Create a new event.
- Set Do you want to stream this event to Yes.
- Select Teams webinar v2.
- Select Open settings to configure meeting options.
- Save the event record. Saving creates the Teams meeting.
- Build the registration experience using the event registration experience for Customer Insights - Journeys.
- After registrations are collected, send registrants an email from the Customer Insights - Journeys email designer using Join in Teams from the Link to menu.
Important behavior differences called out in the documentation:
- Registrations are managed in Customer Insights - Journeys and are regularly synced to the corresponding Teams webinar.
- The attendee URL is created when the event is saved, but it should not be shared directly. The recommended method is to send the attendee-specific Join in Teams link by email.
- That Join in Teams link generates a unique attendee URL for each registrant and is also used to create check-in records for attendance insights.
- The Teams meeting owner becomes the user who created and saved the webinar in Customer Insights - Journeys, and that owner can’t be changed after creation.
- Changing the meeting type and saving again cancels the original meeting and generates a new URL.
- Tenant authentication and permissions must be configured by an administrator before Teams webinars v2 can be used successfully in Customer Insights - Journeys.
If the concern is specifically that native Teams webinars feel more registration-friendly, the available documentation confirms that Customer Insights - Journeys relies on its own event registration experience and email-based attendee join flow rather than the direct Teams registration flow.
References: