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

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

Microsoft Purview Insider Risk Management (IRM) will be adding a new role–Data Security Investigation Contributor–to the Insider Risk Management Investigators role group. This will allow members of the Insider Risk Management Investigators role group to launch a Data Security Investigation (DSI) from an IRM case.

DSI is a new AI-powered solution that enables data security teams to identify incident-related data, conduct deep content analysis, and mitigate risk within one unified solution. DSI enables data security admins to efficiently identify incident-relevant content by searching their Microsoft 365 data estate to locate emails, Teams messages, Copilot prompts and responses, and documents. Once the investigation is scoped, DSI’s generative AI capabilities allow admins to gain deeper insights into the impacted data, revealing critical security risks and sensitive information. Investigative capabilities include the ability to categorize evidence, perform vector searches, and examine impacted data for security and sensitive data risks. DSI visualizes correlations between investigation data, users, and their activities. To mitigate identified risks, DSI facilitates secure collaboration between partner teams. Post-investigation learnings can be used to refine existing policies to strengthen an organization’s security practices.

The integration between IRM and DSI allows an IRM investigator to identify when a risky user needs deeper investigation to launch a pre-scoped investigation directly from the user activity pane, allowing them to view content analysis related to that user and better assess post-incident data impact.

This message is associated with roadmap ID 485707. 

[When this will happen:]

Public Preview (Worldwide): We will begin rolling out early April 2025 and expect to complete by late April 2025.

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

[How this will affect your organization:]

With this update, members of the Insider Risk Management Investigators role group will be able to create Data Security Investigations from an Insider Risk Management case. Members of the Insider Risk Management Investigators role group will not be able to view the Data Security Investigation unless they are assigned the Data Security Investigation Investigator role.

[What you need to do to prepare:]

This rollout will happen automatically by the specified date 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 admins about this change and update any relevant documentation.

Microsoft Purview Insider Risk Management correlates various signals to identify potential malicious or inadvertent insider risks, such as IP theft, data leakage and security violations. Insider Risk Management enables customers to create policies based on their own internal policies, governance and organizational requirements. Built with privacy by design, users are pseudonymized by default, and role-based access controls and audit logs are in place to help ensure user-level privacy.

You can access the Insider Risk Management solution in the Microsoft Purview compliance portal.

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

Microsoft Purview Insider Risk Management (IRM) is introducing enhanced detection capabilities that allow organizations to identify sensitive files and text shared to any cloud application or website—including Generative AI platforms—via the network layer. This capability is powered by integration with third-party network partners, enabling data capture at the network level.

IRM correlates signals to detect potential insider risks such as IP theft, data leakage, and policy violations. Built with privacy by design, IRM pseudonymizes users by default and includes role-based access controls and audit logs to help ensure user-level privacy.

This message is associated with Microsoft 365 Roadmap ID 484084.

[When this will happen:]

Public Preview: We will begin rolling out mid-July 2025 and expect to complete by late July 2025.

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

[How this will affect your organization:]

Organizations will gain visibility into sensitive data shared to any cloud application or website via the network layer. This helps strengthen insider risk detection and supports compliance and data protection efforts across cloud environments.

This capability will be available by default but requires admin configuration to take effect at Insider Risk Management > Insider Risk Management settings > Policy indicators > Network indicators (preview):

[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 Insider Risk Management configuration to assess the impact on your organization. You may want to notify your admins and/or users about this change and update internal documentation.

• Complete network onboarding as outlined in Learn about Microsoft Purview Network Data Security (preview) | Microsoft Learn
• Enable network indicators in IRM and incorporate them into your Insider Risk Management policies to begin leveraging this new detection capability.

Learn more: Configure policy indicators in insider risk management | Microsoft Learn (will be updated before rollout)

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

[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.

Updated October 7, 2025: We have determined that this message was not published to the appropriate audience. You can safely disregard this message. Thank you for your feedback.

[Introduction]

This is a reminder based on our previous communication (MC1117814) regarding the Viva Engage email sender domain update. Please ensure your email configurations are updated, as we plan to roll out the new email domains for your tenant starting Monday, October 6, 2025.

[When this will happen:]

• Rollout begins: Monday, October 6, 2025
• Expected completion: Tuesday, October 7, 2025
• Applies to U.S. and EU tenants currently receiving messages from @yammer.com and @eu.yammer.com.

[How this will affect your organization:]

All emails from Viva Engage will now come from a new domain instead of yammer.com or eu.yammer.com The exact sender domain depends on the data residency for your Viva Engage network:

• US geo: from @yammer.com to @engage.mail.microsoft
• EU geo: from EU​.yammer.com to @eu.engage.mail.microsoft

In addition to the domain change, Viva Engage email addresses will now include a tenant-specific prefix to help differentiate your organization’s environment such as test and production tenants. For example, fabrikam.onmicrosoft.com will result in a “fabrikam” prefix. Continuing with this example, sender addresses may include:

• [email protected] – for digest emails, leader identification, community expert identification, delegate notifications and others.
• [email protected] – for community posts, storyline updates, and other user activity notifications.
• [email protected] – for leadership announcements and other broad communications.

For networks in the EU geo, you should change the sender domain in the examples above to [email protected], etc.

These changes affect all Viva Engage emails, including notifications, announcements, and digests.

[What you need to do to prepare:]

Admins should review these configurations before and during rollout:

• Email Transport / Mail Flow Rules: Update any rules referencing @yammer.com (or EU.yammer.com) to also include @engage.mail.microsoft (and EU.engage.mail.microsoft) so encryption, forwarding, or redirection rules keep working.
• Security Filters: Add the new domains to spam filters or allowlists if they were previously trusted. 
• Outlook Inbox Rules: Notify users to update personal rules that filter by domain (e.g., moving Yammer emails to a folder). Otherwise, Engage emails may land directly in their inbox.
• Safe Senders / Allow Lists: Add the new domains to org-level and user safe sender lists to prevent misclassification as junk.

Please communicate these changes in advance so users know how their rules or filters may be affected. If you don’t use custom rules, no changes are needed; the switch will occur automatically.

Learn more: Viva Engage Email Sender Domain Update

[Compliance considerations:]

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

Viva Engage (previously known as Yammer) networks are being upgraded. The retirement of ‘legacy’ networks and enforcement of mandatory upgrades were first announced via the Message center on September 1, 2022 (MC424414). Additional notification arrived via the Message center in 2023, 2024, and 2025, with Service Health Dashboard alerts indicating the need to upgrade networks as soon as possible.

Legacy networks that have not upgraded will become inaccessible to users on October 13, 2025.

[How this will affect your organization:]

If your network is not in Native Mode, you will lose access to all network content. Users will be unable to login to your legacy network, and your network will be scheduled for deletion at a future date. 

If you lose access to your network, please open a support case with Microsoft as soon as possible. Microsoft’s support team will help guide you through the upgrade process.

[What you need to do to prepare:]

For networks created before January 16, 2020:

To determine whether your network is in Native Mode, an Engage admin must log into the Engage admin center and navigate to “Network admin -> Native Mode for Microsoft 365.” Networks in Native Mode will have a green banner announcing the completion of the upgrade process. If you do not see a green banner, please follow the steps in this guide as soon as possible.

For networks created after January 16, 2020:

Your network was automatically created in Native Mode. No action is necessary.

[Introduction]

We’re introducing the Agent Dashboard, a new dashboard available as part of Copilot Analytics in Microsoft Viva. This dashboard provides visibility into key agent adoption trends and associated Copilot credit usage. It supports insights into agents used within Microsoft 365 Copilot, which may be:

• Built using Microsoft Copilot Studio, SharePoint, or the Microsoft 365 Agents Toolkit
• Built by employees, your organization, Microsoft, or Microsoft partners

This release also enhances the Adoption tab of the Copilot Dashboard, allowing users to view agent insights directly and access the Agent Dashboard for deeper analysis.

[When this will happen:]

• Public Preview (Worldwide): Begins rolling out in late November 2025, expected to complete by late November 2025.
• General Availability (Worldwide): Begins rolling out in early February 2026, expected to complete by late February 2026.

[How this affects your organization:]

Who is affected:

• Leaders, delegates, adoption specialists, and administrators using Microsoft Viva Insights
• Tenants with at least 50 Microsoft 365 Copilot licenses assigned

What will happen:

• A new Agent Dashboard will be available in Viva Insights under Copilot Analytics
• Users will find:
  • Key adoption metrics with historical trends (up to 6 months):
    • Number of active agents
    • Number of active agent users
    • Number of agent responses
    • Copilot credits used
    • Number of users using Copilot credits
    • Percentage of Copilot users using agents
    Screenshot 1: Key adoption metrics with historical trends, including active agents, active users, agent responses, and Copilot credit usage.

    

  • Monthly and weekly user retention trends, with comparison across groups
  Screenshot 2: Monthly and weekly user retention trends, with comparison across groups.

  

  • Top agents based on the following, with the ability to dive deeper into specific agents:
    • Active user count
    • Agent responses
    • Copilot credits consumed
    Screenshot 3: Agent highlights along with a table of top agents, each with active usage metrics and the ability to dive deeper.

    

    Screenshot 4: Individual agent deep dive page with key adoption metrics and trends over time.

    

• Minimum group size threshold must be met for agent activity insights.
• Learn more: Configure manager settings
• The Adoption tab of the Copilot Dashboard will also include:
  • Contextual insights on how Copilot users are leveraging agents and credits
  • Direct entry points to the Agent Dashboard
  Screenshot 5: Entry points to the Agent Dashboard from the Copilot Dashboard Adoption tab, including agent usage and Copilot credit usage insights.

  

  [What you can do to prepare:]

  • Review and assess the impact for your organization
  • Manage access to the Agent Dashboard using VFAM controls at user, group, and tenant levels (nested under Viva Insights Web app VFAM controls)
  • Consider reviewing with your works council
  • Update training and documentation as needed
  • Additional details will be available on MS Learn once this functionality is released, in a separate Agent Dashboard section: Copilot Analytics introduction

  [Compliance considerations:]

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

We’re improving the email preview experience in Microsoft Defender for Office 365 to provide a clearer, more consistent, and secure workflow. These updates are designed to reduce ambiguity, simplify interactions, and reinforce security protections—helping organizations confidently use this feature as part of their protection strategy.

When this will happen:

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

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

How this affects your organization:

Who is affected: Quarantine administrators Microsoft Defender for Office 365 as well as users with access to review and preview messages within quarantine.

The update is specifically for the preview capability within the quarantine experience. What will happen:

• The update consists of three main parts:
  • Streamlined view options: The plain text view option will be retired to unify preview behaviors across Defender experiences.
  • Clearer handling of URLs: The hover-over preview for URLs will be limited to reinforce that links in quarantine preview are not clickable.
  • Simplified content loading: The “Load external content” button will be removed for some scenarios. Content will render in a secure, isolated environment.

Quarantine administrators and users will experience a simplified preview interface with clearer rendering and reduced visual cues for URL interactivity:

What you can do to prepare:

• Update any internal documentation that references the quarantine preview experience.
• Communicate these changes to helpdesk and support teams to reduce confusion.
• No configuration changes are required; the update will apply automatically.

Compliance considerations:

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

To streamline integration options and align with partner offerings, Microsoft is retiring the managed connectors for UKG and Blue Yonder in Microsoft Teams Shifts. This change supports a transition to more flexible and scalable integration methods, including partner apps and custom APIs.

When this will happen:

• The retirement will take effect on November 14, 2025.

How this affects your organization:

Who is affected:

• Organizations currently using the UKG or Blue Yonder managed connectors in Teams Shifts.
• Admins planning to deploy these managed connectors.

What will happen:

• The UKG and Blue Yonder managed connectors will no longer be available in Teams Shifts after November 2025.
• Existing users will need to transition to alternate solutions before the retirement date.
• New customers will not be able to deploy these managed connectors going forward.

What you can do to prepare:

• Work with your Microsoft account team to complete your transition plan.
• UKG customers can adopt the UKG Flow app available in Teams. Learn about UKG Flow for Microsoft Teams.
• Other customers can build custom integrations using Create a custom integration to sync your workforce management system with Shifts | Microsoft Learn.
• Communicate this change to helpdesk and operations teams managing workforce scheduling.
• Update internal documentation to reflect the retirement and new integration paths.
• For questions, contact your Microsoft account representative.

[Introduction:]

We’re introducing support for emojis in custom section names in Microsoft Teams. This update allows users to personalize and visually organize their workspace more expressively, aligning with familiar experiences from other collaboration platforms like Slack. Initially, this feature will be available on Teams for Desktop and Web, with support for Teams on Mobile coming next semester.

This message is associated with Microsoft 365 Roadmap ID 503300.

[When this will happen:]

• Targeted Release: Rolling out early November 2025; expected completion by mid-November 2025.
• General Availability (Worldwide): Rolling out late November 2025; expected completion by end of November 2025.

[How this affects your organization:]

Who is affected: All Microsoft Teams users across commercial and education tenants.

What will happen:

• Users will be able to insert emojis directly into custom section names in Teams:

 

• Emojis will appear in the left navigation pane, providing visual anchors for sections:

 

• This feature is ON by default and does not require admin configuration.
• No changes to existing admin policies or controls.

[What you can do to prepare:]

• No action is required to prepare.
• If desired, communicate this update to helpdesk staff to address potential user questions.
• Consider updating internal documentation if section naming conventions are referenced.

[Compliance considerations:]

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

• Information about audit table and data changes
• Information about Dataverse auditing

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

Updated October 7, 2025: This release has completed as of October 3, 2025. Thank you for your patience.     

Earlier this year, the new Microsoft device ecosystem platform built on the Android Open-Source Project (AOSP) was announced delivering state-of-the art security, reliability, and manageability with Microsoft Intune. Microsoft Teams Android devices will be migrating to this platform. The first step in the migration is a firmware update to Microsoft Teams Android devices in 2024. The firmware update will move devices from Android device administrator to Android AOSP management.

[When this will happen:]

A Preview program for select Microsoft Teams Android devices is targeted for Q2 of calendar year 2024. General release of the firmware update with the Android AOSP management stack will happen starting in Q4 of calendar year 2024 throughout Q1 of calendar year 2025 for all eligible Microsoft Teams Android devices. Auto updates will commence starting May 15th into Q3 calendar year 2025.

Eligible Microsoft Teams Android devices will initially receive a manual firmware update in Teams Admin Center so IT admins can manually verify the migration on their own schedule on select devices of their choosing.

Eventually, the firmware update for migration will be scheduled as an automatic firmware update in Teams Admin Center. This automatic firmware update can be deferred for up to 60 days from first availability based upon the admin configured stages in Teams Admin Center.

[How this will affect your organization:]

The firmware upgrade, including the support for Intune management of Android (AOSP) devices must be accepted. It can be deferred for up to 60 days after it is first available. This can be done in the same way as other firmware upgrades in Teams Admin Center. 

Devices will continue to remain signed in after the firmware upgrade.

Certain legacy devices will not receive the firmware upgrade for Android (AOSP) management in Intune. These devices will continue using Device Administrator.

[What you need to do to prepare:]

Policies will not be migrated automatically between Android device administrator and Android (AOSP) platforms. IT admins will need to create the appropriate new policies under the Intune Android (AOSP) platform to support their Microsoft Teams Android Devices.

This will need to be done before taking the firmware update for a successful migration.

More details on enabling support and creating enrollment profiles and policies for Intune AOSP can be found here: Moving Teams Android Devices to AOSP Device Management | Microsoft Community Hub