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

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

 What and Why

We’re introducing a new capability that allows users with a Microsoft 365 Copilot license to scope and control Copilot Chat responses by selecting specific content sources. This enhancement is designed to improve the relevance and accuracy of Copilot responses by limiting them to user-selected sources, aligning with customer feedback for more transparent and customizable AI interactions.

This message is associated with Microsoft 365 Roadmap ID 496596

Rollout Schedule

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

Impact on Your Organization

• Who is affected:
  • Users with a Microsoft 365 Copilot license.
• What will happen:
  • Users will see a new option to select content sources when using Copilot Chat.
  • Copilot responses will be scoped only to the selected sources, improving control and precision.
  • This feature will follow a standard rollout and is enabled by default.
  • There is no impact to admin settings or policies.
  • No changes to existing Copilot behavior unless users actively select sources.

Action Required/Recommendations

• No admin action is required.
• This feature does not impact admin controls or require configuration.
• We recommend:
  • Informing helpdesk staff of this new user-facing capability.
  • Updating internal documentation if you provide guidance on Copilot usage.

Compliance Considerations

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

Updated May 26, 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 mid-July 2026 (previously mid-June) and expected to complete in late July 2026 (previously late June).
• General Availability: Rolling out in late July 2026 (previously late June) and expected to complete by late August 2026 (previously late July).

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

[Introduction]

We’re updating how entities inserted from Add Work Content under the + menu behave in Microsoft 365 Copilot and Copilot Chat. With this change, entity names (such as document titles, people names, or other referenced objects) will no longer be inserted as text within the input box, making it easier for users to craft clean prompts without needing to manually delete entity labels. This feature is available to both users with a Microsoft 365 Copilot license (Microsoft 365 Copilot users) and users without a Microsoft 365 Copilot license (Copilot Chat users), but the experience varies.

This message is associated with Microsoft 365 Roadmap ID 552592.

[When this will happen]

General Availability (Worldwide): Rollout begins in late May 2026 (previously mid-May) and completes early June 2026 (previously end of May).

[How this will affect your organization]

Who is affected: All users with access to Microsoft 365 Copilot and Copilot Chat in commercial (non-government) clouds.

What will happen:

• When users insert entities through Add Work Content (+):
  • The entity pill will appear in context, but the entity name will no longer be inserted as text in the chat input box:

     

• This change creates a cleaner prompt-building experience by removing extraneous text.
• No admin controls are changing.
• This update is enabled by default for all tenants.

[What you can do to prepare]

No action is required.

Optional steps include:

• Informing helpdesk or training teams about the change.
• Updating internal documentation that references entity insertion behavior in Copilot or Copilot Chat.

Learn more: Using Context IQ to refer to specific files, people, and more in Microsoft 365 Copilot and Copilot Chat | Microsoft Support

[Compliance considerations]

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

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

[Introduction]

Adaptive scopes for SharePoint DLP policies in Microsoft Purview enable you to target SharePoint sites based on site attributes instead of manually maintaining static site lists. As sites are created or updated, adaptive scopes automatically adjust membership, ensuring that DLP policies remain aligned to your environment without ongoing manual updates.

This message is associated with Microsoft 365 Roadmap ID 549288.

[When this will happen]

• Public Preview: We began rollout in early February 2026 and expect to complete by late‑February 2026.
• General Availability (Worldwide): We will begin rollout in late August 2026 (previously early June) and expect to complete by late September 2026 (previously end of June).

[How this will affect your organization]

Who is affected: Admins who manage Data Loss Prevention (DLP) policies for SharePoint in Microsoft Purview.

What will happen:

With adaptive scopes for SharePoint, your organization will –

• Apply DLP policies more efficiently and at scale.
• Automatically target the correct SharePoint sites based on attributes such as URL, name, or metadata.
• Ensure new or updated sites are protected without manual list maintenance.
• Reduce administrative overhead by removing the need to maintain static site lists.
• Maintain consistent DLP policy coverage as your SharePoint environment grows and changes.

Additional notes:

• There is no impact to user workflows.
• The feature is not enabled by default; admins must create and assign adaptive scopes.

[What you can do to prepare]

To prepare for this update, you can:

• Verify licensing and permissions.
• Ensure your tenant has Microsoft 365 E5 or E5 Compliance licensing and that you hold the required Purview roles.
• Learn more: Configure adaptive scopes – Adaptive Scopes | Microsoft Purview | Microsoft Learn
• Navigate to Adaptive scopes.
• Go to Microsoft Purview compliance portal → Settings → Roles & scopes → Adaptive scopes (screenshot 1):

  

• Create an adaptive scope.
• Select + Create scope.
• Provide a name and description.
• Choose SharePoint sites as the scope type (screenshot 2):

  

• Define the scope criteria.
• Use the query builder to set rules based on SharePoint site attributes such as:
  • Site URL
  • Site name
  • Custom metadata
• Review and create the scope.
• Confirm your criteria and create the scope. The system evaluates and updates scope membership automatically.
• Verify scope membership.
• Review included sites using the Adaptive scopes details pane (screenshot 3):

  

• Apply the scope to a DLP policy.
• When creating or editing a SharePoint DLP policy, select your adaptive scope (screenshots 4 and 5):

  

  .

  

• Allow time for periodic evaluation.
• Changes to adaptive scopes may take time to reflect across applied policies.

[Compliance considerations]

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

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

[Introduction]

Recap without saving transcript provides an alternative now for Copilot users to generate a meeting summary using live meeting context, in case where saving a meeting transcript or recording is not preferred or allowed.

This capability is intended for scenarios where organizations want AI‑generated recaps but have policies that limit or prohibit the retention of transcripts or recordings. When disabled, no AI recap is generated. Existing Copilot licensing and tenant‑level AI controls continue to apply.

This feature will be available to users with an M365 Copilot (Premium) license across platforms, including desktop (Windows and Mac), web, and mobile.

This message is associated with Microsoft 365 Roadmap ID 558286.

[When this will happen:]

• Targeted Release: We will begin rolling out early July 2026 (previously early June) and expect to complete by mid-July 2026 (previously mid-June).
• General Availability (Worldwide): We will begin rolling out late July 2026 (previously mid-June) and expect to complete by mid-August 2026 (previously late June).

[How this affects your organization:]

Who is affected:

• Microsoft Teams meeting organizers and participants with an M365 Copilot (Premium) license
• Microsoft 365 administrators managing Copilot and AI controls

What will happen:

• Teams admin center – Tenant admins will have control to opt in or out for AI features (e.g. Copilot, Intelligent Recap) for the meeting under the tenant. This feature is controlled by AI toggle/setting in the admin center. If AI is disabled at the tenant level, this experience is not available.
• Meeting options (before meeting) – Meeting organizers with a Copilot license can enable or disable Recap without saving transcript in meeting options under Copilot and other AI before the meeting
• In-Meeting controls (during meeting) – Meeting organizers with a Copilot license can enable or disable Recap without saving transcript anytime during the meeting via the AI toggle (appears at top-left). Participants can see whether AI is being turned on/off, while participants cannot change this setting.
• Post-meeting AI summary – When enabled, Intelligent Recap will generate an AI summary even if recording and transcription are not turned on. Meeting attendees with Copilot license can view the AI summary after the meeting. No transcript or recording is saved as part of this experience.
• Storage – When enabled, a doc will be stored in organizer’s OneDrive for default 120days, and it will be configurable in admin center for longer/shorter days as needed.
• Deletion – For post-meeting AI summary, organizer can choose to delete the content from the Recap page, and it will result in the deletion of the doc in organizer’s OneDrive, and vice versa.

[What you can do to prepare:]

• Review your organization’s AI and Copilot governance policies to determine whether this experience aligns with your compliance posture.
• If you want to opt out, disable the AI toggle in your tenant settings to prevent Recap without saving transcript from being used.
• Update internal guidance and helpdesk documentation to reflect that meeting recaps may be generated without recordings or transcripts.
• Communicate this change to meeting organizers, especially in regulated environments.

[Compliance considerations:]

• Building new KPIs using an intuitive formula editor that supports calculations based on case attributes, event data, timestamps, and existing metrics.
• Modify, refine, or delete custom metrics as business needs evolve, with changes automatically reflected across all visualizations using those metrics.
• Integrate custom KPIs seamlessly into all process intelligence experience tiles and components, and display them in process maps, trend charts, statistical breakdowns, and comparative analyses just like standard metrics.
• Define metrics that reflect your unique business context, such as weighted performance scores, custom cost calculations, compliance rates, or domain-specific efficiency ratios.
• Reuse custom KPIs throughout the process intelligence experience, applying them to filters and analysis scenarios. Custom metrics are evaluated dynamically against your process data, ensuring calculations remain current with each data refresh and providing consistent measurement across your process intelligence environment.

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

[Introduction]

Microsoft Teams is introducing support for displaying digital signage on idle Teams panel devices. This capability extends existing digital signage scenarios already available on Teams Rooms front-of-room displays, helping organizations deliver consistent branding and communications across shared spaces.

Admins can configure digital signage at both the tenant-wide and device-specific level through the Teams Rooms Pro Management portal. This feature supports select third-party providers such as Appspace and XOGO, and is available with Teams Rooms Pro or Teams Shared Spaces licenses.

This message is associated with Microsoft 365 Roadmap ID 558852.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• Admins managing Microsoft Teams Rooms and Teams panels
• Organizations using or planning to use digital signage in shared spaces
• Environments with Teams Rooms Pro or Teams Shared Spaces licenses

What will happen:

• Teams panels can support digital signage when idle.

Screenshot 1: Example of digital signage on a Teams panel:



• Admins can configure signage per device or device group. They can also configure default signage settings for the tenant.
• Configuration will be available in Teams Rooms Pro Management portal > Settings > Digital signage.

Screenshot 2: Example settings for configuring a digital signage source for Teams Panels specifically:



• Supported 3rd party providers include Appspace and XOGO.
• Available with Teams Rooms Pro or Teams Shared Spaces licenses.
• Feature is available by default for admins to configure.
• No user impact unless enabled.

[What you can do to prepare:]

No immediate action is required before rollout.

• Review your current digital signage strategy for Teams Rooms and shared spaces.
• Plan content optimized for Teams panels:
  • Recommended resolution: 1280 × 800
• Use separate digital signage sources for Teams panels and front-of-room displays:
  • Teams panels have smaller displays than front-of-room screens.
  • Content designed for larger displays may not render well on panels.
• Configure signage settings when available:
  • Navigate to Teams Rooms Pro Management portal > Settings > Digital signage.
• Consider using separate signage content sources for:
  • Front-of-room displays, and
  • Teams panels (due to smaller screen size).
• To set up a digital signage source specifically for Teams panels, when assigning a signage source to devices, choose the Teams panels only option on the preference setting Show signage on Teams panels.
• Validate compatibility with supported partners (for example, Appspace or XOGO).
• Notify facilities or communications teams responsible for signage.

Learn more: Configure digital signage on Teams Rooms | Microsoft Learn (will be updated before rollout)

[Compliance considerations:]

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

[Introduction]

To improve discoverability and customization of keyboard shortcuts in Microsoft Teams, we’re adding search functionality to the Keyboard shortcuts dialog. This enhancement helps users quickly find shortcuts by either the action name or the key combination, reducing time spent scanning long lists and making shortcut customization easier and more efficient.

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

[When this will happen:]

• Targeted Release (Worldwide): We will begin rolling out in early June 2026 and expect to complete by early June 2026.
• General Availability (Worldwide): We will begin rolling out in early June 2026 and expect to complete by late June 2026 (previously early July).

[How this affects your organization:]

Who is affected:

• All Microsoft Teams users who access the Keyboard shortcuts dialog.

What will happen:

• Users can search for keyboard shortcuts by:
  • The name of the action (for example, “Mute” or “Open settings”).
  • The keyboard shortcut combination (for example, “Ctrl+Shift+M”).
• The enhancement applies to:
  • Viewing existing shortcuts.
  • Customizing personal keyboard shortcuts.
• The feature is enabled by default.
• Existing Teams policies and admin configurations are respected.
• No changes to user workflows unless users choose to search or customize shortcuts.

Screenshot 1: Default keyboard shortcut dialog experience:



Screenshot 2: Use the search box in the upper-right corner to enter a keyword and find relevant keyboard shortcuts:

[What you can do to prepare:]

• No action is required.
• Consider the following optional steps:
  • Inform helpdesk and support teams about the improved shortcut discovery experience.
  • Update internal user training or documentation that references Teams keyboard shortcuts.
  • Share a short tip with users highlighting that shortcuts can now be searched by name or key combination.

[Compliance considerations:]

The change allows users to choose whether to use the new search capability within the Keyboard shortcuts dialog. No other compliance impacts have been identified.

[What and Why]

We are introducing Infographics in Microsoft Copilot Notebooks, a new capability that enables users to transform notebook content into clear, structured visual summaries generated from grounded references. This feature improves clarity, reduces manual effort, and helps teams share insights faster. It supports personal and team productivity by enabling users to communicate complex ideas more effectively within their existing workflow.

[Rollout Schedule]

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

[Impact on Your Organization]

Who is affected

Users with access to Microsoft Copilot Notebooks in Microsoft 365 tenants

Platforms/Services

Microsoft Copilot Notebooks in Microsoft 365 apps (web)

What will happen

• Users can generate infographics directly from notebook content.
• Infographics are created using grounded references in the notebook.
• Users can preview generated infographics.
• Users can copy or download infographics for reuse.
• Generated infographics are automatically saved within the notebook.
• The feature is enabled by default for eligible users.
• Existing Microsoft 365 and Copilot admin policies are respected.
• This is an additive capability and does not disrupt existing workflows.

[Action Required/Recommendations]

No action is required.

Recommended:

• Inform users about this new capability.
• Update internal documentation if you reference Copilot Notebooks.
• Review existing Copilot policies to ensure alignment with your organization’s requirements.

[Compliance considerations]

[What and Why]

Microsoft Teams will introduce a new in-meeting toggle that allows licensed meeting organizers and presenters to turn Meeting AI (including Copilot, Facilitator, and meeting recap) on or off during a live meeting. This change builds on existing Meeting AI behavior and provides real-time flexibility to control when AI is active.

Licensed organizers and presenters can capture insights when discussions are valuable and turn off AI when conversations shift to sensitive topics. The toggle respects existing tenant policies and compliance controls.

This message is associated with Microsoft 365 Roadmap ID 558286.

• Targeted Release: Early June 2026 – Mid-June 2026
• General Availability (Worldwide): Mid-June 2026 – End of June 2026

Who is affected

• All Microsoft 365 tenants with Meeting AI (Copilot and/or Facilitator) enabled by policy and in Meeting Options
• Licensed organizers and presenters in Teams Meetings

• Microsoft Teams (Desktop, Web, and Mobile)
• Microsoft 365 Copilot (Meeting AI, Facilitator, recap)

• A new Meeting AI toggle will appear in the Teams meeting toolbar: 

  

• Licensed organizers and presenters can turn Meeting AI on or off during meetings: 

  

• Toggles are shown only when Meeting AI is allowed by policy.
• An AI status indicator will show participants whether Meeting AI is active.

Existing tenant policies and meeting options are respected:

• If Meeting AI is disabled by policy, the toggles will not appear.

When Meeting AI is turned off:

• Copilot, Facilitator responses, and Notes will no longer be generated.
• Previously generated artifacts remain available and governed by retention policies.
• If AI is used without transcription, speech-to-text data stops and Recap is not generated.

Important: Transcription Dependency

• When AI is used with transcription, they remain coupled:
• Turning on Meeting AI automatically turns on transcription and generates a recap.
• Starting transcription automatically enables Meeting AI and recap.
• To prevent Meeting AI usage, transcription and Meeting AI must remain off.

• Meeting options configured before meetings
• Recording, transcription, and sensitivity labels behavior
• Retention and compliance policies
• Licensing requirements for Copilot and Meeting AI

No action is required for this rollout.

Recommended actions:

• Update internal training and documentation to explain:
• Where the Meeting AI toggle appears
• Who can use the toggle (licensed organizers and presenters)
• Communicate to end users:
• Starting transcription automatically enables Meeting AI and recap
• Meetings that must avoid AI should not use transcription
• Prepare helpdesk teams to support user questions about:
• Controlling Meeting AI during meetings
• Understanding transcription-related behavior

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

• Shared audio enables two people to listen to the same audio from a single Windows 11 PC at the same time.
• Task Manager now provides enhanced visibility into NPU usage, including new metrics and AI activity insights.
• Multi‑App Camera allows multiple apps to access the camera simultaneously. Basic Camera mode enables simplified camera functionality, useful for troubleshooting when your camera is not working correctly
• You can now choose a custom name for your user folder on the Device Name page during Windows setup. User folder names must follow standard Windows naming requirements.

What and Why

The June 2026 Windows security update will be released as a hotpatch baseline update rather than a standard hotpatch update. This baseline refresh is required periodically to maintain the trusted foundation that enables future hotpatch updates to install without requiring device restarts.

Rollout Schedule

This change applies to the June 2026 Windows security update.

Impact on Your Organization

Who is affected:

• Organizations with Windows devices enrolled in hotpatch updates

Platforms / Services:

• Windows
• Windows Update
• Hotpatch-enabled devices

What will happen:

• Hotpatch-enabled devices will receive the June 2026 security update through the standard Windows Update servicing process.
• A device restart will be required to complete installation.
• After installation and restart, the update will appear in update history and compliance reporting as usual.
• Devices remain enrolled in hotpatch, and the next restart-free hotpatch update is expected in August 2026.

Devices not enrolled in hotpatch and devices using standard Windows updates are not affected.

Action Required / Recommendations

• Ensure update deployment policies remain in place.
• Plan for and communicate the one-time restart requirement.
• No additional configuration changes are required.

Additional information

Hotpatch updates overview

Compliance considerations

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