Microsoft Roadmap, messagecenter and blogs updates from 26-03-2026

Updated March 25, 2026: We have updated the timeline. This post has also been updated to remind customers that this feature is default-on for Copilot Dashboard users with full company-level data access. The export output remains de-identified, with each user represented by a hashed ID. Please review and take any actions as appropriate for your organization. Thank you for your patience.

This MC post is associated with Roadmap ID 500872.

[Introduction:]

To support deeper analysis of Copilot adoption, Microsoft is introducing a new export capability in the Copilot Dashboard. This feature allows dashboard users with company-level access to download de-identified Copilot usage metrics, aggregated by user and week, from the past six months. Organizations can use this data to track adoption trends, optimize licensing, and support AI transformation strategies.

This feature requires at least 50 Microsoft 365 Copilot licenses and applies to the Viva Insights web app.

[When this will happen:]

• Public Preview: Begins in early December 2025 (previously late November 2025), completes by late December 2025.
• General Availability (Worldwide): Begins in late April 2026 (previously late March), completes by early May 2026 (previously early April).

[How this affects your organization:]

Who is affected:

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, as well as global analysts and admins. 

Note: Group managers with data access limited to their own teams will not have access to this feature.

What will happen:

• Users will be able to export de-identified, row-level Copilot usage metrics from the dashboard.
• The dataset includes weekly, user-level metrics from the past six months.
• The export supports Copilot usage analysis across apps (such as Word, Excel, Teams), and includes two attributes: Organization, and Job function.
• Organizations can use the data to track usage patterns, generate insights to inform adoption strategies, optimize licensing, and measure ROI.
• The feature is enabled by default for eligible users.
• Admins can manage access via Viva Feature Access Management (VFAM) settings, under Module: Viva Insights; Feature: Copilot Metrics Export.
• No impact to user workflow unless accessed by eligible users.

Screenshot 1 – View of the new Microsoft Copilot dashboard: 

Screenshot 2 – Example of output: 

[What you can do to prepare:]

• Review the assignment of the Copilot dashboard users with full company-wide data access and adjust VFAM policies as needed.
• Communicate the upcoming feature to eligible users so they know what to expect.
• No admin setup is required to start using the export.
• Admins can disable the feature at the tenant or group level at any time using VFAM settings.

Learn more: 

Microsoft Viva Feature access management | Microsoft Learn

Connect to the Microsoft Copilot Dashboard for Microsoft 365 customers | Microsoft Learn

[Compliance considerations:]

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

Updated March 25, 2026: We have updated the content. Thank you for your patience. 

[Introduction]

We are resurfacing MC670435, published September 2023 to remind admins of the Microsoft Teams Premium self-service trial capability. This message serves as a reminder as we begin a broader rollout of the feature announced in 2023. As we expand rollout and introduce additional entry points for this feature, we want to ensure continued awareness and readiness.

[When this will happen:]

Ongoing rollout. 

[How this will affect your organization:]

When rolled out, users within your organization will be able to directly initiate a Teams Premium trial. These self-service trial licenses will be a part of your Microsoft organizational tenant, and you will be able to manage these licenses like other Microsoft subscriptions. You will be able to cancel these trial licenses at any time.

If you choose to disable the self-serve trials, please refer to self-service trial controls. After disabling the policy, it may take between 24-72 hours for the trial entry point to be removed from Teams. We also recommend fully restarting the app (quit and relaunch) to ensure the change is reflected.

You will also be able to fully control whether trials are converted to paid subscriptions. Users will not need to input payment information when signing up. If a user would like to convert to a paid license, they must work with you directly to do so as there is no auto-renew functionality for these trials. If a user isn’t upgraded to a paid subscription, all services included in their Microsoft Teams Premium will end, and the user may lose read only access to data generated by Teams Premium, stored in Microsoft Teams, OneDrive, and SharePoint.

Users in tenants where self-service trials are disabled may still see the “Get Premium” prompt when accessing features that require a premium license. This is expected behavior and helps signal user interest to admins. It can also help identify which users in your organization may need a Teams Premium license, allowing you to better manage and allocate your available licenses.  To reduce confusion and prevent users from submitting license requests, admins can customize the license request flow. Instead of showing the default request form, they can configure a custom message explaining that license requests are not supported in their organization. For setup instructions, see Use your own request process – Microsoft Learn.

Microsoft Teams Premium helps make your Teams meetings more intelligent, protected, and engaging. Unlike other meeting and collaboration tools, Teams Premium brings advanced capabilities for meetings, virtual appointments, and webinars together for one low cost. You can learn more about Teams Premium here.

The customer data for all services associated with the Microsoft Teams Premium trial will be handled in accordance with the Microsoft Online Subscription Agreement and the Product Terms.

[What you need to do to prepare:]

Global or billing admins can use the same self-service purchase controls to disable self-service trials while making use of subscription management capabilities to oversee and manage trial licenses on the Your Products page in the Billing section of Microsoft 365 admin center.

Note: This is a new Teams Premium trial and is enabled or disabled independently of past trial offerings.

Review our updated self-service purchase and trial documentation here. We’ve added important information about the way trials work, the data that is collected, and the terms that apply.

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

Expected in mid-June 2026 (previously mid-February), as part of our modernization efforts, we are updating the Intune Data Warehouse with a new architecture to enhance scalability, performance, and align with the reporting infrastructure. The Intune Data Warehouse provides structured access to historical Intune data through an OData API, enabling you to build custom reports and dashboards using tools like Power BI and Excel. This update includes several key changes to be aware of:

• Historical data reset: Once updated, the data will be reset and there will only be approximately 30 days of data.
• Updated licensing definition: The “IntuneLicensed” property will now include all forms of Intune licensing and grace periods.
• Surrogate key refresh: Surrogate keys will be regenerated as part of the infrastructure update.

[How this will affect your organization:]

If your organization is using the Intune Data Warehouse you will need to be aware of this upcoming change. Additionally, if you are using the Intune Data Warehouse (beta) Power BI connector, support for this connector will be discontinued. A new connector will be available, requiring use of the OData feed link within the Intune admin center.

[What you need to do to prepare:]

• Ensure your reporting tools are configured to use the OData feed from the Intune admin center.
• If you are using the Intune Data Warehouse (beta) Power BI connector, transfer to the OData feed. For instructions refer to: Connect to the OData feed for the Intune Data Warehouse for your tenant
• Back up any historical data you wish to retain before this update.
• Review any dependencies on surrogate keys and prepare for key refreshes.
• Familiarize yourself with the updated licensing definitions and reporting behavior.

[Additional information:]

For more details on the data warehouse and alternative solutions, please refer to:

• Intune Data Warehouse API Endpoint
• Integrating Azure Data Factory and the Microsoft Intune Export API

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

[Introduction:]

We’re introducing the ability to add public web links as references in Microsoft Copilot Notebooks. This enhancement allows users to ground Copilot responses on specific public web pages, expanding the types of content that can be used to inform and contextualize their work.

A Microsoft 365 Copilot license is required to use this feature.

This message is associated with Microsoft 365 Roadmap ID 516040.

[When this will happen:]

General Availability (Worldwide): Rollout will begin in late April 2026 (previously late March) and is expected to complete by end of April 2026 (previously late March).

[How this will affect your organization:]

Who is affected: All users of Microsoft Copilot Notebooks with a Microsoft 365 Copilot license.

What will happen:

• Users will be able to add public web links as references in their Copilot Notebooks.
• This expands current capabilities, which already support referencing Word, PowerPoint, Excel, and other file types.
• Users can now ground Copilot on public web content without needing to convert it to a file format (such as PDF).
• The feature will be enabled by default.

[What you can do to prepare:]

No specific preparation is required. However, we recommend:

• Informing users about the upcoming capability to enhance their productivity.
• Updating internal documentation if you provide guidance on using Copilot Notebooks.

[Compliance considerations:]

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

[Introduction]

Microsoft is retiring the -Credential parameter used when connecting to Exchange Online PowerShell. Starting with module versions released in July 2026 and later, the -Credential parameter will be removed from both Connect-ExchangeOnline and Connect-IppsSession cmdlets. Organizations using this parameter in automation scripts must migrate to a supported authentication method before that date. This change improves security by moving away from legacy authentication methods that do not support modern protections such as multifactor authentication (MFA).

[When this will happen:]

• The -Credential parameter will be removed from Connect-ExchangeOnline and Connect-IppsSession cmdlets in Exchange Online PowerShell module versions released beginning July 2026.
• A separate server-side retirement of the underlying authentication flow is planned for a later date and will be communicated in advance.

[How this affects your organization:]

Who is affected:

• Microsoft 365 administrators using Exchange Online or Security & Compliance PowerShell
• Organizations with automation scripts that use the -Credential parameter

What will happen:

• If your organization uses the -Credential parameter in PowerShell scripts or automation workflows connecting to Exchange Online or Security & Compliance PowerShell, those scripts will break when you update to an Exchange Online PowerShell module version released beginning July 2026.
• No impact if your organization does not use the -Credential parameter

What you can do to prepare:

• If you are using the -Credential parameter, begin migrating your scripts now. Do not wait until July 2026. Choose the appropriate alternative based on your scenario:

• Interactive admin access: Switch to modern authentication with MFA. Learn more: Connect to Exchange Online PowerShell.
• Automation outside Azure: Use app-only authentication (certificate-based). Learn more: App-only authentication for unattended scripts in Exchange Online PowerShell and Security & Compliance PowerShell.
• Automation within Azure: Use managed identity authentication (no secrets required). Learn more: Use Azure managed identities to connect to Exchange Online PowerShell.
• Review internal documentation and communicate changes to admins

• If you are not using the -Credential parameter, no action is required.

Additional information

This change is currently client-side only and will not take effect automatically. Your existing scripts will continue to work if you continue using an Exchange Online PowerShell module version released before July 2026. The -Credential parameter will only be removed when you upgrade to a module version released in July 2026 and later.

A separate server-side retirement of the Credential parameter authentication flow is planned for a later date. When that occurs, the -Credential parameter will stop functioning even on older module versions. Microsoft will communicate that timeline separately and provide advance notice before any service-side changes take effect.

We strongly recommend migrating proactively rather than waiting, to avoid disruption when either change occurs. If you have questions or concerns, contact Microsoft Support or leave a comment on the Exchange Team Blog post.

[Compliance considerations:]

1. https://globaldisco.crm.dynamics.com/api/discovery/v1.0/Instances
2. https://globaldisco.crm.dynamics.com/api/discovery/v2.0/Instances
3. https://globaldisco.crm.dynamics.com/api/discovery/v1.0/Instances({id})

1. Identify any applications or scripts that call globaldisco.crm.dynamics.com REST API endpoints.
2. Update your applications to use the Power Platform List Environments API instead of the GDS endpoints.
3. Test your updated integrations against the new endpoints to verify compatibility.

• Detection of missing or broken tool calls.
• Validation of routing and orchestration flows.
• Early identification of behavior regressions.
• Clear feedback indicating which tools or topics were not invoked.

[Introduction]

We are introducing Microsoft Purview Data Lifecycle Management (DLM) retention support for Microsoft Teams call logs. Microsoft Teams stores call logs in several persistent locations, such as Call Detail Record (CDR) logs, which are currently retained indefinitely. However, regulatory requirements in various countries specify maximum retention periods for calling-related logs, creating a potential compliance gap. This update enables organizations to manage retention or deletion of Teams call logs to meet regulatory obligations, while still supporting evolving product features and business needs.

This message is associated with Microsoft 365 Roadmap ID 559261.

[When this will happen:]

General Availability (Worldwide): Rollout will begin in late April 2026 and is expected to complete by late April 2026.

[How this affects your organization:]

Who is affected:

• Microsoft 365 compliance administrators
• Organizations using Microsoft Teams calling

What will happen:

• Compliance admins can apply Microsoft Purview DLM retention and deletion policies to Teams call logs.
• Teams call logs stored with Teams compliance data in Exchange Online mailboxes are no longer retained indefinitely by default.
• Existing Purview retention capabilities and workflows are respected.
• There is no direct impact to user calling experiences.

[What you can do to prepare:]

• Review your regulatory and business requirements for retaining Teams call logs.
• Create or update Microsoft Purview retention policies to retain or delete Teams call logs as required once the feature is available.
• Update internal compliance documentation and guidance for your compliance and legal teams.

[Compliance considerations:]

[Introduction]

We are introducing a new priority cleanup workflow in Microsoft Purview Data Lifecycle Management that allows administrators to permanently delete (hard delete) specific OneDrive and SharePoint content types, even when retention policies or holds are in place. This capability helps reduce data exposure risk from rapidly growing Copilot-related content while maintaining compliance through required eDiscovery admin review and approval.

This change is associated with Microsoft 365 Roadmap ID 558343.

[When this will happen:]

General Availability (Worldwide) Rollout begins late May 2026 and is expected to complete by mid-June 2026.

[How this affects your organization:]

Who is affected:

• Microsoft 365 administrators managing Microsoft Purview Data Lifecycle Management
• Organizations using OneDrive for Business and SharePoint Online with retention policies or holds

What will happen:

• Admins can create a priority cleanup policy targeting specific content types in OneDrive and SharePoint.
• A new Delete data permanently option enables hard deletion of targeted items.



• Content deleted through this workflow is fully removed and is no longer discoverable in:
  • SharePoint search
  • Copilot experiences
  • eDiscovery (after required approval)
• For content under hold, eDiscovery admin review and approval is required before deletion.
• This capability is not enabled by default and requires explicit admin configuration.
• There is no change to user workflows unless an admin configures and applies a priority cleanup policy.

[What you can do to prepare:]

• Review your organization’s data risk and retention strategy, especially for Copilot-generated content such as Teams transcripts.
• In Microsoft Purview, plan and configure a priority cleanup policy if permanent deletion is required for specific content types:
  • Navigate to Microsoft Purview portal > Data Lifecycle Management > Priority cleanup.
  • Create a new policy and select Delete data permanently in the policy settings.
• Ensure appropriate eDiscovery admin roles and approval processes are in place for content under hold.
• Update internal governance or compliance documentation to reflect this new deletion capability.

Learn more: Compare types of groups in Microsoft 365 – Microsoft 365 admin | Microsoft Learn

[Compliance considerations:]

Video Recap for Teams Meetings

[Introduction]

We are introducing video-based meeting recaps in Microsoft Teams to help users quickly catch up on meetings they missed or revisit key moments. Video recap creates narrated video highlights from recorded meetings, combining key takeaways with short video clips that showcase important discussion points. This enhancement builds on intelligent meeting recap and is designed to save time and improve information retention.

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

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• Users who view recorded Microsoft Teams meetings.
• Organizations with users licensed for Microsoft 365 Copilot.
• Only users with a Microsoft 365 Copilot license can access the video recap.

What will happen:

• Availability and eligibility
  • For recorded meetings conducted in English, users with a Microsoft 365 Copilot license will receive a Video recap, accessible from the upper-left area of the meeting recap page.

  

  • Video recap is currently supported for recorded meetings conducted in English only. For meetings in other spoken languages, the Video recap button will not appear.
  • The feature is enabled by default for eligible users.
• Video recap experience
  • Video recap is generated once per meeting.
  • For any given meeting, all users with a Microsoft 365 Copilot license receive the same video recap, including the full video content and AI-generated narrated audio.
  • The video recap presents narrated highlights and short video clips of key moments.
  • The narrated audio is an AI-generated voiceover based on the meeting recording and transcript.
• Sharing and administration
  • Organizers can share the meeting recap page.
  • Any meeting participant who is granted access to the recap will also have access to the video recap, subject to existing permissions and licensing.
  • No new administrative configuration or policy changes are required.

[What you can do to prepare:]

• No action is required from administrators.
• Consider updating internal training or help documentation to include video recap for Teams meetings.
• Inform helpdesk staff that users may see a new Video recap button on the meeting recap page for recorded meetings in English.

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

[Compliance considerations:]

The video recap shares the same permissions, retention policies, and compliance controls as the original meeting recording.