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

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

[Introduction]

Brand Impersonation Protection for Teams Calling adds proactive safeguards against fraudulent or deceptive external callers who attempt to appear as trusted organizations. This helps reduce social-engineering risks and improves tenant security when users receive first-contact external calls. This update aligns with Microsoft’s ongoing investments in caller identity protection and secure collaboration.

This message is associated with Microsoft 365 Roadmap ID 543239.

[When this will happen:]

Targeted Release: Rollout will begin mid-May 2026 (previously early May) and is expected to complete by late May (previously late April).
General Availability: Timelines will be communicated in a future message.

[How this affects your organization:]

Who is affected:

• All organizations using Microsoft Teams Calling that receive inbound VoIP calls from first-contact external callers.

What will happen:

• Teams will evaluate inbound calls for signs of brand impersonation.
• Users will see high-risk call warnings before answering suspicious calls.
• Warnings may continue during the call if risk signals persist.
• Users can accept, block, or end the call.
• The feature will be enabled by default.
• Existing Teams Calling policies remain unchanged.

[What you can do to prepare:]

No admin action is required at this time.

• Inform helpdesk staff that users may begin seeing high-risk call warnings.
• Update internal training materials if applicable.
• Review Microsoft documentation on caller ID security when available.

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

[Compliance considerations:]

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

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

[Introduction]

We’re introducing a new co-branding capability that will allow organizations to display a branded footer at the bottom of the Chat screen in the Microsoft 365 Copilot app. This update will enable admins to add their organization’s logo to their users’ Microsoft 365 Copilot app, helping users confirm they are using their trusted, work-managed Copilot experience.

This feature will begin rolling out in early May 2026 (previously late March) and is expected to complete by mid-June 2026 (previously end of May).

This message is associated with Microsoft 365 Roadmap ID 555852.

[When this will happen]

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

[How this will affect your organization]

Who is affected

• All Microsoft 365 tenants using the Microsoft 365 Copilot app.

What will happen

• Admins will be able to upload a logo in the Microsoft 365 admin center to customize the footer in the Microsoft 365 Copilot app.
• The footer will display an “Approved by [Logo]” indicator to help users confirm they are in an organization-approved Copilot environment: 

  

• Only the logo from your organization’s theme configuration will be used; other theme elements will not be applied in this release.
• This feature will be off by default and will require admin configuration.
• There will be no user impact unless an admin enables the footer.

[What you can do to prepare]

No action will be required unless you want to enable the branded footer.

Admins who want to configure this feature should:

• Review and verify your organization’s theme configuration in the Microsoft 365 admin center.
• Upload the logo you want to display in the Microsoft 365 Copilot app footer once rollout begins.
• Use the existing theme management flow to apply co-branding once the feature is available.

For configuration guidance: Customize the theme for your organization | Microsoft 365 | Microsoft Learn

[Compliance considerations]

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

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

[Introduction]

We’re introducing several new Copilot Notebooks features to the Frontier Public environment to help users learn faster, create content more efficiently, and collaborate more easily within their organization. These enhancements build on customer feedback and expand how Copilot can reason over notebook content and connected Microsoft 365 resources. Each feature will reach General Availability (GA) on its own schedule following Frontier Public availability.

[When this will happen:]

• Frontier Public rollout: Beginning late March, 2026, with broad availability across Frontier Public tenants by March 28, 2026.
• General Availability (GA) (Worldwide): Rolling rollout from early April 2026 through early June 2026 (previously early May). Each feature will reach GA on its own schedule.
• Rollout is gradual; availability may vary by tenant and feature.

[How this affects your organization:]

Who is affected:

• All Copilot Notebooks users (in the Microsoft 365 app and OneNote) in Frontier Public tenants

What will happen:

• The following new Copilot Notebooks features will become available to Frontier Public tenants starting in late March 2026 and will transition to General Availability according to the timelines listed below. All features are enabled by default.
• Chat and Page Interactivity: Allows users to edit and create pages in a notebook directly through chat.
  • Frontier Public: late March, 2026
  • GA: mid-April to early June 2026
• Study Guide: Automatically generates quizzes, flashcards, topic pages, and other learning tools based on notebook content.
  • Frontier Public: late March, 2026
  • GA: mid-May to late May 2026 (previously Late April)
• SharePoint Sites and Folders grounding: Allows users to add SharePoint sites and folders as references so Copilot can use them when reasoning and generating content.
  • Frontier Public: late March, 2026
  • GA: late May to early June 2026 (previously Early April)
• PowerPoint agent in Copilot Notebooks: Enables users to create PowerPoint presentations using notebook content and references in a few clicks.
  • Frontier Public: late March, 2026
  • GA: late May to early June 2026 (previously May)
• Word agent in Copilot Notebooks: Enables users to create Word documents using notebook content and references in a few clicks.
  • Frontier Public: late March, 2026
  • GA: late May to early June 2026 (previously May)
• Sharing to Microsoft 365 Modern Groups: Allows notebooks to be shared directly with Microsoft 365 Modern Groups.
  • Frontier Public: late March, 2026
  • GA: April 2026
• Mind maps: A new interactive visual artifact that helps users understand notebook content through a grounded map of key topics, themes, and relationships. Users can explore nodes, view summaries, and use notebook chat to learn more. Generated Mind Maps are retained for 30 days and remain private to the creator, including in shared notebooks. 
  • Frontier Public: late March, 2026
  • GA: mid-May to early June 2026
• Existing Microsoft 365 permissions and access controls are respected.
• No general limitations are known beyond those noted for individual features.

[What you can do to prepare:]

• No admin action is required.
• Consider:
  • Informing helpdesk and support teams about new Copilot Notebooks capabilities.
  • Updating internal training or adoption materials to reflect the new features.
  • Reviewing how Copilot Notebooks are used in your organization to ensure appropriate SharePoint access is in place.

Learn more: Get started with Microsoft 365 Copilot Notebooks (will be updated before GA rollout)

[Compliance considerations:]

All other compliance areas reviewed (data storage changes, Purview controls, audit, eDiscovery, retention, DLP, Conditional Access, GDPR data subject rights, third-party integrations, admin reporting) are not impacted.

Updated May 4, 2026: We have updated the content. Thank you for your patience. 

[Introduction]

We are adding new Copilot metrics across Microsoft 365 apps to help you better understand how users engage with Copilot. These metrics include actions taken in the Microsoft 365 Copilot app, Microsoft Edge, and OneNote, and intent-based usage across Outlook, Word, Excel, and PowerPoint. This update expands visibility into how users adopt Copilot and supports improved insights in the Copilot Dashboard and Advanced Analysis in Copilot Analytics. 

This message is associated with Microsoft 365 Roadmap ID 557981.

[When this will happen]

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

[How this affects your organization]

Who is affected

• This capability is available to users who are licensed for Microsoft 365 Copilot.
• All Microsoft 365 tenants with access to Copilot Dashboard or Copilot Analytics in Viva Insights

What will happen

• New metrics will appear in the Copilot Dashboard and Advanced Analysis.
• You will be able to track Copilot usage in the Microsoft 365 Copilot app, Microsoft Edge, and OneNote:

   

  

• Additional intent-based scenarios will be measured in Outlook, Word, Excel, and PowerPoint. These scenarios include suggested replies, translation, coaching, and clean data.
• The feature will be enabled automatically for all tenants.
• No configuration changes or policy updates are required.

[What you can do to prepare]

• No action is required before rollout.
• You may choose to notify relevant teams about the new metrics.
• Update internal documentation if your organization tracks Copilot usage analytics.
• Review updated online documentation when it becomes available in early May.

[Compliance considerations]

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

Updated May 4, 2026: We have updated the content. Thank you for your patience. 

[Introduction]

Intelligent summaries in Copilot Dashboard help you quickly understand what’s driving Copilot adoption in your organization. These AI‑generated insights highlight key usage trends, areas of success, and opportunities where focused attention can accelerate value. Suggested prompts guide deeper exploration of underlying drivers and adoption patterns.

This message is associated with Microsoft 365 Roadmap ID 557681.

[When this will happen]

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

[How this will affect your organization]

Who is affected

• Admins using the Microsoft 365 Copilot Dashboard in Microsoft Viva and Microsoft 365

What will happen

• Intelligent summaries will appear automatically in the Copilot Dashboard:

   

• Admins will see AI‑generated insights that highlight adoption trends and key usage patterns.
• Suggested prompts will be available to help admins drill into specific drivers and areas of opportunity.
• No configuration changes are required; the feature is on by default for eligible tenants.
• Existing admin controls and permissions remain unchanged.
• There is no user workflow impact.

[What you can do to prepare]

No action is required before rollout.

If helpful for your organization, you may:

• Notify helpdesk or training teams about the new summaries.
• Update internal documentation that references the Copilot Dashboard.
• Review updated online documentation, which will be refreshed as rollout begins in late April.
• If you choose not to use this feature, you can roll back by disabling intelligent summaries using available admin controls.

[Compliance considerations]

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

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

[Introduction]

We’re improving the Viva Engage experience in Microsoft Teams for iOS by bringing pinned resources and related communities into the Teams mobile app. Pinned resources highlight important links and files within a community, while related communities help users discover other relevant Viva Engage communities. These are two separate features that work together to improve information access and community discovery.

This update aligns the iOS experience with Engage on the web, the Engage mobile app, and Teams for Android, helping users discover important content and related communities more easily—especially those who rely on Teams on iOS as their primary communication tool.

This message is associated with Roadmap ID 559107.

[When this will happen:]

• General Availability (Worldwide): Rollout begins in late May 2026 (previously early May) and is expected to complete by late July 2026 (previously early June).

[How this affects your organization:]

Who is affected:

• Users who access Viva Engage communities in Microsoft Teams on iOS
• Community admins who manage Viva Engage communities

What will happen:

• Users will see pinned resources for a community directly within Teams on iOS.
• Users will see related communities surfaced within the community experience.



• The experience will match what is already available in the Viva Engage mobile app, Viva Engage on the web, and Teams for Android.
• The feature is enabled by default.
• There are no changes to existing admin policies or configurations.

[What you can do to prepare:]

No admin action is required.

• Communicate this update to end users who use Teams on iOS.
• Encourage Viva Engage community admins to review pinned resources and related communities.
• Update internal documentation or helpdesk guidance, if applicable.

[Compliance considerations:]

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

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

[Introduction]

To help organizations schedule shared spaces more efficiently, Microsoft Teams will introduce the ability for users to book future meetings directly from Teams panel devices running on Android. This change reduces the need to switch to a desktop or mobile calendar and helps streamline ad‑hoc and near‑term scheduling in shared spaces. The feature will be available for rooms with Teams Rooms Pro and Shared Device licenses.

This message is associated with Microsoft 365 Roadmap ID 557168.

Note: This feature is supported only on Teams panel devices running Android and is not available on non‑Android panel hardware.

[When this will happen]

• General Availability (Worldwide, GCC, GCCH): We will begin rolling out in mid-May 2026 (previously early May) and expect to complete in mid-May 2026 (previously early May).

[How this affects your organization]

Who is affected

• Organizations using Microsoft Teams Rooms panels on Android
• Admins managing Teams Rooms Pro or Shared Device licensed rooms
• Users who schedule meetings from Teams panel devices

What will happen:

• When enabled by an admin, users will be able to book future meetings directly from a Teams panel by browsing the room calendar: 

  

• Available time slots will include any open time through midnight the next day:
   

• If enabled by an admin, users will be able to add a guest while booking from the panel.
• The feature will be OFF by default and requires admin configuration.
• Existing room booking and calendar policies will continue to be respected.

[What you can do to prepare]

No immediate action is required at this time.

Before rollout, admins can:

• Review the upcoming setting in the Teams admin center.
• Decide whether to enable future room booking from Android‑based panel devices.
• Decide whether to allow users to add guests while booking.
• Inform helpdesk or facilities teams about this upcoming capability.

Read the release notes for devices in Microsoft Teams:  What’s new in Microsoft Teams devices | Microsoft Teams | Microsoft Learn

[Compliance considerations]

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

[Introduction]

Azure PST Import provides a structured, PowerShell-based way for administrators to import PST files stored in Azure Blob Storage into Exchange Online mailboxes, which are commonly used to store archived Outlook mailbox content. This capability helps organizations migrate historical email data in a controlled and auditable way by validating readiness before importing and by providing reports throughout the process. The process starts by creating an Azure PST Import endpoint to establish the connection between Azure storage and Exchange Online. Administrators then run a migration batch in Analyze mode to review readiness and validate the input before proceeding. Once the analysis results are reviewed, they use those results to create and start the import batch, which begins importing the PST files into the specified mailboxes.

This message is associated with Microsoft 365 Roadmap ID 557559.

[When this will happen]

Global rollout

• Start: August 31, 2026 (previously May 4)
• Complete: September 1, 2026 (previously May 15)

[How this affects your organization]

Who is affected

• Microsoft 365 administrators managing Exchange Online
• Administrators using Microsoft Purview Data Lifecycle Management
• Organizations that import PST files into user or archive mailboxes

What will happen

• Administrators complete the Azure PST Import process using PowerShell cmdlets only.
• The workflow includes:
  • Creating an Azure PST Import migration endpoint
  • Running a migration batch in Analyze mode to validate readiness
  • Reviewing analysis results and reports
  • Creating and starting the import batch
  • Performing post-import cleanup
• This experience is not available through a graphical user interface (GUI).
• Existing mailbox prerequisites and quotas are validated before importing begins.
• There is no direct user impact; the feature is admin-driven.

[What you can do to prepare]

• Ensure your Azure storage account and container exist and are reachable; the endpoint creation cmdlet validates both during setup.
• Grant the Storage Blob Data Reader role to the Office 365 Import Service app on the target storage account. Without this permission, creating the Azure PST Import endpoint will fail.
• Prepare your batch input files (XML and/or CSV) and run the migration batch in Analyze mode first so the service can validate readiness before importing.
• Confirm analysis prerequisites for target mailboxes:
  • Appropriate license assigned
  • Mailbox is not inactive or soft-deleted
  • Recipient type is UserMailbox
  • Archive is enabled if importing to archive
  • Quota validations (ArchiveQuota / RecoverableItemsQuota) occur during analysis
• Validate PST files ahead of time:
  • Analysis verifies that all specified PST files exist
  • PST file size is validated during analysis

For detailed cmdlet usage and guidance, review the Azure PST Import documentation on Microsoft Learn.

[Compliance considerations]

Updated May 5, 2026: We have updated the content below to show as intended. Thank you for your patience.

[Introduction]

We’re introducing Calendar Agentic capabilities in Microsoft 365 Copilot to help users reduce meeting overload and automate routine calendar decisions. With natural-language instructions, users can allow Copilot to automatically accept, follow, decline, or remove canceled meetings based on rules they define. This capability builds on existing Copilot agent controls and respects current tenant compliance and governance settings, while helping users save time and stay focused.

[When this will happen]

Rolling out to Frontier:

• Rollout start: Late April 2026
• Rollout end: Early May 2026

[How this affects your organization]

Who is affected

• Users with a Microsoft 365 Copilot license using:
  • Outlook (classic and new)
  • Outlook on the web
  • Microsoft Teams
  • Outlook mobile (iOS and Android)
• IT admins who manage Copilot agent access and policies in Microsoft 365

What will happen

• Calendar Agentic capabilities will appear in Microsoft 365 Copilot Chat from calendar-related surfaces.
• Users can enable agentic actions by selecting Allow Actions (Frontier) in Copilot Chat.
• Users can create ongoing, natural-language calendar instructions (for example, “Always accept meetings from my manager if my calendar is free”).
• Calendar Agentic experiences respect each user’s Outlook working hours settings.
• A new activity history view will show actions taken by Copilot, grouped by Accepted, Followed, Declined, and Deleted, with an explanation for each action.
• The feature is enabled by default for users who have Copilot and are allowed to use agents.
• No new admin controls are introduced; existing Copilot agent policies apply.
• Calendar Agentic experiences act only on the signed-in user’s calendar and does not operate across mailboxes or tenants.

What is not changing:

• Existing admin policies, permissions, retention, and compliance boundaries remain unchanged.
• No changes are made to data residency, audit logging, or Purview enforcement.

[What you can do to prepare]

• No action is required if your organization already allows Copilot agents.
• Review your existing Copilot agent policies to confirm which users are permitted to enable agentic actions.
• Consider notifying helpdesk or end users that Copilot may take automated calendar actions once users enable the feature.
• Update internal guidance if you document Copilot or Outlook calendar behavior.

Learn more: 

• Copilot in Outlook: New agentic experiences for email and calendar | Outlook Blog
• Frontier program – Microsoft Adoption

[Compliance considerations]

1. The store administrator configures dedicated hardware stations in Headquarters, each with a payment terminal assigned.
2. The sales associate enables shared shift on their register, except when the cash drawer is not present, in which case they do not need a shared shift for this feature.
3. From the POS, the associate selects the desired dedicated hardware station — typically the one nearest to where they are serving the customer.
4. When the customer is ready to pay, the POS routes the payment request to the terminal on the selected hardware station.
5. The associate completes the transaction at the customer’s location without returning to the register.

• Dedicated hardware stations must be configured by an IT admin or store manager in Headquarters before using.
• Each hardware station requires an associated payment terminal.
• Shared shifts must be enabled on the register.

[Introduction]

We’re expanding Microsoft Purview Data Loss Prevention (DLP) controls for Microsoft 365 Copilot and Copilot Chat to help organizations reduce the risk of untrusted or externally sourced content influencing AI‑generated responses. This new capability allows admins to exclude emails from external senders from being used as grounding data during Copilot prompt processing. When enabled, Copilot continues to generate responses using trusted internal Microsoft 365 data sources, subject to existing licensing and policy controls.

This message is associated with Microsoft 365 Roadmap ID 548671.

[When this will happen]

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

[How this affects your organization]

Who is affected

• Organizations using Microsoft 365 Copilot (Premium) or Copilot Chat
• Admins managing AI governance, security, and data protection using Microsoft Purview

What will happen

• A new DLP policy control will be available for Microsoft 365 Copilot and Copilot Chat.
• When enabled by an admin:
• Emails sent from external or untrusted domains are excluded from being:
  • Referenced
  • Summarized
  • Used as grounding data by Copilot
• Copilot continues to generate responses using trusted internal Microsoft 365 data sources (for example, SharePoint, OneDrive, and internal Exchange content), subject to existing licensing and policy.

This change does not:

• Affect email delivery, retention, eDiscovery, or user access
• Change existing Copilot interaction behavior unless the policy is explicitly configured

Default state:

• Off by default.
• There is no change unless an admin enables this control in Microsoft Purview.

Screenshot 1. Select Microsoft 365 Copilot and Copilot Chat as the DLP policy location: 

Screenshot 2. New DLP setting to restrict processing of external email content: 

[What you can do to prepare]

No action is required if you do not plan to use this capability.

If you want to enable the feature:

• Create or update a DLP policy for Microsoft 365 Copilot in the Microsoft Purview portal.
• Review existing DLP configurations to understand potential Copilot impact.
• Ensure your admin account has the required DLP and Purview roles.
• Inform IT, security, and helpdesk teams about the new control.
• Update internal documentation related to AI governance and Copilot usage.

Learn more:

• Learn about data loss prevention | Microsoft Purview | Microsoft Learn
• Learn about using Microsoft Purview Data Loss Prevention to protect interactions with Microsoft 365 Copilot and Copilot Chat | Microsoft Purview | Microsoft Learn
• Permissions – Create and deploy data loss prevention policies | Microsoft Purview | Microsoft Learn

[Compliance considerations]