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

Updated May 11, 2026: We have decided not to move forward with this change at this time. We apologize for any inconvenience.

Introduction

We’re updating the default behavior of Microsoft Teams Copilot in meetings. Copilot without transcription will become the default mode for newly scheduled Teams meetings where Copilot is allowed. Additionally, conversation history will now persist during meetings, improving multitasking and continuity of insights.

This update is associated with Microsoft 365 Roadmap ID 478611.

When this will happen

General Availability (Worldwide): We have decided not to move forward with this change at this time. 

[What’s changing?]

Who is affected:

• Affected tenants: If your TeamsMeetingPolicy was created or modified before the Copilot without transcription policy option was introduced (June 2024), your tenant will be affected by this change.
• Not Affected: If your TeamsMeetingPolicy was created or modified after June 2024 when the Copilot without transcription option was introduced, your tenant will not be affected.

What will happen:

• The default Copilot policy will change from EnabledWithTranscript to Enabled for both new and existing Teams meetings where Copilot is allowed.
• Copilot and Facilitator will no longer automatically start transcription for meetings in affected tenants.
• Users must manually enable transcription to use post-meeting Copilot or Facilitator queries.
• Conversation history will persist during meetings for Copilot without transcription.
• Tenants with TeamsMeetingPolicy created or modified after June 2024 are not affected.

If adopting the new defaults:

• Review TeamsMeetingPolicy for transcription dependencies.
• Update internal documentation and training.
• Communicate to users how to enable transcription when needed.

Optional admin steps to retain current behavior:

• Update Global and Custom TeamsMeetingPolicy settings via TAC or PowerShell.
• TAC UI Portal: Navigate to Teams Admin Center and set the Copilot policy default value as required. For example, if the current default value is desired, update it to a different value, then set it back. Please ensure both TeamsMeetingPolicy and all Custom Policies are updated.
• PowerShell example to set Copilot policy to EnabledWithTranscript for all relevant meeting policies:

  get-csteamsmeetingpolicy | ? {
    $_.Identity -ne "Tag:AllOn" -and
    $_.Identity -ne "Tag:AllOff" -and
    $_.Identity -ne "Tag:Default" -and
    $_.Identity -ne "Tag:Kiosk" -and
    $_.Identity -ne "Tag:RestrictedAnonymousAccess" -and
    $_.Identity -ne "Tag:RestrictedAnonymousNoRecording"
  } | % {
    $_.Identity;
    set-csteamsmeetingpolicy -identity $_.Identity -Copilot EnabledWithTranscript
  }
      

Learn more: 

• Manage Microsoft 365 Copilot in Teams meetings and events | Microsoft Teams | Microsoft Learn
• Use Copilot without recording a Teams meeting | Copilot in Teams | Copilot | Microsoft Support

Compliance considerations

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

Introduction

We’re introducing enhancements to OneDrive that simplify the process of managing files when employees leave your organization. These updates improve visibility, streamline bulk transfers, and help ensure important content remains accessible and shared appropriately.

This feature is associated with Microsoft 365 Roadmap ID 493946.

When this will happen

General Availability (Worldwide, GCC, GCCH, DoD): We will begin rolling out in mid-October 2025 and expect to complete by end of May 2026 (previously early May).

How this affects your organization

Managing OneDrive content for departing employees is now more efficient. Key improvements include:

• Redesigned notifications: Account cleanup emails are now more prominent, reducing the chance of being overlooked.
• Improved filtering: New filters help managers quickly locate shared or important files.
• Bulk file transfer with preserved sharing: The “Move and keep sharing” feature allows multiple files to be transferred while retaining existing sharing permissions.
• Consolidated alerts: When six or more files are moved, collaborators receive a single streamlined notification.

These updates help ensure a smooth handover and reduce the risk of losing critical files.

When a user account is deleted, OneDrive access is automatically granted to the manager or designated secondary owner. The recipient receives an email notification with access details and information about the OneDrive retention period. Seven days before the retention period ends, a second reminder email is sent, stating that the OneDrive will be permanently deleted in seven days.

Steps to transfer files:

1. From the email, click View files to access the departing user’s OneDrive.
   
2. Use the Shared filter to view only shared files, or All to see everything.
3. Select files using the checkbox in the table header.
   
4. Click Move to, choose a destination, and check Keep sharing with the same people.



5. Click Move to again to complete the transfer.

Collaborators will receive a single notification once the move is complete:

What you can do to prepare

No admin action is required before rollout. You may want to:

• Inform managers and secondary owners about the new experience.
• Update internal documentation to reflect the new transfer process.
• Watch this guided walkthrough: Simplified file transfer for departing employees

Learn more: OneDrive retention and deletion – SharePoint in Microsoft 365 | Microsoft Learn

Compliance considerations

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

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

[Introduction]

To enhance wireless content sharing in meeting spaces, Microsoft Teams Rooms on Windows devices will soon support Miracast. This complements existing options like Teams Cast and HDMI ingest and is available for devices including touch boards. This feature is exclusive to Teams Rooms Pro.

This message is associated with Roadmap ID 506748.

• Targeted release: We will begin rolling out in mid-May 2026 (previously early May) and expect to complete by mid-May 2026 (previously end of March).
• General Availability: We will begin rolling out mid-May 2026 (previously end of March) and expect to complete by late May 2026 (previously mid-April).

Who is affected: Admins managing Teams Rooms on Windows devices with Teams Rooms Pro licenses.

What will happen:

• Miracast will be available as a wireless sharing option in Teams Rooms on Windows.
• The feature will be OFF by default and can be enabled via a tenant-wide toggle in the IT admin portal.
• Laptop devices must support Miracast to use this feature.
• No impact to end-user workflow unless enabled by admin.

• Review your Teams Rooms device compatibility with Miracast.
• Enable the feature via the IT admin portal if desired.
• Communicate the availability of Miracast to helpdesk and meeting room support staff.
• Update internal documentation to reflect the new sharing option.

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

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

[Introduction]

We’re updating the Copilot experience in Microsoft 365 apps with simplified entry points for easier discovery and connection to Copilot in the context of working inside of Word, Excel, PowerPoint. In addition to the simplified UI outlined below, users will also see curated suggestions designed to help them get started with Copilot to edit their documents.

We’re reducing the number of entry points to Copilot in Word, Excel and PowerPoint so Copilot feels consistent, predictable and integrated with in-app workflows.

The new UI includes:

• A Copilot Dynamic Action Button (DAB) at the bottom-right corner of the screen replacing the static button in the ribbon.
  • This is an always-available, in-app Copilot primary entry point.
  • The button allows a user to “dock” or move it to the side when they want to focus on the content.
  • A user can right-click the Copilot button and select Dock or drag the icon to dock to the right of the content (or left of content for right-to-left locales). To re-engage with Copilot, a user simply clicks the smaller icon or drag it back to the canvas.
• A contextual entry point on the canvas appears when a user selects text or takes action on canvas with Copilot.
• Suggested User Actions (SUAs) show on hover from the Copilot Dynamic Action Button to offer contextual prompts that help a user know how to engage with Copilot.
• Keyboard and screen reader access: The ability for to work with Copilot in Microsoft 365 apps when using a keyboard and screen readers has also been simplified.
  • For users who have been using Alt + H, F, X to open the Copilot pane in Word, Excel and PowerPoint, they can now press F6 to give focus to the Copilot button and then use the up arrow to move between suggested prompts.
  • Over time, Copilot keyboard shortcuts are being unified across Microsoft 365 apps and platforms, bringing consistency and supporting keyboard-first users and anyone using a screen reader.
  • The updated shortcuts listed below are already available in Outlook and Word (Windows and Mac), with other apps coming soon.

[When this will happen:]

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

• Word, Excel, PowerPoint (Web, Desktop, Mobile): rollout started for small % of users with a Microsoft 365 Copilot license and pinning enabled. These users will see the entry point for Copilot move out of the ribbon, represented by the icon pictured below.
• We will continue the rollout progressively for users with a Microsoft 365 Copilot license.

Who is affected:

• Microsoft 365 users of Word, Excel, and PowerPoint across web, desktop, and mobile who are eligible for Microsoft 365 Copilot.

What will happen:

• The Copilot entry point will move from the app ribbon into the document canvas. Users will see a new button in the canvas to open Copilot.
• Contextual prompt suggestions will appear to help users engage with Copilot.
• The feature remains ON by default for eligible users across web, mobile, and desktop.
• Admins can still disable Copilot using the “Pin Microsoft 365 Copilot Chat” setting in the admin center.
• No changes to Copilot functionality or value.
  

  

• No admin action is required.
• If your “Pin Microsoft 365 Copilot Chat” setting is configured to “Do not pin,” update it to “Pin” if you want users without a Copilot license to access Copilot Chat in Microsoft 365 apps.
• Learn more:
  • Manage Microsoft 365 Copilot Chat.
  • Pin Microsoft 365 Copilot Chat in the Microsoft 365 apps

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

• Quality Evaluation Agent
• Case Management Agent
• Customer Intent Agent

[Introduction]

To support more effective in-person collaboration, Microsoft Teams is expanding AI-powered meeting notes with the Facilitator agent to Teams Rooms on Windows. This enhancement allows teams meeting in a physical room to capture real-time notes, decisions, and action items—without requiring a scheduled or hybrid meeting. The experience is designed to ensure notes are securely stored in your tenant while no data remains on the room device after the meeting ends.

This feature is associated with Microsoft 365 Roadmap ID 560318.

[When this will happen]

General Availability

• Worldwide and GCC: We will begin rolling out in late June 2026 and expect to complete by mid-July 2026.
• GCC-H: We will begin rolling out in mid-July 2026 and expect to complete by mid-August 2026.
• DoD: We will begin rolling out in mid-August 2026 and expect to complete by early September 2026.

[How this affects your organization]

Who is affected

• Organizations using Teams Rooms on Windows
• Rooms licensed with Teams Rooms Pro

What will happen

• During an in-person meeting, users can start AI-powered notes by selecting the Take notes button on the Teams Rooms console.
• Notes appear on the front-of-room display or touch board during the meeting: 

  

• Notes are stored in tenant-owned SharePoint embedded storage.

• Access to notes requires adding your work account using the Access notes button on the Teams Rooms console: 

  

• After the meeting, notes can be viewed and edited by participants with access via the meeting recap in the meeting chat on the Teams desktop client.:
• If no participant was added during the note-taking session via Access notes, notes are deleted automatically.

Default state:

• The feature is available automatically once licensing and prerequisite configurations are met.
• No additional admin enablement is required beyond existing settings.

[What you can do to prepare]

No immediate action is required if your organization already meets the prerequisites.

To prepare:

• Confirm Teams Rooms Pro licenses are assigned to applicable rooms.
• Ensure Facilitator is enabled in your tenant.

• Verify Loop components are enabled:
  • IsLoopEnabled
  • IsCollabMeetingNotesFluidEnabled
• Ensure meeting transcription is enabled in Teams meeting policies.
• Consider notifying helpdesk staff and users about:
  • How to start notes in an in-person meeting
  • Where notes are stored and accessed after the meeting

Learn more:

• Allow Facilitator in the Teams admin center – Set up Facilitator in Microsoft Teams | Microsoft Teams | Microsoft Learn
• Meetings – Admins- Manage transcription and captions for Teams meetings | Microsoft Teams | Microsoft Learn
• Settings management for Loop functionality in Teams – Admin policies for Loop components and Loop workspaces | Microsoft 365 | Microsoft Learn

[Compliance considerations]

• update.microsoft.com 
• sls.update.microsoft.com 
• tas02.sls.update.microsoft.com 

• Configuring firewall and proxies for smooth Windows updates
• Windows Update security 
• Transport Layer Security protocol 
• Connection endpoints for Windows 11 Enterprise 
• Scan changes and certificates add security for Windows devices using WSUS for updates 

Updated May 11, 2026: We have decided not to move forward with this change at this time. We apologize for the inconvenience.

View and monitor Loop usage in the tenant through existing Microsoft 365 admin usage dashboards.

This message is associated with Microsoft 365 Roadmap ID 421611.

[When this will happen:]

General Availability (Worldwide): We have decided not to move forward with this change at this time. 

[How this will affect your organization:]

Once available, administrators can view and monitor Loop usage in the tenant through the existing Microsoft 365 admin usage dashboards.

[What you need to do to prepare:]

There is nothing you need to do to prepare. These changes will roll to your tenant automatically.

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

[Introduction]
A new organization-level Cloud Policy setting (OCPS) is available, allowing admins to block creation of tenant-owned Loop workspaces. When this setting is on, the “New workspace” ability in the Loop app will be unavailable. The only valid option for creating workspaces will be through standard channels in Teams, as these are connected to and managed by existing Microsoft 365 Groups. For more information about creating workspaces in Teams standard channels, visit Loop Workspaces in Teams Channels – Microsoft Support.

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 late April 2026 (previously early April) and expect to complete by early May 2026 (previously late April). 

[How this will affect your organization:]

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. Workspace creation must be initiated from the Loop app within standard Teams channels.

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.