Microsoft Roadmap, messagecenter and blogs updates from 24-04-2026

Updated April 23, 2026: We have updated the timeline and content. Thank you for your patience.

Applies to: Teams for Windows desktop and Teams for Mac desktop 

[Introduction:]

All meeting participants joining from native apps on Windows and macOS will be able to request to start collaborative annotations when a screen or window is being shared. The annotations start only after the active sharer approves the request. This capability is available exclusively in the new Microsoft Teams experience on native Windows and macOS apps.

This release also introduces a meeting option in the Participation section, allowing organizers and co-organizers to choose who can start annotations. By default, “Everyone” can access the “Start Annotation” button, but organizers and co-organizers can limit it to just the “Active Sharer”, making the button visible only to the person currently sharing their screen or window.

Note: Users can view and annotate in Teams on the web but cannot initiate annotations. Anonymous users in the meeting will not be able to send a request.

This message is associated with Microsoft 365 Roadmap ID 89975.

[When this will happen:]

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

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

[How this will affect your organization:]

After the rollout, meeting participants who are not sharing their screens will have the ability to request an annotation session. This request will be sent to the presenter sharing their screen, who can choose to accept or deny it.

Meeting Organizer Settings (Meeting Options)

A new “Who can start annotations?” option appears under the Participation section in Meeting Options. Organizers and co-organizers can select

• Everyone (default) — All participants see the “Start Annotation” button
• Active Sharer — Only the person currently sharing sees the annotation button 

Participant Annotation Request Flow 

When a participant who is not the active sharer wants to annotate, they click the “Start annotation” button in the meeting toolbar. A confirmation dialog appears, and once the participant clicks “Request”, a notification is sent to the presenter for approval.

1. Click the “Start annotation” button in the meeting toolbar to initiate an annotation request.



2. Confirm the request in the dialog box. Once approved, annotations start request will be sent to active sharer



3. Request sent notification confirms the request is pending and the presenter needs to approve it. 

Presenter Approval Experience

The active sharer (presenter) receives a notification at the top of their screen indicating that a viewer wants to start annotations. The presenter can choose to Deny or Allow the request.

[What you need to do to prepare:]

This rollout will happen automatically by the specified dates with no admin action required before the rollout. You may want to:

• Notify your users about this change and how the annotation request/approval flow works 
• Update relevant documentation to reflect the new meeting option and participant behavior 
• Educate meeting organizers on the new “Who can start annotations?” meeting option under Participation 
• Communicate to end users that they can now request to start annotations during screen sharing sessions 

This change will be available by default. 

Additional Resources: 

• Use annotation while sharing your screen in Microsoft Teams – Microsoft Support (will be updated before rollout)
• How to use Collaborative Annotations in a Microsoft Teams meeting (2022)
• Microsoft 365 Roadmap ID 89975

Updated April 23, 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-June 2026 (previously mid-May) and is and expected to complete by early July 2026 (previously early June).

[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 April 23, 2026: We have updated the timeline. Thank you for your patience. 

To improve security and user experience, Teams Mobile users on Android and iOS will soon be able to choose which browser opens non‑Office and PDF links. This update encourages the use of Microsoft Edge—which supports Single Sign-On (SSO), Copilot, and enhanced security—while still allowing users to choose their preferred browser.

General Availability (Worldwide): Rollout will begin in late February 2026 and is expected to complete by early May 2026 (previously late February).

General Availability (DoD, GCC, and GCCH): Rollout will begin in late February 2026 and is expected to complete by early May 2026 (previously late February).

During rollout, we will monitor user satisfaction (DSAT), Microsoft Edge installation rates, and retention.

[How this affects your organization]

Who is affected: All users of Microsoft Teams Mobile on Android and iOS.

What will happen:

• When users tap a non‑Office (Word, Excel, PowerPoint) or PDF link, a pop-up will appear at the bottom of the screen (a bottom sheet) prompting them to choose a browser.
• If Microsoft Edge is not installed and the user selects Edge, they will be prompted to download it.
• A new Links in Teams setting will appear in Teams Mobile settings:



• This feature will be enabled by default for all tenants.

Admins can manage this feature using PowerShell:

• Policy name: TeamsMobilityPolicy
• Attribute:LinksInTeams
• Allowed values:
  • OfferBrowserOptions — enables the feature
  • UseSystemDefaults — disables the feature

[What you can do to prepare]

IT Admins:

• Review and configure the LinksInTeamsattribute under TeamsMobilityPolicy via PowerShell.
• Update internal documentation and notify helpdesk teams about the new browser-selection experience.
• If your organization prefers to disable this feature, set LinksInTeams to UseSystemDefaults.

Users – To change your preferred browser:

1. Tap your profile icon in the upper-left corner of the Teams Mobile app.
2. Select Settings.
3. Select Links in Teams.
4. If Microsoft Edge is not installed and selected, you will be prompted to download it.

[Compliance considerations]

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

Updated April 23, 2026: We have updated the timeline. Thank you for your patience. 

Introduction

Microsoft is improving the reading and review experience in Microsoft 365 Copilot by enabling PDFs to open directly within Copilot when users click them. This update streamlines content access and reduces context switching based on customer feedback.

When this will happen:

General Availability (Worldwide): Rollout will begin in mid-April 2026 (previously mid-February) and is expected to complete by early May 2026 (previously late February).

How this affects your organization:

   Who is affected:

• All Microsoft 365 users who interact with PDFs in Microsoft 365 Copilot.
• A Microsoft 365 Copilot license is required to use this feature.

   What will happen:

• Users who click a PDF inside Copilot will have it open directly within the Copilot interface.
• The feature is enabled by default for all tenants.
• No admin configuration changes are required.
• Existing Purview policies for PDFs continue to apply.

What you can do to prepare:

• No action is required from administrators.
• Optionally notify helpdesk/support teams of the updated PDF experience.
• Update internal documentation if it describes Copilot PDF behavior.

Compliance considerations:

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

Updated April 23, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

We are updating the file-opening experience in Microsoft 365 Copilot Chat. When users click on cited Word, Excel, or PowerPoint content in Copilot Chat, the file currently opens in a new browser tab. With this update, supported files can open directly within Copilot chat to streamline viewing. This change does not apply to Copilot Mobile, Copilot in Edge, Copilot in Excel, Copilot in Word, or Copilot in PowerPoint.

[When this will happen:]

General Availability (Worldwide): rollout will begin in mid-April 2026 (previously late February) and is expected to complete by early May 2026 (previously early March).

[How this affects your organization:]

Who is affected:

• Users who access and open Word, Excel, or PowerPoint file citations within Copilot Chat in the web experience.
• A Microsoft 365 Copilot license is required to use this feature.

What will happen:

• Supported Word, Excel, and PowerPoint files will open directly inside Copilot Chat instead of opening in a new browser tab.
• This enhancement does not change permissions, data access, or existing configuration.
• The feature will be enabled by default.
• There is no change to Copilot Mobile, Copilot in Edge, Copilot in Excel, Copilot in Word, or Copilot in PowerPoint.

[What you can do to prepare:]

No admin action is required for this update.

• Notify helpdesk or training teams about the streamlined in-Copilot Chat file-opening experience.
• Update internal documentation if it describes file citation behavior.

[Compliance considerations:]

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

Updated April 23, 2026: We have updated the content. Thank you for your patience. 

[Introduction]

Microsoft is announcing the General Availability (GA) of federated Copilot connectors for Microsoft 365 Copilot.

Federated Copilot connectors enable users to securely connect Copilot to popular third‑party sources and retrieve data in real time using the Model Context Protocol (MCP). These connectors do not store or index customer data in Microsoft services; access occurs in real time using the user’s identity, while administrators retain full governance and control through the Microsoft 365 admin center.

With GA, federated Copilot connectors will be supported in Researcher agent, Microsoft 365 Chat, and Agent Mode in Excel, enabling users to bring external data directly into their workflows.

[When this will happen]

• General Availability (Worldwide): 
  • Admins would have started seeing federated Copilot connectors in Microsoft 365 admin center starting on April 20, 2026. Public documentation will be updated in the upcoming weeks. 
  • Rollout for users will begin in late April 2026 and complete by late May 2026.

[How this affects your organization]

Who is affected

• Organizations with Microsoft 365 Copilot Premium licenses

What will happen

• Microsoft‑published federated Copilot connectors (connector type: MCP) will appear under Microsoft 365 admin center → Copilot → Connectors and will be enabled by default.
• Admins will be able to:
  • View all Microsoft‑published federated Copilot connectors in one place.
  • Identify federated Copilot connectors by filtering on connector type: MCP.
  • Use staged rollout to enable specific connectors for selected users or groups.
  • Disable any connectors that do not align with organizational policies.
    • Admins can bulk‑disable all connectors using CLI, then selectively re‑enable individual connectors within the admin center.
• Users will be able to connect to federated Copilot connectors directly from:
  • Researcher agent
  • Microsoft 365 Chat
  • Agent Mode in Excel
• Public documentation will be updated as the rollout progresses.

Screenshot 1 – Manage federated Copilot connectors:

Screenshot 2 – Connect and use federated Copilot connectors:

Microsoft‑published federated Copilot connectors available at GA include:

• Canva
• HubSpot
• Linear
• Intercom
• Google Calendar
• Google Contacts
• Notion
• Moody’s
• LSEG

Note: Microsoft may initially release a subset of the connectors listed above, with additional Microsoft‑published federated Copilot connectors becoming available over time with prior notice.

The S&P connector, previously part of the announcement, will not be part of the GA release and will now be available at later date. 

Create Custom Federated Copilot Connectors

With GA, admins can now create custom federated Copilot connectors for internal or specialized data sources by connecting their own MCP server endpoint.

This allows organizations to:

• Extend Copilot to proprietary systems or internal tools.
• Control authentication, authorization, and data exposure through their MCP server. 
• Provide users secure, real‑time access to internal data without indexing or storage in Microsoft.

Custom connectors are managed alongside Microsoft‑published connectors in the Admin Center, ensuring consistent governance and lifecycle management.

Screenshot 3 – Create custom federated Copilot connectors

[What you can do to prepare]

• Review available Microsoft‑published federated Copilot connectors in Microsoft 365 admin center → Copilot → Connectors.
• Use the 7‑day, admin‑only review window before the connectors become available to users to validate compliance, risk posture, and readiness.
• Plan a staged rollout strategy using Entra ID group targeting if you want to enable connectors gradually.
• Disable any connectors that do not meet your organization’s security or compliance standards.
• Review your third‑party provider agreements, including data residency and licensing terms, before enabling federated Copilot connectors.
• Update internal documentation or helpdesk guidance as needed.

Note: By using Microsoft 365 Copilot connectors, you, as the data controller, authorize Microsoft to index third‑party data or otherwise send Customer Data and Personal Data to third‑party services, as well as retrieve third‑party data and import it into your Microsoft 365 tenant according to your configurations.

[Compliance considerations]

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

Updated April 23, 2026: We have updated the timeline and content. Thank you for your patience.

[Introduction]

We are expanding Microsoft Planner integration in Microsoft Teams by enabling Planner tabs in Shared and Private channels. This change allows teams to plan and track work directly within the channel where collaboration occurs, including scenarios that require restricted membership or cross-organization collaboration.

Only basic plans are being made available in Shared and Private Channels. Premium capabilities will come at a later date.

This message is associated with Roadmap ID 558928.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• Microsoft Teams users working in Shared or Private channels
• Microsoft 365 administrators managing Teams and Planner

What will happen:

• Users can add Planner as a tab in Shared and Private channels using the + (Add a tab) experience.
• Users can create a new plan for the channel or add an existing plan associated with that channel.



• Planner inherits channel permissions and Microsoft 365 compliance controls.
• Planner plans in shared and private channels will use the channel SharePoint for storage and access. Hence membership will be limited to channel members.
• The feature is enabled by default and requires no admin configuration.
• There is no change to Planner behavior in standard channels.

[What you can do to prepare:]

No admin action is required.

• Update internal Teams and Planner documentation.
• Inform users that Planner is available in Shared and Private channels.
• Review governance policies related to Teams and Planner usage.

[Compliance considerations:]

Introduction

To improve compliance and legal review workflows, Microsoft is enhancing how Microsoft Whiteboard content appears in Microsoft Purview eDiscovery. Based on customer feedback, Whiteboard artifacts returned in eDiscovery search sets can now be opened and reviewed directly in a readable HTML format, eliminating the need to download and open files separately in the Whiteboard app.

When this will happen:

This capability is rolling out now and will complete by late April 2026.

How this affects your organization:

Who is affected:

• Compliance, legal, and eDiscovery reviewers using Microsoft Purview eDiscovery
• Administrators managing Purview eDiscovery investigations that include Microsoft Whiteboard content

What will happen:

• Whiteboard files returned as artifacts in eDiscovery search sets can be opened directly within the eDiscovery experience
• Whiteboard content is rendered as readable HTML for faster review and understanding
• Reviewers no longer need to download Whiteboard files to view their contents
• The feature is enabled by default and respects existing Purview permissions and controls

What you can do to prepare:

No action is required.

• This capability is enabled automatically.
• Existing Microsoft Purview eDiscovery workflows, permissions, and policies continue to apply.
• You may want to inform compliance and legal teams that Whiteboard artifacts are now viewable directly in eDiscovery.
• To learn more about Whiteboard data controls and organization-level settings, review Manage data for Microsoft Whiteboard.

Compliance considerations:

This change enhances how existing Whiteboard data is viewed within Microsoft Purview eDiscovery. No new data is stored, and existing compliance, retention, and security controls continue to apply.

Updated April 23, 2026: We have updated the content. Thank you for your patience. 

[Introduction]

Earlier communication indicated a change in direction; however, Microsoft will continue to add support for passkeys (FIDO2) in the Enabled state within Registration Campaigns. This is the final direction and aligns with our long‑term passkey adoption strategy.

We are making an update to Passkeys (FIDO2) support within Microsoft Entra Authentication Methods Registration Campaigns.

Passkeys (FIDO2) will continue moving forward to General Availability as the targeted authentication method for Registration Campaigns in the Enabled state as previously communicated in MC1253746. 

Passkey (FIDO2) will also move forward as the targeted authentication method for Registration Campaigns in the Microsoft Managed state for tenants that meet our in-scope criteria. 

[When this will happen]

• General Availability (Worldwide): Rollout will begin in mid‑May 2026 to Microsoft Managed state and is expected to complete by late June 2026.

[How this affects your organization]

Who is affected

• Microsoft Entra tenants using Authentication Methods Registration Campaigns
• Tenants with Passkeys (FIDO2) enabled
• Only tenants that meet the Microsoft‑managed eligibility criteria described below

What will happen

Enabled state

• Passkeys (FIDO2) will be supported as the targeted authentication method for Registration Campaigns in the Enabled state.
• Over time, we will incrementally refine the logic for Passkeys nudges in Microsoft Registration Campaigns to guide users toward the appropriate passkey registration experience based on their passkey profile scope. Initially, the logic may not account for edge‑case scenario if users have any passkey profile restrictions, but we are actively expanding and improving it on an ongoing basis. When users have passkey profile restrictions (for example, device bound only passkeys allowed), the registration experience triggered by the nudge may not be optimal.

Microsoft‑managed state

• Passkeys (FIDO2) will be introduced as the targeted authentication method in the Microsoft‑managed state for eligible tenants.

Tenants are impacted when all of the following conditions are met:

• The Passkeys (FIDO2) authentication method policy is Enabled.
• Allow self‑service setup is Enabled.
• Target specific AAGUIDs is not selected (no AAGUID restrictions configured).
• The Authentication Methods Registration Campaign state is set to Microsoft‑managed.
• The tenant has at least one user enabled for both synced passkeys and device‑bound passkeys.

Only users who are enabled for both synced and device‑bound passkeys, with no passkey profile restrictions configured (for example, attestation enforcement or AAGUID restrictions), will receive a passkey registration nudge during sign‑in.

For impacted tenants, the following Registration Campaign settings will be automatically updated:

• Targeted authentication method changes from Microsoft Authenticator to Passkeys (FIDO2).
• Days allowed to snooze changes from 3 days to 1 day (no longer configurable).
• Limited number of snoozes changes from Enabled to Disabled (no longer configurable).
• Default user targeting changes from voice call or text message users to all MFA‑capable users.

After these changes take effect, targeted users will begin receiving passkey registration nudges during sign‑in after completing multifactor authentication.

Rollout will occur incrementally across eligible Microsoft Entra tenants.

[What you can do to prepare]

No action is required at this time.

If you plan to enable passkey registration nudges in the future:

• Ensure users are enabled for both synced and device‑bound passkeys.
• Remove any passkey profile restrictions (such as AAGUID or attestation requirements).
• Set your Authentication Methods Registration Campaign to Microsoft‑managed or Enabled.

[Compliance considerations]

Updated April 23, 2026: We have updated the content. Thank you for your patience. 

[Introduction]

We’re making a change to the characters allowed in naming and description fields across Microsoft Purview eDiscovery. As part of ongoing security hardening efforts, this update strengthens input validation for eDiscovery cases, holds, searches, and review sets to improve service resilience and reliability.

[When this will happen:]

General Availability (Production, GCC, GCC High, DoD): This change will begin rolling out in mid-May 2026 and is expected to be completed by late May 2026.

[How this affects your organization:]

Who is affected:

Organizations with users or administrators who create or manage Microsoft Purview eDiscovery:

• Cases
• Holds
• Searches
• Review sets

What will happen:

• Beginning May 15th, 2026, the following special characters will no longer be permitted in naming or description fields when creating or editing:
  • + (plus sign) 
  • = (equals sign) 
  • @ (at sign) 
  • / (forward slash) 
  • * (asterisk) 
• This restriction applies to:
  • Case name and description
  • Hold policy name and description
  • Search name and description
  • Review set name and description
• Existing entities are not affected.
  • Cases, holds, searches, and review sets that already contain these characters will continue to function normally.
• Editing triggers enforcement:
  • If a user edits an existing entity’s name or description (e.g., updating an eDiscovery case name) that contains a restricted character, they will see a validation message prompting them to remove the special character before saving. Note that this does not apply when an existing hold policy is being reapplied or when data sources are added to or removed from hold policies.
  • The original name and description are preserved until the user chooses to make changes.
• New entities are enforced immediately:
  • Any newly created case, hold, search, or review set must not contain restricted characters in name or description fields.

[What you can do to prepare:]

No admin action is required to enable this change. However, we recommend the following:

• Inform your eDiscovery users that the characters + = @ / and * will no longer be accepted in entity names and descriptions.
• Review and update existing naming conventions or templates that include these characters.
• Update internal documentation or guidance for eDiscovery naming standards.
• Communicate this change to helpdesk and compliance teams to prepare for validation messages when editing existing entities.

Learn about eDiscovery (Premium) | Microsoft Learn

No data loss will occur. Existing entities retain their current names and continue to function. Enforcement applies only at the time of creation or editing.

[Compliance considerations:]

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

[Introduction]

We are introducing the File Quarantine action in Microsoft Purview Data Loss Prevention (DLP) for SharePoint and OneDrive to help organizations better protect sensitive data. When a file violates a Purview DLP policy, it can be automatically isolated to prevent further access or sharing, allowing administrators to review and take appropriate action. This capability adds an additional layer of protection against accidental data exposure while supporting everyday collaboration.

This message is associated with Microsoft 365 Roadmap ID 557190.

[When this will happen:]

• Public Preview: Rolling out in mid‑April 2026 and expected to complete by early May 2026
• General Availability (Worldwide): Rolling out in early June 2026 and expected to complete by mid‑June 2026

[How this affects your organization:]

Who is affected:

• Admins managing Microsoft Purview DLP policies for:
• SharePoint Online
• OneDrive for Business
• Compliance and security administrators responsible for data protection and investigation workflows

What will happen:

• A new Quarantine action will be available when creating or editing DLP policies for SharePoint and OneDrive.
• When a file violates a DLP policy configured with the Quarantine action:
• The file is automatically isolated in an admin‑controlled quarantine location.
• Access to the original file is prevented to stop further sharing or exposure.
• A tombstone file replaces the original file at its source location:
• Contains admin‑defined messaging
• Informs users the file has been quarantined
• Preserves collaboration context
• Administrators retain visibility through:
• Audit logs
• DLP alerts
• Activity Explorer
• Files must be restored manually by an administrator.
• Original sharing permissions are not automatically reinstated upon restore.
• This feature is not enabled by default and requires configuration within a DLP policy.

[What you can do to prepare:]

• Create an admin‑owned SharePoint site to serve as the quarantine location.
• Configure quarantine settings in Purview DLP settings:
• Destination folder
• Tombstone message
• Review and restrict access permissions for the quarantine site.
• Validate behavior using DLP policies in simulation mode before broad enforcement.
• Update internal operational processes for quarantine reviews and restore requests.
• Communicate this change to your helpdesk and compliance teams.

Learn more:

• Get started with DLP file quarantine for SharePoint and OneDrive | Microsoft Learn
• Create a DLP policy to quarantine files in SharePoint and OneDrive | Microsoft Learn 

[Compliance considerations:]

[Introduction]

We’re introducing annotation support for single application window sharing on macOS in Microsoft Teams. Presenters can now share a single application window and enable meeting participants to annotate directly on top of that content—without sharing their entire desktop. This update helps protect privacy while enabling more focused and interactive collaboration during training sessions, workshops, and client meetings.

This message is associated with Microsoft 365 Roadmap ID 559611.

Screenshot: Annotation tools on shared single application window in Teams on macOS:

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• Teams users on macOS who present or participate in meetings using screen sharing
• Microsoft 365 admins managing Teams meeting experiences

What will happen:

• Users on macOS will be able to annotate directly on a shared application window (for example, a document, browser tab, or design tool).
• Participants can use drawing and highlighting tools to call attention to specific areas during presentations or discussions.
• Presenters can collaborate without sharing their entire screen.
• The feature will be available by default once released to your tenant.
• Existing Teams meeting and sharing policies will continue to apply.
• No changes to admin configuration are required.

[What you can do to prepare:]

No action is required.

• Inform your helpdesk and training teams about this new collaboration capability.
• Update internal documentation related to Teams meeting or screen sharing workflows.
• Communicate this change to macOS users who frequently present content in Teams meetings.

Learn more: Use annotation while sharing your screen in Microsoft Teams | Microsoft Support

[Compliance considerations:]

• Meeting participants can enable or disable annotation during a shared window session in Teams meetings.

[Introduction] 

Microsoft Teams will introduce the ability for users to test their microphone and speaker before joining a meeting. This improvement helps users confirm that they have selected the correct audio devices, reducing audio issues and helping meetings start on time with fewer disruptions.

This message is associated with Microsoft 365 Roadmap ID 560074.

[When this will happen]

• Targeted Release: Rollout will begin in early May 2026 and is expected to complete by mid-May 2026.
• General Availability (Worldwide): Rollout will begin in mid-May 2026 and is expected to complete by late May 2026.
• General Availability (GCC, GCC High, and DoD): Rollout will begin in mid-May 2026 and is expected to complete by mid-May 2026.

[How this affects your organization]

Who is affected

All Microsoft Teams users across Microsoft 365 tenants, including Commercial, GCC, GCC High, and DoD environments.

What will happen

• Before joining a meeting, users will see a Test mic and speaker option on the pre‑join screen:

   

• Users will be able to record and play back a short audio clip to confirm that their microphone and speaker work correctly: 

  

• The feature will be enabled by default and won’t require admin configuration.
• This change does not modify meeting audio settings or policies. 

[What you can do to prepare]

• Admins don’t need to take any action.
• Consider updating internal documentation or notifying helpdesk staff about the new pre‑join audio experience.

[Compliance considerations]

Microsoft identified no compliance considerations. Review this change as appropriate for your organization.

Updated April 23, 2026: We have updated the content. Thank you for your patience. 

[Introduction]

To support deeper analysis of Copilot agent adoption and usage across your organization, Microsoft will introduce a new export capability in the Agent Dashboard. This feature will allow eligible users to download de‑identified Copilot agent usage data for analysis, helping organizations track adoption trends, optimize licensing, and support AI transformation strategies, while maintaining existing privacy and access controls. User identifiers are removed from the output.

This feature will require at least 50 Microsoft 365 Copilot licenses and will apply to the Viva Insights web app.

This message is related to Roadmap ID 560538. 

[When this will happen]

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

[How this affects your organization]

Who is affected

• Agent Dashboard users with full company‑level data access, including:
  • Senior leaders (as identified in Microsoft Entra ID)
  • Admin‑assigned company‑level users
  • Delegates with company‑level access
  • 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

• Eligible users will be able to export de‑identified, user‑level Copilot agent metrics and agent attributes aggregated by user and week, for up to the past six months. User identifiers are removed from the output.
• The export will include multiple data tables, such as:
  • Copilot agent metadataincluding agent name, creator type, and publishing source
  • Copilot agent usage metrics, including the number of responses generated
  • Copilot agent credit usage and user retention metrics
  • People metadata, including organization and function type
• By default, this feature will be ON for all eligible users.
• Admins will be able to manage or disable the feature at the tenant or group level at any time using Viva Feature Access Management (VFAM):
  • Module: Viva Insights
  • Feature: Agent Metrics Export
• There will be no impact to user workflows unless the feature is accessed by eligible users.

Screenshot – View of the Agent Dashboard:

[What you can do to prepare]

• No action is required to enable this feature.
• If you do not want this feature enabled by default, you can disable it at the tenant or group level using Viva Feature Access Management (VFAM).
• Review which users have full company‑level access to the Agent Dashboard.
• Communicate the upcoming change to eligible users so they understand the new export capability and its intended use.

Learn more:

• Connect to the Agent Dashboard | Viva Insights | Microsoft Viva | Microsoft Learn
• Delegate access to the Copilot Dashboard, Agent Dashboard, and Copilot insights | Viva Insights | Microsoft Viva | Microsoft Learn
• Manage settings for the Microsoft Copilot Dashboard, Agent Dashboard, and Viva Insights web app | Viva Insights | Microsoft Viva | Microsoft Learn
• Using Entra ID data – Connect to the Microsoft Copilot Dashboard for Microsoft 365 customers | Viva Insights | Microsoft Viva | Microsoft Learn
• Viva features management – Control access to features in Microsoft 365 | Microsoft Viva | Microsoft Learn

[Compliance considerations]

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

[Introduction]

We’re enhancing Customer Connect in Microsoft Teams by adding appointment booking, enabling customers to book follow-up meetings directly from your business website. This helps small businesses turn website conversations into scheduled consultations and ensures appointments are automatically managed in Teams and staff calendars.

This message is associated with Microsoft 365 Roadmap ID 557172.

[When this will happen:]

• General Availability (Worldwide): We will begin rolling out in early May 2026 and expect to complete by early May 2026
• General Availability (GCC): We will begin rolling out in early May 2026 and expect to complete by late May 2026

[How this affects your organization:]

Who is affected:

• Microsoft 365 tenants using Customer Connect in Microsoft Teams
• Customers licensed for Microsoft 365 Business Basic, Business Standard, or Business Premium
• Teams administrators who manage Customer Connect settings

What will happen:

• Website visitors can schedule appointments directly through the embedded Customer Connect widget.
• Scheduled appointments are automatically:
  • Added to the assigned staff member’s Outlook calendar
  • Posted to the Customer Connect requests channel with appointment details
• No changes occur to the existing Customer Connect experience until an admin enables and configures appointment scheduling.
• Each tenant can assign up to 25 users as Customer Connect support agents.
• Note: Customer Connect was previously released under the name Live Chat in Teams. Documentation may refer to both names while the naming transition is in progress. Refer to MC1287369 for more information.

[What you can do to prepare:]

• Set up Customer Connect in Microsoft Teams if not already configured. Learn more: Set up and manage live chat | Microsoft Learn.
• Enable appointment scheduling from the Teams Admin app.

Screenshot:  Admin enables Customer Connect appointment scheduling and assigns staff availability:



• Configure appointment settings, including:
  • Adding or removing staff eligible for appointments
  • Defining staff availability hours
  • Creating, editing, or removing appointment types offered to customers
• Review internal support processes and update documentation or helpdesk guidance as needed.

[Compliance considerations:]

• Microsoft 365 Copilot is also installed.
• Copilot wasn’t installed by the user.
• Copilot wasn’t launched in the last 28 days. 

• Learn more at WindowsAI Policy CSP.
• Get the April 14, 2026—KB5083769 (OS Builds 26200.8246 and 26100.8246) security update.