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

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

Microsoft Teams Events invite emails will be separated based on the role of the participant. Event organizers will get an email explaining the specific roles of participants in the event. Similarly, each presenter will get a separate calendar invite, allowing the organizers of town halls to maintain separate invites for attendees. 

This message is associated with Microsoft 365 Roadmap ID 476488.

[When this will happen:]

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

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

General Availability (GCC, GCC High): We will begin rolling out late July 2026 (previously late April) and expect to complete by late August 2026 (previously late May).

[How this will affect your organization:]

This feature update allows the organizers of town halls to maintain separate invites for attendees.

[What you need to do to prepare:]

This rollout will happen automatically with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate.

Updated May 21, 2026: Phasing out to Legacy Auth Token (EAT) has been initiated and will complete by June 8th 2026. Thank you for your patience. 

[Introduction]

We’re retiring the use of external access tokens for actionable messages and transitioning to Microsoft Entra-based authentication. This update enhances security and aligns with modern identity standards, providing a more robust and compliant experience for actionable messages.

[When this will happen]

This change takes effect on May 15, 2026. After this date, external access tokens will no longer be supported.

[How this affects your organization]

Who is affected:

Organizations using actionable messages that currently rely on external access tokens.

What will happen:

• Actionable messages that depend on external access tokens will fail after May 15, 2026.
• All integrations and workflows using actionable messages must adopt Microsoft Entra authentication.
• This change improves security posture by leveraging Entra’s identity and access management capabilities.

• Review all actionable message implementations in your organization.
• Update integrations to use Microsoft Entra authentication before May 15, 2026.

Learn more:

• Actionable messages in Outlook and Office 365 Groups
• Enable Entra token for Actionable messages

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

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

[Introduction]

As AI agents become deeply embedded in enterprise ecosystems, they are evolving beyond simple tools or workflows into an autonomous digital workforce. These agents can interpret user intent, access and manipulate enterprise data, execute actions on behalf of users, and even make real-time decisions. In many ways, they operate like human insiders only with machine-speed data processing capabilities.

To govern and protect these agents effectively, organizations require visibility into their activities, contextual understanding of their actions, and the ability to flag or block risky behavior. Now, Insider Risk Management can be extended to detect and remediate potentially risky agent activities.

Features:

• Copilot Studio & Azure AI Foundry Integration: Detect potentially risky activities of agents hosted on Copilot Studio, Azure AI Foundry, and Agent 365 platforms
• Risky AI Usage Policies: Define and enforce policies specific to AI agents accessing sensitive data or performing high-risk actions.
• IRM for Agent Users: Extend IRM in Purview to govern agent-driven workflows and protect organizational data.

This message is associated with Microsoft 365 Roadmap ID 516032.

[When this will happen:]

• Public Preview: We will begin rolling out early December 2025 and expect to complete by mid-January 2026.
• General Availability (Worldwide): We will begin rolling out mid-June 2026 (previously early May) and expect to complete by end of July 2026 (previously late May).

[How this affects your organization:]

On the Overview page in the Insider Risk Management solution, you will be able to access the overall risk profile of agents deployed in your organization.

The Risky Agents policy will be automatically deployed for all agents hosted on Copilot Studio and Azure AI Foundry across your organization. Alerts from this policy will be generated when an agent’s activity exceeds the thresholds configured in this automatically deployed Risky Agents policy. These alerts can be found under Agents > Alerts on the left pane.

[What you can do to prepare:]

• Review the public facing documentation to learn more about this exciting new offering: Learn about Insider Risk Management policy templates | Microsoft Learn
• Review the new Insider Risk Management interface in the Microsoft Purview portal, which now includes separate sections for Users and Agents.
• Review and tune the Risky Agents policy based on your organization’s requirements.
• If you don’t wish to track agent activities, you can delete the automatically deployed Risky Agents policy. 

Learn more:

• Help dynamically mitigate risks with Adaptive Protection | Microsoft Learn
• Create and manage Insider Risk Management policies | Microsoft Learn
• Learn about Insider Risk Management policy templates | Microsoft Learn

Updated May 20, 2026: We’re reminding you that billing for High Volume Email will begin soon. To avoid service disruption, ensure your billing configuration is set up before billing starts. We have updated the content below. Thank you for your patience. 

[Introduction]

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

Usage will be metered starting June 1, 2026, based on the number of expanded delivered recipients. Pricing is $42 per one million recipients (equivalent to $0.000042 per recipient) through Microsoft commerce.

To ensure uninterrupted service, you must configure your billing settings before billing starts. If billing is not configured by this date, your organization may experience interruption in High Volume Email message delivery until billing is set up.

This message is associated with Microsoft 365 Roadmap ID 382633.

[When this will happen]

• Public Preview: Available now.
• General Availability (worldwide): Available now. 
• Billing for High Volume Email will begin on June 1, 2026.

[How this affects your organization]

Who is affected

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

What will happen

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

Screenshot 1 – Create new HVE specific accounts: 

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

[What you can do to prepare]

To continue using High Volume Email without interruption:

1. (Optional) Review your current usage of High Volume Email. For more information, see View HVE usage report.
2. (Required) Set up billing configuration for High Volume Email. For more information, see Set up Billing for High Volume Email.
3. (Required) Verify that your billing configuration is active and correctly associated with your tenant.

You may want to:

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

[Compliance considerations]

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

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

[Introduction]

As organizations deploy AI agents that can access enterprise data and take action on behalf of users, governing and securing agent activity becomes critical. Microsoft Purview will extend its data security and compliance capabilities to include AI agents, helping organizations gain visibility into agent behavior, assess risk, and apply consistent governance controls.

Microsoft Purview for agents will introduce Data Security Posture Management (DSPM) – AI Observability and Insider Risk Management for agents. DSPM helps organizations understand where sensitive data is, assess data-related risk, and continuously improve their security and compliance posture.

This message is associated with Microsoft 365 Roadmap ID 516032.

[When this will happen]

• Public preview: Rollout started in December 2025 and is expected to complete in late April 2026.
• General availability (Worldwide): Rollout will begin in mid-June 2026 (previously early May) and is expected to complete by end of July 2026 (previously late May).

[How this affects your organization]

Who is affected

• Microsoft 365 administrators responsible for security, compliance, and governance
• Organizations using or planning to deploy AI agents
• Tenants with Microsoft 365 E7 or Agent 365 subscriptions

What will happen

• DSPM – AI Observability and Insider Risk Management for agents will move from preview to general availability. Learn more about activation.
• With Microsoft 365 E7 or Agent 365 subscriptions, admins will be able to:
  • Monitor and analyze AI agent activity across enterprise environments
  • Identify potentially risky or non-compliant agent behavior
  • Apply governance policies aligned with organizational requirements

Insider Risk Management for agents

• Microsoft Purview Insider Risk Management correlates various signals to identify potential malicious or inadvertent insider risks, such as IP theft, data leakage, and security violations.
• Admins will be able to create policies based on their own internal policies, governance, and organizational requirements.
• The solution is built with privacy by design:
  • Users are pseudonymized by default.
  • Role-based access controls and audit logs help ensure user-level privacy.
• These capabilities will not be available without Microsoft 365 E7 or Agent 365 subscriptions.
• There will be no user impact unless AI agents are deployed and governed by admins.

[What you can do to prepare]

• Review whether your organization currently uses or plans to deploy AI agents that access enterprise data.
• Activate your Microsoft 365 E7 or Agent 365 subscription if you plan to use DSPM – AI Observability and Insider Risk Management for agents.
• Review and update internal security, compliance, and AI governance policies.
• Inform security and compliance stakeholders about this upcoming capability.

Learn more: Overview of Microsoft Agent 365 | Microsoft Agent 365 | Microsoft Learn

[Compliance considerations]

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

[Introduction]

We’re enhancing the PowerPoint Live experience in Microsoft Teams by introducing slide text selection with Copilot explanations for meeting attendees. This update helps users quickly understand unfamiliar terms, acronyms, or complex concepts directly within a live presentation—without interrupting the presenter or asking questions in chat.

This message is associated with Microsoft 365 Roadmap ID 557256.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• All Microsoft Teams users attending meetings with PowerPoint Live
• Tenants with Microsoft 365 Copilot (Premium) enabled

What will happen:

• Attendees can select text on a PowerPoint Live slide during a meeting.
• Copilot will provide on-demand explanations for selected text, including:
  • Acronyms and abbreviations.
  • Technical or domain-specific terms.
• Explanations are shown privately to the attendee and do not disrupt the presenter or other participants.
• The feature is on by default for eligible tenants where Copilot is available.

Screenshot 1: Select the Copilot feature from the Presenter View toolbar at the bottom of the screen:

Screenshot 2: Select any text from the slide:

Screenshot 3: After selecting a word or phrase on the slide (for example, “protocol”), select Explain this from the available Copilot options:

Screenshot 4: Copilot opens the chat pane and provides an explanation for the selected content:

[What you can do to prepare:]

• No admin action is required to enable this feature.
• Review your organization’s Copilot for Microsoft 365 policies to ensure they align with your internal AI usage guidelines.
• Inform helpdesk and support teams about this new attendee capability.

[Compliance considerations:]

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

[Introduction]

The new Outlook for Windows now allows users to store S/MIME encryption certificates directly within Contacts. This capability enables users to save recipients’ public certificates and use them to send S/MIME encrypted emails, improving secure communication and continuity when transitioning from classic Outlook for Windows (Win32). Certificates previously stored in Contacts in classic Outlook will automatically be available in new Outlook.

This message is associated with Microsoft 365 Roadmap ID 518288.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• Users of new Outlook for Windows
• Organizations that use S/MIME encryption

What will happen:

• Users can store recipients’ S/MIME public certificates directly in Contacts.

Screenshot: To add a S/MIME certificate, go to Your contacts > Certificates > Add certificate:



• Stored certificates can be used to encrypt outgoing email to those recipients.
• Certificates saved in Contacts in classic Outlook (Win32) will automatically carry over.
• Feature is available by default; no admin configuration required.
• No impact to users who are not using new Outlook for Windows.

[What you can do to prepare:]

• No admin action is required to enable this feature.
• If your organization uses S/MIME:
  • Instruct users to add or import S/MIME public certificates into Contacts.
  • Communicate how to select S/MIME encryption when composing emails. Learn more: Send S/MIME or Microsoft Purview encrypted emails in Outlook | Microsoft Support.
• Update internal documentation for users transitioning from classic Outlook.
• Inform helpdesk teams of this improved certificate handling experience.

[Compliance considerations:]

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

[Introduction]

Microsoft is introducing a new Copilot chat pane in OneNote Mobile (Android) for users licensed with Microsoft 365 Copilot (Premium). This update adds a new Summary feature that allows users to generate concise summaries of longer OneNote pages, as well as ask questions about their notes, directly within the OneNote mobile app. This helps users review and interact with note content more efficiently while on the go.

This message is associated with Microsoft 365 Roadmap ID 422323.

[When this will happen]

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

[How this affects your organization]

Who is affected

• Users with Microsoft 365 Copilot (Premium) licenses
• Users accessing OneNote on Android
• All Microsoft 365 tenants

What will happen

• Users with a Microsoft 365 Copilot (Premium) license will see a Copilot chat pane in the OneNote mobile app on Android: 

  

• The Copilot chat pane allows users to generate concise summaries of longer OneNote pages and ask questions about their notes: 

  

• Existing Microsoft 365 Copilot controls, permissions, and policies continue to apply.
• Users without a Microsoft 365 Copilot (Premium) license are not impacted.

[What you can do to prepare]

• No admin action is required before rollout.
• Ensure that users who should access this feature are assigned a Microsoft 365 Copilot (Premium) license.
• Consider informing helpdesk staff and users about the availability of Copilot chat and the Summary feature in OneNote mobile.
• Review existing Microsoft 365 Copilot governance, compliance, and usage policies to ensure they align with your organization’s requirements.

[Compliance considerations]

• Automated, Intelligent Scheduling:
• Real-time, policy-compliant schedule adjustments based on changing contact center demands.
• Learns from supervisor actions to generate optimal daily schedules.
• Supports both intraday adjustments and short-term schedule planning.
• Improves service levels, agent utilization, and customer satisfaction.
• User Experience & Controls:
• “Schedule People” page with filters and multiple calendar views.
• LLM-powered chat interface for supervisors to use natural language to schedule, reschedule, or adjust shifts.
• Multi-turn conversations, clarification prompts, and real-time display of schedule changes.
• All actions comply with labor policies, CSR preferences, skill matching, and cost efficiency.
• Transparency, Logging, and Compliance:
• Detailed logging of all actions, including manual overrides, for compliance and continuous improvement.
• Immediate notifications and recommendations for supervisors in case of scheduling failures, with system fallback to the last known good state.
• Admin-accessible logs for audit and troubleshooting, with privacy and security controls.
• Additional Highlights:
• Out-of-the-box scheduling rules and policy management.
• Integration with forecasting and time management agents for optimal shift planning.
• Clear, actionable notifications for supervisors and agents.
• Robust fallback and error-handling logic, including user guidance for out-of-scope requests.

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

[Introduction]

New Outlook for Windows now supports Lightweight Directory Access Protocol (LDAP) directories for S/MIME certificate lookup. This enables tenants to configure LDAP directories for their organization as well as enabling users to configure LDAP directories themselves. Once configured, users can find recipients’ public encryption certificates from the directories when sending encrypted email, improving secure collaboration with external partners. This is especially valuable for tenants who collaborate with external partners and rely on public/partner LDAP directories to store public S/MIME certificates of users. 

This message is associated with Microsoft 365 Roadmap ID 518287.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

•  Organizations that use S/MIME encryption with external recipients whose public certificates are hosted in third-party LDAP directories 
•  Admins managing Exchange Online

What will happen:

• Admins can configure LDAP directories using Exchange Online PowerShell.
• Users can add LDAP directories in Settings > Mail > S/MIME in new Outlook.
• When composing an S/MIME encrypted email, users can select recipients from the LDAP directory via the To field. This will directly enable Outlook to retrieve the certificate from the selected LDAP directory. If users add a recipient directly to the ‘To list’, Outlook will scan all available certificate sources, including the configured LDAP directories.
• LDAP endpoints must not require authentication, as authentication is not currently supported.

Screenshot: “Add LDAP directory” option in Settings > Mail > S/MIME and LDAP recipient picker in the To field during message composition:



• Feature is enabled by default once available.
• No impact to:
  • Classic Outlook for Windows users
  • Organizations not using LDAP for S/MIME certificate discovery

[What you can do to prepare:]

• No action is required to enable this feature
• If your organization uses LDAP for S/MIME certificates:
  • Identify LDAP directory endpoints used by your organization
  • Run the Add-LdapDirectory cmdlet to register a new directory:

  Add-LdapDirectory -Organization "contoso.com" -Id "corp-ldap" -Host "ldap.corp.com" -Port 636 -UseSsl

  • Configure directories using Exchange Online PowerShell (Add-LdapDirectory).
  • Ensure LDAP endpoints do not require authentication.
  • Communicate guidance to users transitioning to new Outlook: Set up Outlook to use S/MIME encryption | Microsoft Support.

Learn more: Configure S/MIME in Exchange Online | Microsoft Learn (will be updated before we complete rollout)

[Compliance considerations:]

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

• View evaluation progress and execution status
• See partial results as individual inputs are processed

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

[Introduction]

Data Security Investigations (DSI) provides proactive AI-powered insights within the Data Security Posture Management (DSPM) experience. With this rollout, Microsoft Purview expands this capability so that when DSPM detects potential data exfiltration risks, DSI automatically analyzes the associated content across key sensitive data categories, such as intellectual property, financial data, and credentials, and surfaces results directly within DSPM. This integration helps security teams identify and prioritize risks earlier, streamline investigations, and act faster to protect sensitive data.

Important: These insights are available only when Data Security Investigations (DSI) is configured and Data Security Posture Management insights is activated.

This message is associated with Microsoft 365 Roadmap ID 560327.

[When this will happen]

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

[How this affects your organization]

Who is affected

• Security admins and analysts using Microsoft Purview Data Security Posture Management (DSPM) with Data Security Investigations (DSI) enabled
• Organizations with DSPM configured for exfiltration detection scenarios and access to DSI

What will happen

• When DSPM identifies potential data exfiltration, DSI analyzes the underlying content against sensitive data categories.
• This change brings DSI content analysis directly into the DSPM workflow, so analysts no longer need to switch tools to understand what data is at risk in a potential exfiltration event.
• AI-generated insights appear directly within the DSPM experience, allowing analysts to understand what sensitive data is at risk. Image 3. DSPM view showing proactive AI insights: 

  

• Once enabled, no additional action is required for the insights to appear.
• Analysts can investigate further using the Go to investigation option, which opens the relevant context in Data Security Investigations. Image 2. Go to investigation experience in DSI: 

  

• Admins can enable proactive AI insights within DSPM as part of the Prevent exfiltration to risk destinations objective. Image 3. Enable proactive AI insights setting in DSPM:

  

• This capability helps reduce triage time and improves prioritization of investigation efforts.
• There is no impact to users.
• This feature requires DSPM to be configured, the Prevent exfiltration to risk destinations objective enabled, and Data Security Investigations (DSI) to be available and enabled in your tenant.
• Proactive AI insights only appear when Data Security Investigations (DSI) is available and enabled.

[What you can do to prepare]

• No action is required if you are not using DSPM or DSI.
• Ensure Data Security Investigations and Data Security Posture Management are configured in your tenant.
• Assign appropriate roles for DSPM and DSI to your security team.
• Enable the Prevent exfiltration to risk destinations objective in DSPM.
• Enable proactive AI insights within DSPM.
• Educate your security team on the updated investigation workflow.

Learn more:

• Data Security Investigations | Microsoft Purview
• Data Security Posture Management | Microsoft Purview

[Compliance considerations]

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

[What and Why]

As Microsoft Teams has added meeting capabilities over time, the meeting controls and share panel have grown crowded, contributing to mis-clicks between high‑impact actions like Share, Leave, and Raise hand, and to accidental shares of unintended content. Drawing on extensive customer feedback and telemetry, we’re introducing two coordinated updates: simplified meeting controls and a redesigned share panel. Together, they make core actions easier to find, reduce accidental clicks, and give users more confidence when sharing content.

This update supports personal and team productivity by reducing friction in everyday meetings and improving confidence when presenting or sharing content.

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

[Rollout Schedule]

• Targeted Release: We will begin rolling out in early July 2026 and expect to complete by late July 2026.
• General Availability (Worldwide): We will begin rolling out in early August 2026 and expect to complete by late August 2026.
• General Availability (GCC, GCC High): We will begin rolling out in early September 2026 and expect to complete by late October 2026.
• General Availability (DoD): We will begin rolling out in early October 2026 and expect to complete by late November 2026.

[Impact on Your Organization]

Who is affected:

• All Teams work and school users joining meetings

Platforms:

• Teams for Windows desktop
• Teams for Mac desktop
• Teams for the web
• Not in scope: Teams (consumer), iOS, Android, Teams Rooms, Linux

What will happen:

• Meeting controls will be center‑aligned, with microphone, camera, and share grouped together.
• The Leave button will be separated to reduce accidental exits.
• Less‑used actions will move into a reorganized More menu.

Screenshot: New More options menu 

• Users can personalize meeting controls by pinning, unpinning, and rearranging controls using drag and drop.
• The redesigned share panel will include:
  • Live previews of screens and windows.
  • A tabbed layout (Screens & Apps, Interactive Files, More options).
  • A two‑step share confirmation to reduce accidental sharing.

Screenshot: Reorganized share panel

• The new experience is enabled by default and cannot be disabled at the tenant level.
• During rollout, users may opt in early and can temporarily return to the previous experience from Teams settings.
• Existing meeting app pinning policies will continue to be honored.
• New meeting app pinning policies will support up to two apps pinned to the main meeting controls, with additional apps available in the More menu.

Known limitations:

• Meeting controls customization preferences (such as pinned controls) do not sync across devices at launch. Preferences persist across meetings on the same client. Cross‑device sync is planned for a future release.
• The opt‑out toggle for the new meeting experience is controlled by individual users and cannot be managed at the tenant level. This opt‑out is a temporary adoption aid and will be retired in a future release. Microsoft will provide advance notice via a separate Message Center post before removal.

[Action Required / Recommendations]

No immediate action is required.

We recommend that you:

• Review existing Teams meeting app pinning policies and plan future policies around the two‑app limit.
• Communicate this change to users, helpdesk, and internal support teams ahead of the June 2026 rollout. Detailed change management guidance for Champions and IT Pros/admins, along with user training resources, will be published in early May 2026 on adoption.microsoft.com.
• Update internal documentation and training materials to reflect:
  • The new meeting controls layout.
  • User customization options.
  • The updated share panel experience.

[Compliance Considerations]

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

[What and Why:]

Microsoft Purview Data Loss Prevention (DLP) policy updates will now sync significantly faster across Microsoft 365 services. The policy sync service-level agreement (SLA) is being reduced from up to 2 hours to 30 minutes, helping security and compliance teams enforce protections more quickly after making policy changes. This improvement supports enterprise-ready security and compliance without adding administrative overhead.

This message is associated with Microsoft 365 Roadmap ID 558682.

[Rollout Schedule:]

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

[Impact on Your Organization:]

• Who is affected: Microsoft 365 administrators managing Microsoft Purview Data Loss Prevention (DLP) policies.
• Platforms / Services: Microsoft Purview and Microsoft 365 services where DLP policies are enforced.
• What will happen:
  • DLP policy updates will sync within 30 minutes instead of up to 2 hours.
  • Policy enforcement across supported services will occur more quickly.
  • The improvement is enabled by default.
  • No changes to existing admin workflows are required.

[Action Required / Recommendations:]

• No action required.
• This change is applied automatically. Your organization will begin benefiting from faster policy sync times as the update rolls out.
• Optionally, inform security and compliance teams that DLP changes will take effect more quickly to support faster response expectations.

[Compliance considerations:]

This change improves the timing of DLP policy enforcement but does not change policy behavior, data processing, or data storage.

[What and Why]

Users are currently blocked from sending messages in Microsoft Teams while a file upload is in progress, which can disrupt real-time collaboration. With this update, file uploads will occur asynchronously in the background, allowing users to continue sending messages without interruption.

This message is associated with Microsoft 365 Roadmap ID 560813.

[Rollout Schedule]

• Targeted Release: Rollout will begin in mid-June 2026 and is expected to complete by late June 2026.
• General Availability (Worldwide): Rollout will begin in late June 2026 and is expected to complete by late June 2026.

[Impact on Your Organization]

Who is affected

All Microsoft Teams users who send files in chats or channels

Platforms/Services

• Microsoft Teams
• Desktop (Windows, Mac)
• Web
• Mobile (iOS, Android)

What will happen

• Users will be able to send chat messages while files are uploading.
• File uploads will occur asynchronously in the background.
• The message input box will no longer be blocked during uploads.
• There are no changes to how files are stored or shared.
• Existing compliance, retention, and security policies remain unchanged.
• This feature will be enabled by default for all tenants.

[Action Required / Recommendations]

• No action is required.
• Consider informing your users about improved file upload behavior in Teams chats.
• Update internal training or support documentation if you reference file-sharing workflows.

[Compliance considerations]

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

[Introduction]

Microsoft Teams Rooms on Android (MTR-A) will support joining webinars and structured meetings with a dedicated attendee experience. Structured meetings are meetings where organizers restrict presenter permissions and assign attendee roles. This update enables room devices to join these event types as attendees and use attendee features during the session. This capability requires Teams Rooms Pro.

This message is associated with Microsoft 365 Roadmap ID 547824.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• Organizations using Microsoft Teams Rooms on Android (MTR-A) with Teams Rooms Pro licenses
• Admins managing Teams Rooms devices and meeting policies
• Users joining webinars or structured meetings from conference rooms

What will happen:

• Microsoft Teams Rooms on Android (MTR-A) devices can join webinars and structured meetings as attendees from the room console.

Screenshot 1: Webinar front-of-room experience:



Screenshot 2: Webinar console view:



• Rooms will use an attendee role-based experience, separate from presenter controls and views.
• When enabled by meeting options, room attendees can use:
  • Chat
  • Reactions
  • Raise hand
  • Captions
  • Participant roster and visibility controls
• Rooms no longer require a separate personal device to participate in these sessions.
• Layouts are optimized for single-screen and dual-screen rooms to emphasize shared content and active speaker or stage view.
• For webinars and structured meetings, the room display (front‑of‑room) can be restricted to curated stage content, using managed or on‑stage view behavior.
• Organizers can include rooms as attendees; attendee identity may not be shown in webinars, depending on event configuration.
• Availability depends on the device running a version of Teams Rooms on Android that supports this feature.
• Rooms can be used for co-viewing webinars and structured meetings, allowing multiple in-room participants to join from a shared device while still accessing attendee features.
• Supports use in large conference rooms and organization-wide events.
• Applicable to scenarios such as training sessions, organization-wide updates, and leadership broadcasts.

[What you can do to prepare:]

• Ensure your Teams Rooms on Android devices are:
  • Enabled and actively managed.
  • Licensed with Teams Rooms Pro (validated at join time)/
• Update Teams Rooms devices to the latest available version.
• Review internal guidance for meeting organizers to:
  • Add rooms as attendees where appropriate.
  • Configure meeting options to allow desired attendee interactions (chat, reactions, etc.).
• Communicate this update to helpdesk and user communities, especially teams that host webinars or large meetings.

Learn more: Host or attend an event from a Microsoft Teams Room (MTR) – Microsoft Support

[Compliance considerations:]

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

In 2018, we announced that we were no longer making feature updates to Exchange Web Services (EWS) in Exchange Online, and we advised developers to move to Microsoft Graph.

In September 2023, we announced that on October 1, 2026, we will start blocking EWS requests to Exchange Online.

We are now less than 12 months from October 1, 2026. We have made progress on closing most parity gaps with more changes in development to be released in the coming quarters. Please refer to Deprecation of Exchange Web Services in Exchange Online for up-to-date guidance and roadmap information.  

You are receiving this notification because there are EWS applications in your tenant.

If you haven’t already, start the process of working with your application development organization and your application vendors to either sunset or migrate active EWS applications on your tenant to the Graph API, Power Platform, or Copilot Declarative Agents.

The vast majority of custom EWS applications can be safely migrated to alternative technologies today.

[When this will happen:]

October 1, 2026

[How this affects your organization:]

In October 2026 we will begin disabling EWS on all M365 tenants worldwide. EWS Applications that have not been migrated will stop functioning.

The following applications on your tenant use EWS:

Entra Application IDs with EWS traffic and recommendations for next steps:

Apple Mail for Mac (f8d98a96-0999-43f5-8af3-69971c7bb423) – Apple Mail for Mac – No action required if risk is acceptable

Next Steps

1. Review your application portfolio now to get an understanding of which apps need to be updated by your organization and which ones require updates from vendors.
2. While EWS applications are active on your tenant, lower your risk of a successful attack by reviewing and updating the security practices for your organization. In particular, enable Multi Factor Authentication (MFA) for all users including test accounts.
3. Prioritize EWS app modernization on your engineering schedule to ensure enough time to address any functionality gaps
4. Disable EWS in your tenant or enable Baseline Security Mode when you no longer have applications that depend on it.

Note on Apple Mail for Mac

We provide a set of open-source tools and tutorials to aid in discovery, analysis and AI assisted modernization of EWS applications.

Thank you in advance for taking steps to improve the security posture of your M365 tenant. We are extremely excited about the growing opportunities that the Microsoft 365 platform offers to developers, and we remain fully committed to our journey to empower developers with the best features and tools.

• Unlocks trustworthy analysis inside agents and prompts by employing deterministic, reproducible computation instead of best-effort large language model (LLM) reasoning for data questions.
• Lowers the skill barrier for advanced analytics by letting users ask analytical questions in natural language.
• Generates tables and visualizations of results programmatically that users can see, download, and reuse.

• As an uploaded file in an agent chat.
• As a referenced knowledge source in a SharePoint documents library.

[Introduction]

Microsoft Teams is improving the quick sharing experience by enabling search for cloud files directly within the attach file picker. This helps users find and attach the right files more quickly when sharing in chats and channels.

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

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• Users who share and attach files in Microsoft Teams chats and channels using the quick sharing (Attach) experience.
• Organizations that use cloud files available through Microsoft 365 (for example, OneDrive and SharePoint) in Teams.

What will happen:

• Users will be able to search for cloud files directly in the attach file picker during the quick sharing experience.
• The change reduces time spent browsing folders during file attachment.
• Users will only see files they already have permission to access.
• No changes are expected to existing file sharing permissions or policies.

[What you can do to prepare:]

• No action is required.
• Optional: Inform your helpdesk that users may notice a new search capability when attaching cloud files in Teams.
• Optional: Update internal documentation or training materials related to sharing and attaching files in Teams.

[Compliance considerations:]

[Introduction]

We’re introducing a Quick Share option for images in Microsoft Teams to help users share visual content faster across chats and channels. This update extends Quick Share to images in Teams, allowing users to quickly share or copy image links directly from familiar interaction points, while preserving existing permissions.

This message is Associated with Roadmap ID 560816

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• Users who share or interact with images in Microsoft Teams chats, channels, and shared tabs

What will happen:

• Users will see a Quick Share option for images in Microsoft Teams.
• The option is available from:
  • Hover actions
  • Right‑click context menus
  • Overflow menus
  • Shared tabs
• Users can quickly:
  • Share images
  • Copy image links
• Existing Microsoft Teams and Microsoft 365 sharing permissions continue to apply.
• The feature is enabled by default.
• No new admin controls are introduced.

Screenshot 1: Microsoft Teams chat and channel environment where images are shared and viewed:



Screenshot 2: When an image is present in a Teams chat or channel, users can access image‑level actions directly from the image:

[What you can do to prepare:]

• No action is required.
• Consider notifying helpdesk or support teams about this Microsoft Teams image‑sharing enhancement.

[Compliance considerations:]

[What and Why]

Data Security Posture Management (DSPM) in Microsoft Purview is now generally available. This capability helps organizations better understand, assess, and improve their data security posture across Microsoft 365 by identifying risks, surfacing insights, and guiding remediation actions. This release aligns with our continued investment in enterprise-ready security and compliance tools to help you protect sensitive data at scale.

This message is associated with Microsoft 365 Roadmap ID 542790.

[Rollout Schedule]

General Availability (Worldwide): Late-May 2026 – Late June 2026

[Impact on Your Organization]

Who is affected

• Admins and security/compliance teams using Microsoft Purview in Microsoft 365 tenants

Platforms/Services

• Microsoft Purview (web experience)

What will happen

• The Data Security Posture Agent will be generally available in DSPM.
• The feature provides centralized insights into data risks and posture across your environment.
• Admins will be able to view recommendations and take actions to improve data security posture.
• The experience transitions from preview to GA with no disruption to existing configurations.
• No change to existing policies or configurations is required.
• Availability is aligned with your tenant’s Microsoft Purview deployment.

[Action Required / Recommendations]

No action is required.

As a best practice, you may want to:

• Review DSPM capabilities in Microsoft Purview and assess how they fit into your data security strategy.
• Explore configuration and usage guidance:
  • Learn how to set up the new data security posture agent.
  • Review how to use DSPM insights and recommendations.
• Notify your security and compliance teams of this availability.
• Update internal documentation if you reference Purview DSPM capabilities.

Learn more: 

• Get started with the Data Security Posture Agent | Microsoft Purview | Microsoft Learn
• Using the Data Security Posture Agent – Considerations for Microsoft Purview Data Security Posture Management | Microsoft Purview | Microsoft Learn

[Compliance Considerations]

[Introduction]

We’re introducing a new file download manager experience in Microsoft Teams to streamline file downloads and reduce on-screen interruptions. This update simplifies download notifications while still making it easy for users to find downloaded files after the download completes.

This message is associated with Roadmap ID 560815.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• All users downloading files in Microsoft Teams (desktop and web)
• All tenants worldwide

What will happen:

• File download notifications in Teams will automatically dismiss after approximately 4 seconds.
• Users will have an option to open or locate downloaded files after the download completes.
• The experience is enabled by default.
• Existing file permissions, storage locations, and security controls remain unchanged.

[What you can do to prepare:]

• No action is required.
• Optionally, inform helpdesk or support teams about the updated download behavior to reduce user questions.
• Update internal documentation if it references the Teams file download experience.

[Compliance considerations:]

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