Microsoft Roadmap, messagecenter and blogs updates from 01-11-2025

Updated October 30, 2025: Due to emerging changes, we are postponing this feature launch. We will communicate updated launch timelines as soon as they are available. We apologize for any inconvenience.

Microsoft Purview is launching a new Personalization page that will help users personalize their individual experience on Purview.

This message is associated with Microsoft 365 Roadmap ID 483884.

[When this will happen:]

Public Preview (Worldwide): We will communicate via Message center when we are ready to proceed.

General Availability (Worldwide): We will communicate via Message center when we are ready to proceed.

[How this will affect your organization:]

The following features will be included in this initial rollout:

• Ability to pin or unpin solutions to the left navigation bar
• A new Personalization page where users can:
• Toggle visibility of the solution bar
• Choose to show solution walk-through on next sign in
• Export personalization data stored for the signed-in user
• Delete preferences one by one or all at once

The new Personalization page will be at Microsoft Purview > Settings (in top right corner) > Personalization:

On the new Personalization page, users will be able to hide or remove solution tiles and choose to show solution walk-throughs:

These changes will be available by default.

[What you need to do to prepare:]

This rollout will happen automatically by the specified dates with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation.

Updated October 30, 2025: We have updated the timeline and the content. Thank you for your patience.

Introduction

We’re updating the default behavior of Microsoft Teams Copilot in meetings. Copilot without transcription will become the default mode for newly scheduled Teams meetings where Copilot is allowed. Additionally, conversation history will now persist during meetings, improving multitasking and continuity of insights.

This update is associated with Microsoft 365 Roadmap ID 478611.

When this will happen

General Availability (Worldwide): We will begin rolling out in mid-January 2026 (previously early November 2025) and expect to complete by early February 2026 (previously mid-November 2025).

[What’s changing?]

Who is affected:

• Affected tenants: If your TeamsMeetingPolicy was created or modified before the Copilot without transcription policy option was introduced (June 2024), your tenant will be affected by this change.
• Not Affected: If your TeamsMeetingPolicy was created or modified after June 2024 when the Copilot without transcription option was introduced, your tenant will not be affected.

What will happen:

• The default Copilot policy will change from EnabledWithTranscript to Enabled for both new and existing Teams meetings where Copilot is allowed.
• Copilot and Facilitator will no longer automatically start transcription for meetings in affected tenants.
• Users must manually enable transcription to use post-meeting Copilot or Facilitator queries.
• Conversation history will persist during meetings for Copilot without transcription.
• Tenants with TeamsMeetingPolicy created or modified after June 2024 are not affected.

If adopting the new defaults:

• Review TeamsMeetingPolicy for transcription dependencies.
• Update internal documentation and training.
• Communicate to users how to enable transcription when needed.

Optional admin steps to retain current behavior:

• Update Global and Custom TeamsMeetingPolicy settings via TAC or PowerShell.
• TAC UI Portal: Navigate to Teams Admin Center and set the Copilot policy default value as required. For example, if the current default value is desired, update it to a different value, then set it back. Please ensure both TeamsMeetingPolicy and all Custom Policies are updated.
• PowerShell example to set Copilot policy to EnabledWithTranscript for all relevant meeting policies:

  get-csteamsmeetingpolicy | ? {
    $_.Identity -ne "Tag:AllOn" -and
    $_.Identity -ne "Tag:AllOff" -and
    $_.Identity -ne "Tag:Default" -and
    $_.Identity -ne "Tag:Kiosk" -and
    $_.Identity -ne "Tag:RestrictedAnonymousAccess" -and
    $_.Identity -ne "Tag:RestrictedAnonymousNoRecording"
  } | % {
    $_.Identity;
    set-csteamsmeetingpolicy -identity $_.Identity -Copilot EnabledWithTranscript
  }
      

Learn more: 

• Manage Microsoft 365 Copilot in Teams meetings and events | Microsoft Teams | Microsoft Learn
• Use Copilot without recording a Teams meeting | Copilot in Teams | Copilot | Microsoft Support

Compliance considerations

Updated October 30, 2025: We have corrected the timeline to reflect the actual rollout dates. Thank you. 

Introduction

To enhance privacy and improve meeting reliability, we’re updating how live captions and real-time text (RTT) behave in Microsoft Teams meetings. These updates ensure that captions are more secure when transcription is off and improve the stability of caption display across devices and scenarios.

This message is associated with Microsoft 365 Roadmap ID 499616.

• Targeted Release: Began September 1, 2025, completes by September 17, 2025 (previously September 15).
• General Availability:
  • Worldwide, GCC, GCC High: October 1-17, 2025 (previously September 15–29).
  • DoD: October 21-28, 2025 (previously September 25–October 3).

• When transcription is off, captions will now display only the last five minutes of dialogue, enhancing privacy by limiting visible history.
• When transcription is on, captions will show the full meeting conversation from the time transcription starts until the transcription ends.

• A previous issue where repositioning captions could cause text loss has been resolved. Captions will now remain intact when moved.
• These improvements also apply to real-time text (RTT), ensuring a consistent and reliable experience across both features.
• This update applies to Microsoft Teams on desktop and Mac platforms.

• Inform users about the new five-minute limit for captions when transcription is off.
• Update internal training materials and documentation for users who rely on live captions or RTT.
• No admin action is required to enable this feature.

Learn more:

• Use live captions in Microsoft Teams meetings | Microsoft Support
• View live transcription in Microsoft Teams meetings | Microsoft Support

Compliance considerations

No compliance considerations identified, review as appropriate for your organization.

Updated October 31, 2025: We have updated the timeline for resumption of Microsoft Entra Delete signals in Viva Glint. Thank you for your patience.

[Introduction]

To improve data traceability and support organizational compliance needs, Microsoft Viva Glint is introducing a new configuration option that allows administrators to retain the first name and last name of deleted users. Previously, while survey response data could be retained, identifying information for deleted users was not available. This update aligns with customer feedback requesting more granular control over user data retention.

This message is associated with Message ID MC1113670. 

[When this will happen:]

• General Availability: Rollout will begin mid-October 2025 and is expected to complete by late-October 2025.
• We will continue planned maintenance associated with MC1113670 in June 2026. We will now resume the processing of Entra Delete signals on July 1, 2026 (previously November 1, 2025). Users identified by these signals will be marked for data deletion in accordance with your organization’s configured User Data controls.

We have currently paused the automatic process of Delete signals received from Microsoft Entra and as a result, we will not be automatically deleting any people data from Viva Glint. During this period, there may be slight delays in processing these requests. However, all requests will be completed within 90 days of resumption of these signals on July 1, 2026. 

In the meantime, If you would like to manually delete any user data from Viva Glint, please follow the instructions here: Responding to Data Subject Requests (DSRs) in Viva Glint | Microsoft Learn.

[How this affects your organization:]

• Who is affected: Viva Glint administrators managing user data retention settings.
• What will happen:
  • A new admin toggle will allow configuration of first name and last name retention for deleted users.
  • When enabled, first and last names of deleted users will be retained.
  • When disabled, first and last names of deleted users will be replaced with “Deleted user”.
  • If raw data export is enabled, deleted user data will be exported in accordance with User Data controls.
  • Changes will only apply to deleted users from the point of feature release and going forward, not retrospectively.
  • This feature will be enabled by default at rollout.
  Screenshot 1: Admin view in Viva Glint showing the new configuration option for retaining first and last names of deleted users.

[What you can do to prepare:]

• Review your organization’s data retention policy and configure the toggle accordingly by November 1, 2025.
• Notify relevant stakeholders or helpdesk staff about this change.
• Update internal documentation if you reference Viva Glint data retention settings.

Learn more: Manage General Settings in Viva Glint

[Compliance considerations:]

Updated October 31, 2025: We have updated the content. Thank you for your patience.

Introduction

To help organizations better assess and improve their identity security posture, Microsoft Secure Score is being enhanced with new improvement actions based on Microsoft Defender for Identity recommendations. These updates provide more accurate insights and actionable guidance to strengthen your security configuration.

When this will happen:

• Public Preview: Rollout begins early November 2025, completes by mid-December 2025
• General Availability (Worldwide, GCC, GCC High, and DoD): Rollout begins early November 2025, completes by mid-December 2025

How this affects your organization:

• Who is affected: Admins managing Microsoft Secure Score and organizations with Microsoft Defender for Identity sensors deployed.
• What will happen:
  • New posture recommendation will appear in Microsoft Secure Score as improvement actions: Change password for on-prem accounts with potentially leaked credentials
  • This recommendation is visible only if your tenant has a Defender for Identity sensor deployed.
  • The update is enabled by default and requires no configuration changes.
  • No impact to end-user workflow unless acted upon by the admin.
  • Please be aware of a related Microsoft Entra ID recommendation that is recently released, titled: “Change password for accounts with leaked credentials”. The Microsoft Entra ID recommendation is focused on cloud-based user accounts, whereas the Microsoft Defender for Identity recommendation targets on-prem user accounts.

What you can do to prepare:

• No admin action is required before or after rollout.
• Review your current identity configuration to assess potential impact.
• Notify relevant administrators and update internal documentation as needed.
• Regularly review Microsoft Secure Score to monitor and act on new improvement suggestions.
• Learn more: Microsoft Secure Score 

Compliance considerations:

No compliance considerations identified, review as appropriate for your organization.

[Introduction]

Content Explorer contains significant volumes of data, and can sometimes feel overwhelming, leading to concerns about too many false positives in Microsoft Purview. To address this, we are introducing Classifier Scoping in Content Explorer. Classifier Scoping empowers customers to define exactly what data they want to see, significantly reducing noise and helping them focus on what matters most.

This message is associated with Microsoft 365 Roadmap ID 518224.

[When this will happen:]

• Public Preview: We will begin rolling out mid-November 2025 and expect to complete by early December 2025
• Worldwide: We will begin rolling out late December 2025 and expect to complete by mid-January 2026.

[How will affects your organization:]

• Who is affected: Microsoft Purview administrators using Content Explorer.
• What will happen:
  • Admins can define and scope views in Content Explorer using selected classifiers, sensitivity labels, and retention labels.

  

  • These scoped views can be saved and reused with a few clicks.
  • No changes to user workflows.
  • The feature will be available by default once rolled out; no opt-in required.

[What you can do to prepare:]

• No action is required to enable this feature.
• After rollout, admins can:
  • Define scoped views in Content Explorer using classifiers and labels.
  • Save and apply these views to streamline data analysis.

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

Agents in OneDrive lets you group files and folders together, so you can ask questions, get summaries, and find key details across your project—without having to reselect items each time. Agents are saved in your OneDrive and can be shared with your team, making collaboration and staying up to date easier. This new capability helps users work more efficiently by turning OneDrive into a workspace for AI-powered project assistance.

This message is associated with Microsoft 365 Roadmap ID 469503.

General Availability (Worldwide): Rollout will begin in mid-November 2025 and is expected to complete by late November 2025.

Who is affected: Users with a Microsoft 365 Copilot license assigned to either work or school accounts (Microsoft 365 commercial or education tenants). 

What will happen:

Users will see a new agent option in OneDrive.

How to use Agents in OneDrive:

• Create your Agent: When users first select the Copilot button in OneDrive or the +Create or upload button, a guided experience will introduce agents and walk users through how to create and use them. From there, users can create an agent from their OneDrive using the +Create or upload option and then select the Agent option (screenshot 1):

 

• Alternatively, users can select the files to include in an agent, then choose Create an agent from the Copilot toolbar dropdown menu (screenshot 2):

 

• Access your agent as a file in OneDrive (.agent extension), filter by file type “agent” (screenshot 3):

 

• Open the agent to ask questions and get answers from your documents.
• Edit or update your agent anytime to change its sources, name, or instructions (screenshot 4):

 

• Share your agent with your team to collaborate and keep everyone informed (screenshots 5 & 6):

 

No admin action is required at this time.

You may wish to:

• Communicate this change to helpdesk staff.
• Update internal documentation to reflect the new agent capabilities in OneDrive.
• Encourage users to explore agents to improve project efficiency using AI.

[Introduction:]

We’re updating the AI Disclaimer experience in Microsoft Copilot Chat based on customer feedback. Some users found the disclaimer too distracting, while others felt it was too subtle. To address this, we’re introducing admin controls that allow organizations to customize how the disclaimer appears, improving user awareness and flexibility.

[When this will happen:] 

Rollout will begin in late November 2025 and complete by:

• Worldwide & GCC: Early December 2025
• GCC High & DoD: Mid-December 2025

[How this affects your organization:]

Who is affected: All users of Microsoft Copilot Chat across all endpoints.

What will happen:

• The AI Disclaimer below the Input Box will be OFF by default.
• Admins will have a new toggle to enable the disclaimer.
  • If enabled:
    • The disclaimer will display bolded text for increased visibility.
    • Admins can configure a custom URL or use the default link to Microsoft documentation.
    • Both Starter and Premium users can see the Input Box and the AI Disclaimer (if enabled), so a Copilot license is not explicitly required for visibility.

Screenshot 1 and 2: The top image shows the default experience with no AI Disclaimer visible. The bottom image shows the AI Disclaimer with Heightened Awareness enabled by the admin. 

[What you can do to prepare:]

• Review the new AI Disclaimer toggle in the Admin Portal once available.
• Decide whether to enable the disclaimer for your organization.
• If enabling, prepare a custom URL to include in the UX. 
• Communicate this change to helpdesk staff and Copilot users.
• Update internal documentation if you reference the disclaimer experience.

Learn more: Transparency Note for Microsoft Copilot | Microsoft Support

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

To strengthen Microsoft’s security posture, we’re introducing updates to Microsoft Purview that enhance audit logging and enforce Entra conditional access policies for eDiscovery admins. These changes help ensure that sensitive content is accessed only by users who meet your organization’s security requirements.

[When this will happen:]

General Availability (Worldwide, GCC, GCCH, and DoD): Rollout will begin and is expected to conclude in late November 2025.

[How this affects your organization:]

Who is affected: Admins using Microsoft Purview for eDiscovery and subject to Entra conditional access policies.

What will happen:

• When eDiscovery admins preview a file in the Purview portal, the action will be logged under the FilePreviewed activity in Audit logs.
• eDiscovery and Compliance admins who do not meet Entra conditional access policies (such as MFA or Trusted Network Policy) will be blocked from accessing SharePoint Online content via the Purview portal.
  • Access behavior is being altered. Previously, eDiscovery Admins could access SharePoint Online content in Purview regardless of their compliance with Entra Conditional Access policies. With this update, access will be restricted for non-compliant admins, representing a change in enforcement behavior.
  • Microsoft recommends compliance with Entra policies to maintain uninterrupted access.
  • As a temporary workaround, Global admins may use the exclude Users and groups option to exempt specific eDiscovery admins from conditional access enforcement.

[What you can do to prepare:]

• Ensure all eDiscovery admins comply with your organization’s Entra conditional access policies.
• Review and update your conditional access configurations if exemptions are needed.

Learn more:

• Audit log activities | Microsoft Purview | Microsoft Learn
• How To: Configure the multifactor authentication registration policy | Microsoft Entra ID Protection | Microsoft Entra | Microsoft Learn

[Compliance considerations:]

[Introduction]

To help organizations better protect sensitive files in transit, we’re introducing a public preview for extending Microsoft Purview Data Loss Prevention (DLP) policies to the network through integration with Entra Global Secure Access Internet Access. Through this integration, organizations can intercept and inspect file traffic at the network layer and enforce actions based on DLP policy conditions. It helps prevent sensitive files from being shared with untrusted cloud applications through browsers, apps, APIs, add-ins, and more—including generative AI platforms, cloud storage, and content-sharing services—while managing alerts and incidents through Purview and Microsoft Defender.

This message is associated with Roadmap ID 522096.

[When this will happen:]

• Public preview: Rollout begins mid-November 2025 and completes by mid-December 2025.
• General availability: Rollout begins mid-June 2026 and completes by mid-July 2026.

[How this affects your organization:]

• Who is affected: Microsoft 365 tenants with E3 or E5 licenses; Admins managing Microsoft Purview DLP and Entra Global Secure Access.
• What will happen:
  • A new “Inline Web Traffic” scenario will be available in Purview DLP policy creation.
  • Admins can configure granular policies and rules to detect and protect sensitive files transmitted to over 35,000 unmanaged cloud applications.
  • Policy matches, alerts, and incidents will be managed centrally in Microsoft Purview and Microsoft Defender.
  • The feature will be available by default but requires configuration to activate.

[What you can do to prepare:]

• Ensure your GSA administrator configures the following in Entra Global Secure Access:
  • Enabled the internet access traffic profile and ensure the correct user assignments apply.
  • Configure TLS inspection and configure a TLS inspection policy.
  • Create a file policy and add a rule that specifies the action “Scan with Purview”.
  • Configure a security profile with the above policies and link it to a conditional access policy.
• Your global admin must activate Purview pay-as-you-go to enable this capability. No charges will apply during public preview.
• Review your current DLP and network configurations to assess impact.
• Communicate this change to helpdesk and security teams.
• Update internal documentation to reflect new policy options.
• For more details, refer to: Learn about data loss prevention

[Compliance considerations:]

[Introduction]

Microsoft is introducing the Employee Self-Service Agent, a custom agent that you can configure and extend to streamline HR and IT support experiences. This agent acts as a unified entry point for employees to access information and complete common workplace tasks, reducing friction and improving productivity across your organization.

This message is associated with Microsoft 365 Roadmap ID 487836.

• Targeted Release: Started early June 2025
• Public Preview (Worldwide): Started early July 2025
• General Availability (Worldwide): Begins early November 2025

[How this affects your organization:]

Who is affected:

• Employee service delivery teams (e.g HR function/IT function)
• Organizations using Microsoft 365 Copilot Studio
• Admins managing HR and IT support workflows
• Employees accessing self-service support through Copilot

What will happen:

• Admins and agent makers can configure the agent to integrate with existing systems of record and publish it.
• Employees will see Employee self service agent as a unified interface to access HR and IT support in M365 Copilot.
• No changes will be made to existing policies or user permissions by default.

[What you can do to prepare:]

• No immediate action is required.
• Review your current HR and IT support workflows and areas of most tickets to identify common employee scenarios that could benefit from enabling with ESS.
• Determine which systems of record (e.g., ticketing, HRIS) you may want to connect to the agent.
• Inform helpdesk or support teams that a new self-service agent will be available later this year.

Learn more: Overview of the Employee Self-Service agent (will be updated before rollout)

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

We’re launching a Pre-Purchase Plan (P3) for Microsoft Copilot Studio: a prepaid capacity option on Azure rails. This plan is Microsoft Azure Consumption Commitment (MACC)-eligible, offers annual commitment discounts, auto-monetizes overages at Pay-As-You-Go (PayGo) rates, and uses a single external meter that spans Copilot Studio, Dynamics 365 out-of-box (OOB) agents, and Moveworks OOB agents. Usage is externally reported under M365—Productivity & Business Process KPI.

[When this will happen:]

Customer availability begins November 1, 2025.

[How this will affect your organization:]

Who’s affected:

• IT administrators
• Procurement and finance teams (MACC)
• Platform owners for Copilot Studio, D365 OOB, and MW OOB

What’s changing:

• Purchase annual, prepaid Commit Units (CU) with tiered discounts; overages billed at PayGo rates
• A single meter aggregates usage across Copilot Studio, D365 OOB, and MW OOB
• MACC is decremented at purchase; revenue is recognized upon consumption; unconsumed credits are recognized in the final month

Copilot credit options (CU ↔ credits):

   Standard P3 (fastest):

• 1 CU = $1
• Example: 3,000 CU list price = $3,000; sold at $2,850 (5% discount)
• Converts to 300,000 credits at $0.01/credit

   Custom P3 (developer-friendly):

• 1 CU = $0.01 (CU ≡ Copilot Credit)
• Example: 300,000 CU (credits) list price = $3,000; sold at $2,850 (5% discount)
• Longer lead time (non-standard)

   P3 Mechanics:

• 1-year prepaid, use-it-or-lose-it, auto-renewing model
• Overage billed at PayGo
• Revenue recognized as consumed; remaining credits recognized in the final month

[What you can do to prepare:]

• Choose between Standard and Custom CU mapping
• Align MACC and budget with forecasted consumption
• Review procurement processes for annual prepay and auto-renew
• Coordinate with platform owners to leverage the single meter

Additional Information:

• Usage across Copilot Studio, D365 OOB, and MW OOB is metered together and reported under M365
• Custom P3 offers intuitive credit mapping but requires longer implementation lead time

[Introduction]

We’re improving external collaboration in Microsoft Teams by enabling file attachments and Loop sharing in 1:1, group and meeting chats with external users. This update improves the collaboration experience for Files and Loop and add a new control for IT admins. Specifically, Files and Loop components will be shared automatically with external participants in the chat and won’t require any action by the sender by default. Additionally, Entra B2B Guests in your organization will be able to attach and share files from their home tenant’s OneDrive or SharePoint. 

This change applies to Teams for Windows desktop, Mac desktop, and web and is associated with Roadmap ID 492625.

Screenshot 1: Files are automatically provisioned.

Screenshot 2: Files shared have an external label and always open on Web.

[When this will happen:]

• Targeted Release: Rollout begins late October 2025; expected to complete by mid-November 2025
• General Availability (Worldwide): Rollout begins mid-January 2026

[How this affects your organization:]

Who is affected:

All Microsoft Teams users in your organization who participate in 1:1, group, or meeting chats with external users, including guest and Teams for Free users.

What will happen:

With this update:

• Unless the user chooses to share File and Loop by pasting links, external users in chat will be automatically provisioned to allow frictionless collaboration.
• You can disable automatic provisioning and have the user change permissions manually by using policy controls.
• If disabled, users will have to manually provision the file to users in the chat.
• Guest users will be able to upload files from their home tenant’s OneDrive and SharePoint.
• Files shared by external users will continue to display an External tag for clarity.
• Loop components will now be rendered inside external chats in Teams.
• Recipients will access File and Loop components as B2B guests within the resource tenant. If they are not already added as guests, they will need to give consent and might need to complete MFA, depending on your company’s B2B policy, before viewing the chat content.

• No action is required to enable the feature—it will be automatically available as the rollout progresses.
• To disable the automatic provisioning behavior for files and loops set the AutoShareFilesInExternalChats attribute of TeamsMessagingPolicy to Disabled. Learn more: Set-CsTeamsMessagingPolicy documentation.
• To provide seamless Loop access experience for external users, we recommend turning on Entra B2B Guest Access. Refer to: Microsoft Entra B2B integration for SharePoint & OneDrive – SharePoint in Microsoft 365 | Microsoft Learn.
• For configuration guidance, refer to: Set-CsTeamsFilesPolicy documentation (documentation will be updated before rollout).

Compliance considerations

We've released updates to the following update channel for Microsoft 365 Apps:

• Current Channel

[When this will happen:]

We'll be gradually rolling out this update of Microsoft 365 Apps to users on that update channel starting October 30th, 2025 (PST).

[How this will affect your organization:]

If your Microsoft 365 Apps clients are configured to automatically update from the Office Content Delivery Network (CDN), then no action is required.

If you manage updates directly you can now download this latest update and begin deployment.

[What you need to do to prepare:]

To get more details about this update view the following release notes:

• Current Channel

• Receiving SIP X-Headers: Voice agents can access incoming SIP X header values by defining variables that match the header names.
• Sending SIP X-Headers: During external phone number transfers, voice agents can select up to five variables to pass as SIP X headers.

• Historical and real-time data visualization
• Ability to pause and resume proactive engagements
• Customizable reporting
• Intuitive user interface
• Integration with third-party systems
• Scalability to accommodate the needs of growing proactive engagements

Updated May 28, 2024: To ensure customer confidence in our product line, we are extending the support for Teams Live Events beyond the previously announced deadline of September 30th, 2024. We have concluded through customer feedback that this change to our initial deprecation plan, by maintaining support for Live Events, will empower customers to produce large events as established and provide more time to upgrade to town hall, our new digital streaming event solution for large events, on their own schedule. Town hall will continue to serve as the platform where we will deliver new product value to our customers.

Teams Live Events will continue to be supported. We want to ensure that customers can upgrade to town hall on their own schedule as we work to bring new features and capabilities to town hall. Town hall is already available for commercial customers in public clouds, and we are adding new features regularly.

If you are using Teams Live Events for your large-scale digital events, you can continue to do so past the previously announced deprecation date of September 30th, 2024. However, we encourage you to try town hall, which offers a more modern and interactive experience for your live events. 

You don’t need to do anything at this time to continue using Teams Live Events. If you have directed your organization to not schedule Live Events after September due to the deprecation announcement, you may now schedule Live Events past September 2024. For more information please refer to our blog post regarding this announcement: Updates for Town Hall in Microsoft Teams and Teams Live Events.

 —Original message below for reference—

With the introduction of Town halls in Microsoft Teams, Teams Live Events will be retired for commercial customers on September 30, 2024. This provides commercial customers with a 12-month window to prepare for the retirement and transition off Teams Live Events. 

[When this will happen:]

September 30, 2024

[How this will affect your organization:]

After September 30, 2024, Teams Live Events will no longer be supported, and access will be discontinued. Customers will not be able to schedule, start, or join any events on Teams Live Events after this date. Existing recordings will be available to access until December 31, 2024. If customers want to retain any recordings from prior events, they will need to download the recordings and upload them to a different location before December 31, 2024. Between now and September 2024, customers can continue to use Teams Live Events with no change in their existing experience. However, our recommendation is that customers (both existing and new) transition to and start to use town halls as it becomes generally available on October 5, 2023.

[What you need to do to prepare:]

To prepare your organization for the transition we advise:

• Start to use town hall as it becomes generally available on October 5.
• Learn more about town hall when documentation becomes available on adoption.microsoft.com and learn.microsoft.com on October 5.
• Start planning to download recordings your organization wishes to retain before December 31, 2024.