On June 30, 2026, Microsoft will pull the plug on Teams Live Events. But the real deadline already hit: since February 3, no organization can schedule a new Live Event past that date. If you work in IT, internal communications, or executive production, your window to act is closing fast. Existing Live Events scheduled before the cutoff can still run through February 28, 2027, but relying on that grace period is a gamble—every day you wait shrinks your time to rebuild, test, and stabilize the replacement.

This isn’t a vague deprecation warning. It’s a sequenced shutdown with concrete dates that affect what you can create, who can present, and how your audiences will join. Here’s what changed, what it means for you, and exactly how to move your critical broadcasts to Microsoft’s new town hall format—without breaking anything on the day of the event.

The Lock Is Active: What’s Already Stopped

Microsoft originally signaled a “July 2026” retirement window, but the enforcement began much earlier. According to the official Microsoft Learn documentation, the timeline is now locked at three crucial points:

  • February 3, 2026 – Scheduling freeze. No one can create a Teams Live Event scheduled for any date after June 30, 2026.
  • April 15, 2026 – Viva Engage (formerly Yammer) stopped creating new Live Event instances, cutting off another integration path.
  • June 30, 2026 – The platform and its Microsoft Graph APIs retire. After this date, only existing events that were scheduled before the freeze can be managed, and that management window lasts only until February 28, 2027.

That means if you were planning to roll out a new quarterly town hall for Q3 2026 using the old Live Event tool, you’re already too late. The scheduling interface will reject any date beyond the cutoff. Events already on the books are grandfathered, but you can’t add new ones.

For IT teams, the shock may come from integrations you forgot about. Dynamics 365 could schedule Live Events, and those are now equally constrained by the June 30 boundary. If your marketing or sales teams have semi-automated webinars flying out of CRM, those pipelines may break silently until someone tries to schedule the next one.

What This Retirement Means for You

Microsoft’s move isn’t just a rebranding. It’s a shift from a specialized broadcast tool to a unified, template-driven event platform. The impact hits three groups differently.

For IT Administrators

The primary burden is on you. You own the tenant-wide policies, licensing, and continuity of service. Starting now, you need an immediate inventory of every scheduled Live Event across all departments. That includes events owned by communications, HR, investor relations, training, and executive offices—not just those visible to the central IT event calendar.

Licensing also changed. On April 1, 2026, Microsoft’s Teams Enterprise licensing update made town hall and webinar capabilities more broadly available without extra add-ons for most users. That lowers the barrier to migration, but it doesn’t remove the need to check capacity. Town halls have attendee limits tied to licensing; events above standard thresholds require an Attendee Capacity Pack. If your CEO’s all-hands routinely draws 15,000 people, you need to verify that the assigned organizer’s license can scale that high—not just assume because Live Events handled it.

For Event Organizers and Producers

Producers and presenters will face a different workflow. Town halls are not a one-to-one replica of Live Events. The presenter experience, Q&A controls, external guest access, and recording management have shifted. If your team relies on external encoder hardware (like a Tricaster or Wirecast), note that the “external app or device” production method isn’t supported in town halls in the same way; you’ll need to adopt the Teams desktop client or a Teams-certified encoder for streaming.

Rehearsals become essential. Microsoft added a town hall restart capability for desktop and Mac clients, which is a welcome safety net—but it’s no substitute for a full dry run with external attendees and the exact network conditions of event day.

For Attendees and External Guests

The attendee experience changes, too. Live Events allowed true anonymous public viewing without any sign-in. Town halls support anonymous attendees, but the join flow and interactivity (like moderated Q&A) differ. If you’ve published join links that will be live for months—on public websites, marketing emails, or printed invitations—every one of those URLs must be updated. A broken link is the most visible, most embarrassing failure mode, and it hits days before the broadcast, not during.

The Road to Retirement: How We Got Here

Teams Live Events launched in 2019 as a way to hold large-scale, one-to-many broadcasts with up to 10,000 attendees. It leaned on a combination of Teams client, Stream, and external encoder support. But the architecture was separate from the core Teams meeting engine, requiring different policies, licensing, and production tools.

Microsoft began signaling the shift in 2024 when it introduced town halls—a unified event type that brings the large-audience format under the same meeting-infrastructure umbrella as webinars and regular Teams meetings. Town halls offer some capabilities Live Events never had (co-organizer support, real-time reactions, and tighter Microsoft eCDN integration), while dropping others (PPT sharing as a separate input, multi-language captions at event time). The April 2026 licensing changes were the strategic nudge: by baking town hall features into standard Enterprise plans, Microsoft removed a cost objection for many organizations.

The current retirement timeline is not unexpected, but the scheduling lock three months before the actual retirement is tighter than many admins anticipated. If you thought you had until July to plan, you’ve lost months.

Your Migration Playbook: Five Steps to a Safe Transition

The worst thing you can do is treat this as a bulk “convert all events” project with a single script. Each event has its own audience, production requirements, and risk profile. Here’s how to move forward.

1. Inventory Every Live Event—Now

Don’t assume your central IT calendar shows everything. Pull a report from the Teams admin center, PowerShell, or Graph API for all Live Events scheduled across the tenant. Include events sourced from Dynamics 365, Viva Engage, and any third-party scheduling tools that write into the Teams calendar. For each event, record:

  • Date, time, organizer, producers, presenters
  • Expected audience size and type (internal, guests, anonymous)
  • Production method (Teams client, external encoder)
  • Whether the event is part of a recurring series or a copied template
  • Joining URL, registration links, and all places those links are published
  • Recording and reporting destinations

This list will drive every decision you make next.

2. Classify Each Event: Keep, Rebuild, or Replace

Go through the inventory and assign one of three labels:

  • Keep (grandfather): Only for events that are already scheduled, fall within the February 28, 2027 operating window, and are too far along to safely change—invitations sent, production rehearsed, executive approvals locked. Grandfathering is a temporary exception, not a strategy. Document why you’re keeping it, who owns it, and its end date.
  • Rebuild as a town hall: For all recurring series, business-critical broadcasts, and events with long-lived public links. This means creating a brand-new town hall from scratch—not copying the Live Event object—and validating every production element.
  • Replace with a webinar or meeting: Not every event needs broadcast scale. Smaller, interactive sessions may fit better in a Teams webinar or standard meeting. Don’t force a town hall just because Live Events is going away.

3. Set Up Town Hall Policies and Licensing

Before you rebuild a single event, go to the Teams admin center under Meetings > Events policies. Select or create a policy, then:

  • Enable town hall scheduling for the intended organizers.
  • Configure who can attend (everyone, people in your org, etc.).
  • Confirm that the organizer’s license includes town hall features. For events above the default capacity, procure an Attendee Capacity Pack and assign it to the actual host.

Test the policy with real organizer accounts—global defaults don’t always translate when service principals or group assignments are involved.

4. Rebuild and Test Each Town Hall

For every migrated event, create a fresh town hall, assign new production roles, and test thoroughly:

  • Recreate the presenter and producer lineup; guests need a new join flow.
  • Test external attendee access and anonymous join, if applicable.
  • Validate Q&A moderation, captions, recording storage, and presenter transitions.
  • Run a full rehearsal with managed devices, external attendees, and the network you’ll use on event day.
  • Replace every Live Event URL in invitations, websites, emails, QR codes, and support docs. Assign one person to verify links from outside the tenant.

5. Close the Loop on Reporting and Recordings

Live Events reports and recordings won’t magically map to town hall equivalents. Before decommissioning an old event, document what data your business actually needs: attendee join times, duration, engagement, caption files, recording locations. Then run a town hall pilot and confirm the outputs satisfy audit, compliance, and communications requirements. If something is missing, identify an alternative data source—don’t wait until the first quarterly review to discover the gap.

Looking Ahead: Life After Live Events

Once June 30 hits, the workflow simplifies because no new Live Events can be created. But don’t relax yet. Maintain a register of all grandfathered events through February 28, 2027, each with an accountable owner, rehearsal date, support plan, and retirement date for associated documentation. Remove Live Events from internal request forms, playbooks, training materials, and architecture diagrams. Update help-desk scripts so frontline staff don’t guide users to “just create a Live Event.”

Microsoft’s shift to town halls is ultimately a good thing: one set of policies, one licensing model, and a more resilient platform. But the transition demands hands-on project management in the next few months—not just a memo. The scheduling lock is already in your rearview mirror. The next big date is June 30, and the events you plan to run after that need to be born as town halls.