Microsoft Roadmap, messagecenter and blogs updates from 18-09-2025

Updated September 17, 2025: We have updated the timeline. Thank you for your patience.

Microsoft Teams Events invite emails will be separated based on the role of the participant. Event organizers will get an email explaining the specific roles of participants in the event. Similarly, each presenter will get a separate calendar invite, allowing the organizers of town halls to maintain separate invites for attendees. 

This message is associated with Microsoft 365 Roadmap ID 476488.

[When this will happen:]

Targeted Release: We will begin rolling out late March 2026 and expect to complete by early April 2026.

General Availability (Worldwide): We will begin rolling out early April 2026 and expect to complete by mid- April 2026.

General Availability (GCC, GCC High): We will begin rolling out mid-April 2026 and expect to complete by early May 2026.

[How this will affect your organization:]

This feature update allows the organizers of town halls to maintain separate invites for attendees.

[What you need to do to prepare:]

This rollout will happen automatically with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate.

Updated September 17, 2025: After further review, this has been delayed to a later date. We apologize for any inconvenience.

Introducing a new feature that will bring interactive agents into Microsoft Teams meetings and 1-on-1 calls. Users will be able to engage with agents as a group or privately, with zero-state prompts and history support for seamless interactions. Before this rollout, only agents built on Microsoft Copilot can support sessions, which means they can remember the context of previous interactions in the same session, for more relevant responses. Custom agents do not yet have session support.

After this rollout, all agents from Microsoft 365 Copilot Chat and Microsoft Copilot Studio will be available for users in their meetings and calls. This feature will allow developers to invite colleagues to give feedback and securely test agents, without affecting sensitive data or production channels.

A Microsoft 365 Copilot license or a Microsoft 365 license is required to use this feature. As part of the Microsoft 365 SKUs, if users have access to declarative agents in Microsoft Copilot Chat, agents are available in their meetings and calls. No license is required for custom engine agents.

This message applies to Teams for Windows desktop, Teams for Mac desktop, and Teams for the web.

This message is associated with Microsoft 365 Roadmap ID 490564.

[When this will happen:]

Targeted Release: We will communicate via Message center when we are ready to proceed. 

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

[How this will affect your organization:]

After this rollout, users will be able to discover and acquire new agents (and view installed ones) from the existing apps pane in meetings by using @mentions or the + button in the compose box in chat.

Benefits:

• Easy access and interaction with agents during meetings and calls
• Seamless interactions with zero-state prompts and history support
• Private and group-scoped agents for personal assistance and for improved group collaboration

This feature will be available by default. No action is required to enable this feature for meetings and 1-on-1 calls.

Users will be able to privately interact with an agent in their meetings and calls. In this screenshot, a user begins a private chat with the Contoso agent to ask questions related to the context of the meeting:

Users can choose to escalate a private agent interaction to the group. In this screenshot, a user has added a private agent. The user can then share the agent to the group, adding it to the meeting chat for everyone to view and interact with the agent:

[What you need to do to prepare:]

This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your users about this change and update your relevant documentation.

To prepare for rollout, admins can pre-pin meeting agents for their tenants, enabling users to easily discover and use the most relevant agents for their work.

Learn more: Agents for Microsoft 365 Copilot | Microsoft Learn (will be updated before rollout)

September 17, 2025, Update: The rollout to Word, Excel, PowerPoint and OneNote has started and is expected to complete in the coming weeks.

Updated July 29, 2025, Update: The rollout for Word, Excel, PowerPoint and OneNote has been delayed to mid-August. The original timing has been updated in the original message. Additionally, Copilot Chat in the apps will respect the most recent user state (open or closed) when opening a file. 

We’re excited to announce that we are making Copilot Chat available as a side-by-side experience in Word, Excel, PowerPoint, Outlook, and OneNote to help users access AI in their flow of work.

Copilot Chat in Word (Windows desktop) for users without a Microsoft 365 Copilot license. UI elements subject to change.

Users can open Copilot Chat from the app ribbon. Copilot Chat in the apps will respect the most recent user state (open or closed) when opening a file.  

Copilot Chat will be available in these apps for users with a Microsoft 365 Copilot license, and for users without a Microsoft 365 Copilot license who have pinning enabled. We will update the text of the Pin Microsoft 365 Copilot Chat admin setting to reflect its expanded scope across Microsoft 365 apps.

Pin Microsoft 365 Copilot Chat in the Microsoft 365 admin center: Existing setting with updated language

This message is associated with Microsoft 365 Roadmap ID 494830

[When this will happen:]

General Availability:

• • Outlook for Web, new Outlook for Windows, and classic Outlook for Windows: Rollout of this change starts in late June and completes in the weeks following.
• • Outlook for Mac: Rollout of this change for Mac starts in mid-July and completes in the weeks following.
• • Word, Excel, PowerPoint, OneNote (Web, Mac, Windows): Rollout of this change starts in mid-August and completes in the weeks following.
  • Windows: Current Channel rollout will start in mid-August. Monthly Enterprise Channel rollout will be included as part of Patch Tuesday in September.
  • Mobile (Word/PowerPoint) / iPad (all) rollout will start no earlier than mid-August.

[What you need to do to prepare:]

No admin action is required. However, if your Pin Microsoft 365 Copilot Chat admin setting is configured to “Do not pin,” you should adjust it to “Pin” if you want your users without a Microsoft 365 Copilot license to access Copilot Chat in their Microsoft 365 apps.

Learn more about pinning and managing Copilot Chat: Manage Microsoft 365 Copilot Chat | Microsoft Learn.

[Compliance considerations:]

• Does the change alter how existing customer data is processed, stored, or accessed? No.
• Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data? No. 
• Does the change provide a new way of communicating between users, tenants, or subscriptions? No. 
• Does the change provide end users any new way of interacting with generative AI? No.

Updated September 17, 2025: We have updated the timeline. Thank you for your patience.

Introduction

Starting September 9, 2025, we will begin retiring the ‘Mobile devices’ page from the Settings module in Outlook Web Access and new Outlook. This change simplifies device management and aligns with modern tools that offer more robust controls for administrators and end users.

When this will happen

• Start: October 6, 2025 (previously September 9)
• Complete: November 6, 2025 (previously October 9)

How this will affect your organization

After this change, users will no longer be able to manage mobile device connections to their Microsoft 365 Exchange mailbox directly from Outlook Web Access or new Outlook. Instead, they should use one of the following supported alternatives:

• Microsoft Intune (Endpoint Manager): For administrators to monitor, enforce policies, and remotely wipe devices. 
• My Account portal: For users to view and manage their connected devices.
• iOS and Android native tools: For remote wipe capabilities in case of lost or stolen devices.

What you need to do to prepare

No admin action is required. This change will roll out automatically. We recommend:

• Informing your users about the upcoming change.
• Updating internal documentation.
• Sharing the alternative device management options listed above.

Learn more: 

• Mobile devices options in Outlook on the web | Microsoft Support (Article will be updated once this change takes effect.)
• Learn about managing and securing your devices in Microsoft Intune | Microsoft Learn
• Manage your work or school account connected devices from the Devices page | Microsoft Support
• Erase a device in Find Devices on iCloud.com | iCloud User Guide | Apple Support
• Find, secure, or erase a lost Android device | Google Support

Compliance considerations

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

Updated September 17, 2025: We have updated the timeline. Thank you for your patience.

Introduction

Connectivity changes between cmdlets and other M365 services like SharePoint and Exchange will need a new flag to be specified. Starting August 31, 2025, customers will need to use at least Exchange Online PowerShell v3.9.0 and later, with – EnableSearchOnlySession parameter when running Connect-IPPSSession to run the following eDiscovery cmdlets.  

When this will happen

This change will take effect on September 26, 2025 (previously September 19).

How this affects your organization

To maintain functionality and align with modern authentication standards, customers must use Exchange Online PowerShell v3.9.0 and later and include the EnableSearchOnlySession parameter when running Connect-IPPSSession to execute the following cmdlets:

• New-ComplianceSearchAction
• New-CaseHoldPolicy, Set-CaseHoldPolicy, Remove-CaseHoldPolicy
• New-CaseHoldRule, Set-CaseHoldRule, Remove-CaseHoldRule
• New-ComplianceSecurityFilter, Set-ComplianceSecurityFilter, Get-ComplianceSecurityFilter, Remove-ComplianceSecurityFilter

This change does not impact users accessing eDiscovery through the Purview portal. These cmdlets also remain incompatible with Certificate-Based Authentication (CBA).

You are receiving this message because one or more users in your organization are actively using these eDiscovery features.

What you can do to prepare

• Update scripts and workflows to include the -EnableSearchOnlySession parameter when connecting to Security & Compliance PowerShell.
• Ensure your organization is using Exchange Online PowerShell version 3.9.0 or later.
• For more information, visit: Learn about eDiscovery solutions in Microsoft Purview

Compliance considerations

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

Updated September 17, 2025: We have updated the timeline. Thank you for your patience.

Introduction

We’re introducing the Microsoft 365 Copilot agents report, a new Power BI report available in Microsoft Viva Insights. This report provides visibility into the usage of declarative agents, which extend Microsoft 365 Copilot capabilities. It enables leaders and admins to understand adoption trends across their organization and explore usage patterns for individual agents.

This new feature is associated with Microsoft 365 Roadmap ID 488104.

When this will happen

Public Preview (Worldwide): We will begin rolling out in early October 2025 (previously mid-September) and expect to complete by mid-October 2025 (previously late September).

General Availability (Worldwide): We will begin rolling out in early December 2025 and expect to complete by late December 2025.

How this affects your organization

The report will be available to leaders, delegates, managers, and analysts with access to the Reports page in Viva Insights. It includes:

A summary of agent adoption over time, agent responses, and usage by creator type, including a preview of top agents used:

Agent usage within Microsoft apps that include Copilot experiences:

A list of agents used in your organization, sorted by active users:

A deep dive into individual agent usage and retention, segmented by organization:

In aggregated metrics, insights from all in-scope agents will be included. To protect employee privacy, individual agent metrics will only be shown if usage meets the minimum group size threshold.

What you can do to prepare

• Review the impact of this report for your organization.
• Consider engaging your works council if applicable.
• Update training materials and documentation.

Learn more: 

• Copilot Analytics introduction | Viva Insights | Microsoft Viva | Microsoft Learn
• Customize Viva Insights privacy settings – Minimum group size | Viva Insights | Microsoft Viva | Microsoft Learn
• Declarative agents for Microsoft 365 Copilot overview | Extensibility | Microsoft 365 Copilot | Microsoft Learn

Compliance considerations

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

Updated September 17, 2025: We have updated the timeline. Thank you for your patience.

Introduction

We’re introducing a new Open in Word action button in Microsoft 365 Copilot Chat. This feature allows users to seamlessly transfer Copilot-generated responses into Microsoft Word for further editing, formatting, or collaboration. It enhances productivity by bridging AI-generated content with familiar document workflows.

When this will happen

General Availability (Worldwide): Rollout begins in late September 2025 (previously mid-September) and is expected to complete by early October 2025 (previously late September).

How this affects your organization

Users with a Copilot license will see a new Open in Word button within Microsoft 365 Copilot Chat. This feature is on by default and requires no configuration. It enables users to move Copilot responses directly into Word, streamlining content creation and editing workflows.

There is no impact to existing workflows or user permissions. The feature is designed to enhance usability without requiring training or support.

What you can do to prepare

• No admin action is required. The feature will be available automatically to all users with a Copilot license.
• You may wish to inform users about this new capability to encourage adoption and improve productivity.

Compliance considerations

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

Updated September 17, 2025: We have updated the timeline. Thank you for your patience.

Introduction

Viva Engage is introducing a successor to legacy Private Content Mode (PCM) in Yammer: When explicitly enabled, Verified admins and Engage admins will be able to open, view, and take moderation actions on conversations in private communities they are not members of. This capability is intended to support timely moderation and safety response without requiring admins to join each private community. Network admins and corporate communicators are not included in scope. This is a feature available to all Microsoft 365 tenants but requires an explicit, per‑admin opt‑in via a toggle in the Engage Admin Center.

This message is associated with Microsoft 365 Roadmap ID 498493.

When this will happen

General Availability (Worldwide): We will begin rolling out mid-September 2025 and expect to complete by late September 2025.

How this affects your organization

When a Verified admin or Engage admin (Yammer administrator in Entra) turns on the new Private Content Mode toggle in the Engage Admin Center:

• They can view community feed, conversations, post conversations and moderate them for any private community that they are not a member of.
• Moderation actions supported in private communities (without membership) include delete, mute, close, plus other standard conversation actions. Admins may also start new conversations or reply in those communities; such activity appears in their All-activity feed on their storyline.
• Manage certain community settings like managing community experts, the files tab being shown. You can learn more on what they can and cannot do in the Monitor private content in Viva Engage documentation – which will be updated at the time of general availability.
• Private content mode will persist for that particular admin user until it is explicitly disabled in the Engage admin center.  

To enable/disable this mode:

Go to Engage Admin Center > Governance & Compliance > Data Management > and toggle Private Content Mode On or Off.

While enabled, a persistent, non‑dismissible banner appears across the Engage web UX. 

Important limits:

• Private messages can only be viewed via data export or the ediscovery tool going forward.
• Community specific files and events will not be visible in private communities unless the admin is a member; admins also cannot attach media/files when posting in such communities while operating under PCM. Access to SharePoint‑scoped content remains governed by SharePoint/Entra permissions.
• No accidental discovery: Private communities the admin isn’t a member of will not appear in Home feed and digests: content is only reachable via community navigation, or direct links.
• Network Analytics: no change to aggregation. Admins may continue to see aggregate counts, but drill‑down views only include posts from public communities or communities they are a member of.

What you can do to prepare

• Decide who should have access: Limit enablement to Verified admins and/or Engage admins with moderation responsibilities.
• Update policies and training: Clarify appropriate use of this mode (purpose‑bound moderation, least‑privilege, no browsing).
• Plan for audit and oversight: The enablement/disablement of this mode is audit‑logged (who and when). Review your audit pipelines and retention to ensure these events are captured and monitored. 

Compliance considerations

Updated September 17, 2025: We have updated the timeline. Thank you for your patience.

[Introduction:]

We’re introducing a new Library experience in the Microsoft 365 Copilot app. Library provides a central, visual-first destination in the Microsoft 365 Copilot app where users can easily access their Copilot-generated content like images and Pages and as Copilot-generated content shared with them. This experience helps users easily find and manage their Copilot-generated content in one place, streamlining productivity and reducing content fragmentation.

• Targeted Release (Worldwide): Rollout begins in early October 2025 (previously late September) and is expected to complete by early October 2025 (previously late September).
• General Availability (Worldwide): Rollout begins in mid-October 2025 (previously late September) and is expected to complete by mid-October 2025 (previously late September).

Who is affected:

• All users with Copilot chat enabled in Microsoft 365.

What will happen:

• A new Library section will appear in the Microsoft 365 Copilot app, in the left navigation menu.
• Library will consolidate Copilot-generated images (from Copilot Chat and Create experiences) and Copilot Pages into a single, unified view.
• The Pages section will be removed from the left navigation menu in the Microsoft 365 Copilot app. Users can find their existing Pages in the new Library section instead. There is no change to the experience to create a new Page via Copilot Chat.
• Library is on by default for users with Copilot chat enabled.
• If Copilot chat is disabled by the admin, the Library will not be available.
• No changes to existing admin policies or configurations.

• No admin action is required.
• There are no new controls or configuration steps associated with this change.
• Review the following documentation for more details: Copilot pages for IT Admins – Sep 2024 update 

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

Updated September 17, 2025: We have added additional information to the “Admin action” bullet in the “Chat history transition” section.

[Introduction]

As announced in MC1096218, we are making Copilot Chat available as a side-by-side experience in Word, Excel, PowerPoint, Outlook, and OneNote to help users access AI in their flow of work. Users can open Copilot Chat from the app ribbon. Copilot Chat in the apps will respect the most recent user state (open or closed) when opening a file. During this transition, some previous Copilot Chat features available to licensed Microsoft 365 Copilot users in Word and PowerPoint will be improved, retired, or temporarily unavailable as we create a more unified Copilot Chat experience.

[When this will happen:]

• See MC1096218 for the latest on rollout of the new Copilot Chat experience.
• Feature availability in the new Copilot Chat experience in Word and PowerPoint varies by platform and capability. See the feature breakdown below.

[How this will affect your organization:]

Word features:

PowerPoint features:

Chat history transition

The new Copilot Chat experience in apps introduces shared memory and unified chat history across Microsoft 365 apps and the Microsoft 365 Copilot app, creating a more consistent experience. With this update, previous in-app chat history will not be accessible in the new experience.

• What’s changing: Chat history from the previous in-app chat experience in Word and PowerPoint will no longer be accessible.
• Why: The experience improvements are built on a new system and chat history will start fresh.
• Admin action: If needed, tenant admins may use audit logs to retrieve previous chat history in the apps, which they can find by searching the audit log. Users cannot download or save the previous in-app chat history themselves.
• New experience: Copilot Chat will maintain its own history, shared across all supported apps.

User experience images

Image 1: PowerPoint – Translate a presentation

Image 2: PowerPoint – Add speaker notes to current presentation

Image 3: PowerPoint – Create a presentation in the current presentation

Image 4: PowerPoint – Add a slide to the current presentation

Image 5: Word – Generate an audio overview of your document

[What you need to do to prepare:]

No admin action is required to reenable these features once they become available. You may want to update user materials to reflect these changes.

Updated September 17, 2025: We have updated the title and content. Thank you for your patience.

We’re expanding Microsoft 365 Copilot Search capabilities within Microsoft 365 Admin Center to AI admin and Global reader roles. This is to provide organizations with enhanced control and flexibility in managing AI-powered search experiences. AI admin role enables designated admins to configure, monitor, and govern Copilot Search capabilities across their tenant. Global reader roles provide read-only capabilities to Acronyms and Bookmarks configuration in Copilot Search. 

General Availability (Worldwide): Rollout begins late September 2025. 

• Admins assigned AI Admin Role will be able to manage Copilot Search settings and capabilities for their organization.
• Admins assigned Global Reader Role will be able to have read-only capability Copilot Search settings for their organization.
• This feature is on by default for tenants with eligible licenses and assigned roles.
• No changes will be made to existing admin roles unless explicitly assigned.

• Ensure that designated admins are assigned the AI Admin Role and Global Reader role.
• Confirm that your organization has the Microsoft 365 Copilot license.
• Review role assignment practices in Microsoft Entra ID to manage access.

Learn more: About admin roles in the Microsoft 365 admin center – Microsoft 365 admin | Microsoft Learn

Compliance considerations:

[Introduction]

We’re introducing Viva Amplify in SharePoint, a new capability that enables communicators to distribute SharePoint news posts across multiple Microsoft 365 channels—including Outlook, Viva Engage, Teams, and additional SharePoint sites. This enhancement helps streamline content distribution and improve audience reach, all from within the SharePoint experience.

Screenshot: Amplify from SharePoint

This message is associated with Microsoft 365 Roadmap ID 473450.

• Target Release: Scheduled for early October

• General Availability: We will begin rolling out late September 2025 and expect to complete by mid-October 2025.

Who is affected: Users with a Viva Amplify license who create or manage SharePoint news posts.

What will happen:

• To Amplify a news post, first ensure the post is published. Once published, the Amplify button will appear in the SharePoint news post toolbar for users with edit access.
• Content is automatically optimized for each endpoint—no manual formatting required.
• Users with edit access to a published SharePoint news post can click the Amplify button in the toolbar to select channels and audiences, then publish the content across Outlook, Viva Engage, Teams, and other SharePoint sites.
• After a news post is amplified, communicators can select Analytics from the toolbar to view detailed engagement metrics. The Amplify Analytics help users understand how content is performing and where it’s having the most impact.
• Engagement metrics include (but are not limited to)
  • Total views
  • Unique views
  • Dwell time
  • Reactions
  • Engagement metrics by channel
• These insights help communicators analyze performance and tailor future content for better reach—all without leaving the SharePoint interface.

• No admin action is required unless you’ve created internal guidance for end users.
• Ensure relevant users have Viva Amplify licenses.
• Review and update any internal documentation or helpdesk materials that reference SharePoint news publishing.
• Communicate this change to content creators and corporate communicators.

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

To improve the accuracy of Microsoft Secure Score and better reflect your organization’s security posture, we’re updating the improvement actions related to Microsoft Defender for Identity. This update introduces new posture recommendations that will appear as Secure Score improvement actions, helping you identify and remediate potential identity risks more effectively.

• Public Preview: Begins mid-October 2025; expected completion by mid-November 2025.
• General Availability (Worldwide, GCC, GCC High, DoD): Begins late October 2025; expected completion by late November 2025.

Who is affected:
Organizations with Microsoft Defender for Identity sensors installed in their identity infrastructure.

What will happen:

• New posture recommendations will be added to Microsoft Secure Score as improvement actions:
• Identify service accounts in privileged groups
• Remove stale Active Directory accounts
• Identify Entra ID privileged accounts that are also privileged in Active Directory
• Locate accounts in built-in Operator Groups
• Disable Entra Seamless SSO
• These recommendations will be available by default.
• Your Secure Score will update automatically based on these new actions.

• No admin action is required before or after rollout.
• Review your current configuration to assess potential impact.
• Notify your identity and security admins about the upcoming changes.
• Update any internal documentation that references Secure Score or Defender for Identity.
• Regularly review Secure Score improvement actions to stay informed of new recommendations.

Learn more: Microsoft Secure Score documentation

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

[Introduction:]

Microsoft Teams introduced a new SlimCore-based optimization for Citrix VDI environments and Windows endpoints in late 2024. This update delivered improved performance, reliability, and quality compared to the legacy WebRTC-based optimization. It also unlocks new features such as Gallery view (3×3 and 7×7), QoS, HID support, custom backgrounds, hardware acceleration, and 1080p video. Microsoft recommends enabling this optimization ahead of the upcoming WebRTC deprecation announcement.

[When this will happen:]

This update is available now. Microsoft recommends configuring your environment as soon as possible to ensure continued access to new Teams features.

Who is affected: Admins managing Citrix DaaS/CVAD environments where Microsoft Teams is deployed

What will happen:

• You are receiving this message because we detected that your Citrix DaaS/CVAD environment is not configured to allow the custom virtual channels needed by Microsoft Teams so it can optimize users with the SlimCore architecture.
• If the virtual channels are not whitelisted, Microsoft Teams will only be able to optimize using the legacy WebRTC-based offloading.
• Since the new SlimCore-based optimization is where all new features will be introduced, Microsoft strongly recommends IT administrators reconfigure Citrix Studio policies.
• SlimCore-based optimization will not be available until the Citrix Studio policy that allows virtual channels is updated.
• Users will miss out on new Teams features and performance improvements.
• Microsoft will deprecate WebRTC optimization in a future update.

[What you can do to prepare:]

To enable SlimCore-based optimization:

• Review and update the Virtual channel allow list policy in Citrix studio.
• Whitelist the following virtual channels: MSTEAMS, MSTEAM1, and MSTEAM2.
• Deploy the Citrix Plugin alongside the Citrix Workspace app. This plugin is a client-side component that terminates the custom virtual channel on the Workspace app. 
• Refer to the configuration article for detailed steps: New VDI solution for Teams | Microsoft Teams | Microsoft Learn

[Compliance considerations:]

Support for Visio 2016 and 2019, Microsoft Project 2016 and 2019, and several other products will also end on October 14, 2025. Organizations using these products should upgrade as soon as possible to maintain security, compliance, and performance.

[When this will happen:]

October 14, 2025

[Impact on your organization:]

After end of support, Office 2016 and Office 2019 suites, standalones, and servers will no longer receive security updates or other fixes, and no technical assistance will be available for devices still running them. Continuing to run unsupported software may expose your organization to security vulnerabilities and compliance risks and may affect the reliability and performance of services.

[What you can do to prepare:]

To mitigate these risks while maintaining access to desktop Office apps, we recommend upgrading devices to a Microsoft 365 or Office 365 suite that includes Microsoft 365 Apps (for enterprise or for business). Microsoft 365 Apps provides always-up-to-date versions of familiar apps like Word, Excel, and PowerPoint for desktop, mobile, and web with continuous support under the Modern Lifecycle Policy, and is eligible for use with the Microsoft 365 Copilot add-on.

For scenarios that require a fully disconnected solution, we recommend upgrading to Office LTSC 2024. Office LTSC 2024 includes a subset of the value in Microsoft 365 Apps and will be supported until October 2029 under the Fixed Lifecycle Policy.

Take steps to prepare for this transition with the following resources:

• Read the upgrade guidance for an overview of how to move from Office 2016 or Office 2019 to Microsoft 365 Apps.
• Consider engaging Microsoft FastTrack, a Microsoft support service, for moving to Microsoft 365.

Plan ahead to avoid potential disruptions and keep your organization’s software environment secure and up to date. 

[Compliance considerations:]

Starting in October 2025, Microsoft Edge version 141 will introduce the Adobe-powered PDF viewer as the default experience for enterprise users on Windows. This change enhances performance, accessibility, and compatibility, and introduces exclusive enterprise features. It follows our earlier public announcement and aligns with Roadmap ID 489231 and MC post MC1072406.

General Availability: Migration will occur on a phased rollout. Rollout will begin October 2025 and will complete March 2026. 

Who is affected:

• All enterprise users on Windows using Microsoft Edge.

What will happen:

• The Adobe-powered PDF viewer will replace the legacy viewer as the default experience.
• User interface and controls will remain unchanged.
• The new viewer offers improved performance, accessibility, compatibility, and exclusive enterprise features.

Admins can manage the experience using two policies:

NewPDFReaderEnabled: Controls the default viewer in Edge for Windows. 

NewPDFReaderWebView2List: Controls viewer behavior in WebView2 apps. 

Policy behavior:

No action is required if your organization is ready to adopt the new viewer.

If you wish to manage the experience:

• Enable the new viewer early using the NewPDFReaderEnabled policy.
• Opt-out by disabling the same policy. Opt-out will be supported until June 2026, at which time the policy will be deprecated and any remaining organizations will be moved to the new viewer. 
• Review and update internal documentation if needed.
• Communicate this change to helpdesk or support teams.

Learn more: Microsoft Edge and Adobe partner to improve the PDF experience.

For support, contact your Microsoft CSAM or CSS representative.

• Microsoft 365 LTI is generally available (worldwide) on September 15, 2025.

• Who is affected: Admins and users of LMS platforms including Canvas, Schoology, Blackboard, D2L Brightspace, Moodle, and others who use Microsoft 365 Education tools.

• Microsoft 365 LTI will be available for deployment in supported LMS platforms.
• Users will gain unified access to OneDrive, Assignments, Teams, Class Notebook, Reflect, and more—directly within the LMS.
• Educators can add content, create assignments, and schedule meetings from a single interface.
• Replaces the retired Teams Meetings and Teams Classes LTI tools.
• Restores the OneNote Class Notebook auto-provisioning feature from LMS rosters.
• Reduces clutter by eliminating the need to enable multiple tools separately.

• Admins must deploy the new Microsoft 365 LTI integration to enable access for users.
• Review the overview and deployment guides to assist with setup.
• Communicate this change to helpdesk and instructional staff.
• Update internal documentation to reflect the new LTI tool.
• If you previously used the Teams Meetings or Teams Classes LTI tools, you’ll need to transition to the new Microsoft 365 LTI to restore functionality those tools provided.

Introduction

With the rollout of Preview in Manage what attendees see, Teams town hall has now reached full feature parity with Teams live events. We’re encouraging all Teams live events users to make the switch and take advantage of the richer, more flexible capabilities available in town hall—like enhanced presenter controls, streaming attendee chat, reactions, and improved attendee experiences. Now is the time to transition and prepare your organization for the future of large-scale virtual events.

This message applies to Teams for Windows desktop, Teams for Mac desktop, and Teams for the web and is associated with Microsoft 365 Roadmap ID 487431.

When this will happen

This transition is now supported. The Manage what attendees see feature is available, and Teams Town Hall is ready for full adoption across your organization.

How this affects your organization

There is no immediate impact to you or current Teams live events users. However, Teams town hall offers a more modern and engaging experience for large-scale virtual events. Organizations are encouraged to begin transitioning to Teams town hall to prepare for future deprecation of Teams live events.

What you can do to prepare

Ensure that your IT policy is enabled for Teams town halls.

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 September 16th, 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