Viva Engage Teams Town Hall Creation Ends Dec 7: Migration Steps

Microsoft says that starting December 7, 2026, users can no longer create Microsoft Teams town hall events from Viva Engage. Events that were already scheduled will still run as planned. To prepare, tell your event organizers and communications team, have them create new events through the Events experience in Viva Engage (or directly in Teams), and update any internal guides that describe the old route.

The announcement is Message Center post MC1552394, published November 13, 2026, with roadmap ID 537280 referenced in the mirror of the post. The Message Center mirror lists no separate update date as of November 15, 2026.

What the Teams town hall creation retirement is

MC1552394, titled "Retirement of Teams town hall event creation in Viva Engage," is tagged as a major change with user impact and admin impact. It applies to Android, iOS and web. It has one date: December 7, 2026.

The change is narrow. It removes one way of creating events, not events themselves:

• Retired on December 7, 2026: creating new Teams town hall events from Viva Engage.
• Unchanged: events already scheduled keep running as planned.
• Replacement: the Events experience in Viva Engage, or creating the event in Teams.

This sits within a larger move. Microsoft's Teams blog describes a new unified Teams events experience, where the Meet app becomes the home for events and a dynamic scheduling flow replaces the old setup, so features are no longer tied to a single event type. Microsoft's roadmap item 537280 describes an Engage Events update that adds a broadcast option for large-scale produced events and meetings-based events, plus a single Events landing page for the event lifecycle. The roadmap lists that item as launched, general availability, with a GA date of "April CY2026".

Microsoft has also retired earlier event routes in the same area. Search results that include Microsoft Message Center items MC1227085 and MC1226495 relate to Engage live events and Teams live events. Those are separate retirements from the one covered here, and this article does not rely on them for any date. If you still have anything scheduled from the older live events tooling, check those posts in your own Message Center.

Who it affects and availability

According to MC1552394, the affected groups are:

• Event organizers who create Teams town hall events from Viva Engage.
• Communications teams that organize these events.

The Message Center post does not say which cloud environments are affected, such as GCC. The roadmap item for the related Engage Events update lists "Worldwide (Standard Multi-Tenant)" as its cloud. If you run a government cloud, check your own Message Center for how the post is scoped to your tenant, because the public mirror does not answer it.

The post does not mention price. In its Teams events announcement, Microsoft states that starting April 1, 2026, town hall and webinar capabilities, including advanced features, are available to all Teams Enterprise users without Teams Premium, and that Attendee Capacity Pack licenses scale digital and hybrid events up to 100,000 attendees. Microsoft Support's Engage event page does not cover licensing or attendee capacity, so confirm those against Microsoft's licensing documentation. India and the US are not treated differently in any page we opened.

Requirements

To follow the steps below you need:

• For organizers: access to Viva Engage. Per Microsoft Support, any user can create an event on their own storyline, and only community admins can create community events. To create a storyline event for a leader, you must be a delegate with access to that leader's storyline.
• For broadcast production: the Teams desktop app. Microsoft Support says broadcast production of town halls requires it, because the Teams web app does not support it.
• For Teams admins: a role that can edit Events policies in the Teams admin center (Microsoft's page does not name the role, so check your role assignments).
• A Teams events policy that allows town halls for the organizers. The setting is described later in this article.

How to check whether you're affected

MC1552394 asks you to inform organizers and communications teams, so the first job is to find them. Microsoft does not publish a report for this in the pages we opened, so use what you know of your tenant:

1. Ask your communications team and Viva Engage community admins whether they schedule town halls from Engage today.
2. Review internal documentation, training decks and intranet pages that describe creating Teams town hall events from Viva Engage. These are the documents MC1552394 says to update.
3. List upcoming events and note any that were created from Engage. They continue as planned per Microsoft, but any new event needs the new route.
4. Read the post in your own admin center to see the exact scope for your tenant: Microsoft 365 admin center > Health > Message center, then search for MC1552394.

How to move to the Events experience in Viva Engage, step by step

These steps are from the Microsoft Support page "Organize an Engage event", opened on November 15, 2026. Microsoft's page does not state a menu label beyond those quoted here, so no other labels are given.

Create an event in Viva Engage

1. Use either route:
   • Open your storyline or a community, select the Events tab, then select Create event.
   • From the top level of Engage, select Create new in the left navigation, then choose Event.
2. Enter the title, dates and times. The start and end dates define the event's time window.
3. Choose Storyline or Community as the host. This determines who can attend and where content is stored.
4. Choose the event type:
   • Async is the default and has no video. Leave the Enable broadcast or meeting toggle off.
   • For a Meeting or Broadcast, turn on the Enable broadcast or meeting toggle, then choose one.

MC1552394 names the Engage event kinds as town hall, community town hall and AMA events. The support page describes the options as above, so use the Events form to see how those kinds appear in your tenant. The mapping between the two sets of names is not spelled out in the pages we opened.

Assign roles and set visibility

• Organizer: the creator, with full edit and delete control.
• Co-organizers: up to 10 per event. They can moderate, change engagement settings and update recordings.
• Presenters: can share content, screen, voice and video. Organizers assign them, and the assignments sync with Teams presenter settings.
• Featured users: appear on the event landing page, and the event shows on their storylines.

Storyline events can be public (anyone in the organization can join) or private (only organizers, presenters and invited people or groups). Community events follow the community's privacy setting at creation time.

Things that change how you work

• Calendar invites go automatically to organizers, co-organizers and presenters. Edit events only in Engage, not in Outlook or Teams.
• Recording is on by default for meetings and broadcasts. Organizers can confirm this in Teams meeting options.
• Organizers can export event posts as a CSV covering the previous 28 days. Network admins can disable this in the Engage Admin Center under Content management; it is enabled by default.

Create the event directly in Teams instead

MC1552394 also allows creating the event in Teams. Microsoft's Teams blog describes the new events experience as living in the Meet app, with a Discover tab and a Manage tab, templates and event pages created automatically when you save. That post was published February 3, 2026, when the experience was in public preview, and it does not give step-by-step creation instructions. As of November 15, 2026, we did not open a Microsoft page with the exact Teams scheduling labels for this route, so follow Microsoft's current Teams events documentation rather than a guess.

How to check and set the Teams events policy (admins)

Microsoft Learn's page "Manage who can schedule and attend events in Microsoft Teams" (updated November 7, 2026 in its metadata) documents the policy that decides who can create town halls.

1. In the left navigation of the Teams admin center, go to Meetings > Events policies.
2. Select an existing policy or create a new one.
3. For events optimized for large audiences, such as town halls, turn the Events optimized for a large audience toggle On or Off.
4. Select Save.

The same setting in PowerShell is the -AllowTownhalls parameter:

Set-CsTeamsEventsPolicy -Identity <policy name> -AllowTownhalls Enabled

Use Disabled to prevent organizers with that policy from creating these events. Microsoft Learn warns that if you change the value to Off after a user schedules an event, they can't run or start the event. Don't switch it off for a team that still has town halls scheduled.

Attendance is a separate setting. The Learn page documents Who can attend events optimized for a large audience, with the values Everyone, Everyone in my organization excluding guests and Everyone in my organization including guests, and the -TownhallEventAttendeeAccess parameter. By default it is Everyone.

Limitations, testing and rollback

• No rollback is documented. MC1552394 describes a retirement, not a preview. The post gives no way to keep the old creation route past December 7, 2026.
• Not stated in the post: whether the Engage button or menu entry disappears or shows a message, what error appears, and whether recurring events or templates are affected. If your organizers use recurring events, test one in the new Events experience before the cutoff.
• Edit location: Microsoft Support says to edit Engage events only in Engage, not in Outlook or Teams.
• Pilot first: before December 7, ask one organizer to create a test event through the Events experience, add a presenter and confirm the invite and recording behavior described above.
• Roadmap and Message Center can change. The mirror shows no update date as of November 15, 2026, but Microsoft can update the post. Recheck it in your admin center before the cutoff.

Privacy and admin notes

• The Message Center post does not describe data handling for this change. Recording is on by default for meetings and broadcasts in Engage events, per Microsoft Support, so organizers should know that before a pilot.
• Event content location depends on the host: the host choice of Storyline or Community determines who can attend and where content is stored.
• CSV export of event posts can be turned off by network admins in the Engage Admin Center under Content management.
• Use the Teams events policy to limit who can create events and who can attend. Note the Everyone default for attendance if you hold internal-only town halls.
• If you hold regulated communications, record where the events are stored and for how long. Microsoft's pages we opened do not give recording retention figures for these events.

For related reading on Teams policy, see Teams meeting policies for recording and lobby and Teams external access vs guest access.

What we checked

• Opened Message Center post MC1552394 on the mc.merill.net mirror on November 15, 2026: published November 13, 2026, act-by December 7, 2026, roadmap ID 537280, no update date listed. The mirror summarizes the post rather than reproducing it, so confirm wording in your admin center.
• Opened the Microsoft Support page "Organize an Engage event" on November 15, 2026 and copied the labels Events, Create event, Create new, Event, Storyline, Community and Enable broadcast or meeting.
• Opened the Microsoft Learn page on Teams events policies and cross-checked the setting Events optimized for a large audience against the -AllowTownhalls parameter; both appear in the same table on the page.
• Opened the roadmap item 537280 on the mirror: status Launched, general availability, "April CY2026", last updated May 18, 2026, which fits the "new Events experience" in MC1552394.
• Opened the Microsoft Teams blog post on the new unified Teams events experience (February 3, 2026) and confirmed the April 1, 2026 licensing statement and the 100,000-attendee capacity figure as Microsoft states them there.
• A web search for the December 7, 2026 date returned no second source; only MC1552394 gives it. The mirror is a community copy of Microsoft's post.
• Not tested on a live tenant. We could not confirm what the Engage interface shows after the cutoff, or the exact Teams scheduling labels for creating a town hall directly in Teams.

Last tested: 2026-11-15

Sources

• MC1552394: Retirement of Teams town hall event creation in Viva Engage (mirror of Microsoft 365 Message Center)
• Roadmap item 537280 (mirror of the Microsoft 365 roadmap)
• Organize an Engage event, Microsoft Support
• Microsoft Teams events: a new unified experience, Microsoft Community Hub
• Manage who can schedule and attend events in Microsoft Teams, Microsoft Learn