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

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

 Coming soon for Microsoft Teams: Meeting participants will be able to request an annotation session while someone else is sharing their screen.

This message applies to Teams for Windows desktop and Teams for Mac desktop. (Users can view and annotate in Teams on the web but cannot initiate annotations.)

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:

If the request is accepted, the annotation session will start for everyone in the meeting:

Anonymous users in the meeting will not be able to send a request.

This change will be available by default.

[What you need to do to prepare:]

This rollout will happen automatically by the specified dates with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation as appropriate.

Learn more: Use annotation while sharing your screen in Microsoft Teams – Microsoft Support (we will update this before rollout)

Watch: How to use Collaborative Annotations in a Microsoft Teams meeting (2022)

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

We’re enhancing the contact experience in Microsoft Outlook Mobile (iOS and Android) by introducing profile-enriched contacts and automatic duplicate contact management. These improvements aim to streamline contact views and provide richer organizational context.

This message is associated with Microsoft 365 Roadmap ID 493753.

This feature has previously been released to the People Hub in new Outlook for Windows. More details in MC927963 (Updated) New Microsoft Outlook for Windows: People Hub improvements (published November 2024, updated April 2025).

[When this will happen:]

General Availability (Worldwide): We will begin rolling out mid-July 2025 (previously late June) and expect to complete by end of May 2026 (previously end of February).

[How this will affect your organization:]

Before this rollout, Outlook Mobile may have displayed multiple entries for the same contact and lacked organizational profile context.

After this rollout:

• Contacts will be unified into a single enriched view, displaying additional profile information from your organization’s directory (where available).
• Identical duplicate contacts will be automatically hidden.
• These enhancements will be on by default and apply to both iOS and Android versions of Outlook Mobile. No admin controls exist.
• Users can access their contact list by selecting Contacts from the Apps section in the Outlook Mobile app.

[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 update internal documentation.

After the feature is rolled out, please ensure that users have updated to the latest version of Outlook for iOS or Outlook for Android.

Learn more: Manage Outlook contacts in your organization – Microsoft Support

Updated March 16, 2026: We have temporarily disabled the automatic installation of the Microsoft 365 Copilot app to eligible devices with the Microsoft 365 desktop apps. We will provide another update once we re-enable these installations.

Introduction

Starting in December 2025, Microsoft will begin automatically installing the Microsoft 365 Copilot app on Windows devices that have Microsoft 365 desktop client apps. This app provides a centralized entry point for accessing Copilot experiences and AI-powered capabilities across Microsoft 365. This change simplifies access to Copilot and ensures users can easily discover and engage with productivity-enhancing features.

When this will happen

Rollout begins in early December 2025 (previously early October) and completes mid-December 2025 (previously mid-November)

How this affects your organization

Who is affected:

• The Microsoft 365 Copilot app will not automatically deploy to eligible Microsoft 365 desktop apps devices during this time.
• Existing installations are unaffected.

What will happen:

• The Microsoft 365 Copilot app will be automatically installed on Windows devices that have Microsoft 365 desktop apps, unless administrators opt out.
• The app will appear in the Start menu as a new entry point for accessing Copilot experiences across Microsoft 365.
• On devices where the app is already installed, no visible change will occur.
• The app installation is enabled by default and does not require user interaction.
• This change does not apply to customers in the European Economic Area (EEA).

What you can do to prepare

Admin Actions

• Use other app deployment methods to install the Microsoft 365 Copilot app until this capability is restored. You can use Intune and other software management tools to deploy the app.
• Monitor this post for the next update on re-enablement.

User Impact

• Users may see a new app icon for Microsoft 365 Copilot in the Start menu.
• On many devices, the app may already be installed, resulting in no visible change

Compliance considerations

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

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

Outlook mobile users can now prepare for their meetings using Copilot chat with a single tap. This feature is available on Android and iOS platforms and requires a Microsoft 365 Copilot license. It helps users quickly access relevant meeting information, making preparation more efficient and personalized.

This message is associated with Microsoft 365 Roadmap ID 516568.

[When this will happen:]

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

[How this affects your organization:]

• Who is affected: Users of Outlook mobile on Android and iOS who have a Microsoft 365 Copilot license.
• What will happen:
  • Eligible users will see a new Copilot chat option to prepare for meetings directly within Outlook mobile.
  • The feature will be ON by default for licensed users. To turn off Copilot in Outlook review Turn off Copilot in Microsoft 365 apps | Microsoft Support.
  • No admin configuration is required.
  • Existing policies and permissions are respected.

Screenshots 1-3 provide a view of the previous experience:

Screenshots 4-5 provide a view of the new experience – Selecting Prepare will take users to Copilot Chat, enabling users to ask follow-up questions:

[What you can do to prepare:]

• No admin action is required at this time.
• If desired, communicate this feature to helpdesk staff.
• Update internal documentation if you detail this feature.
• Ensure users have the appropriate Microsoft 365 Copilot license to access this feature.

[Compliance considerations:]

Updated November 12, 2025: We are postponing the GA release for this feature at this time. We apologize for any inconvenience.

[Introduction]

We’re introducing AI-powered enhancements to the SharePoint FAQ web part to help content owners keep FAQs accurate and fresh with less effort. These updates are based on customer feedback and aim to improve content reliability and reduce manual upkeep. Key improvements include AI-suggested updates, seamless import of existing FAQs, and the ability to ground answers in SharePoint Pages.

This message is associated with Roadmap ID 482198.

• Public Preview (Worldwide, GCC): Rollout begins in late November 2025 and completes by early January 2026 (previously early December 2025).
• General Availability (Worldwide, GCC): We will update via Message center when we are ready to proceed.

Who is affected: Content authors using the SharePoint FAQ web part with a Microsoft 365 Copilot license.

What will happen:

The following enhancements will be available to improve FAQ management and content accuracy:

• On-demand AI-suggested FAQ updates: Authors can manually trigger a freshness check. AI will analyze grounding files and viewer-submitted questions to identify outdated or inaccurate FAQ entries and suggest revisions.
Screenshot 1: FAQ authors can trigger an on-demand update check whenever new AI-generated update suggestions are available.

Screenshot 2: FAQ authors can review and approve AI suggestions to keep the content accurate and up to date.



• Seamless import of existing FAQs: Authors can copy and paste curated FAQ content directly into the SharePoint FAQ web part, enabling quick integration of existing knowledge assets.

Screenshot 3: FAQ authors can easily import Q&A pairs by simply pasting content.



• SharePoint Page as grounding source: FAQ answers can be grounded in SharePoint content, including the current page or other selected pages, improving response reliability and contextual relevance.

Screenshot 4: FAQ authors can use the current page or existing pages as reference sources.

[What you can do to prepare:]

• No admin action required: The feature will be enabled by default for eligible users.
• Notify content authors and site owners about the new capabilities.
• Update internal documentation or training materials as needed.
• Review the updated FAQ web part documentation when available (expected late November).

Use a FAQ web part in SharePoint (documentation will be updated in late November)

[Compliance considerations:]

Updated March 16, 2026: We have updated the timeline. This feature will be enabled for en-US only initially. Thank you for your patience. 

[Introduction:]

Audio summaries help users absorb content quickly, but they’ve traditionally been passive, one-way experiences. Listeners can’t clarify, explore, or dive deeper without breaking flow — forcing them to pause, switch modes, and manually search for answers. Based on feedback for more dynamic and immersive audio experiences, Microsoft is introducing real-time voice interactions in Podcast. The new interactive podcast feature transforms this into a dynamic, conversational experience, where users can join the hosts’ discussion of their document, ask questions in real time, and uncover insights naturally — staying immersed while gaining understanding faster.

This message is associated with Microsoft 365 Roadmap ID 523206.

[When this will happen:]

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

[How this affects your organization:]

• Who is affected: Customers with Copilot licenses who generate audio overviews.
• What will happen:
  • Users will be able to join podcast conversations and ask questions in real time.
  • The feature enhances document-based podcasts with interactive voice capabilities.
  • The feature will be ON by default for eligible users.
  • No changes to existing admin policies are required.

[What you can do to prepare:]

• No admin action is required.
• Communicate this change to helpdesk staff.
• Update internal documentation if you reference podcast or audio overview features.
• For more information, refer to upcoming documentation in the Microsoft Learn portal.

[Compliance considerations:]

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

Updated March 16, 2026: We have updated the timeline. This feature will be enabled for en-US only initially. Thank you for your patience. 

[Introduction:]

Read Aloud is evolving from a passive listening tool into an interactive experience. By integrating Copilot Q&A, users can now ask questions and refine their understanding of document content in real time—without interrupting their workflow. This enhancement supports accessibility, improves comprehension, and helps users stay focused while gaining insights faster.

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

This message is associated with Microsoft 365 Roadmap ID 523205.

[When this will happen:]

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

[How this affects your organization:]

• Who is affected: All users of Read Aloud in Microsoft 365. Users with a Microsoft 365 Copilot subscription will receive the enhanced experience.
• What will happen:
  • Users with Copilot will see a new interactive voice-driven Read Aloud experience.
  • The entry point remains the same as classic Read Aloud.
  • Users without Copilot will continue to use the classic Read Aloud functionality.
  • No changes to admin policies or configurations are required.
  • The feature is enabled by default for eligible users.

[What you can do to prepare:]

• No admin action is required.
• Notify your users about the upcoming change.
• Update internal documentation if you reference Read Aloud functionality.
• If you manage helpdesk communications, consider sharing a short blurb about the new experience.

[Compliance considerations:]

Updated February 20, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

To improve collaboration and streamline meeting workflows, Microsoft Teams is introducing the ability to consult and merge Public Switched Telephone Network (PSTN) callers into active meetings—even when those callers are behind auto-attendants or Interactive Voice Response (IVR) systems that require Dual-Tone Multi-Frequency (DTMF) navigation. This enhancement allows users to reach subject matter experts via dial-in and seamlessly bring them into the broader conversation.

This message is associated with Microsoft 365 Roadmap ID 518218.

• Targeted Release: Rolling out early April 2026 (previously early March), expected to complete by mid-April 2026 (previously mid-March).
• General Availability:  Rolling out mid-April 2026 (previously late March), expected to complete by late April 2026 (previously early April).

[How this affects your organization:]

• Who is affected: All Microsoft Teams users who initiate or manage meetings with PSTN participants. Administrators overseeing Teams meeting policies and call configurations.
• What will happen:
  • Users can consult with PSTN or Voice over Internet Protocol (VoIP) participants via the Participants panel.
  • A new interface will allow users to access a dialpad to navigate IVR systems and auto-attendants using DTMF tones.
  • Once the external party is reached, users can merge them into the ongoing meeting.
  • No changes to existing administrator policies; feature is enabled by default.

[What you can do to prepare:]

• No administrator action is required for this rollout.
• If your organization uses custom training or helpdesk documentation, consider updating it to reflect this new capability.
• Before rollout, we will update this post with new documentation.

[Compliance considerations:]

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

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

“Hey Copilot” to start voice in Copilot on Windows devices

[Introduction]

Starting late November 2025, we’re introducing a new hands-free way to activate voice in Microsoft 365 Copilot on Windows devices. Users will be able to start a voice chat with Copilot by saying “Hey Copilot”. To end the conversation, users need to press the “Dismiss/X” button in the voice chat controls. In the future, users will be able to end the chat with a voice command. This allows users to stay in the flow of work, without switching apps or windows, while getting assistance from Copilot using voice.

Important: The “Hey Copilot” feature is off by default.

Users can manually enable the feature by going to Settings > Quick view in the Microsoft 365 Copilot app and turning on the Listen for “Hey Copilot” toggle. When on, this capability operates locally on the device and only activates by “hearing” the trigger word “Hey Copilot” without recording or storing any conversation. Text transcripts from voice conversations with Copilot are stored and managed in the same way as text conversations in the Microsoft 365 Copilot app. No user or Copilot audio is stored. For more information about data retention for Copilot, see Data, Privacy, and Security for Microsoft 365 Copilot.

This message is associated with Microsoft 365 Roadmap ID 497848.

[When this will happen]

Preview (Frontier): Begins rolling out at the end of November 2025.

General Availability (Worldwide): Begins rolling out end of February 2026 (previously late December 2025) and is expected to complete by mid-April 2026.

[How this will affect your organization]

• Users will be able to start a voice conversation with Copilot hands free, saying “Hey Copilot” once turned on.
• The “Hey Copilot” feature is off by default and must be turned on by users in Copilot settings.
• When on, this capability operates locally on the device and only activates by “hearing” the trigger word “Hey Copilot” without recording or storing any conversation.
• There is no admin control to disable this feature by an admin at a tenant or group level.
• Voice in Microsoft 365 Copilot is currently available only for Copilot licensed users and this feature will be available only to those same users.
• Activation respects organizational compliance boundaries and only responds when explicitly called.
• To mute or end the conversation, the user must click to “Mute” or “Dismiss” as needed. At that point, Copilot stops listening. Copilot will end the session after 60 seconds of inactivity, giving users a notice after the first 30 seconds. 
• The feature will not activate if audio from another app is on or when the user’s device is locked.
• This feature is supported in English only, but once activated, users can have conversation in any language Copilot that supports.

[What you need to do to prepare]

This feature will roll out default off but users will be prompted in product to try this feature by turning it on in the Copilot settings.

To enable, users need to go to Microsoft 365 Copilot app on Windows devices and enable it in settings and ensure that microphone permissions and device settings are compatible with voice activation

• Review how privacy and security of organizational data is protected when using this feature: Data, Privacy, and Security for Microsoft 365 Copilot
• Communicate the availability and benefits of this feature to your users.
• Remind users to ensure that microphone permissions and device settings are compatible with voice activation.

[Learn more]

How “Hey Copilot” voice chat wake word works in Microsoft 365 Copilot – Microsoft Support

Frequently asked questions about voice features in Microsoft 365 Copilot

Get started with voice features in Microsoft 365 Copilot

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

With this release, users can discover and add SharePoint agents directly within Microsoft Teams chats on Desktop and Mac. Agents can be added via the Add Agents and Bots option in the chat roster dropdown, which opens the in-context store for discovery and selection. This enables users to quickly bring SharePoint agents into conversations to support collaboration.

Additionally, SharePoint agents are available in the Teams Store under the Agents category, making them easier to find and deploy across Teams experiences.

This message is associated with Microsoft 365 Roadmap ID 515465.

[When this will happen]

• Targeted Release: Rolling out in early May 2026 (previously early April) and expected to complete in mid-May 2026 (previously mid-April 2026).
• General Availability: Rolling out in mid-May 2026 (previously mid-April) and expected to complete by end of May 2026 (previously end of April).

[How this affects your organization]

• Who is affected: All users of Microsoft Teams on Desktop and Mac.
• What will happen:
  • Users will be able to discover and add SharePoint agents from the in-context store in Teams chats.
  • SharePoint agents will be available in the Teams Store under the Agents category.
  • Agents can be added via the Add Agents and Bots option in the chat roster dropdown.
  • No admin action is required; the feature is enabled by default.
  • Existing policies are respected; no changes to admin controls are needed.

[What you can do to prepare]

• Ensure that intended users have E3 or E5 (with Teams) licensing, and one of the following options: 
  • Microsoft 365 Copilot license OR
  • Pay-as-you-go (PAYG) separately setup for SharePoint agents on MAC.

• Inform helpdesk staff in case users have questions about accessing or using SharePoint agents.
• Share this update with users to highlight new collaboration opportunities.
• Update internal documentation if you maintain guidance on Teams agents or bots.

Learn more: Share an agent from SharePoint in Teams | Microsoft Support

[Compliance considerations]

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

Updated March 16, 2026: We republished the Microsoft 365 Root Certificate Chain Bundles for Worldwide (WWMT) and GCC High / DoD (ITAR) after identifying that the previously published bundles were missing required information. If you already completed the steps in this message, you must download the updated bundle and complete the certificate trust steps again as soon as possible. Failure to trust the updated DigiCert Global Root G2 chain and its intermediates may result in mail flow disruption once providers begin distrusting the DigiCert G1 root.

We’ve been notified that some email providers may distrust the DigiCert G1 root on April 15, which could result in broad ecosystem‑wide email impact. To ensure Exchange Online can rotate certificates ahead of this event, customers must trust the DigiCert Global Root G2 certificate authority by March 22 (previously March 15). Thank you for your patience. 

[Introduction]

Action might be required to avoid service disruption. To maintain secure and uninterrupted mail flow with Exchange Online, organizations must ensure their servers and clients trust the DigiCert Global Root G2 Certificate Authority (CA) and its subordinate CAs. 

Organizations that rely on custom certificate trust stores, disabled Windows CTL updates, or older runtime environments might be impacted and may need to update their trusted certificate chains.

[When this will happen:]

Organizations must complete required certificate trust updates before March 23, 2026 (previously March 16).

[How this affects your organization:]

Who is affected:

This change applies to all organizations (Worldwide, GCC, GCC‑High, DoD) that:

• Send or receive email with Exchange Online and
• Either:
• Your organization has disabled the Windows CTL Updater feature that by default downloads the Certificate Trust List (CTL).
  • The CTL contains trusted and untrusted root certificates. Learn more: Certificates and trust in Windows.
  • This scenario may apply if your organization maintains its own set of trusted Root and Intermediate Certificates via Group Policy or via a redirected Microsoft Automatic Update URL. Learn more: Configure trusted roots and disallowed certificates in Windows.
  • You can determine whether the Windows CTL Updater feature is disabled by reviewing the Who needs to take action section of this Microsoft guidance: Trust DigiCert Global Root G2 Certificate Authority to Avoid Exchange Online Email Disruption.
• You use older or custom application environments such as:
• Legacy Java/JDK/JRE runtimes
• Embedded systems and appliances
• Custom or outdated Linux images
• Air‑gapped systems
• Third‑party email gateways or security appliances that perform certificate chain validation

This change applies to any system performing full certificate chain validation against Exchange Online, including Exchange Server, security appliances, and third-party email gateways. If you use third-party email appliances, please contact the vendor directly for support.

Windows systems with the CTL Updater enabled (default) do not require action.

What will happen:

If the DigiCert Global Root G2 certificate or required intermediates are missing or cannot be retrieved during TLS negotiation:

• Outbound email clients may:
• Refuse to send email when strict certificate validation is enforced
• Fall back to unencrypted SMTP if allowed
• Inbound SMTP connections from Exchange Online may fail or be delayed
• Email flow reliability may be reduced
• Systems not using up‑to‑date certificate chains may be unable to validate TLS certificates presented by Exchange Online

If your organization already maintains the current Office 365 certificate chains, no impact is expected.

[What you can do to prepare:]

Required actions:

If your environment has disabled Windows CTL updates or relies on older/custom runtimes, complete the actions outlined in the What you must do section of: Trust DigiCert Global Root G2 Certificate Authority to Avoid Exchange Online Email Disruption

Specific actions include:

• Review whether Windows CTL Updater is disabled in your organization.
• Confirm whether SMTP servers, security appliances, and gateways fully trust the DigiCert Global Root G2 CA and subordinate CAs.
• Ensure outdated or custom runtimes (Java, Linux, embedded systems, etc.) include the required certificates.
• Contact your third‑party email appliance vendor if they manage certificate chains.
• Update internal documentation and inform helpdesk teams as required.

No action required if:

• You are using Windows systems with CTL Updater enabled (default behavior), and
• Your organization already trusts the latest Office 365 certificate chains.

[Compliance considerations:]

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

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

[Introduction]

To help organizations streamline approval workflows and improve governance, users who request a Microsoft 365 Copilot license will be able to submit a business justification with their request. Admins will see this justification during review, enabling faster and more informed decisions while reducing manual follow-ups.

This message is associated with Microsoft 365 Roadmap ID 547731.

[When this will happen]

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

[How this affects your organization]

Who is affected:

• Users who request Microsoft 365 Copilot licenses
• Admins who review, approve, or manage Copilot license requests

What will happen:

• Users requesting a Copilot license will see a new field to provide a business justification.
• Admins will see the justification as part of the review experience.
• The feature will be on by default with no tenant configuration required.
• Existing license request workflows will continue to function as they do today.
• There will be no impact to the user experience unless they request a Copilot license.
• No changes to admin policies, settings, or reporting.

Screenshot 1 – A license request will be created when the user clicks Request License:

Screenshot 2 – On the next screen, there is an option to provide a business justification for the request; this step is optional:

Screenshot 3 – View of the dropdown menu with business justification options:

[What you can do to prepare]

No action is required.

Optional steps:

• Notify helpdesk or approvers about the new justification field.
• Review or update internal documentation as needed.
• If you track license request metadata, ensure your internal workflows and tools account for the justification field.

[Compliance considerations]

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

[Introduction]

Copilot highlights in Viva Glint provides AI‑generated, structured summaries of employee survey results directly within supported Glint reports. The feature appears as a collapsible card at the top of the report and surfaces key insights—including strengths, opportunities, team‑level differences, and trends—to help managers and leaders move from data to action faster. Copilot highlights will be automatically available for users who have access to Copilot in Viva Glint, with no additional configuration required.

This message is associated with Microsoft 365 Roadmap ID 558111.

[When this will happen]

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

[How this affects your organization]

Who is affected

• Organizations using Viva Glint
• Admins who manage Copilot in Viva Glint access in the Microsoft 365 admin center
• Users with Glint roles that include dashboard and reports access when Copilot in Viva Glint is enabled
• Users must have a license for Viva Glint, Microsoft Viva Suite, or Microsoft Viva Workplace Analytics and Employee Feedback to access Copilot highlights.
• A Microsoft 365 Copilot license is not required to use Copilot in Viva Glint or Copilot highlights.

What will happen

• Copilot highlights will appear automatically as a collapsible card at the top of Team Summary and Executive Summary reports.
• There will be no separate toggle to configure; the feature will be enabled automatically when Copilot in Viva Glint is turned on.
• Summaries may include up to three structured sections:
  • Overview and key outcomes: Response rate, key outcome trend, top strengths
  • Team scores: Team breakdowns, increases/decreases, high/low scoring teams
  • Top opportunities: Score, benchmark comparison, risk classification
• Multilingual summaries will be generated in each user’s configured Viva Glint dashboard language.
• Interpretation rules will surface only notable findings based on respondent group size.
• No new data sources will be introduced; summaries will use existing report data.
• Existing access policies, data permissions, and confidentiality thresholds will remain unchanged.
• No changes will be made to dashboard access, user permissions, or privacy protections.

[What you can do to prepare]

• Verify Copilot access settings:
  • Go to admin.microsoft.com → Settings → Viva → Viva Glint → Manage settings for Microsoft Copilot in Viva Glint.
  • Confirm Copilot in Viva Glint is turned on at the tenant level.
  • If needed, adjust access policies to limit Copilot visibility to specific users or groups.
• Inform report viewers: Let managers and leaders know that AI‑generated summaries will appear at the top of supported reports. Users can collapse the card if they prefer to review data directly.
• No additional configuration is required: Copilot highlights will be automatically available when Copilot in Viva Glint is enabled.
• Learn more: Manage Viva Glint Copilot access in the Microsoft 365 admin center | Viva Glint | Microsoft Viva | Microsoft Learn

[Compliance considerations]

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

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

[Introduction]

We’re introducing a new Follow option for meetings in Outlook Mobile.  This feature helps users stay informed when they cannot attend by prompting organizers to record the meeting and by ensuring followers receive key updates and follow‑up items.

[When this will happen]

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

[How this affects your organization]

Who is affected

• All users who schedule or respond to meetings in Outlook Mobile. Attendees will only see the option to respond with Follow if a meeting has two or more participants and when the organizer has requested responses.

What will happen

• A new Follow option will appear as the third option in the mobile RSVP menu. To select “Maybe,” tap the three dots … : 

  

• The Maybe RSVP option will move into the overflow menu:  

  

• The No response option will move to the second position in the RSVP list.
• The feature will be on by default for all tenants.
• Organizers may receive prompts to record the meeting or address follow‑up items when attendees choose to Follow.
• No changes to existing Outlook or Exchange Online admin policies.

[What you can do to prepare]

No admin action is required.

Optional steps:

• Notify helpdesk and support teams about the updated RSVP options and UI behavior.
• Update internal end‑user documentation if your organization provides guidance for meeting responses.

Learn more: Follow a meeting in Outlook | Microsoft Support

[Compliance considerations]

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

1. In the Power Apps maker portal, navigate to Wrap from the left navigation pane.
2. Select the desired app and select Wrap on the command bar.
3. When you reach the manage output step, select Dataverse to store your wrapped app binaries in Dataverse.
4. Navigate to Wrap projects, select View builds, and download your files directly from Dataverse.

• Percentage-based sampling to evaluate a defined number of qualifying interactions.
• Absolute count sampling to cap the total number of interactions evaluated per schedule.

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.

[Introduction]

As previously announced in MC1221452, Microsoft Registration Campaigns will support Passkeys (FIDO2) as an additional authentication method starting in early April 2026. This update helps organizations accelerate adoption of phishing‑resistant credentials by allowing administrators to opt users into Passkeys and deliver Passkey registration nudges during sign‑in.

[When this will happen] 

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

[How this affects your organization]

Who is affected

• Microsoft 365 tenants using Microsoft Registration Campaigns
• Tenants configured in either Microsoft‑managed or Enabled states
• Users who are MFA‑capable and eligible for Passkeys (FIDO2)

What will happen

Microsoft‑managed state

Your tenant will be 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.

When these conditions are met, the following settings will update automatically:

• The targeted authentication method will change from Microsoft Authenticator to Passkeys (FIDO2).
• Days allowed to snooze will change from three days to one day. (This setting will no longer be configurable.)
• Limit number of snoozes will be disabled. (This setting will no longer be configurable.)
• Targeting will expand to all MFA‑capable users. (This setting will no longer be configurable.)
• Default user targeting will change from voice call or text message users to all multifactor authentication (MFA)–capable users.

Affected users will receive Passkey registration nudges at sign‑in after completing MFA.

We will roll out these changes incrementally over time to in‑scope tenants.

Enabled state

Passkey (FIDO2) can be selected as the Targeted Authentication Method when Microsoft Registration Campaigns are in the Enabled state. 

Note: Registration Campaigns support targeting only one authentication method at a time—either Microsoft Authenticator or Passkeys (FIDO2), but not both simultaneously.

[What you can do to prepare]

Opting into Passkey Registration Nudges:

• The user is MFA‑capable
  • They have at least one registered MFA method
  • They can successfully complete MFA at sign‑in
• Under Authentication methods > Policies, the user is in scope for Passkeys (FIDO2)
• Under Authentication methods > Policies > Passkeys (FIDO2) > Configure, make sure you have Allow self-service set up checked. 

Important Guidance:

We will roll out these changes incrementally to in-scope tenants starting in early April. This rollout will take time, and even if your tenant meets the eligibility criteria, you may not see the changes immediately. 

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 every edge‑case scenario, but we are actively expanding and improving it on an ongoing basis. When users have passkey profile restrictions (for example, AAGUID restrictions), the registration experience triggered by the nudge may not be optimal.   

Using Passkeys Despite Restrictions

You can still set Passkeys as the target authentication method in Microsoft Registration Campaigns. However, users may encounter a poor or confusing experience if they have passkey profile restrictions.

Example: 

If a user is scoped into specific AAGUID synced passkeys only, they may see a Passkey nudge at sign‑in. If they attempt to register a device‑bound passkey, the registration will fail because they are not in scope for that passkey type. 

Recommended next steps

• Review your Registration Campaign state by early April 2026.
• Communicate this change to helpdesk or support teams.
• Update internal documentation on authentication method enrollment.
• If you prefer to continue targeting Microsoft Authenticator, verify this configuration before rollout.

Learn more: How to enable passkey (FIDO2) profiles in Microsoft Entra ID (preview) | Authentication | Microsoft Entra ID | Microsoft Entra | Microsoft Learn

[Introduction]

We’re adding support for .eml and .msg file uploads in Microsoft 365 Copilot, including Copilot Chat and the Microsoft 365 Copilot app. This update makes it easier for users to include email files as context when prompting Copilot, helping them generate more relevant and grounded responses.

This message is associated with Microsoft 365 Roadmap ID 552591.

[When this will happen]

• General availability (Worldwide): Rollout begin in late February 2026 and is expected to complete by late March 2026.

[How this affects your organization]

Who is affected

• All users in Microsoft 365 tenants who have access to Microsoft 365 Copilot Chat or the Microsoft 365 Copilot app.

What will happen

• Users will be able to upload .eml and .msg files directly when interacting with Copilot.
• Uploaded files can be used as grounding context for prompts.
• This feature is available by default; no admin configuration is required.
• There is no change to existing policies governing file handling or data access.

[What you can do to prepare]

No action is required. This feature will roll out automatically.

Optionally, you may:

• Inform helpdesk or support staff in case users ask about new upload capabilities.
• Update internal Copilot usage or prompt‑writing guidance to reflect expanded supported file types.

[Compliance considerations]

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

[Introduction]

Teams Phone user multi-line provides greater flexibility for organizations whose users manage multiple business numbers. This capability allows administrators to assign up to 10 telephone numbers to a single Teams Phone user, all within one Teams account. Users can make and receive calls from multiple numbers across Teams desktop, Teams mobile, and Teams devices without switching accounts or hardware. This enhancement supports a familiar and localized calling experience for users who work across regions, roles, or business lines.

This capability supports scenarios such as:

• Establishing local presence across multiple regions
• Supporting users with multiple roles or responsibilities
• Allowing executives, assistants, or support teams to manage multiple business lines within one Teams account

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

[When this will happen:]

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

[How this will affect your organization:]

Who is affected:

• Organizations using Microsoft Teams Phone
• Teams administrators who manage phone number assignments
• Users assigned more than one business telephone number
• A Teams Phone license is required to use this feature

What will happen:

• Admins can assign up to 10 telephone numbers to a single Teams Phone user.
• Assigned numbers appear as separate lines in the Calls app in Microsoft Teams.
• Additional numbers automatically appear for users after assignment; no user configuration is required.
• This feature is Off by default. Admin must configure for it to be available to users. 

[What you can do to prepare:]

No action is required before this feature rolls out.

After the feature becomes available, administrators can:

• Review which users may benefit from having multiple phone numbers.
• Assign and manage additional telephone numbers in the Microsoft Teams admin center.
• Confirm that each telephone number has a valid emergency address configured.
• Ensure assigned numbers comply with regional telecommunications regulations and existing Teams Phone requirements.

Managing multi-line number assignments requires the Teams Administrator role (or equivalent permissions).

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

[Compliance considerations:]

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

Introduction

To improve reliability, compliance, and collaboration, we’re updating where Microsoft Whiteboard files created from a Teams Channel tab are stored. Previously, these whiteboards were saved in the OneDrive of the user who created them, which could lead to access issues due to sharing settings, Information Barriers, or Conditional Access policies.

With this update, whiteboards created from Teams Channels will be stored in the associated SharePoint site for the channel, aligning Whiteboard with the storage behavior of other Microsoft 365 apps and ensuring consistent access for all channel members.

When this will happen:

We will begin rolling out this change in late September 2026.

How this affects your organization:

• Who is affected:
  • All Microsoft Teams users who create or collaborate on Whiteboards using the Teams Channel tab app
• What will happen:
  • Whiteboards created from a Teams Channel tab will be stored in the channel’s SharePoint site.
  • All channel members will have consistent access based on channel permissions.
  • Existing Microsoft 365 compliance and security policies continue to apply.
  • Whiteboards will be discoverable from the Whiteboard board picker.
  • The change is enabled by default.

What you can do to prepare:

No action is required from administrators.

Recommended optional steps:

• Review internal documentation or helpdesk guidance that references Whiteboard storage locations.
• Inform support teams that Whiteboards created in Teams Channels are now SharePoint-based for troubleshooting and access requests.

[Compliance considerations:]

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

Admins will be able to ensure that new Loop workspaces are connected to and managed by an existing Microsoft 365 Group, similar to SharePoint Team sites.

This message is associated with Microsoft 365 Roadmap ID 422725

[When this will happen:]

General Availability (Worldwide): We will begin rolling out early April 2026 (previously early March) and expect to complete by late April 2026 (previously late March). 

[How this will affect your organization:]

Once Microsoft 365 Roadmap ID 422728 is available, end-users will have the ability to choose existing Microsoft 365 Groups for managing new Loop workspaces. This means that new Loop workspaces can optionally be connected to and managed by an existing Microsoft 365 Group, similar to how SharePoint Team sites are managed.

Additionally, Microsoft 365 Roadmap ID 422725 covers the capability to ensure that new Loop workspaces are connected to and managed by an existing Microsoft 365 Group, similar to SharePoint Team sites (it will not be an option for users to skip selecting an existing Microsoft 365 group if this policy is configured).

While this setting may align with existing governance processes, it’s important for admins to note that scenarios like automatic aggregation of Teams meeting content into a Loop workspace, or the creation of small, short-term project workspaces, will be more challenging for end-users unless they can skillfully select an existing M365 group during creation. Please consider this tradeoff in your adoption strategy.

If your organization has governance tools for SharePoint Communication sites that work effectively in a reactive manner (i.e., governance is applied after the site is created), Microsoft recommends extending this process to include Loop workspaces rather than using this policy.

[What you need to do to prepare:]

There is nothing you need to do to prepare. This capability will roll to your tenant automatically.