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

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

[Introduction]

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

This message is associated with Microsoft 365 Roadmap ID 543239.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

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

What will happen:

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

[What you can do to prepare:]

No admin action is required at this time.

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

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

[Compliance considerations:]

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

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

[Introduction]

AI‑powered meeting assistant bots—such as transcription and summarization services—are increasingly used to enhance productivity in online meetings. While these tools can be valuable, some bots may access meetings without the knowledge or consent of the meeting organizer or the hosting tenant, which can create data security, privacy, and compliance risks.

To help organizations protect meeting content and increase visibility into automated participants, Microsoft Teams is introducing a new capability that detects external meeting assistant bots as they attempt to join meetings. This update gives organizers greater awareness and control and provides administrators with clear controls to manage how detected bots are handled in meetings hosted across the organization.

This message is associated with Microsoft 365 Roadmap ID 558107.

[When this will happen]

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

[How this will affect your organization]

Who is affected

• All organizations using Microsoft Teams meetings, including GCC tenants
• Meeting organizers and Teams administrators

What will happen

• Teams will detect external meeting bots as they attempt to join meetings hosted by your organization.
• When detected, bots will be clearly labeled in the meeting lobby experience.
  • Note: There might still be bots that are undetected by the system due to their intrinsic behavior. Please inform your users to report them out directly from the app/meeting. This will help us improve our detection system.
• Organizers will be able to:
  • approve or deny detected bots from the meeting lobby.
  • see clearly which participants have been identified as bots.
  • remove detected bots during the meeting if necessary.
• These organizer controls are designed to help ensure that bot participation in meetings is an intentional and informed decision.
• A new meeting policy will be available in the Teams admin center that allows admins to configure how detected bots are handled (do not detect bots, require approval). In the future, we intend to provide more granular controls to admins, as appropriate.
• Bot detection will be enabled by default for all tenants.
• Teams will continue improving detection accuracy; however, some bots may not be detected in all scenarios.

[What you can do to prepare]

No action is required at this time.

However, we recommend that Teams admins:

• Review the new meeting policy in the Teams admin center once it becomes available.
• Keep the default setting, which requires organizers to approve detected bots before they join meetings (recommended).
• Choose a stricter or more permissive option based on your organization’s collaboration and compliance requirements.
• Inform meeting organizers that they may see new indicators and approval prompts when detected bots attempt to join meetings.
• Update internal helpdesk or governance documentation if your organization documents meeting join or lobby controls behavior.
• Monitor future Message center updates for expanded administrative controls.

[Compliance considerations]

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

[Introduction]

To help organizations deliver more polished and branded town hall events, Microsoft Teams is introducing the ability for organizers and presenters to upload custom background images in the Manage what attendees see experience. This enhancement allows teams to replace default backgrounds with branded visuals—such as company logos or event-specific designs—so presenters and shared content appear consistently on brand for attendees. This feature is available for Teams events organizers with a Teams Enterprise license. This update applies to Teams for Windows desktop and Mac desktop.

This message is associated with Microsoft 365 Roadmap ID 561493.

[When this will happen]

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

[How this affects your organization]

Who is affected

• Organizers and presenters of Teams town hall events
• Users assigned a Teams Premium license
• Tenants using Manage what attendees see in town halls

What will happen

• Organizers and presenters can upload custom background images directly within the Manage what attendees see experience.
• Uploaded backgrounds appear behind presenters and shared content in supported town hall layouts.
• JPEG and PNG image formats are supported, with recommended resolution guidance shown during upload.
• Custom backgrounds appear alongside existing default background options in the background picker.
• The feature is enabled by default for eligible users and applies only to town hall events where Manage what attendees see is enabled.
• There is no change to standard Teams meetings or webinars.

[What you can do to prepare]

• No admin action is required before rollout.
• Consider notifying users who organize or present town halls about this new capability.
• Prepare branded background images that align with your organization’s visual identity guidelines.
• Update internal documentation or event playbooks if you provide guidance on hosting town halls.
• Optionally, run a test town hall event to familiarize presenters with the upload flow and attendee experience.

Learn more: Customize the event screen – Manage what attendees see in Microsoft Teams | Microsoft Support

[Compliance considerations]

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

[Introduction]

A new Security Detection Report in the Teams admin center provides a unified view of messaging security detections across signals such as impersonation, malicious URLs, and weaponizable file types. This centralized reporting experience improves visibility into threats in Teams and helps admins investigate and respond to suspicious activity more efficiently.

This message is associated with Microsoft 365 Roadmap ID 560702.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• Admins who manage Microsoft Teams environments and security operations
• Security and helpdesk teams responsible for investigating messaging threats

What will happen:

• A new Security Detection Report will be available in the Teams admin center under Analytics & reports > Protection reports > Security detections report.

Screenshot: Example of a Security Detection Report:



• The report provides centralized visibility into messaging security detections across Teams, including impersonation attempts, malicious links, and unsafe file types.
• Admins can review detection details such as:
• Sender
• Recipient context
• Detection type
• Available user actions
• Admins can export report data for further investigation, including additional metadata such as sender identifier and thread ID.
• The following messaging security protections are enabled by default:
• Impersonation detection does not require configuration.
• Malicious link scanning can be managed through Messaging safety settings in the Teams admin center.
• Unsafe file type scanning can be managed through Messaging safety settings in the Teams admin center.
• Admins can block malicious external users identified in the report through External access settings to prevent further communication attempts.

[What you can do to prepare:]

• Review current Messaging safety settings to confirm malicious link and file scanning configurations.
• Familiarize security and helpdesk teams with the new report and export capabilities.
• Update investigation and response workflows to incorporate Teams detection signals.
• Use Teams admin center navigation path to locate the report:
  • Analytics & reports > Protection reports > Security detections report
• Update internal documentation or runbooks if you document security investigation processes.

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

[Compliance considerations:]

Introduces enhanced admin reporting for monitoring and investigating messaging security detections.

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

[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 early August 2026 (previously early July) and is expected to complete by mid-August 2026 (previously mid-July).
• General Availability (Worldwide): Rollout will begin in mid-August 2026 (previously mid-July) and is expected to complete by late August 2026 (previously late July).

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

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

[What and Why]

We are introducing proximity join support for presenters in Microsoft Teams events (town halls, webinars, and structured meetings) using Teams Rooms on Windows and Android. This improvement enables presenters to quickly connect their personal device to a nearby Teams Room system, delivering a more seamless and efficient presentation experience. This update enhances hybrid meeting scenarios by simplifying room system interactions and improving presenter productivity.

This message is associated with Microsoft 365 Roadmap ID 561550.

[Rollout Schedule]

• General Availability (Worldwide, GCC, and GCCH): Begins rolling out in early June 2026 and completes by mid-July 2026 (previously mid-June).

[Impact on Your Organization]

Who is affected

• Presenters participating in Teams events (town halls, webinars, structured meetings)
• Organizations using Teams Rooms on Windows or Android devices

Platforms/Services

• Microsoft Teams
• Teams Rooms on Windows
• Teams Rooms on Android
• Desktop/mobile Teams clients (for proximity join initiation)

What will happen

• Presenters can use proximity join from their personal device to connect to nearby Teams Rooms during events.
• The connected Teams Room can be used to support live presentations.
• The experience is designed to reduce setup time and simplify presenter workflows in shared spaces.
• This feature will be enabled by default.
• No changes to existing policies or configurations are required.

[Action Required/Recommendations]

No action is required to enable this feature.

Recommended actions:

• Inform presenters and meeting organizers about this improved experience.
• Update internal training or documentation for Teams Rooms and hybrid presentations.
• Review Teams Rooms configurations to ensure devices are updated and functioning as expected.

[Compliance considerations]

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

• Default-deny allowlist: All certified connectors and actions are blocked unless explicitly added. New connectors are blocked by default until an administrator reviews and allows them. Business and non-business classifications have been removed for connectors and actions to improve clarity.
• Design-time and runtime enforcement: Makers now get immediate feedback while authoring an app, flow, or agent, not only at runtime when data is changing. Makers are blocked from adding restricted connectors or actions while authoring, and the platform performs a last-mile check at runtime.
• Govern AI tools: Admins can block an MCP server just like any other connector or action.
• Action-level control: Allow a connector while disabling specific risky, deprecated, or internal actions. Triggers, internal, and deprecated actions are clearly tagged.
• Automatic scaling: Because ACP is native to environment groups, the right policy follows each environment created through personal developer environments and routing, no environment-by-environment overhead is required.
• ACP-only mode: Optionally skip classic data policy evaluation entirely for a clean governance posture.

1. Review inventory. Use Power Platform inventory (preview) under Manage > Inventory to see connector and operation usage across apps, flows, and agents so you can anticipate impact before activating ACP.
2. Test on a single environment. Apply ACP under Security > Data and privacy in the Power Platform admin center. No Managed Environments are required for a single environment. The policy remains off until you activate it.
3. Build your allowlist. Starting from default-deny, add the certified connectors and actions your teams require. New connectors are blocked by default, so plan for ongoing allowlist reviews.
4. Scale with environment group. Applying ACP across an environment group requires Managed Environments. Configure on the group’s Rules tab.
5. Run hybrid with DLP. Keep existing DLP policies in place for custom connectors, HTTP connectors, and scenarios not yet at parity while you migrate to ACP.
6. Evaluate ACP-only mode. Test it in public preview to prepare for migration off of DLP policies.

[What and Why]

The Recap app in Microsoft Teams provides a centralized experience for users to find, review, and catch up on meeting recaps. By bringing recordings, transcripts, and AI-powered summaries together, this feature improves personal productivity and helps users quickly stay informed across meetings.

Quick filters help users find the right meetings faster, while audio recap capabilities enable efficient review of multiple meetings in a podcast-style format. Users can also browse and revisit meeting recaps from the past 30 days, making it easier to stay up to date.

This message is associated with Microsoft 365 Roadmap ID 564614.

[Rollout Schedule]

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

[Impact on Your Organization]

Who is affected

•  All Microsoft Teams users

Platforms/Services

• Microsoft Teams for Windows
• Microsoft Teams for Mac
• Microsoft Teams for web
• Mobile support coming soon

What will happen

• The Recap app is a first-party Microsoft Teams core app.
• A new Recap app will be available in Teams and accessible from the app store in the left rail: 

  

• The app is pre-installed but not pinned by default.
• Users will be able to:
  • View meeting recaps from the past 30 days
  • Filter meetings by date, participants, or keywords
  • Access recaps for meetings that include a recording or transcript
  • Watch video recaps or listen to audio recaps: 

    

    

  • Generate a combined audio recap across multiple meetings: 

    

• Users can access the Recap app from the Teams app store by selecting Apps and then Recap, browse recent meetings, and open individual recaps to view or listen.
• AI-powered recap features such as audio recap, video recap, and intelligent summaries require a Microsoft 365 Copilot license.
• Users without a Copilot license can still access recordings and transcripts based on existing permissions.
• The feature is enabled by default.

[Action Required/Recommendations]

No action is required.

Consider the following recommendations:

• Review and update internal training and adoption materials.
• Communicate Copilot licensing requirements for AI-generated recap features.
• Pin the Recap app for your organization using Teams admin center (app setup policies) to improve discoverability.

[Compliance considerations]

No compliance considerations have been identified for this change.

[What and Why]

Microsoft is retiring the Office 365 E3 Developer subscription for tenants with active licenses. This change simplifies developer offerings and directs customers to supported Microsoft 365 Developer Program subscriptions. Your tenant has one or more active Office 365 E3 Developer subscriptions that are impacted by this change.

[Timeline]

• Affected tenants will receive a 90-day notice prior to license cancellation.
• On September 14, 2026, Office 365 E3 Developer licenses will be canceled.
• After cancellation, access to associated services will no longer be available unless you transition to another supported subscription.

[Impact on Your Organization]

Who is affected

• Tenants with one or more active Office 365 E3 Developer subscriptions

Platforms/Services:

• Microsoft 365 services associated with these licenses

What will happen

• Office 365 E3 Developer licenses will be canceled after the notice period.
• Access to all associated services will end if licenses are not transitioned before cancellation.
• The subscription is no longer available for purchase or renewal.
• No automatic migration to another subscription is provided.

[Action Required/Recommendations]

If the subscription is not in use, no action is required.

Complete one of the following before September 14, 2026:

• Transition to a standard Microsoft 365 or Office subscription. This is the recommended path for most customers and helps preserve existing data and workloads.
• Apply to the Microsoft 365 Developer Program (https://aka.ms/m365devprogram) if your tenant is used for development and meets eligibility requirements.
• Review dependencies including users, apps, and data.
• Migrate development workloads to a supported environment.
• Communicate this change to admins and support staff.

For additional help, contact Microsoft Support.

[Compliance considerations]

[What and Why]

Copilot Notebook, a new Copilot-powered workspace in OneNote, helps users organize, reason over, and take action on their content. This feature brings advanced Copilot capabilities directly into OneNote on Mac, enabling users to generate insights, structure ideas, and work more effectively within their notes.

A Microsoft 365 Copilot license is required to access this feature.

This message is associated with Microsoft 365 Roadmap ID 565863.

[Rollout Schedule]

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

[Impact on Your Organization]

Who is affected

• Users with a Microsoft 365 Copilot license using OneNote on Mac

Platforms/Services

• OneNote for Mac
• Microsoft 365 Copilot

What will happen

• Copilot Notebook will be available within OneNote on Mac as a new Copilot-enabled workspace.
• Users will be able to access AI-powered capabilities to organize, analyze, and act on their notebook content.
• This feature is enabled by default for users with a Microsoft 365 Copilot license.
• There is no admin control to disable the feature. Only users assigned the required license will have access. 
• There are no changes to existing admin configurations or policies.

[Action Required/Recommendation]

No action is required.

You may consider the following:

• Inform users about the availability of Copilot Notebook in OneNote for Mac.
• Ensure eligible users have appropriate Microsoft 365 Copilot licenses assigned.
• Confirm they are running the latest version of OneNote on Mac to access this feature.
• Review internal documentation or training materials to include this feature if applicable.

Learn more: [To be updated closer to launch.] What are Microsoft 365 Copilot Notebooks in OneNote? | Microsoft Support

[Compliance considerations]

[What and Why:]
Microsoft is enhancing Microsoft 365 Copilot release preferences by adding support for Microsoft Entra ID groups. This update enables admins to assign groups—not just individuals—to Standard or Deferred release audiences, providing more flexible, enterprise-ready control over how Copilot updates are deployed. This improvement supports phased rollouts, targeted validation, and stronger change management practices—helping organizations reduce risk and confidently adopt new Copilot capabilities.

[Rollout Schedule:]
General Availability (Worldwide): Rolling out from late June 2026 through late July 2026

[Impact on Your Organization:]

Who is affected:

• Microsoft 365 administrators configuring Copilot release preferences
• Organizations using Standard or Deferred release options for Microsoft 365 Copilot

Platforms/Services:

• Microsoft 365 admin center (web)
• Microsoft 365 Copilot

What will happen:

• Admins can assign Microsoft Entra ID groups to Standard or Deferred release audiences
• Groups can be used to override the tenant-wide release preference
• Enables targeted rollout scenarios such as:
• Assigning pilot groups to Standard release for early validation
• Assigning sensitive departments to Deferred release for additional review time
• Nested groups are not supported
• Total enrollment (users + group members) is limited to 100 users
• Feature is available through existing release preference controls in the Microsoft 365 admin center
• No change to end-user experience unless they are included in a targeted release group

[Action Required / Recommendations:]
No immediate action is required.

If you plan to use this capability:

• Identify or create Microsoft Entra ID groups for release targeting
• Ensure total enrolled users (including group members) remain within the 100-user limit
• Assign groups in the Microsoft 365 admin center under release preferences
• Regularly review group membership for compliance with limits
• Update internal rollout, pilot, and change management documentation

Additional resources:
Learn more about the modern change management model

[Compliance considerations:]

• This change introduces an admin control that can be configured using Entra ID group membership
• No other compliance considerations identified; review as appropriate for your organization

• PowerPlatformInfra
• PowerPlatformPlex