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

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

 Coming soon: Users can share Microsoft Teams apps or agents from the app or agent profile and from the app side panel in Teams.

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

A Microsoft 365 Copilot license is not required to share agents as described in this message. If a user has access to the agents, the users will be able to share them.

This message is associated with Microsoft 365 Roadmap ID 483355.

[When this will happen:]

Targeted Release: We will begin rolling out early November 2025 and expect to complete by mid-November 2025.

General Availability (Worldwide): We will begin rolling out mid-November 2025 and expect to complete by early December 2025

[How this will affect your organization:]

After this rollout:

• Users can select the Share option when hovering on the app or agent icon in 1:1 chat mode with the app or agent.
• After a user selects the +Apps icon from the three-dot menu in the top right of any chat, the user can right-click to share the app or agent.

Share option from hovering on app/agent icon:

Sharing from right panel:

This change will be on 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. Review your current configuration to determine the impact for your organization. You may want to notify your users about this change and update any relevant documentation.

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

The new Microsoft Planner for the web (https://planner.cloud.microsoft) brings together the simplicity of Microsoft To Do, the collaboration of Planner, and the advanced capabilities of Microsoft Project into one platform. Planner for the web offers a comprehensive and scalable solution, whether users are managing individual tasks or overseeing professional-grade projects. All users with an existing Project for the web license will have access to Planner. (A Microsoft Teams license is also required to use Planner in Teams.)

Starting early August 2025, we will retire Project for the web and will redirect its users to Planner for the web and Planner for Teams, for a smooth transition.

Premium plans from Project for the web automatically will be available in Planner, ensuring users experience a seamless migration without losing any data.

We will add these capabilities to Planner before the redirect goes into effect:

• Users will be able view and manage non-default environment plans in Planner.
• We will rename Project Power app to Planner power app (and the button to open the plan in Project will be replaced with a button to open the plan in Planner).
• Project settings in the Microsoft 365 admin center will move to the Planner page in the admin center.
• Tenants with only Project licenses will be able to access basic plan functionality in Planner.
• We will roll out the new Planner to GCC High.

User experience in Project and Roadmap for the web and Teams

• When launching Project for the web or Roadmap for the web, users will see a page directing them to open Planner for the web, they will not be able to dismiss this screen or use Project or Roadmap for the web.
• Existing Project tabs in Teams will no longer open the associated project, and instead will show users a page to inform them to re-pin their tab using the Planner tab for Teams
• Existing Roadmap tabs in Teams will no longer open the associated roadmap, and instead will show a page directing users to the Planner app in Teams
• Users will no longer have access to view or create Roadmaps in Project for the web, but their Roadmap data will remain in Dataverse
• We will remove the Project tab and Roadmap tab apps from the Teams app store.

[When this will happen:]

• For Worldwide: We will begin rolling out early August 2025 and expect to complete by mid-August 2025.
• For GCC: We will begin rolling out mid-August 2025 and expect to complete by late August 2025.
• For GCC High: We will begin rolling out late August 2025 and expect to complete by early October 2025 (previously mid-September).

[How this will affect your organization:]

Due to low usage and our efforts to simplify the user experience, these Project for the web features are not available in Planner:

• Users will need to migrate their existing Roadmaps to Portfolios because Planner does not support opening roadmaps. Learn more about migrating Roadmaps to Portfolios: Manage multiple plans with portfolios in Microsoft Planner – Microsoft Support
• Portfolios in Planner do not support adding rows for Microsoft Azure DevOps or Microsoft Project Online
• Import MPP is not available in Planner. Learn more about how to use the Project Power App to import projects from Microsoft Project for Windows desktop: Move your project from Project desktop to Project Power Apps – Microsoft Support
• Users are not able to pin Portfolios as a Teams tab
• Activity reports in Admin Center are not available for premium plans in Planner.
• The ability to add new Roadmap items from within Project Online will be removed.

[What you need to do to prepare:]

• This retirement will happen automatically by the specified dates with no admin action required before or after the rollout. Review your current configuration to assess the impact on your organization.
• You may want to notify your users and update any internal documentation to reflect these changes.
• Migrate existing Roadmap data to Portfolios in Planner before the redirect rollout date.
• Inform your users to proactively re-pin your Projects in Teams tabs using the Planner in Teams tabs
• Start using Planner in your organization today to minimize disruption when the redirect is rolled out
• Supporting adoption resources: The new Microsoft Planner

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

Copilot Dashboard users can now view metrics that reflect both summarized and recapped meeting activity, offering a more complete view of Copilot’s impact in Teams. These updates replace previous Copilot Assisted Hour calculations and meeting metrics with unified “summarized or recapped” metrics, helping leaders better understand usage across their organization. The updated metrics are available in both the Copilot Dashboard and the M365 Copilot Impact report in Advanced Insights, with additional query support for Intelligent Recap meeting metrics.

This change is associated with Microsoft 365 Roadmap ID: 494687 

[When this will happen:]

Public Preview: We will begin rolling out this change late September 2025 (previously late July) and expect to complete by late October 2025 (previously late September).

General Availability (Worldwide): We will begin rolling out this change late November 2025 (previously late October) and expect to complete by late December 2025 (previously late November).

[How this will affect your organization:]

• Copilot Assisted Hours and Value calculations: values displayed under these metrics will increase, including for prior months, since these numbers will now include meetings where users accessed Intelligent Recap feature on Microsoft Teams.

  

• Meetings card: meeting hours and meetings summarized metrics will be updated to include meetings where Intelligent Recap was accessed.

  

Users who have access to Advanced Insights will see similar updates in the M365 Copilot Impact report. They will also be able to include “Meetings recapped” and “Meeting hours recapped” metrics in their flexible queries.

[What you need to do to prepare:]

The changes mentioned do not impact eligibility criteria to access the M365 Copilot Dashboard or the Microsoft 365 Copilot Impact report on Advanced Insights.

To view the updated metrics in Advanced Insights, you can access the pre-computed Microsoft 365 Copilot Impact report. You can also set-up your own query to customize metrics and additional organizational attributes.

To learn more, please see the following:

1. How to access the Copilot Dashboard and understand Copilot Assisted Hours metrics: Connect to the Microsoft Copilot Dashboard for Microsoft 365 customers | Microsoft Learn
2. To access the Microsoft 365 Copilot Impact report and understand Copilot Assisted Hours metrics: Microsoft 365 Copilot impact report | Microsoft Learn 
3. How we define Copilot meeting metrics: Advanced insights metric descriptions | Microsoft Learn 
4. How to access Advanced Insights: Introduction to advanced insights | Microsoft Learn

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

We’re introducing a new user feature in Microsoft Teams that allows individuals to save any message—whether it’s a post, reply, or chat—and access it later from the Saved view in their Chat or Teams list. Clicking a saved message will open the full conversation in the right pane, enabling users to review or respond directly. This helps users quickly return to important information without scrolling through long threads.

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

This message is associated with Microsoft 365 Roadmap ID 496369.

[When this will happen:]

Targeted Release: We will begin rolling out early August 2025 and expect to complete by mid-August 2025.

General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late August 2025 and expect to complete by late October 2025.

[How this will affect your organization:]

After this rollout, users will be able to save their messages and recall them later to support their personal workflows:

Users can go to the three-dot menu for a message and select Save this message:

The saved message will display in the user’s Saved messages list in their Chat and Teams lists:

[What you need to do to prepare:]

No admin action needed and no admin controls exist. This feature will be available by default.

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

Before rollout, we will update this post with new documentation.

Compliance considerations:

• Does the change alter how existing customer data is processed, stored, or accessed (e.g. documents, emails, chats, etc.)? Yes. Saving a message creates a copy of the original message. If the original message is deleted, the saved copy will also be deleted in accordance with existing retention policies. No admin action is required, but an existing retention policy must be in place.

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

Introduction

As part of the final phase of the Viva Engage rebranding, we’re updating the email sender domains used for Viva Engage communications. This change ensures a consistent and secure brand experience across all surfaces and completes the transition from Yammer to Viva Engage.

This update was previously communicated in MC679739, “Yammer Rebranding to Viva Engage Domain Migration Update,” in October 2023.

When this will happen

• The email sender domain rollout will begin in early September 2025 (previously late August) for U.S. and EU tenants currently receiving messages from @yammer.com and @eu.yammer.com respectively. The entire rollout is expected to complete by Q1 CY2026 (previously late October).

• A fallback/coexistence period will be in place between September (previously August) and by Q1 CY2026 (previously late October). during which both the old and new domains will be supported. During this time, some users within a tenant may receive emails from the old domain while others receive them from the new domain.

How this will affect your organization

The sender domain for Viva Engage emails will change as follows:

• From @yammer.com to @engage.mail.microsoft for U.S. and global regions.
• From @eu.yammer.com to @eu.engage.mail.microsoft for European regions.

These new domains are secured with industry-standard authentication protocols (e.g., SPF) to help prevent spoofing and ensure reliable delivery.

To enhance security and reduce cross-tenant spam, sender addresses will now include a tenant-specific prefix. You may see emails from:

• [email protected] (digests, delegate, leader identification, community expert and other notifications)
• [email protected] (community, storyline, and activity notifications)
• [email protected] (leadership announcements)

These changes apply to all Viva Engage tenants, regardless of license tier (e.g., Viva P1, P2), and affect all Viva Engage emails, including notifications, announcements, and digests.

Third-party integrations (e.g., journaling, archiving, or routing systems) that rely on the @yammer.com domain for classification or authentication may be impacted. Any such configurations should be reviewed and updated to recognize the new domains.

An example of a new Viva Engage email notification sent from the updated @engage.mail.microsoft domain:

What you need to do to prepare

Admins should review and update the following configurations:

• Transport rules and email gateways: Update any rules that reference @yammer.com to include the new domains.
• Exchange filtering: Ensure filtering rules remain effective with the new sender domains.
• Outlook rules: Inform users that any rules based on @yammer.com will no longer apply. Users can manually update or remove these rules.

No admin action is required unless your organization has custom configurations based on the old domain.

Learn more: Yammer is evolving to Viva Engage | Viva Engage Blog

Compliance considerations

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

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

Introduction

We’re retiring the Deploy Shifts to your frontline teams at scale feature in Microsoft Teams Admin Center. Starting September 5, 2025, this functionality will no longer be available. We recommend using the Teams web or desktop app to manage Shifts, where ongoing investments will continue to enhance scheduling capabilities.

When this will happen

The retirement will begin September 25, 2025.

How this affects your organization

You’re receiving this message because your organization uses Microsoft Teams. If you do not currently use the Deploy Shifts to your frontline teams at scale feature in Teams Admin Center, no action is required.

After September 5, 2025:

• Admins will no longer be able to deploy Shifts at scale via Teams Admin Center.
• Shifts management will continue to be supported in the Teams web and desktop apps.

What you can do to prepare

No admin action is required. This change will occur automatically on the specified date.

To continue managing Shifts, use the Teams web or desktop app:

• Learn more: Deploy Shifts to your frontline teams at scale

Compliance considerations

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

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

Introduction

We’re retiring support for inline SVG images in Outlook for Web and the new Outlook for Windows starting early September 2025. This change enhances security and aligns with current email client behavior, which already restricts inline SVG rendering.

When this will happen

When this will happen

• Worldwide rollout: Begins early September 2025, expected to complete by mid-September 2025.
• GCC, GCC-H, DoD, Gallatin rollout: Begins mid-September 2025, expected to complete by mid-October 2025 (previously late September).

How this affects your organization

• Inline SVG images will no longer be displayed in Outlook for Web or the new Outlook for Windows. Instead, users will see blank spaces where these images would have appeared.
• This change affects less than 0.1% of all images used in Outlook, so impact is expected to be minimal.
• SVG images sent as classic attachments will continue to be supported and viewable from the attachment well.
• This update helps mitigate potential security risks, such as cross-site scripting (XSS) attacks.

What you can do to prepare

No action is required from users or administrators.

We recommend:

• Updating internal documentation to reflect this change.
• Informing users who may rely on inline SVGs in email communications.

Compliance considerations

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

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

To better reflect the identity and functionality of the Microsoft 365 Copilot app, we are updating the executable name on Windows devices. This change improves clarity for IT admins, developers, and users managing diagnostics or process monitoring.

When this will happen:

This update will roll out to affected users with the next app update after late October 2025 (previously late September).

How this affects your organization:

With the change, the executable name for the Microsoft 365 Copilot Windows app will change from Webviewhost.exe to M365Copilot.exe. For users who installed the app via the Microsoft Store, the update will happen automatically on September 20 if their device settings allow for automatic updates. For users who installed the app through other platforms or have settings that do not allow automatic updates, the change will happen once users update their app.

This update does not affect app functionality or user experience.

What you can do to prepare:

No action is required unless your organization has dependencies on Webviewhost.exe. If so, update those references to M365Copilot.exe to ensure continued functionality.

Compliance considerations:

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

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

Introduction

We’re introducing Teams Collaborative Notes (powered by Loop) in group chats across desktop and web experiences. This feature enables users to co-create and edit notes, agendas, and action items directly within the Teams chat interface, enhancing real-time collaboration without switching contexts.

This message is associated with Roadmap ID 498159.

When this will happen

• Public Preview: Rollout begins late September 2025 and completes by early October 2025.  
• General Availability: Rollout begins early October 2025 (previously late September) and completes by late October 2025 (previously early October).

How this affects your organization

Users will see a new Notes tab in group chats, allowing them to create and collaborate on Loop components such as agendas and action items. These components are editable inline, supporting synchronous collaboration directly within Teams.  

This feature is on by default for all tenants. Users do not need to install anything to begin using it.

What you can do to prepare

• You can manage this feature via the Teams Admin Center. If desired, Collaborative Notes can be disabled at the tenant level.
• Review internal documentation and training materials to ensure users are aware of the new Notes tab and its capabilities.

Compliance considerations

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

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

Introduction

To streamline reporting experiences and focus development efforts on modern integration paths, we’re retiring the legacy Power BI integration within SharePoint lists and libraries. This change supports improved performance and flexibility through supported alternatives like Export to Power BI and Power BI Desktop connections.

• Retirement begins mid-November and ends mid-December 2025.
• There will be no extensions.

• Who is affected: Organizations currently using the Visualize the List or Visualize the Library feature in SharePoint Online.
• What will happen:
  • Users will no longer be able to create new reports directly from SharePoint lists or libraries using the legacy integration.
  • Previously published reports created using this integration will no longer be accessible.
  • The Export to Power BI feature and Power BI Desktop connectivity remain supported and unchanged.

• No admin action is required. However, we recommend the following steps:
• Notify users who rely on the Visualize the List or Visualize the Library feature.
• Update internal documentation to reflect the retirement and guide users to supported alternatives.
• Inform users that they can view the list of published reports directly from the same Integrate menu of the list or library. More information in: Create a report quickly from a SharePoint list or library in the Power BI service – Power BI | Microsoft Learn
• Share these resources with users:
  • Export to Power BI from SharePoint list: Create a semantic model from a SharePoint List – Power BI | Microsoft Learn
    
  • Create a report on a SharePoint list in Power BI Desktop: Create a report on a SharePoint List in Power BI Desktop – Power BI | Microsoft Learn
  • Blog post: Deprecation of Power BI Integration within SharePoint Lists and Libraries | Microsoft Power BI Blog | Microsoft Power BI

Compliance considerations:

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

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

[Introduction]

Starting in late October 2025, Microsoft will begin automatically installing the Microsoft 365 companion apps—People, Files, and Calendar—on Windows 11 devices that already have Microsoft 365 desktop client apps. These taskbar-integrated apps are designed to streamline everyday workflows, helping users stay focused, reduce context switching, and complete tasks faster.

With Copilot integration, users can ground their prompts in the right context—whether it’s a shared file, a meeting, or a collaborator. This integration allows users to catch up, summarize, and take action more efficiently.

This message is associated with Microsoft 365 Roadmap ID 486856.

[When this will happen:]

General availability: Rollout begins late October 2025 and is expected to complete late December 2025.

[How this affects your organization:]

Who is affected:

All users on Windows 11 devices with Microsoft 365 desktop client apps.

What will happen:

• Microsoft 365 companion apps (People, Files, Calendar) will be automatically installed.
• Admins can opt out of automatic installation via Device Configuration settings.
• If Copilot pinning is not yet enabled, admins will be able to pin both Copilot and companion apps starting mid-October.
• If you’ve already enabled Microsoft 365 Copilot pinning in the Microsoft 365 Admin Center, note that companion apps are not included in the pinning configuration at this time but you will be able to enable companions pinning starting mid-October.
• On devices where the apps are already installed, no visible change will occur.
• Installation is enabled by default and does not require user interaction.
• Apps will appear in the Start menu and provide quick access to people, files, and calendar data from the Microsoft Graph.

[What you can do to prepare:]

• Notify users about this change via an internal announcement to set expectations.
• Update any relevant internal documentation to reflect the availability of these apps.
• If you want to opt out of automatic installation:
  1. Go to Microsoft 365 App Admin Center.
  2. Navigate to Customization -> Device Configuration.
  3. Select Modern App settings
  4. Choose Microsoft 365 companion apps
  5. Uncheck Enable automatic installation of Microsoft 365 companion apps and Microsoft 365 Apps
• Learn more: Overview of Microsoft 365 companion apps – Microsoft 365 Apps | Microsoft Learn
• Check out the latest features here: Get Started with Microsoft 365 companion apps | Microsoft Support

App highlights:

People app features:

• Look up colleagues by name, skills, role, location and more.
• View profile cards, availability, and organizational charts.
• Send messages and start chats.
• Use Copilot to ask people-related questions like, What does this person work on? or Draft a message to catch up.
• Type freeform prompts for any colleague directly in the app.

File app features:

• Find Microsoft 365 and locally downloaded files.
• Preview file content and share with colleagues.
• Filter by person, file type, or activity (Created, Shared, Edited, or @Mentioned).
• Use Copilot to summarize, catch up, and act on files.

Calendar app features: 

• Find events by organizer, attendees, or title. 
• View agenda or day at a glance. 
• Open meeting details and join directly from the calendar. 
• Edit meetings, chat with participants, or copy the meeting link. 
• Use Copilot to prepare for upcoming meetings or catch up on missed ones.

[Compliance considerations:]

[Introduction:]

To improve transparency and streamline post-export workflows, Microsoft Purview eDiscovery is enhancing metadata reporting in the item.csv files generated during Add to Review Set and Export processes. These updates are designed to provide deeper insights into item-level attributes and improve error traceability.

This message is associated with Microsoft 365 Roadmap ID 506220.

[When this will happen:]

• General Availability (Worldwide, GCC, GCCH, DoD): Rollout will begin in early October 2025 and is expected to complete by mid-November 2025.

[How this affects your organization:]

Who is affected: Admins and users working with Microsoft Purview eDiscovery (Standard and Premium) workflows, particularly those who rely on metadata exports for review and automation.

What will happen:

• The item.csv report will have the follow updates:
  • Status: Indicates if the item is processed successfully or has errors.
  • Error Detail: Detailed error messages for the item.
  • Custodian: SMTP address of the custodian the item was associated with.
  • Sensitivity label: GUID of the sensitivity label applied to the item.
  • IsEncrypted: True or false value to indicate if the item is encrypted.
  • SharePoint Item Content Type ID: Hexadecimal value representing the SharePoint content type.
• Admins will continue to have access to reports generated prior to this update. Newly generated reports will include the updated metadata fields and structure.
• These changes will enhance visibility into item-level processing and support downstream automation and auditing.

[What you can do to prepare:]

• Review and update internal documentation to reflect the new field names and structure in the item.csv report.
• Adjust automation or post-export workflows to rely on field names rather than fixed column positions.
• Communicate these changes to relevant compliance and legal teams.
• Learn more: Learn about eDiscovery | Microsoft Purview | Microsoft Learn

[Compliance considerations:]

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

[Introduction]

[When this will happen:]

Preview (GCC, GCCH, and DoD): Rollout will begin in late September 2025 and is expected to complete in late October 2025.

[How this affects your organization:]

• Who is affected: This configuration option applies only to devices running the unified sensor (v3.x).
• What will happen:
  • A new configuration option will be available in Asset rule management.
  • Admins can apply the Unified Sensor RPC Audit tag to onboarded domain controllers running the unified sensor (v3.x).
  • Devices with this tag will have WFP-based RPC monitoring enabled.
  • Once applied, the configuration is enforced on existing and future devices that match the rule criteria.
  • Tagged devices will appear in Device inventory for visibility and auditing.
  • This feature is opt-in and not enabled by default.

[What you can do to prepare:]

• No action is required unless you want to enable the feature.
• If needed, enable the new configuration option by creating an asset management rule to apply the tag.
• Communicate this change to your security and compliance teams.

Learn more: Microsoft Defender for Identity sensor v3.x prerequisites (Preview)

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

[Introduction]

As part of this transition, Microsoft Teams is now available at https://teams.cloud.microsoft, in parallel with its previous domain. This change enhances security by using Microsoft’s exclusive top-level domain, .microsoft, which helps prevent spoofing and builds user trust.

Learn more by reading the 2023 blog post Introducing cloud.microsoft: a unified domain for Microsoft 365 apps and services.

[When this will happen:]

[How this affects your organization:]

Who is affected: Admins managing Microsoft Teams, Teams apps, and network configurations. All users accessing Microsoft Teams.

What will happen:

• Users will be automatically redirected to teams.cloud.microsoft.
• No user action is required; existing links and bookmarks will continue to work.
• Users may notice that the new application domains are lacking the “.com” extension. This is by design, as “.microsoft” is Microsoft’s own top-level domain – and this exclusivity allows for additional security and protection against spoofing.
• Admins can disable redirects via the Teams Admin portal if needed.
• The cloud.microsoft domain has been a part of standard Microsoft network guidance on domains and service endpoints since April 2023. 

• Educate users to recognize and expect cloud.microsoft as a key domain for Microsoft cloud experiences. You can refer them to What is cloud.microsoft? – Microsoft Support for more information. 
• If your organizational websites, tools, or other materials reference the old URL, those links will be automatically redirected. However, it’s good practice to update those assets to avoid user confusion.
• Update internal documentation, websites, and tools that reference the old Teams URL.
• Partner with developers of in-house Teams apps (including those used in Outlook and Microsoft 365) to follow guidance in: Action required: ensure your Microsoft Teams apps are ready for upcoming domain changes.
• Confirm that *.cloud.microsoft is not blocked on your enterprise network. This should require no action if standard Microsoft network guidance on domains and service endpoints is being followed. 

[Compliance considerations:]

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

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

[Introduction:]

To help users quickly identify external participants in Microsoft Teams and reduce the risk of oversharing sensitive information, we’re introducing Trust Indicators—visual labels (badges or icons) next to people’s names. These indicators signal whether someone is external to your organization, a guest, or an anonymous meeting participant.

[When this will happen:]

Public Preview: Begins rolling out late September 2025; expected completion by late November 2025.

General Availability (Worldwide, GCC, GCC High, DoD): Begins rolling out late November 2025; expected completion by early January 2026.

[How this affects your organization:]

Who is affected: All Microsoft Teams users across commercial, GCC, GCC High, and DoD environments.

What will happen:

• Users will see badges or icons next to names of external participants in Teams:





• The visual indicator will vary depending on the relationship (guest, external, anonymous):



• These indicators will appear across multiple Teams surfaces.
• No admin action is required to enable this feature; it will be ON by default.

[What you can do to prepare:]

No action is required to enable the feature.

Admins can:

• Review the documentation to understand the types of Trust Indicators and their behavior: Representation of users outside your organization | Microsoft Teams | Microsoft Learn
• Communicate this change to helpdesk or support teams.
• Update internal documentation if you reference user identity indicators in Teams.

[Compliance considerations:]

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

[Introduction:]

By the end of October 2025, Microsoft Copilot Studio will receive an updated product icon across both the full-featured web experience and within Microsoft 365 Copilot. This visual update aligns Copilot Studio more closely with the Microsoft 365 Copilot brand and reinforces its role as the platform for building and managing agents.

[When this will happen:]

The updated icon will begin rolling out at the end of October and will appear across in-product experiences and product documentation. Rollout is expected to complete by mid-November 2025.

[How this affects your organization:]

Who is affected: All users who use Copilot Studio for creating agents, including those who create agents via the Microsoft 365 Copilot integration.

What will happen:

• Users will see an updated product icon in the Copilot Studio interface and related documentation.
• This is a visual-only update; there are no changes to functionality, workflows, or agent management.
• No admin settings or policies are impacted.

[What you can do to prepare:]

• No admin action is required.

[Compliance considerations:]

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

[Introduction:]

To enhance the extensibility of Microsoft 365 Copilot, we’re introducing support for Declarative Agents in Biz Chat and Biz Chat Starter within classic Outlook for Windows. Declarative Agents allow users to customize their Copilot experience by integrating plugins, enterprise connectors, and orchestration logic. This update aligns classic Outlook with other Copilot Chat experiences, delivering consistent agent capabilities across platforms.

This update is tracked under Microsoft 365 Roadmap ID 481559.

[When this will happen:]

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

[How this will affect your organization:]

Who is affected:

• Organizations using classic Outlook for Windows with Microsoft 365 Copilot Chat
• Admins managing Copilot extensibility and agent deployment

What will happen:

• Declarative Agents will be available in Copilot Chat within classic Outlook for Windows
• Users will see a right-side panel in Outlook showing:
  • Agents previously installed by the user
  • Agents deployed by the admin
  • Entry points to browse agents in the app store
  • Option to create a new agent
• Declarative Agents in Copilot Chat are enabled by default for Microsoft 365 tenants with Copilot licenses
• No admin opt-in is required to use agents in Copilot Chat
• Advanced agent capabilities (access to SharePoint or Graph connectors) require explicit admin opt-in and billing setup
• Admins can manage agents through the Integrated apps section of the Microsoft 365 admin center, including:
  • Enabling or disabling Declarative Agents for the organization
  • Assigning access to specific users or groups
  • Blocking or removing agents from the organizational catalog
  • Managing agent visibility and availability

Licensing tiers:

• Copilot Chat (Mainline): Requires a Microsoft 365 Copilot license. Users get full access to Declarative Agents, including those integrated with plugins, enterprise connectors, and advanced orchestration features
• Copilot Chat Starter: Designed for non-AI SKU users (users without the Copilot license). These users can still access Copilot Chat and build knowledge-only Declarative Agents, but with limited capabilities

[What you can do to prepare:]

• Review agent management settings in the Integrated apps section of the Microsoft 365 admin center
• Ensure Copilot extensibility is enabled for your organization if you plan to use agents.
• If you plan to use advanced agent capabilities (such as Graph or SharePoint connectors), configure billing and opt-in via the Microsoft 365 admin center or Power Platform admin center.
• Communicate this update to helpdesk and support teams.

Learn more: 

• Declarative agents for Microsoft 365 Copilot overview | Microsoft Learn
• Manage agents for Microsoft 365 Copilot in Integrated Apps

[Introduction]

We’re introducing a new way to quickly summarize emails using Copilot chat in Outlook. With a single click, users can generate concise summaries of email content, helping them stay focused and save time. This feature supports both Classic and New Outlook for Windows and is available to users with a Microsoft 365 Copilot license and pinning enabled.

This message is associated with Microsoft 365 Roadmap ID 503316.

[When this will happen:]

• Targeted Release (Worldwide): Rollout underway by early October 2025; expected completion by early November 2025.
• General Availability (Worldwide): Begins mid-October 2025; expected completion by late November 2025.

[How this affects your organization:]

Who is affected: Users with a Microsoft 365 Copilot license and pinning enabled in Outlook across Android, Desktop, iOS, Mac, Web, and Windows (Classic and New).

What will happen:

Users will see a new option to summarize email content using Copilot chat:

• The feature will be available across Android, Desktop, iOS, Mac, Web, and both Classic and New Outlook for Windows.
• No admin configuration is required; the feature is enabled by default for eligible users.
• Existing policies are respected; no changes to admin controls are needed.

[What you can do to prepare:]

• No action is required.
• You may choose to inform users about the new summarization capability.
• If desired, update internal documentation to reflect the availability of this feature.

[Compliance considerations:]

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

[Introduction:]

Starting in October 2025, Global Administrators and AI Administrators will gain the ability to reassign ownership of shared agents created within the organization. This update improves administrative control and ensures continuity in agent management, especially when employees transition or leave.

This message is associated with Microsoft 365 Roadmap ID 502867.

[How this affects your organization:]

Who is affected: Global Administrators and AI Administrators managing agents in Copilot Studio (Lite and full) and M365 Agents Toolkit.

What will happen:

• Admins can reassign ownership of shared agents to another user.
• Ownership can only be reassigned to users with an active Microsoft 365 Copilot license.
• The new owner will receive full edit and delete permissions.
• The new owner will gain access to any uploaded files associated with the agent.
• The previous owner will lose all access, including read-only rights.
• Phase 1 (Early October): Applies to agents created in Copilot Studio (Lite).
• Phase 2 (Late October): Applies to agents created in Copilot Studio (full) and M365 Agents Toolkit.

Screenshot 1 – Admin view for reassigning agents to a new owner: 

Screenshot 2 – New owner’s view showing the agent available for editing:

• Review shared agents in your environment.
• Plan reassignment workflows for agents tied to departing or transitioning employees.
• Ensure reassigned users have active Microsoft 365 Copilot licenses.
• Communicate this change to helpdesk or support teams.
• Update internal documentation if needed.

[Introduction]

Flow Builder is a Microsoft 365 Copilot agent that enables users to create automation flows using natural language. Based on customer feedback, Flow Builder is now fully included in the $30 Microsoft 365 Copilot license for employee-facing scenarios—no separate license or add-on is required.

[When this will happen:]

General Availability (Worldwide): Rollout begins September 29, 2025.

[How this affects your organization:]

Who is affected: All Microsoft 365 tenants with Copilot licenses.

What will happen:

• Flow Builder will be available to all users with a Microsoft 365 Copilot license ($30/month).
• No additional cost to build, run, or deploy Flow Builder agents.
• Flows are saved in each user’s Power Platform environment.
• Flows follow Microsoft’s standard Data Subject Request (DSR) processes.
• Conversation history is not stored—no chat data is saved or exportable.
• Feature is ON by default for eligible tenants.

Note: To enable Flow Builder in your environment, both AI Step and AI Prompt connectors must be included in your DLP policy.

Screenshot 1: Simply describe to the agent what you would like to automate:

Screenshot 2: Build your automation by simply chatting with AI:

[What you can do to prepare:]

Admins should:

• Confirm Flow Builder is turned on in the Microsoft 365 admin center (Copilot > Agents).
• Review Power Platform environment settings for export/delete options.
• Ensure that both the AI Step and AI Prompt connectors are included in your DLP policy, as both are required to enable Flow Builder in your environment.
• Check tenant-level feedback collection settings (applies across all Flow Builder entry points).
• Update internal documentation to reflect new licensing and privacy details.

[Compliance considerations]

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

Introduction

We’re introducing support for manual uploads of historical HR data in Organizational Data in Microsoft 365. Admins can now specify whether uploaded data is current or historical using a new toggle in the CSV upload experience. For historical data, an effective date can be assigned to ensure accurate processing by downstream apps such as Viva Insights. This enhancement improves data consistency across Microsoft 365 and supports retroactive updates for organizational reporting.

Figure i. Historical upload in Organizational Data in Microsoft 365

When this will happen

General Availability (Worldwide): Rollout will begin in late September 2025 and is expected to complete by late October 2025.

How this affects your organization

Organizations using Organizational Data to manage HR information will gain greater flexibility and control over user record updates. Historical uploads allow you to:

• Correct past data errors
• Build comprehensive user histories
• Align data ingestion with behavioral processing timelines in Viva Insights

What you can do to prepare

You can begin preparing by:

• Reviewing internal HR data sources for historical records
• Preparing CSV files with accurate effective dates for upload
• Understanding how MODIS and Viva Insights process backdated attributes

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

• Chat Agent
• Data Entry Agent
• Data Exploration Agent
• Data Visualization Agent
• Summary Agent

• Customer service representatives can filter and sort based on user groups.
• Administrators can enable intent-based routing for the inbox by bringing in user group support in line with the existing queue support.
• Administrators can configure the open behavior of conversation messaging channels (other than voice) to open as a new session and within the inbox.
• Administrators can configure the card layout that is displayed in the inbox for the conversation entity by adding, removing, or reordering fields.

• Visit the Windows 11 release information page for a list of currently supported Windows versions by servicing option. There you’ll find release dates, build numbers, end of service dates, and release history. 
• Consult Windows release health in the Microsoft 365 admin center for information on Windows 11, version 25H2 known issues and resolutions. Dedicated pages for these known and resolved issues are already available.
• Join Windows Office Hours every third Thursday on the Windows Tech Community for help with your deployment, tips, and best practices. This monthly chat-based Q&A is supported by the Windows, Intune, and Windows 365 product teams. You can post your questions in advance or at any time during the hour. 

Updated September 30, 2025: As a reminder from the post announced on October 31st, 2024, we will be retiring the Utility.SendEmail API on October 31st, 2025. 

In addition, you are now able to identify usage of the API via the Purview audit logs in the admin center

1.  As a tenant admin, navigate to the Microsoft Purview Portal available within the Microsoft 365 Admin Center.
2. Open Audit to search for activities.
3.  Select a date range to run the audit search for (recommend running it for at least 90 days)
4. Put the following text, “SendEmailApiInvoked” into the “Activities – operation names” textbox and click search.
5. The request will be queued, and results will be available once processed.
6. Click on the results and review each of the items.

Use the UserAgent and ApplicationDisplayName to help identify the caller.

[NOTE:] If the ApplicationDisplayName = “Workflow” then the items will be unaffected by this API retirement but will follow the SharePoint 2013 Workflow retirement. We will be retiring the Utility.SendEmail API from SharePoint. The SP.Utilities.Utility.SendEmail could be used to send emails from custom applications or processes within SharePoint Online, including Power Automate, and custom workflows.

From custom code the API can be referenced via REST as (“/_api/SP.Utilities.Utility.SendEmail”) while for CSOM, it would be “Utility.SendEmail” with more information on the original implementation at Utility.SendEmail method for CSOM.

[When this will happen:]

October 31, 2025

[How this will affect your organization:]

Any components, custom code, or Power Automate connections that utilize the SP.Utilities.Utility.SendEmail API, should be updated before the end of life date. The API will stop providing services on the retirement date and will no longer send any email requests from that date.

[What you need to do to prepare:]

Migrate any custom code, power automate, processes or policies running within SharePoint Online that have been configured to send email using the SP.Utilities.Utility.SendEmail API.

The following are recommended or alternative approaches:

1. Use Microsoft Graph to send email using the user: SendMail API (Part of the Outlook mail workload) Automate creating, sending, and processing messages
2. Customizations through Power Automate may also utilize the Outlook connector and utilize “Send an email” within the Actions. Overview of using Outlook and Power Automate 

Learn more:

1. Retirement of the SharePoint SendEmail API
2. Automate creating, sending, and processing messages
3. Overview of using Outlook and Power Automate
4. Learn about the Microsoft Purview portal | Microsoft Learn