Microsoft Roadmap, messagecenter and blogs updates from 20-05-2026

Updated March 20, 2026: We have paused release of this feature at this time. We will update this post when we are ready to move forward. Thank you for your patience. 

Introduction

Microsoft Edge for Business will soon support Rewrite, a new feature powered by Microsoft 365 Copilot Chat. This capability helps users draft and rephrase editable text directly within Edge, enhancing productivity and writing quality. Users can access Rewrite by highlighting editable text and right-clicking to open the context menu.

This message is associated with Microsoft 365 Roadmap ID 420335.

When this will happen

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

How this affects your organization

• Rewrite will be enabled by default for Edge for Business users. 
• Users can access Rewrite by highlighting editable text and right-clicking to open the context menu.

• If Microsoft 365 Copilot is restricted from accessing page content due to Data Loss Prevention (DLP) policies, Rewrite will not function on that content.
• Admins can manage this feature using the InlineComposeEnabled policy setting.

What you can do to prepare

No admin action is required before rollout.

We recommend:

• Reviewing your current DLP configurations to understand how they may impact Rewrite functionality.
• Notifying users about this new capability.
• Updating internal documentation to reflect this change.

Learn more about how DLP affects Copilot access to page content: Microsoft 365 Copilot Chat in Edge and Access to Page Content | Microsoft Edge | Microsoft Learn

Compliance considerations

Updated May 19, 2026: We are updating this post as an informational reminder to help ensure you are informed and can proactively mitigate potential connectivity issues. Please review your configurations. Thank you for your patience. 

[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 and *.static.microsoft are not blocked on your enterprise network. Please ensure your configurations adhere to the guidance in Microsoft network guidance on domains and service endpoints. 

[Compliance considerations:]

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

Updated May 19, 2026: We have updated the timeline. Thank you for your patience.

[Introduction]

To support frontline workers using personal devices, Microsoft is introducing a dynamic onboarding wizard for Microsoft Teams. This experience is designed to simplify setup on Android and iOS devices, especially in environments with security policies like multi-factor authentication (MFA) and mobile application management. The wizard adapts automatically to your organization’s policies, helping drive secure and efficient Bring Your Own Device (BYOD) adoption.

This message is associated with Roadmap ID 523213.

[When this will happen:]

• Public Preview: Rollout begins in late November 2025 and is and expected to complete by mid-January 2026
• General Availability: Rollout begins in mid-August (previously mid-June) and is and expected to complete by mid-September (previously early July).

[How this affects your organization:]

• Who is affected: Frontline workers setting up Microsoft Teams on personal Android or iOS devices
• What will happen:
  • A new onboarding wizard will be available via web, optimized for desktop kiosks or shared PCs
  • The wizard dynamically adjusts based on your organization’s security policies
  • Supports MFA setup, with emphasis on Microsoft Authenticator push notifications
  • This tool is optional and designed to improve BYOD Microsoft Teams adoption

[What you can do to prepare:]

• Review the admin documentation to understand the onboarding wizard’s capabilities and limitations
• Consider integrating the wizard into your new user onboarding workflows
• Communicate availability to helpdesk and frontline managers
• Update internal documentation if you support BYOD Microsoft Teams deployment
• Review documentation at the following link: Set up frontline Teams on personal devices

[Compliance considerations:]

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

Updated March 9, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction:]

Microsoft Edge for Business will soon support summarization and contextual grounding with Microsoft 365 Copilot Chat. This enhancement enables users to ask Copilot questions about multiple open browser tabs, Microsoft 365 documents (such as Word, Excel, PowerPoint), and YouTube videos directly from the Edge side pane.

This message is associated with Microsoft 365 Roadmap ID 496364, 499423, and 499424.

[When this will happen:]

General Availability (Worldwide): We will begin rolling out in late April (previously mid-March).

[How this affects your organization:]

Who is affected: Users signed in to Microsoft Edge for Business with their Entra ID and who have access to Microsoft 365 Copilot.

What will happen:

• Users will be able to ask Copilot questions about open browser tabs, Microsoft 365 documents, and YouTube videos.
• The feature will be off by default.
• If Copilot is restricted from accessing page content via Data Loss Prevention (DLP) or the EdgeEntraCopilotPageContext policy, it will be suppressed to maintain DLP integrity.
• Existing DLP and policy configurations will be respected.

[What you can do to prepare:]

• This rollout will happen automatically by the specified date; no admin action is required before rollout.
• Ensure users who need this capability have access to Microsoft 365 Copilot.
• Ensure your tenant is configured to support Microsoft 365 Copilot and that eligible users meet all licensing prerequisites, including Entra ID sign-in and applicable Microsoft 365 service plans.
• Review your current DLP and Edge policy configurations to determine potential impact.
• Notify users about this upcoming capability.
• Update internal documentation if needed.

Learn more:

• Microsoft 365 Copilot Chat in Edge and Access to Page Content | Microsoft Edge | Microsoft Learn
  
• Microsoft Edge – Policies | Microsoft Edge | Microsoft Learn
  

[Compliance considerations:]

Updated May 18, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

Enable Microsoft Purview to access, process, and store prompt and response data—including associated metadata—from Microsoft Foundry apps and agents. This integration supports key data security and compliance scenarios such as:

• Sensitive information type (SIT) classification
• Analytics and reporting through Microsoft Purview DSPM for AI
• Insider Risk Management
• Communication Compliance
• Microsoft Purview Audit
• Data Lifecycle Management
• eDiscovery

Microsoft Foundry now has direct integration with Microsoft Purview. This capability helps your organization manage and monitor AI-generated data in alignment with enterprise policies and regulatory requirements.

This message is associated with Microsoft 365 Roadmap ID 537271.

• Public Preview: Rolling out mid-December 2025, expected completion mid-January 2026.
• Worldwide: Rolling out end of May 2026 (previously mid-May), expected completion mid-June 2026 (previously mid-April).

• Who is affected: Admins managing Microsoft Foundry and Purview integrations.
• What will happen:
  • Admins can enable a toggle in Foundry to send AI interaction data to Purview.
  • Feature is opt-in; requires admin action to enable.
  • Once enabled, AI interaction data will be monitored and secured for compliance purposes.

• Work with the Foundry subscription owner to enable the toggle in the Foundry control plane.
• Pre-requisite: Assign “Cognitive Services Security Integration Administrator” role.
• Steps:
  • Go to Operate → Compliance.
  • Select the “Security” tab.
  • Select the Azure Subscription.
  • Click the enablement toggle next to “Microsoft Purview.”
• Repeat for other Azure subscriptions as needed.

Learn more: Use Microsoft Purview to manage data security & compliance for Microsoft Foundry | Microsoft Learn

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

Updated May 19, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

To help organizations analyze more recent Microsoft 365 Copilot usage trends, we’re adding a new export option in the Copilot dashboard. In addition to the existing user‑week export (see MC1173208), dashboard users with company‑level access will be able to export a subset of de‑identified Copilot usage metrics aggregated by user and day. This option includes 28 days of activity data and supports more granular, short‑term insights into Copilot adoption. Exported data will usually reflect copilot activity up to 3 days before the export date; actual timing may vary 

A minimum of 50 Microsoft 365 Copilot licenses is required. This feature applies to the Viva Insights web app.

This message is associated with the Microsoft 365 Roadmap ID 547749.

• Screenshot 1 – Export data button in Copilot dashboard:



• Screenshot 2 – Copilot dashboard export options:

  

[When this will happen]

• Public preview: Mid-May 2026 (previously Early April) – End of May 2026 (previously late April)
• General availability (Worldwide): Early September 2026 (previously early August) – End of September 2026 (previously end of August)

[How this affects your organization]

Who is affected

This feature is available to Copilot dashboard users with full company-level data access, including:

• Senior leaders (as identified in Entra ID)
• Admin‑assigned company‑level users
• Delegates with company‑level access
• Global analysts and admins
• Group managers with access restricted to their own teams won’t have access to the user-day export.

What will happen

• A new export option will allow eligible users to download de-identified, row-level Copilot usage metrics aggregated by user and day, covering the most recent 28 days.
• Organizations can use this export to assess short-term usage patterns, support tactical adoption efforts, optimize licensing, and evaluate the impact of recent changes.
• Exported data will usually reflect copilot activity up to 3 days before the export date; actual timing may vary
• The export supports analysis across Copilot-enabled apps (for example, Word, Excel, Teams) and includes two additional attributes: Organization and Job function.
• Copilot activity metrics in exports run within 2 days of Copilot license assignments or removals may not reflect those license changes. Exports run after the 2‑day window will accurately reflect the impact of those license changes in copilot activity metrics under normal conditions.
• Data in previously exported files will not be automatically updated or modified after the export is generated.
• Access to the new user‑day export uses the same Viva Feature Access Management (VFAM) controls as the existing user‑week export (Viva Insights → Copilot Metrics Export). No new access controls are introduced. Existing VFAM settings for the Copilot dashboard export will remain in effect and apply to both day and week level export options after the day level export is released. Please read MC1173208 for more details.

[What you can do to prepare]

• Review and update VFAM settings for users with company‑wide access to the Copilot dashboard.
• Inform eligible users about this new export option.
• No additional admin configuration is required if export functionality is already enabled.
• Admins may disable the export feature for the tenant or specific groups at any time through VFAM.

Learn more:

• Connect to the Microsoft Copilot Dashboard for Microsoft 365 customers | Microsoft Learn
• Microsoft Viva Feature access management | Microsoft Learn

[Compliance considerations]

No compliance considerations identified. Review as appropriate for your organization.

Updated May 18, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

We’re introducing endpoint Data Loss Prevention (DLP) events as a queryable data source in Data Security Investigations (DSI) in Microsoft Purview. With this update, administrators can build endpoint DLP queries directly in DSI using filters such as date range, and DSI will automatically pull files associated with those events into the investigation for analysis. This integration helps security teams examine endpoint DLP activity at scale, reducing time and effort spent triaging individual alerts and improving the ability to identify patterns and potential data exfiltration scenarios.

This message is associated with Microsoft 365 Roadmap ID 558547.

[When this will happen]

• Public Preview: Rollout begins in early June 2026 (previously late April) and completes in early June 2026 (previously mid‑May).
• General Availability (Worldwide): Rollout begins in mid-June 2026 (previously mid‑May) and completes in mid-June 2026 (previously mid‑May).

[How this will affect your organization]

Who is affected

Admins and security investigators using Data Security Investigations (DSI) and endpoint Data Loss Prevention (DLP) in the Microsoft Purview compliance portal.

What will happen

• A new Endpoint DLP tab will appear in the DSI search experience, alongside the existing Query Builder and Audit tabs.
• Admins and investigators can query endpoint DLP events using date range filters (additional filters coming soon).
• Files associated with matching endpoint DLP events will be automatically added to the investigation scope for analysis using DSI’s AI‑powered tools.
• This feature will appear automatically for eligible tenants when rollout completes. No admin action is required to enable it.
• There is no user impact.

[What you can do to prepare]

No action is required. Optionally, you may:

• Review how endpoint DLP query capabilities work within DSI.
• Update internal documentation for alert triage and investigation workflows, if applicable.
• Inform security teams and endpoint DLP administrators about this new capability.

Learn more: 

• Learn about Data Security Investigations | Microsoft Purview | Microsoft Learn
  
• Learn about Endpoint data loss prevention | Microsoft Purview | Microsoft Learn

[Compliance considerations]

Updated May 19, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

Meeting organizers can now select Transcribe only as an automatic meeting option in Microsoft Teams. This setting starts transcription automatically when the meeting begins—without creating a recording—providing more granular control in meetings where recording is restricted due to compliance or privacy policies while still supporting accessibility, Microsoft Copilot, and Intelligent Recap.

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

Screenshot: Updated meeting options showing Off, Record and transcribe, and Transcribe only:

[When this will happen:]

• Targeted Release: We will begin rolling out in late April 2026 and expect to complete by late April 2026.
• General Availability (Worldwide): We will begin rolling out in early May 2026 and expect to complete by early June 2026 (previously mid-May).

[How this affects your organization:]

Who is affected:

• Microsoft Teams meeting organizers with transcription enabled through meeting policies
• Admins managing Teams meeting and recording policies

What will happen:

• Previously, the Record and transcribe automatically meeting option was a single on/off toggle that always started both recording and transcription together.  This option will be replaced with a list of automatic meeting settings when scheduling a meeting:
  • Off: No automatic recording or transcription (default)
  • Record and transcribe: Both recording and transcription start automatically (same as previous automatic recording behavior)
  • Transcribe only: Only transcription starts automatically; no recording is created
• When Transcribe only is selected, the meeting transcript is generated and available after the meeting without any recording artifact being stored.
• The meeting policy AllowTranscription must be set to On for the organizer to see the Transcribe only option.
• If the Who can record and transcribe meeting option is set to No one, all automatic transcription options (including Transcribe only) are forced Off.
• Standard Teams transcription (included in Microsoft 365 E3/E5) is sufficient for the Transcribe only option. No additional license is required.

[What you can do to prepare:]

• No administrative action is required before the rollout.
• Review your organization’s meeting policies to ensure AllowTranscription is enabled for users who require this capability.
• Update internal documentation or training materials to reflect the new meeting option.
• Notify meeting organizers about the availability of the Transcribe only setting.

Learn more: Manage meeting transcription and captions in Microsoft Teams | Microsoft Learn

[Compliance considerations:]

Updated May 19, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

Microsoft Teams is introducing Efficiency Mode, a performance-optimized experience designed for hardware-constrained devices. This change improves app responsiveness and meeting quality by adjusting resource usage based on device capabilities.

This message applies to Teams for Windows desktop and Teams for Mac desktop and is associated with Roadmap ID 560055.

[When this will happen:]

General Availability (Worldwide): Rollout begins in late May 2026 (previously early May) and is expected to complete by end of May 2026 (previously mid-May).

[How this affects your organization:]

Who is affected:

• Users running Microsoft Teams on hardware‑constrained devices (for example, devices with limited CPU, memory)
• 
  
• What will happen:

• Efficiency Mode is enabled by default on eligible devices.
• An Efficiency Mode indicator appears in the Teams app title bar.
• When enabled:
  • Video resolution sent from the user’s camera is dynamically adjusted in meetings.
  • The app launches without a pre-selected chat and shows a static image in the message pane.
• Users can opt out via Settings > General > “Never use efficiency mode.”

[What you can do to prepare:]

• No action is required if the default behavior works for your organization.
• Consider informing helpdesk teams about the new mode and opt-out option.
• Update internal documentation if applicable.

[Compliance considerations:]

Users can enable or disable the feature themselves. No other compliance considerations were identified.

Updated May 19, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

Microsoft Teams is introducing enhanced recap sharing. Meeting organizers can grant access to meeting recordings, transcripts, AI-generated summaries, and notes when copying or sharing a recap link. This update improves how meeting content can be shared with people who were not part of the original meeting.

This message is associated with Microsoft 365 Roadmap ID 559606.

[When this will happen:]

• Targeted Release: We will begin rolling out in late May 2026 (previously mid-May) and expect to complete by end of May 2026 (previously mid-May).
• General Availability (GCC): We will begin rolling out in early June 2026 and expect to complete by early June 2026.
• General Availability (Worldwide): We will begin rolling out in early June 2026 and expect to complete by late June 2026.
• General Availability (GCC High): We will begin rolling out in early July 2026 and expect to complete by early July 2026.

[How this affects your organization:]

Who is affected:

• Microsoft Teams users who organize or attend meetings with recaps enabled.

What will happen:

• Meeting organizers can:
  • Grant access to the meeting recording, transcript, AI summary, and notes when copying or sharing a recap link.
  • Specify which people receive access at the time the recap link is shared.
• Meeting attendees who are not organizers can:
  • Copy or share recap links.
  • Recipients who were not in the meeting will be prompted to request access.
• The feature will be available by default.

To use this feature:

1. Select the Share menu in the top-right corner of the recap page or on the recap thumbnail in the meeting chat.

Screenshot 1: Recap page with Share menu highlighted:

>

Screenshot 2: Meeting chat with Share icon highlighted:



2. If the user is the meeting organizer: The user can specify people and copy or share the recap link while granting recap access to the specified people.

Screenshot 3: Share this recap options available to a meeting organizer:



If the user is not the organizer: The user can copy the recap link or share it by sending the link in a Teams chat. People who were not in the meeting will need to request access.

[What you can do to prepare:]

• No admin action is required.
• Inform users about the new sharing experience.
• Update internal documentation or helpdesk guidance if needed.

Learn more: Recap in Microsoft Teams | Microsoft Support (we will update the Share recap section before General Availability)

[Compliance considerations:]

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

• Questions generated from the last seven days are assigned to the suggested themes
• On a daily basis, new questions are generated.
• Users with sufficient privileges
• Additional metrics, such as the number of questions asked about the theme, answer rate, quality of response, and user feedback, are created.

• Enable manual recording for non-voice engagements through settings.
• Specify which roles can start, stop, review, or download recordings using existing security roles.
• Disable individual capabilities at any time by turning off the relevant settings or removing role permissions.
• Manually link recordings to cases or conversations when sessions don’t originate from voice calls, ensuring recordings are attached to the correct entity.

[Introduction]

To help organizations access more up-to-date Microsoft 365 Copilot insights, we are introducing a new Power BI report and query named Microsoft 365 Copilot latest usage snapshot for analyst users in Viva Insights Advanced Insights.

This report provides Copilot usage data updated daily and includes three months of activity, typically available within two to three days prior to the current date. This capability helps analysts monitor recent adoption trends and better understand short term usage patterns across their organization.

This message is associated with Microsoft 365 Roadmap ID 561325.

[When this will happen]

• Public Preview: We will begin rolling out in early July 2026 and expect to complete by late July 2026.
• General Availability (Worldwide): We will begin rolling out in early November 2026 and expect to complete by late November 2026.

[How this affects your organization]

Who is affected

• Viva Insights users with the Insights Analyst role
• Users who work in the Viva Insights web app and use Power BI for advanced analysis

What will happen

• A new Power BI report and query named Microsoft 365 Copilot latest usage snapshot will be available to eligible analysts.
• Daily Copilot usage data will be available with up to three months of activity history.
• Activity data typically reflects usage up to two to three days before the current date, actual timing may vary.
• The Adoption overview page provides an organization-wide view of Copilot usage, including:
  • adoption trends
  • group-level adoption
  • usage by app and feature

    

• Data can be filtered and segmented using organizational attributes and time ranges to identify patterns and areas of strong or low adoption.
• Custom analysis is supported through the included query based on daily data, with export options through CSV download, the Power BI connector, or Microsoft Fabric.
• Microsoft 365 Copilot licenses and Viva Insights licenses must be assigned to users included in the analysis.
• Availability requires at least 50 Microsoft 365 Copilot licenses in the organization.
• The report is available by default to eligible users, and no additional admin configuration is required.
• Existing Copilot Analytics reports and queries are not changed.

The following metrics are not supported in this report or query at this time:

• Meeting hours recapped by Copilot
• Meeting hours summarized by Copilot in Teams
• Meetings recapped by Copilot
• Total meeting hours summarized or recapped by Copilot
• Total meetings summarized or recapped by Copilot
• Copilot assisted hours or dollar value
• All Copilot for Sales metrics 
• Any metrics related to power users

[What you can do to prepare]

No admin action is required if your organization already meets the prerequisites.

You can prepare by taking the following steps:

• Confirm that appropriate users are assigned the Insights Analyst role in Viva Insights.
• Ensure users have the latest version of Power BI Desktop installed. If users have an older version installed, they should uninstall it and install the latest version before using the report.
  • Getting started with Power BI
• Verify that users included in the analysis have the required licenses assigned.
• Communicate this new capability to analyst users in your organization so they know what to expect.

Learn more: 

• Advanced analysis introduction | Viva Insights | Microsoft Viva | Microsoft Learn
• Getting started with Power BI | Microsoft
• Export query data to Power BI | Viva Insights | Microsoft Viva | Microsoft Learn
• Export query data to Microsoft Fabric | Viva Insights | Microsoft Viva | Microsoft Learn
• Power BI report templates | Viva Insights | Microsoft Viva | Microsoft Learn

[Compliance considerations]

No compliance considerations identified. Review as appropriate for your organization.

• Performance versus target and quota attainment
• Pipeline coverage relative to revenue goals
• Variance between forecasted, actual, and invoiced results
• Identification of operational and revenue risk

Updated May 18, 2026: We have updated the timeline for Phase 2. Thank you for your patience.  

What it is

Microsoft is rolling out a new feature to streamline how app and agent availability is managed across Teams, Outlook, and Microsoft 365 Copilot. Until now, IT admins configured availability settings separately in both the Microsoft 365 Admin Center (MAC) and the Teams Admin Center (TAC), which led to mismatches. With this update, you’ll be able to unify availability policies for apps and agents across both portals, making app management more consistent and efficient.

This message is associated with Microsoft 365 Roadmap ID 393931, 485712 and 503105.

When this will happen:

We will begin rolling out this feature late September 2025 and expect to complete by August 2026 (previously end of June).

1. Phase 1 – Default Tenant Unification of App/Agent Availability

We will begin rolling out this feature at the end of September 2025. This initial phase targets tenants that have never modified their organization-wide defaults, app availability, or block/unblock in either the Microsoft 365 admin center or the Teams admin center. At the end of this phase, agent and app manageability will be unified across both Microsoft 365 admin center and Teams admin center ensuring agent and Microsoft 365 apps availability policies are in alignment for all future administrative changes. This message is associated with Microsoft 365 Roadmap ID 393931.

2.Phase 2 – Modified Tenants Unification of App/Agent Availability

This phase targets tenants that have previously modified their organization-wide defaults, app availability, or block/unblock settings in either admin center. These tenants will be transitioned to a unified management experience across both Microsoft 365 and Teams admin centers.

• For tenants with no agent or app availability differences across both admin centers, guidance will be provided to help maintain unified availability policy for all future changes. We will begin rolling out this feature in early November 2025.
  
  • This message is associated with Microsoft 365 Roadmap ID 485712 & 503105.