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

Updated March 31, 2026: This feature is now available in Frontier. Thank you for your patience.

[Introduction]

We are introducing two new Microsoft Graph APIs that enable admins to programmatically access and manage agents and apps within their organization. These APIs provide greater flexibility for reporting and integration scenarios without relying on manual UI workflows.

This message is associated with Microsoft 365 Roadmap ID 502875.

[When this will happen:]

Frontier (Preview): Now available. 

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

[How this affects your organization:]

Who is affected: Admins managing Copilot agents and apps within Microsoft 365 environments.

What will happen:

• New Graph API endpoints will be available:
  • GET graph.microsoft.com/copilot/admin/catalog/packages – Retrieves a complete inventory of all agents and apps (Microsoft, External, Shared, and Custom).
  • GET graph.microsoft.com/copilot/admin/catalog/packages/{id} – Fetches detailed metadata for a specific agent or app, including properties and manifest details.

• These APIs allow for automated reporting and integration workflows.
• No changes to existing UI workflows or admin policies.
• These Graph API endpoints are available to users with an existing Microsoft 365 license; no additional license or add-on is required.

[What you can do to prepare:]

• Review the Microsoft Graph API documentation to familiarize yourself with usage and capabilities at this time.

[Compliance considerations:]

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

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

[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): Rollout begins in early April 2026 and completes by mid-April 2026.

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

[Introduction]

We’re introducing the Adaptive Front-of-Room Experience for Microsoft Teams Rooms on Android in Town Hall scenarios. This update helps create a distraction-free experience for attendees while giving presenters full control over what’s shown on the front-of-room display. It’s designed to support hybrid Town Halls where presenters and attendees share the same physical space.

A Microsoft Teams Rooms Pro license is required to use this feature.

This message is associated with RMID 500378.

[When this will happen:]

Targeted release: Rollout will begin in early December 2025.

General Availability (Worldwide): Rollout will begin by early February 2026 (previously mid-December 2025) and is expected to be completed by early April 2026 (previously late March).

[How this affects your organization:]

• Who is affected: Organizations must have a Microsoft Teams Rooms Pro license to benefit from this feature. It applies to Teams Rooms on Android devices used in Town Hall scenarios.
• What will happen:
  • Teams Rooms added will join Town Hall meetings in a presenter role by default.
  • The front-of-room display will default to attendee view, showing only stage content and hiding backstage distractions.
  • The console will retain full presenter capabilities, including:
    • Green Room access
    • Backroom chat
    • Off-stage management tools
  • Presenters can switch the front-of-room display to presenter view when needed, without disrupting attendees.

Screenshot – New adaptive Front-of-Room Experience for Microsoft Teams Rooms on Android:

[What you can do to prepare:]

• Confirm your organization has a Microsoft Teams Rooms Pro license.
• When scheduling a Town Hall, add the Teams Room and assign it a presenter role.
• Ensure the room device is running the latest version of the Teams Rooms app.
• Communicate this new capability to Town Hall organizers and facilities teams.
• Update internal documentation if you provide guidance on Town Hall participation.

Learn more: Get started with town hall in Microsoft Teams | Meetings | Microsoft Teams | Microsoft Support

[Compliance considerations:]

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

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

[Introduction]

Organizational Messages will soon include email as a delivery channel, expanding beyond existing surfaces such as the Windows Taskbar, Windows Notifications, Windows Spotlight, and Teams popovers. This enhancement helps organizations reach users through familiar communication channels, improving engagement and adoption.

This message is associated with Microsoft 365 Roadmap ID 503562.

[When this will happen] 

• Public Preview (Worldwide): Rollout began in mid-November 2025 and is expected to complete by late January 2026.
• General Availability (Worldwide): Rollout begins in mid-April 2026 (previously late March) and is expected complete by mid-May 2026 (previously late April).

[How this will affect your organization]

Who is affected: Admins managing Organizational Messages in Microsoft 365.

What will happen:

• Email will be added as a delivery channel for Organizational Messages.
• Admins can send premade, templatized messages via email in addition to existing surfaces like Windows Spotlight, Taskbar, Notification Center, and Teams popovers:



• During Public Preview, new pre-built email templates will be available:

 

• Two welcome messages: Welcome to Copilot and Welcome to Copilot Chat.
• Six weekly Great M365 Copilot Journey emails highlighting features and best practices to drive onboarding and adoption.

[What you need to do to prepare]

No action is required at this time.

[Compliance considerations]

No compliance impacts identified. Review your organization’s policies as needed.

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

[Introduction]

Action Segments empower IT admins to target Organizational Messages using dynamic, pre-defined usage segments. This enhancement helps admins deliver more relevant communications based on user activity. For the Public Preview, there are two Action Segments available: Inactive Microsoft 365 Copilot Users and Inactive Microsoft 365 Copilot Users in Teams.

This message is associated with Microsoft 365 Roadmap ID 503563.

[When this will happen]

• Public Preview (Worldwide): Rollout began in mid-November 2025 and is expected to complete by late January 2026.
• General Availability (Worldwide): Rollout begins in mid-April (previously late March) and is expected to complete by mid-May 2026 (previously late April).

[How this will affect your organization]

• Who is affected:
  • Admins managing Organizational Messages in Microsoft 365.
  • Tenants with Microsoft 365 Copilot licenses (required for Action Segments to apply).
• What will happen:
  • Admins can target messages based on user activity using Action Segments: 
  
  • Two pre-defined segments are available during Public Preview:
    • Inactive Microsoft 365 Copilot Users
    • Inactive Microsoft 365 Copilot Users in Teams
  • No changes to existing admin policies; feature is additive.

[What you can do to prepare]

• No immediate action is required at this time.
• If you want to take advantage of this feature:
• Ensure your organization has Microsoft 365 Copilot licenses (required for Action Segments to apply).
• Review and configure Action Segments in the Microsoft 365 admin center.
• Communicate this change to your helpdesk or support teams.
• Update internal documentation if you detail Organizational Messages or Copilot usage.

[Compliance considerations]

No compliance impacts identified. Review your organization’s policies as needed.

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

[Introduction]

We’re introducing a new flexible layout option in future Teams meetings to give users more control over how shared content and participant videos appear. A resizable divider will let users adjust the space between shared content and the video gallery. Want to focus more on the presentation? Expand the content area. Prefer to see more people? Shrink the content area to make room for more video tiles. Users can also swap the position of content and participants to suit their viewing preference. This works with spotlighted speakers, pinned videos, and Speaker View, providing a more personalized meeting experience—especially helpful on larger or ultra-wide screens.

Screenshot 1: When someone is sharing content or when you are in Speaker view, grab the divider between the left and right views to resize them.

Screenshot 2. When you drag the divider to the left, you will see more people in the right gallery view. When you drag the divider to the right, you will see less people in the gallery but the content or speaker will become larger.

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

When this will happen:

• Targeted Release: Rolling out early January 2026, expected completion by late January 2026.
• General Availability (Worldwide and GCC): Rolling out early February 2026, expected completion by early April 2026 (previously late March).

How this will affect your organization:

Who is affected: All Teams users in Worldwide and GCC environments.

What will happen:

• Users will see a new resizable divider in Teams meetings during content sharing.
• Users can adjust layouts to prioritize content or participant video tiles.
• Users can swap positions of shared content and video gallery.
• Works with spotlighted speakers, pinned videos, and Speaker View.
• Enabled by default; no admin configuration required.

What you can do to prepare:

• No configuration is required; the feature is enabled by default.
• Update training materials and FAQs to explain:
  • How to find and use the resizable divider.
  • How to adjust layouts during content sharing and Speaker View.
• Communicate this change to helpdesk staff to prepare for user questions, especially from those with large or ultra-wide monitors.

Compliance considerations:

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

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

[Introduction]

Microsoft 365 Copilot in PowerPoint will soon support enterprise image libraries hosted on Adobe Experience Manager (AEM). This integration allows users to generate slides using branded images from your organization’s asset library, helping maintain brand consistency and streamline content creation.

This message is associated with Roadmap ID 516037, 516038, and 516039.

[When this will happen:]

General Availability (Worldwide): Rollout begins end of April 2026 (previously end of March) and is expected to complete by end of May 2026 (previously end of April).

[How this affects your organization:]

Who is affected:

• Organizations using Adobe Experience Manager for brand asset management
• Admins and brand managers configuring enterprise image libraries
• PowerPoint users leveraging Microsoft 365 Copilot

What will happen:

• Admins can connect enterprise image libraries from AEM to Microsoft 365 Copilot in PowerPoint.
• Users will be able to generate slides using branded images from AEM.
• If no enterprise image library is connected, the branded image option will be disabled, and only Microsoft 365 images will be available.
• This feature is available by default for admins to configure; no opt-in required.

[What you can do to prepare:]

• Deploy AEM assets Microsoft 365 Copilot Connector by following the steps outlined in the article Deploy the Adobe Experience Manager Assets Microsoft 365 Copilot connector.
• Give your final consent on the Adobe Experience Manager Assets screen



• Ensure images in AEM include robust metadata (keywords, titles, alt-text) for better searchability.
• Communicate this change to your design and marketing teams.
• Update internal documentation if you detail image sourcing for PowerPoint.

Once setup is complete, users can select the New Slide with Copilot icon in the PowerPoint ribbon, enter a prompt, and choose their preferred image source—either Microsoft 365 images or their organization’s branded image library—via the Image Source menu.

Learn more:

• About Adobe Experience Manager Assets Microsoft 365 Copilot connector
• Keep your presentation on-brand with Copilot

[Compliance considerations:]

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

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

[Introduction]

Copilot in PowerPoint lets you create, edit, and refine presentations through natural conversation, directly in your presentation. You can start a new presentation or build on an existing one, asking Copilot to generate slides, update content, improve layouts, and polish design—while preserving formatting, structure, and branding. Available to Microsoft 365 users.

For Microsoft 365 Copilot-licensed users, Copilot can also connects to your brand kit so you can apply branded templates, insert brand‑approved images, and check for brand compliance.

Screenshot – Entry point for Edit with Copilot in PowerPoint

This message is associated with Roadmap IDs 557277, 557276, 557177, 499655, 548520 and 548646.

[When this will happen:]
General Availability (Worldwide): Rollout will begin mid-February 2026 and complete by end of April 2026.

[How this will affect your organization:]

Who is affected:
Users in your organization who use the PowerPoint application and have Microsoft 365 Copilot licenses.

What will happen:

• Users will gain access to Copilot editing capability in Microsoft 365 Copilot for PowerPoint.
• Users can interact with Copilot Chat to edit and refine presentation content.
• Formatting, structure, and branding will be preserved.
• Users can use Enterprise assets to further enhance the presentation.
• Edit with Copilot is available to all eligible users by default; no action is needed by Admins.
• Note: Copilot editing capability is part of Copilot Chat within PowerPoint and is not a standalone feature.

[What you need to do to prepare:]
No action is required.

• Communicate availability of Copilot editing capability to helpdesk staff and users.
• Encourage users to explore the feature to improve presentation workflows.
• Review and update internal documentation if you provide guidance on PowerPoint or Copilot usage.

[Compliance considerations:]

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

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

[Introduction]

The Researcher Agent in Microsoft 365 Copilot empowers users to create rich, detailed reports on any topic they choose whether from work or web content. We are introducing a new output formats in the Researcher Agent that will allow users to export generated reports into infographics. We are also updating the UX for previously existing output formats- Word and Pages.

This message is associated with Microsoft 365 Roadmap ID 546246.

[When this will happen]

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

[How this will affect your organization]

This update gives users greater control over their research reports as they will now be able to convert their reports into a new format for easier viewing, use and sharing. This feature is enabled by default and designed to enhance user productivity without requiring admin configuration.

[What you can do to prepare]

• No action is required at this time.
• Admins may wish to inform users of the new output format available in the Researcher Agent in Microsoft 365 Copilot.

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

[Introduction]

We are updating the filter pane in SharePoint Document Libraries and Lists to deliver a faster, more flexible filtering experience. The core functionality remains the same—users can continue filtering by metadata fields as before—but these improvements address performance issues and incorporate customer feedback for a more intuitive interface.

Screenshot: Side-by-side comparison of filter pane before and after changes

[When this will happen:]

• Targeted Release: Rollout begins mid-February 2026 and is expected to complete by late February 2026.
• General Availability (Worldwide, GCC, GCC High, DoD): Rollout begins end of March 2026 (previously late February) and is expected to complete by mid-April 2026 (previously mid-March).

Who is affected: All users of SharePoint Online Document Libraries and Lists.

[What will happen:]

The filter pane will automatically update in its existing location. Users will experience the following enhancements:

• Expand and collapse sections: Control which filter sections appear. Users can expand or collapse individual sections or collapse all sections at once to quickly scan all available filters.
• See all filterable fields: All filterable fields from library or list content will now display without limitations. Because fields are automatically shown, the ability to pin or remove filter fields has been removed.
• Enjoy better performance: Filtering interactions are faster and more responsive across all libraries. Users continue to apply filters as before, including filtering by person, date modified, content type, and any custom metadata columns.

[What you can do to prepare:]

• Update internal documentation or training materials to reflect the new expand/collapse filter pane behavior and removal of the pin/remove filter field functionality.
• Communicate these changes to helpdesk and support staff.
• No admin action or configuration change is required.

[Compliance considerations:]

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

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

[Introduction]

Consecutive Interpretation is a new interpretation mode available as an add‑on to the existing Interpreter agent in Microsoft Teams. It enables structured multilingual conversations in meetings by providing shared, meeting‑level interpretation when enabled by a Microsoft 365 Copilot licensed user.

This mode uses consecutive (turn‑by‑turn) interpretation, meaning participants speak one at a time and each speaker’s words are interpreted before the next speaker begins. This structured flow reduces overlap, improves interpretation accuracy, and helps everyone stay aligned in real time.

Consecutive Interpretation is ideal for back‑and‑forth, interactive discussions where participants need to respond, clarify, and build on each other’s input across languages, such as working sessions, negotiations, and cross‑functional collaboration.

This message is associated with Microsoft 365 Roadmap ID 557180.

[When this will happen]

• Targeted Release: Rollout begins in early May 2026 (previously early April) and is expected to complete by late May 2026 (previously mid-April).
• General Availability (Worldwide): Rollout begins in late May 2026 (previously late April) and is expected to complete by mid-June 2026 (previously early May).

[How this will affect your organization]

Who is affected

• All Microsoft 365 tenants using Microsoft Teams meetings where users are licensed with Microsoft 365 Copilot.

What will happen

• For tenants
  • The new Consecutive Interpretation mode extends the existing Interpreter agent to support structured, interactive multilingual meetings.
  • The existing Interpreter experience remains unchanged unless this new mode is enabled.
• For admins
• No new tenant‑level configuration is required.
• The feature is available to all users with a Microsoft 365 Copilot license.
• Existing compliance, privacy, and data‑handling policies for Interpreter continue to apply.
• For users
• When a Microsoft 365 Copilot licensed user enables the mode, interpretation becomes a shared meeting‑level experience rather than an individual setting.
• Participants speak consecutively, with each turn interpreted and delivered before the next participant begins.

[What you need to do to prepare]

• No action is required to maintain current behavior.
• Ensure any users who intend to use this mode have an active Microsoft 365 Copilot license.
• Consider providing guidance to users about when this mode is best suited (for example, working sessions, negotiations, or detailed multilingual collaboration).

[Compliance considerations]

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

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

[Introduction]

Exchange Online includes email‑sending limits based on three factors: recipient rate limit, recipient limit, and message rate limit. To support customers whose internal communication needs exceed these standard limits, we are introducing High Volume Email (HVE) for Microsoft 365. HVE is designed for large‑scale internal communications and integrates with business applications and devices to support operational and mass‑mailing scenarios. It uses a transactional pricing model based on the number of recipients.

HVE is currently available at no additional cost, with metered billing starting June 1, 2026. Pricing information is now published. For more information, see High Volume Email Is Now Available in Exchange Online.

This message is associated with Microsoft 365 Roadmap ID 382633.

[When this will happen]

• Public Preview: Available now.
• General Availability (worldwide): Rolling out now and rollout is expected to complete early April 2026.

[How this affects your organization]

Who is affected

• Admins managing Exchange Online mail flow and reporting
• Organizations with large-scale internal email distribution needs

What will happen

• A new High Volume Email page will appear under Mail flow in the Exchange admin center.
• Admins can create and manage Mail User accounts enabled for HVE.
• HVE accounts use a dedicated SMTP endpoint for high-volume sending.
• A new High Volume Email report will appear under Reports > Mail flow to help admins monitor HVE usage per account.
• HVE is opt‑in; it does not modify default sending limits or existing mail flow behavior.

Screenshot 1 – Create new HVE specific accounts: 

Screenshot 2 – Manage HVE accounts, including assigned billing policies:

[What you can do to prepare]

No action is required to prepare for this change.

You may want to:

• Review and update any internal documentation that describes email‑sending processes.
• Learn more about setup and configuration: Manage high volume emails for Microsoft 365 Public preview | Mail flow best practices | Exchange Online | Microsoft Learn

[Compliance considerations]

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

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

[Introduction]

Outlook for iOS and Android is adding support for recommended and automatically applied sensitivity labels when you compose an email on your mobile device. With this release, we are extending Recommended Labels to Outlook mobile (iOS and Android), providing the same labeling experience users already have in Outlook on the desktop and web. For recommended labels, you’ll see a prompt to review and apply the suggested label. For automatic labels, they will be applied without needing any action from you. This ensures alignment with your organization’s Microsoft Purview Information Protection labeling policies when sensitive information is detected.

This message is associated with Microsoft 365 Roadmap IDs 557253 and 557254.

[When this will happen]

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

[How this affects your organization]

Who is affected

• Users who compose email in Outlook for iOS and Android
• Organizations with automatic or recommended sensitivity labeling policies configured in Microsoft Purview Information Protection

What will happen

• This update extends Recommended Labels to Outlook mobile (iOS and Android), enabling recommended label prompts when sensitive information is detected.
• Users see recommended sensitivity labels when Microsoft Purview identifies sensitive information during email composition.
• Users are prompted to review and apply recommended labels.
• Automatic labels are applied without user action when required by policy.
• The feature is on by default for organizations with existing Purview sensitivity labeling policies.
• No changes are made to Purview policy configuration, scopes, or publishing.
• Outlook desktop and Outlook on the web are not affected; this update adds support for Outlook mobile only.

Figures 1–3. Examples of users being prompted to review and apply recommended sensitivity labels in Outlook mobile.

[What you can do to prepare]

No action is required if your organization already uses automatic or recommended sensitivity labeling policies in Microsoft Purview Information Protection. Outlook mobile support is added automatically.

Admins may choose to:

• Review existing labeling policies in the Microsoft Purview portal to confirm correct scoping and label publishing.
• Ensure sensitivity labels are published to users who rely on Outlook mobile.
• Communicate this change to helpdesk or support teams.
• Review Microsoft Learn documentation for minimum supported Outlook mobile versions: Sensitivity label capabilities in Outlook – Minimum versions for sensitivity labels in Office apps | Microsoft Purview | Microsoft Learn

[Compliance considerations]

Updated March 25, 2026: We have updated the second bullet in ‘What you can do to prepare’. Thank you for your patience. 

[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:]

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

[Introduction]

Microsoft Teams is improving the copy and paste experience for messages that contain @mentions, shared contacts, and other supported @tags. Previously, when users copied and pasted messages containing mentions, those mentions could be converted into plain text and lose their interactivity.

With this update, Teams preserves supported tags during copy and paste whenever possible. If a tag is valid in the destination conversation, it remains interactive and behaves the same way as when originally authored. If the tag cannot be used in that context, it safely falls back to plain text while preserving the original display text. This ensures a more consistent and reliable messaging experience across chats and channels.

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

[When this will happen:]

• Targeted Release: Rollout begins early May 2026 (previously early April) and is expected to complete by mid-May 2026 (previously mid-April).
• General Availability (Worldwide): Rollout begins mid-May 2026 (previously mid-April) and is expected to complete by late May 2026 (previously late April).
• General Availability (GCC, GCC High): Rollout begins mid-May 2026 (previously early May) and is expected to complete by early June 2026 (previously mid-May).
• General Availability (DoD): Rollout begins early June 2026 (previously mid-May) and is expected to complete by late June 2026 (previously late May).

[How this affects your organization:]

Who is affected:

• All users of Microsoft Teams who copy and paste messages containing @mentions, shared contacts, or other supported tags in chats and channels.

What will happen:

• Supported tags are preserved during copy and paste when the tag is valid in the destination conversation.
• Preserved tags remain interactive and behave the same way as when originally authored.
• If a tag cannot be used in the destination context (for example, due to membership, permissions, or scope limitations), it automatically falls back to plain text while preserving the original display text.
• This reduces confusion, preserves message context, and minimizes the need for users to manually recreate mentions after pasting content.

There is no change to how mentions or notifications behave after a message is sent.

[What you can do to prepare:]

• No admin action is required.
• This feature is enabled by default and will be available automatically once the rollout reaches your tenant.
• Consider notifying helpdesk staff or end users about the improved copy and paste behavior to set expectations.

[Compliance considerations:]

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

• Narrator now provides rich image descriptions on Copilot+ PCs and works with Copilot on all Windows 11 devices, allowing users to get instant on‑device descriptions or ask Copilot for more detail.
• This update improves the design of the dialog boxes in Settings > Accounts > Other users to match the modern Windows look and support dark mode. The visibility of the dialog box option depends on whether the device has a domain joined work or school account.
• This update improves the File Explorer experience, including more reliable unblocking of downloaded files and support for Voice Typing when renaming files.
• This update delivers several display improvements, including support for refresh rates above 1000 Hz, improved auto‑rotation and HDR reliability, and better power efficiency for USB4‑connected monitors during sleep.

• Windows 11, version 26H1: KB5079489
• Windows 11, versions 25H2 and 24H2: KB5086672

Updated March 31, 2026: We have updated the 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.

[When this will happen:]

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

[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:]

• Connect to Microsoft Fabric Lakehouse tables without manual exports or data replication.
• Allow AI-powered agents to query and reason across Dynamics 365 Sales (Dataverse) and Lakehouse data together.
• Add support for operational and financial datasets, including:
  • Revenue actuals
  • Targets and budgets
  • Invoicing and backlog
• View sales and sales operations insights seamlessly within AI-powered research and analysis experiences

• Find MCP servers authored, hosted, or certified by Microsoft.
• Query and explore over 1,470 connectors and their individual actions.
• Discover custom APIs available in your organization or from partner teams.

• Build new MCP servers by selecting connector actions, APIs, and reusable tools.
• Clone an existing MCP server, such as a Dataverse MCP, and tailor it by adding or removing tools to match your scenario.
• Use MCP servers as modular, scenario-focused endpoints that can be reused across agents.

• Accessible as a simple environment scoped URL—no UI required.
• Use in Visual Studio Code, Claude, or any agent or tool that supports HTTP.
• Compose, publish, and maintain MCP servers entirely through API calls.

• Enforce data loss prevention (DLP) policies.
• Apply access controls at both the MCP server and individual tool level.

We've released updates to the following update channel for Microsoft 365 Apps:

• Current Channel

[When this will happen:]

We'll be gradually rolling out this update of Microsoft 365 Apps to users on that update channel starting March 31st, 2026 (PST).

[How this will affect your organization:]

If your Microsoft 365 Apps clients are configured to automatically update from the Office Content Delivery Network (CDN), then no action is required.

If you manage updates directly you can now download this latest update and begin deployment.

[What you need to do to prepare:]

To get more details about this update view the following release notes:

• Current Channel