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

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

Applies to: Teams for Windows desktop and Teams for Mac desktop 

[Introduction:]

All meeting participants joining from native apps on Windows and macOS will be able to request to start collaborative annotations when a screen or window is being shared. The annotations start only after the active sharer approves the request. This capability is available exclusively in the new Microsoft Teams experience on native Windows and macOS apps.

This release also introduces a meeting option in the Participation section, allowing organizers and co-organizers to choose who can start annotations. By default, “Everyone” can access the “Start Annotation” button, but organizers and co-organizers can limit it to just the “Active Sharer”, making the button visible only to the person currently sharing their screen or window.

Note: Users can view and annotate in Teams on the web but cannot initiate annotations. Anonymous users in the meeting will not be able to send a request.

This message is associated with Microsoft 365 Roadmap ID 89975.

[When this will happen:]

Targeted Release: We will begin rolling out early May 2026 (previously mid-April) and expect to complete by mid-May 2026 (previously late April).

General Availability (WW, GCC, GCC High, and DoD): We will begin rolling out mid-May 2026 (previously late March) and expect to complete by late May 2026 (previously late April).

[How this will affect your organization:]

After the rollout, meeting participants who are not sharing their screens will have the ability to request an annotation session. This request will be sent to the presenter sharing their screen, who can choose to accept or deny it.

Meeting Organizer Settings (Meeting Options)

A new “Who can start annotations?” option appears under the Participation section in Meeting Options. Organizers and co-organizers can select:

• Everyone (default) — All participants see the “Start Annotation” button
• Active Sharer — Only the person currently sharing sees the annotation button

After rollout, the default value of Everyone will apply to all newly created meetings. For meetings created before rollout, the setting will be Active Sharer to match the current behavior where only the active sharer can start annotations. Organizers and co-organizers must manually update existing meetings if they want to enable the new behavior for those meetings. 

Participant Annotation Request Flow 

When a participant who is not the active sharer wants to annotate, they click the “Start annotation” button in the meeting toolbar. A confirmation dialog appears, and once the participant clicks “Request”, a notification is sent to the presenter for approval.

1. Click the “Start annotation” button in the meeting toolbar to initiate an annotation request.



2. Confirm the request in the dialog box. Once approved, annotations start request will be sent to active sharer



3. Request sent notification confirms the request is pending and the presenter needs to approve it. 

Presenter Approval Experience

The active sharer (presenter) receives a notification at the top of their screen indicating that a viewer wants to start annotations. The presenter can choose to Deny or Allow the request.

[What you need to do to prepare:]

This rollout will happen automatically by the specified dates with no admin action required before the rollout. You may want to:

• Notify your users about this change and how the annotation request/approval flow works 
• Update relevant documentation to reflect the new meeting option and participant behavior 
• Educate meeting organizers on the new “Who can start annotations?” meeting option under Participation 
• Communicate to end users that they can now request to start annotations during screen sharing sessions 

This change will be available by default. 

Additional Resources: 

• Use annotation while sharing your screen in Microsoft Teams – Microsoft Support (will be updated before rollout)
• How to use Collaborative Annotations in a Microsoft Teams meeting (2022)
• Microsoft 365 Roadmap ID 89975

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

 We’re adding new peripheral health reporting capabilities to the Pro Management portal, enabling admins to proactively monitor device issues in bring your own device (BYOD) rooms and desks.

These reports help identify when peripherals are faulty, missing, moved, or undetectable by a PC—allowing admins to take action before users report problems. Reports for rooms require a Teams Shared Devices license. Desk reporting is currently in public preview.

This change is associated with Microsoft 365 Roadmap ID: 493319

[When this will happen:]

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

[How this affects your organization:]

Admins can now use peripheral status data to detect hardware issues in BYOD rooms and desks before they impact users. This proactive monitoring can reduce support tickets and improve meeting space reliability.

• Reports for rooms require a Teams Shared Devices license.
• Reports for desks are available in public preview and do not yet require a license.

[What you can do to prepare:]

To ensure accurate peripheral status reporting:

• Use multiple peripherals in each room or desk setup. The system compares expected device pairings (e.g., if Peripheral A and B are usually connected together, but A is missing, it will be flagged).
• Simplify connectivity for users by using a single cable solution to connect all peripherals.
• Ensure rooms and desks are bookable and have associated peripherals—this enables the Teams desktop client to send the necessary telemetry. Peripheral association can be done manually or automatically.

[Compliance considerations:]

• Does the change alter how existing customer data is processed, stored, or accessed? Maybe (device telemetry is used for reporting)

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

[Introduction]

Stay on top of your inbox with the new Microsoft 365 Copilot voice experience in the Outlook mobile app—simply open Copilot, tap Voice, and manage your messages through a natural, conversational flow. Ask Copilot to summarize your recent unread emails and then take action like flagging, pinning, archiving, or marking as read—all without the hassle of navigating your inbox by hand. You can interrupt or redirect Copilot at any point in the conversation:

• Read an email thread from start to finish or provide a more detailed summary
• Ask follow-up questions
• Take a triage action for a specific email – flagging, pinning, archiving, or marking as read

The end result

A new way to manage your Outlook mobile inbox that is conversational, hands-free, and convenient for working on-the-go, and more accessible than ever.

[When this will happen:]

• Public Preview (Worldwide): Rollout begins in mid-November 2025 and completes by early February 2026.
• General Availability (Worldwide): Rollout begins in late April 2026 and is expected to complete by end of May 2026.

[How this affects your organization:]

• Who is affected:
  • All users of the Outlook mobile app on iOS and Android with Microsoft 365 Copilot enabled.
  • A Microsoft 365 Copilot license is required to use this feature.
• What will happen:
  • Copilot voice can summarize recent unread emails and offer actions such as flagging, pinning, archiving, or marking as read.
  • Users can interrupt or redirect Copilot at any time to ask follow-up questions, read full threads, or take triage actions.
  • The experience is conversational and hands-free, enhancing accessibility and productivity.
• Key benefits:
  • Helps users stay on top of their inboxes while they’re on-the-go (hands-free, using headphones, on a walk, in between meetings, and beyond)
  • Enables a more accessible Outlook mobile experience
  • Natural, conversational flow – feels as though you’re triaging your inbox live with support from a helpful human

[What you can do to prepare:]

• Ensure users update to the latest version of Outlook mobile on iOS and Android.
• Communicate this change to helpdesk and support teams.
• Update internal documentation if you provide guidance on Outlook mobile or Copilot usage.
• No admin configuration is required; feature will be available by default for eligible users.
  

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

[Introduction]

Voice tethering builds on the recent introduction of Sign Language Mode in Microsoft Teams. When a sign language interpreter voices on behalf of a Deaf or hard‑of‑hearing (D/HH) participant, Teams will now attribute captions, transcripts, and meeting intelligence—such as Copilot notes, summaries, action items, and insights—to the D/HH participant rather than the interpreter. This update ensures accurate representation in meetings, clarifies who is contributing to the conversation, and improves downstream meeting accuracy and accountability.

This message is associated with Microsoft 365 Roadmap ID 553223.

[When this will happen]

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

[How this affects your organization]

Who is affected

• Organizations with meeting participants who are Deaf or hard‑of‑hearing and use sign language interpreters in Teams meetings.
• Any users who participate in meetings with Sign Language Mode enabled.

What will happen

• Voice contributions made by interpreters will be attributed to the D/HH participant across:
  
  • Live captions
  • Meeting transcripts
  • Copilot notes, summaries, action items, and insights
  • Other Teams meeting intelligence
• Meeting data becomes more accurate by ensuring the correct participant is represented.
• Interpreter identity is no longer conflated with the signer they support.
• Sign Language Mode is already available to all users; voice tethering enhances it automatically.
• The feature is on by default when sign language mode and interpreter assignment are used.
• No admin controls are required to enable or manage the feature.

[What you can do to prepare]

No action is required.

Optional preparation steps:

• Inform D/HH users and interpreters that speech attribution in meetings will change.
• Update internal training or accessibility resources if you document interpreter workflows.
• Notify helpdesk or support teams that captioning and transcript attribution will appear differently for interpreted meetings.

[Compliance considerations]

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

Updated April 29, 2026: We have updated the content. Thank you for your patience. 

[Introduction]

We’re expanding model choice in Microsoft 365 Copilot with the addition of Anthropic Claude for users with a Microsoft 365 Copilot license. Claude Sonnet is available in Copilot Chat in Frontier, alongside the latest OpenAI models, giving users the flexibility to choose the model best suited for their tasks. This expansion reflects our commitment to delivering the latest AI innovation for work—while maintaining the security, compliance, and privacy standards customers expect from Microsoft.

[When this will happen:]

• Frontier availability: Claude is available now in Frontier.
• General availability (web/desktop/macOS/mobile): Rolling out gradually; expected completion early April 2026 (previously late March).

[How this affects your organization:]

Who is affected:

• Users with a Microsoft 365 Copilot license

Who is not affected:

• For Government and Sovereign clouds, Anthropic models are not available and will not be visible in the model selector
• For Tenants in EU/EFTA and the UK Anthropic is off by default and requires opt-in

What will happen:

• Microsoft 365 Copilot licensed users will be able to select Claude as an option in the model selector within Copilot Chat.
• In regions where Anthropic is configured as a subprocessor and is set to Off by default, admins can choose to opt in to make Anthropic models available for their organization.
• Enterprise Data Protection for Microsoft 365 Copilot continues to apply, with no changes to existing protections.
• Anthropic operates as a Microsoft subprocessor under the Microsoft Data Protection Addendum and Product Terms.
• Anthropic models are currently excluded from EU Data Boundary and in‑country processing commitments.

[What you can do to prepare:]

• No action is required. However, it’s recommended that you review internal guidance and communicate to users that availability.
• If your tenant is in a region where Anthropic is Off by default, review the subprocessor setting and opt in if you want Anthropic models available to users. Learn more: Anthropic as a subprocessor for Microsoft Online Services | Microsoft Learn
• Learn more about Anthropic as a Microsoft subprocessor: Anthropic as a subprocessor for Microsoft Online Services

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

[Introduction]

We’re adding new building‑level insights to the recommended actions page in the Teams Rooms Pro Management portal. This update helps IT admins identify buildings with high Microsoft Teams Rooms (MTR) utilization that still have bring-your-own-device (BYOD) rooms in them, creating an inconsistent user experience from room to room. These insights support more consistent meeting experiences across buildings and help organizations optimize room‑technology investments. Available with a Teams Rooms Pro or Shared Space license.

This message is associated with Microsoft 365 Roadmap ID 553591.

[When this will happen]

• General availability (Worldwide): We will begin rolling out early June 2026 (previously early May) and expect to complete by mid-June 2026 (previously late May).

[How this affects your organization]

Who is affected

• Organizations using the Teams Rooms Pro Management portal with Teams Rooms Pro or Shared Device licenses

What will happen

• A new building‑level insights view will appear on the portal’s Recommended actions page:

   

• Insights will highlight buildings with high MTR usage and remaining BYOD meeting rooms: 

  

• These insights are designed to help IT create more consistent room to room experiences for users within a building.
• No changes will occur to existing configurations, policies, or settings.
• The feature will be enabled by default for tenants with eligible licenses.

[What you can do to prepare]

No action is required.

If relevant to your organization’s deployment planning, you may:

• Review your current MTR and BYOD room distribution in the Teams Rooms Pro Management portal.
• Update internal documentation or planning guidance as needed.
• Share this update with teams responsible for meeting room technology decisions.

[Compliance considerations]

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

Updated April 29, 2026: We have updated the content. Thank you for your patience.

[Introduction]

We’re introducing new capabilities in Researcher to help teams review AI‑generated research more confidently and reduce rework before using outputs in business decisions.

Critique is a built-in review step in Researcher that automatically checks and improves a draft before it’s delivered. It uses a second reasoning pass to strengthen structure and completeness, prioritize reputable sources, and ensure key statements are grounded in clear citations—so the final report is more reliable and easier to trust.

Council is Researcher’s multi-model comparison mode. It runs the same question through multiple deep‑reasoning research agents (for example, GPT and Claude) in parallel, preserves each model’s full standalone report, and adds a lightweight synthesis “cover letter” that highlights where the models agree, where they diverge, and what each uniquely contributes—so you can compare perspectives and make decisions with higher confidence.

These preview features are initially available only to organizations enrolled in the Microsoft 365 Copilot Frontier program, which provides early access to experimental Copilot capabilities.

This message is associated with Roadmaps 553213 and 558538.

[When this will happen:]

Public preview: Rolling out to Frontier customers by March 30, 2026.

[How this affects your organization:]

Who is affected:

• Organizations enrolled in the Microsoft 365 Copilot Frontier program using Researcher
• Admins managing AI model access, including third-party models such as Anthropic Claude
• Users who generate long-form research reports using Researcher
• A Microsoft 365 Copilot (Premium) license is required to use this feature

What will happen:

• Researcher drafts will run through Critique before delivery, improving structure, completeness, and citation quality, when “Critique” is selected as the option in the model picker. 
• Users will be able to enable Council, which generates:
  • Two independent, full research reports from different reasoning models (for example, GPT and Claude).
  • A concise synthesis “cover letter” summarizing areas of agreement, disagreement, and unique contributions.
• Critique and Council availability is tenant-admin controlled, including the ability to allow or block third-party models such as Claude.
• There is no change to existing user workflows unless the feature is enabled.
• Existing security, compliance, and data handling policies continue to apply.

[What you can do to prepare:]

• Review your AI model access settings and confirm whether Anthropic Claude is enabled for your tenant.
• Decide whether to allow Critique and Council based on your organization’s governance and compliance requirements. There are no separate controls for these features; both are enabled when Anthropic and Claude report generation are turned on.
• Inform helpdesk and support teams about the upcoming preview features.
• Update internal guidance or training materials if Researcher is documented in your organization.

No action is required if you do not plan to enable the preview features.

Learn more: Use model choice in the Researcher agent | Microsoft Support

[Compliance considerations:]

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

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

[Introduction]

We’re improving the RSVP experience in Outlook Mobile by visually highlighting the response a user has selected (Yes, Maybe, or No). This makes it easier for users to quickly see how they’ve responded to a meeting invitation.

[When this will happen:]

General Availability (Worldwide, GCC, GCC High): Rollout begins in early June 2026 (previously late April) and is expected to complete by end of June 2026 (previously early June).

[How this affects your organization:]

Who is affected:

• All users who access Outlook Mobile on iOS or Android
• Applies to Worldwide, GCC, and GCC High tenants

What will happen:

• The selected RSVP option (Yes, Maybe, or No) will be visually highlighted



• Users can quickly confirm how they responded to a meeting invitation and edit as needed



• The feature is enabled by default
• No changes to existing meeting workflows or policies
• No impact to Outlook on the web or Outlook desktop clients

[What you can do to prepare:]

• No admin action is required; the update will roll out automatically
• Consider notifying helpdesk staff of the visual change
• Update internal documentation if needed

[Compliance considerations:]

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

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

[Introduction]

Recap without saving transcript provides an optional way for Copilot to generate a meeting summary using live meeting context, without saving a meeting transcript or recording.

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 June 2026 (previously mid-May) and expect to complete by mid-June 2026 (previously late May).
• General Availability (Worldwide): We will begin rolling out mid-June 2026 (previously early June) and expect to complete by late June 2026 (previously mid-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:

• 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, and organizers or participants with a Copilot license can manage the AI toggle during the meeting through the AI mode dropdown (top‑left indicator).
• During a meeting, organizers and participants with a Copilot license can enable or disable this option.
• When enabled, Intelligent Recap will generate an AI summary even if recording and transcription are not turned on.
• No transcript or recording is saved as part of this experience.
• This feature is controlled by the existing AI toggle. If AI is disabled at the tenant level, this experience is not available.
• The feature is on by default for tenants where Copilot and AI experiences are enabled.

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

Updated April 29, 2026: We have updated the content. Thank you for your patience. 

[Introduction]

Microsoft is introducing an automatic upgrade for shared calendars in Outlook and Exchange Online, transitioning from the legacy MAPI-based model to the modern REST-based model. This server-side upgrade will improve calendar sync reliability, performance, and consistency for delegates and users who access shared calendars. The change is designed to be seamless and will not require any action from users or administrators.

[When this will happen]

General Availability (Worldwide):

Rollout starting early May 2026 and completing by late July 2026

GCC High /DoD:

Rollout starting mid-May 2026 and completing by late July 2026

Note: Rollout will be progressive and timing may vary by tenant.

[How this affects your organization]

Who is affected

• Microsoft 365 tenants using Exchange Online
• Users who have Editor or higher permissions on shared calendars in user or shared mailboxes
• Delegates and users who access shared calendars in Outlook

What will happen

• Shared calendars will be automatically upgraded from the legacy MAPI-based model to the modern REST-based model.
• A new calendar folder will be created in a hidden state and will only become visible to the user once the full sync is successfully completed and validated, ensuring a seamless rollover to the new model.
• The transition is expected to appear seamless, with no interruption to normal user workflows.
• Events older than one year will be excluded from the initial sync window. However, recurring events with instances falling within or after the one-year threshold will still be included in the sync.
• Existing permissions and sharing relationships will be preserved; no re-sharing or permission reset will be required.
• The upgrade process is fully automatic and requires no action from the user — no Outlook restart, profile recreation, or any other manual steps.
• No data loss is expected as a result of this change.
• The rollout will initially support auto-upgrade for up to four shared calendars per delegate or principal, scaling up to six over time. Those managing more than six shared calendars will be excluded from the auto-upgrade and will experience no change to their current setup.

How does it effect the Classic Outlook setting ‘Turn on shared calendar improvements’?

• After migration, Classic Outlook will continue to honour the existing setting. Although shared calendars are upgraded to the REST model at the service level, Classic Outlook will follow the setting and use MAPI-based model if the setting is turned off. This behaviour is limited to Classic Outlook; all other endpoints (Outlook Web, Mobile, Mac, New Outlook) will use REST.

[What you can do to prepare]

No action is required.

We recommend that administrators:

• During migration, a hidden shared calendar folder may be visible to tenant admins and support teams via the Get-MailboxFolderStatistics cmdlet. This is expected and has no impact on end users.
• Monitor for persistent issues, such as missing meetings after the migration window or duplicate calendar folders, and contact Microsoft support if observed.
• If a manual rollback is required after the calendar becomes visible, open a support request through standard Microsoft support channels.

[Compliance considerations]

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

[Introduction]

Microsoft is taking steps to help keep customers safe as AI models become more advanced including plans to incorporate advanced AI models directly into our Security Development Lifecycle (SDL) to identify vulnerabilities and develop mitigations and updates. We are also sharing guidance through Microsoft Security Exposure Management on how customers can reduce their exposure as well as capabilities they can use to take action. You can learn more in our blog here: AI-powered defense for an AI-accelerated threat landscape 

[When this will happen:]

General Availability (Worldwide): available as of April 22, 2026

[How this will affect your organization:]

Customers should review the guidance captured in https://security.microsoft.com/securenow and take action to reduce their exposure in areas where autonomous AI‑driven attacks gain disproportionate advantage – patching, open-source software, customer source code, internet-facing assets, and baseline security hygiene. 

[What you need to do to prepare:]

Customers can review the guidance in Microsoft Security Exposure Management at https://security.microsoft.com/securenow and use the capabilities provided to take action.

[Introduction]

We’re introducing a new Power Automate action that enables automated document generation using document generation forms in SharePoint. This new capability allows customers to streamline document creation by mapping structured inputs directly into predefined templates.

• Generate document from form action allows customers to create documents from a template by mapping form or data inputs to predefined template fields.
• Documents are generated as part of an automated flow and stored in SharePoint.

This capability supports scenarios such as contracts, invoices, letters, and reports using structured templates and form-driven inputs. The action maps input data to template fields and returns the generated document with metadata.

[When this will happen:]

Public Preview: We will begin rolling out in early May 2026 and expect to complete by late May 2026.

[How this affects your organization:]

Who is affected:

• Organizations enrolled in AI in SharePoint Public Preview
• Power Automate users and flow creators
• Teams using SharePoint for document workflows

What will happen:

• A new action Generate document from form (Preview) will be available in Power Automate.
• Feature is only available to preview participants (opt-in required).
• Supports input mapping from forms, lists, Excel, and other sources.
• Documents are generated and stored in SharePoint.
• Automates document creation workflows end-to-end.
• Supports scalable document generation scenarios across business processes (e.g., HR onboarding, approvals, contract generation).
• No changes to existing workflows unless the feature

Important: This capability is only supported for Document Generation forms and requires enrollment in the AI in SharePoint Public Preview.

[What you can do to prepare:]

• Ensure Power Automate is enabled and accessible to users.
• Verify that your organization is approved for the AI in SharePoint Public Preview to use document generation features.
• Ensure appropriate permissions to SharePoint sites and libraries where generated documents will be stored.
• No additional setup required after enrollment.

Learn more: Microsoft SharePoint Connector for Power Automate | Microsoft Learn

[Compliance considerations:]

[Introduction]

We’re introducing new Power Automate capabilities for forms in SharePoint, enabling customers to automate workflows based on form submissions. These features are in Preview and may evolve before full General Availability.

• A new trigger: Form submitted
• A new action: Get form metadata 

[When this will happen:]

• Public preview: We will begin rolling out in early May 2026 and expect to complete by late May 2026.
• This post will be updated with General Availability dates in the future.

[How this will affect your organization:]

Who is affected:

• Power Automate users building flows with SharePoint forms
• SharePoint site owners and creators using forms experiences
• Administrators managing Power Automate and SharePoint

What will happen:

• The Form submitted trigger in Power Automate starts flows when a form is submitted from SharePoint list, file upload, or document generation experiences.
• The Get form metadata action retrieves the form structure, including fields, schema, and configuration, and enables flows to dynamically read form structure.
  • Flows can use form metadata (such as field names, types, required status, and defaults) to dynamically map responses without manual configuration, reducing fragility caused by dependency on fixed field IDs.
• These capabilities enable scalable automation scenarios such as approvals, notifications, integrations with other systems, routing, and orchestration based on form submissions.
• Document generation scenarios require enrollment in AI in SharePoint Public Preview.
• Existing SharePoint permissions are respected, and no additional configuration is required.

[What you can do to prepare:]

• No action is required. 
• Ensure Power Automate is enabled in your tenant.
• Review permissions for SharePoint sites (SharePoint site settings > site permissions) as flows will respect existing SharePoint access controls.
• Communicate updates to flow makers.
• Enroll in AI in SharePoint Public Preview if using document generation.

Learn more: Generate structured documents in a SharePoint document library – SharePoint in Microsoft 365 | Microsoft Learn 

[Compliance considerations:]

[Introduction]

Microsoft Teams Rooms on Android will soon be able to join third-party meetings using Session Initiation Protocol (SIP). This capability enables seamless cross-platform interoperability, allowing users to connect to external meeting services directly from Teams Rooms on Android devices while maintaining a consistent and reliable meeting experience across diverse meeting platforms.

This message is associated with Microsoft 365 Roadmap ID 558539.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• Organizations with Microsoft Teams Rooms on Android devices
• Organizations that host or join third-party meetings from shared meeting spaces
• Admins managing Teams Rooms on Android devices licensed with Teams Rooms Pro

What will happen:

• Users will be able to join supported third-party meetings (for example, Zoom or Webex) directly from Teams Rooms on Android devices when the meeting invitation includes a Session Initiation Protocol (SIP) video meeting address.
• This feature is off by default. Availability of this capability depends on Teams Rooms Pro licensing and appropriate device configuration. 

[What you can do to prepare:]

• Test the feature with your lower-ring Teams Rooms on Android devices.
• Prepare educational material for users in advance of release.
• Identify users who frequently collaborate with external organizations using third-party meeting platforms and communicate upcoming capabilities.
• Ensure that all Teams Rooms on Android devices that require this functionality are licensed with Teams Rooms Pro.
• Update internal documentation for meeting room usage if applicable.
• Communicate this change to your helpdesk and support teams.

Learn more: SIP and H.323 Dialing with Teams Rooms | Microsoft Learn (will be updated before rollout)

[Compliance considerations:]

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

[Introduction]

With IT administrator approval, Microsoft Edge will share selected work browsing history from Microsoft and third‑party apps with Microsoft 365 Copilot Search to improve search result ranking. When users search in Microsoft 365 Copilot Search, Copilot will surface previously visited work pages more quickly, helping reduce time spent re‑finding information. Admins will control availability through a Microsoft Edge policy, and browsing history will be shared only when Microsoft 365 Copilot Search is configured in the Microsoft 365 admin center.

This message is associated with Microsoft 365 Roadmap ID 537283.

[When this will happen]

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

[How this affects your organization]

Who is affected

• Organizations using Microsoft Edge for Business
• Tenants with Microsoft 365 Copilot Search configured in the Microsoft 365 admin center
• Admins managing Microsoft Edge and Microsoft 365 Copilot policies
• Users signed in to Microsoft Edge with a work account

There will be no change for consumer Microsoft Edge users or personal browsing profiles.

What will happen

• If enabled by administrators, Microsoft Edge will share selected work‑related browsing history with Microsoft 365 Copilot Search to improve search result ranking.
• Eligible browsing history will include pages from administrator‑configured Microsoft and third‑party work apps and sites.
• Browsing history will be collected only from Microsoft Edge work profiles.
• Personal browsing profiles and consumer Microsoft Edge users will not be included.
• A user‑visible setting will appear in Microsoft Edge under Settings > Microsoft 365 Copilot, allowing users to turn the feature off when permitted by admin policy.
• If the ShareBrowsingHistoryWithCopilotSearchAllowed policy is disabled, no browsing history will be shared.

[What you can do to prepare:]

• Review and configure the ShareBrowsingHistoryWithCopilotSearchAllowed Microsoft Edge policy to align with your organization’s privacy and compliance requirements.
• Coordinate with Microsoft 365 Copilot administrators to ensure consistent Copilot Search behavior across your tenant.
• Notify security, privacy, and helpdesk teams about the upcoming capability and the user‑visible Edge setting.
• Update internal documentation or user guidance if you describe Microsoft Edge or Microsoft 365 Copilot Search behavior.

Learn more:

• Microsoft 365 Copilot Search | Microsoft 365 Copilot | Microsoft 365 | Microsoft Learn
• Microsoft Edge browser policy documentation ShareBrowsingHistoryWithCopilotSearchAllowed | Microsoft Edge | Microsoft Learn

[Compliance considerations]

The table below summarizes compliance areas impacted by this feature. 

Updated April 29, 2026: We have updated the content. Thank you for your patience. 

[Introduction]

We’re updating dynamic distribution groups (DDGs) in Exchange Online so group membership is available sooner after a group is created or its filter is changed. For DDGs whose filter returns 5,000 members or fewer, membership will be populated during the creation or modification operation, eliminating the previous wait of up to two hours.

This message is associated with Microsoft 365 Roadmap ID 560550.

[When this will happen]

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

[How this affects your organization]

Who is affected

Exchange Online administrators who create or manage dynamic distribution groups using the Exchange admin center (EAC) or PowerShell

What will happen

• For DDGs whose filter returns 5,000 members or fewer, membership will be populated as part of the create or modify operation.
• For DDGs whose filter returns more than 5,000 members:
  • Membership will be populated by a background process within up to 2 hours.

  • A warning message will now be shown at creation or modification time, indicating that membership will be populated in the background.

    Warning in PowerShell:

    

    Warning in EAC:

    

• For modifications, the DDG continues to use the previous membership list until the background process completes.
• The routine 24-hour membership refresh cycle will not be affected.
• This behavior will apply to DDGs created or modified using:
  • Exchange admin center (EAC)
  • PowerShell (New-DynamicDistributionGroup, Set-DynamicDistributionGroup)

Summary of behavior after rollout

[What you can do to prepare]

• No action is required.
• Update internal documentation or helpdesk guidance that references a 2-hour wait time for DDG membership population after creation or modification.
• Inform administrators that immediate membership availability will apply to DDGs whose filter returns 5,000 members or fewer after rollout.

Learn more:

• Create and manage dynamic distribution groups in Exchange Online | Recipients in Exchange Online | Exchange Online | Microsoft Learn
• Troubleshoot dynamic distribution group membership issues | Dynamic distribution groups | Recipients in Exchange Online | Exchange Online | Microsoft Learn

[Compliance considerations]

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

[Introduction]

OneDrive sync on Windows will support syncing up to 1 million items per sync instance per device. This increase is intended to help organizations with large OneDrive and SharePoint libraries sync more content reliably across devices. The capability is planned to be available first in Public Preview (requires the Insiders ring) and later in General Availability.

Devices that do not meet the minimum hardware and configuration requirements will continue to sync at the existing 300,000-item supported limit without disruption.

[When this will happen]

• Public Preview: We will begin rolling out in late April 2026 and expect to complete by late April 2026.

[How this affects your organization]

Who is affected

• Users syncing OneDrive (consumer), OneDrive for Business or SharePoint document libraries on Windows
• Users with libraries that approach or exceed the current 300,000-item supported sync limit
• Preview participants using the Insiders ring

What will happen

• Eligible Windows devices can sync up to 1 million items per sync instance.
• Devices that do not meet the requirements remain supported up to 300,000 items with no change in behavior.
• No disruption is expected for existing sync setups.

Note: Performance is not yet optimized for syncing a high volume of read‑only files or for accounts under legal hold. Microsoft is actively working to improve performance and reliability for these scenarios.

[What you can do to prepare]

No action is required if you do not plan to use Public Preview.

If you plan to evaluate or prepare for this capability:

• Identify devices and users likely to benefit from syncing very large libraries.
• Ensure devices meet the minimum requirements (supported OS, memory, storage, and processor).
• Verify the recommended ideal state configuration for OneDrive and SharePoint sync reliability.
• Inform helpdesk staff and impacted users that Public Preview requires the Insiders ring and that ineligible devices will remain at the current limit.

Learn more: 

• How we release updates through multiple rings – The OneDrive sync app update process | SharePoint in Microsoft 365 | SharePoint | Microsoft Learn
• Recommended sync app configuration | SharePoint in Microsoft 365 | SharePoint | Microsoft Learn
• Restrictions and limitations in OneDrive and SharePoint | Other issues | Troubleshoot | OneDrive | Microsoft Support

[Compliance considerations]

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

• Surface the prioritized actions across various touchpoints in the flow of sellers’ work, ensuring enhanced discoverability of key and time-sensitive actions.
• You can onboard any custom agent or workflow that generates actions for sellers to be prioritized and identified via the above-described experiences.

• Colored tiles make it easy to see, filter and focus on task success, failure, or warnings.
• The timeline allows you to easily see how each task contributes to the overall processing time. Task performance is shown in a Gantt chart which visually indicates tasks running in parallel, as well as tasks dependent on other tasks finishing before they can start.
• The performance analysis allows you to quickly compare the current run against historical runs. Key information that can impact the performance are highlighted, such as changes in the number of source records ingested from a data source.

• Automatic emails generated when a process fails will no longer be sent for temporary failures. If the system can retry the operation, it will only send an email if the process fails and no more retries are possible.
• When exporting diagnostic logs to Azure Monitor, you can now differentiate between a failure that is automatically being retried, and a failure that is permanent. This allows you to avoid sending notifications to your team for processes that automatically self-resolve.
• Previously, certain timeout failures would not result in a failure notification. These timeout failures, if they cannot be retried, will now generate the appropriate permanent failure error.

• Questions generated from the last seven days are assigned to the suggested themes
• On a daily basis, new questions are generated.
• Users with sufficient privileges
• Additional metrics, such as the number of questions asked about the theme, answer rate, quality of response, and user feedback, are created.