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

Updated April 21, 2026: We have paused rollout of Web, Mac, and Desktop releases. Android and iOS will continue to rollout as planned.

[Introduction]

We’re introducing a new way to quickly summarize emails and attachments using Copilot chat in Outlook. With a single click, users can generate concise summaries of email content and attachments, helping them stay focused and save time. This feature is available to Android and iOS users with a Microsoft 365 Copilot license and pinning enabled.

This message is associated with Microsoft 365 Roadmap ID 503316.

[When this will happen:]

• Targeted Release (Worldwide): Rollout started early October 2025; completed mid-October 2025.
• General Availability (Worldwide): Began mid-October 2025; completed mid-October 2025.

[How this affects your organization:]

Who is affected: Users with a Microsoft 365 Copilot license and pinning enabled in Outlook across Android and iOS.

What will happen:

Users will see a new option to summarize email content using Copilot chat:

• The feature will be available across Android, Desktop, iOS, Mac, Web, and both Classic and New Outlook for Windows.
• No admin configuration is required; the feature is enabled by default for eligible users.
• Existing policies are respected; no changes to admin controls are needed.

[What you can do to prepare:]

• No action is required.
• You may choose to inform users about the new summarization capability.
• If desired, update internal documentation to reflect the availability of this feature.

[Compliance considerations:]

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

Updated April 21, 2026: We have updated the timeline. This post has also been updated to remind customers that this feature is default-on for Copilot Dashboard users with full company-level data access. The export output remains de-identified, with each user represented by a hashed ID. Please review and take any actions as appropriate for your organization. Thank you for your patience.

This MC post is associated with Roadmap ID 500872.

[Introduction:]

To support deeper analysis of Copilot adoption, Microsoft is introducing a new export capability in the Copilot Dashboard. This feature allows dashboard users with company-level access to download de-identified Copilot usage metrics, aggregated by user and week, from the past six months. Organizations can use this data to track adoption trends, optimize licensing, and support AI transformation strategies.

This feature requires at least 50 Microsoft 365 Copilot licenses and applies to the Viva Insights web app.

[When this will happen:]

• Public Preview: Begins in early December 2025 (previously late November 2025), completes by late December 2025.
• General Availability (Worldwide): Begins in early May 2026 (previously late April), completes by late May 2026 (previously early May).

[How this affects your organization:]

Who is affected:

Copilot Dashboard users with full company-level data access, including senior leaders (as identified in Entra ID), admin-assigned company-level users, delegates with company-level access, as well as global analysts and admins. 

Note: Group managers with data access limited to their own teams will not have access to this feature.

What will happen:

• Users will be able to export de-identified, row-level Copilot usage metrics from the dashboard.
• The dataset includes weekly, user-level metrics from the past six months.
• The export supports Copilot usage analysis across apps (such as Word, Excel, Teams), and includes two attributes: Organization, and Job function.
• Organizations can use the data to track usage patterns, generate insights to inform adoption strategies, optimize licensing, and measure ROI.
• The feature is enabled by default for eligible users.
• Admins can manage access via Viva Feature Access Management (VFAM) settings, under Module: Viva Insights; Feature: Copilot Metrics Export.
• No impact to user workflow unless accessed by eligible users.

Screenshot 1 – View of the new Microsoft Copilot dashboard: 

Screenshot 2 – Example of output: 

[What you can do to prepare:]

• Review the assignment of the Copilot dashboard users with full company-wide data access and adjust VFAM policies as needed.
• Communicate the upcoming feature to eligible users so they know what to expect.
• No admin setup is required to start using the export.
• Admins can disable the feature at the tenant or group level at any time using VFAM settings.

Learn more: 

Microsoft Viva Feature access management | Microsoft Learn

Connect to the Microsoft Copilot Dashboard for Microsoft 365 customers | Microsoft Learn

[Compliance considerations:]

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

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

We’re introducing cross-tenant group synchronization, a new capability that enables organizations to synchronize security groups across Microsoft Entra tenants. This feature simplifies collaboration scenarios by allowing shared access to resources across tenants while maintaining centralized group management. It also streamlines administration of multiple tenants by centralizing group membership control, reducing duplication and manual overhead. The new group sync functionality will be part of the Microsoft Entra ID Governance / Microsoft Entra Suite license. 

This message is associated with Microsoft 365 Roadmap ID 518221.

• Public Preview: Rollout begins in late January 2026 and completes by late January 2026.
• General Availability (Worldwide, GCC, GCC High, DoD): Rollout begins in late April 2026 and completes by end of May 2026 (previously late April).

• Who is affected: Admins managing Microsoft Entra tenants who want to enable cross-tenant group synchronization.
• What will happen:
  • No impact unless you opt in during Public Preview.
  • Admins can enable synchronization by updating attribute mappings.
  • Cross-tenant access policies in the target tenant must allow group synchronization.

• Identify groups that require synchronization into other tenants.
• Collaborate with admins of other tenants to align on supported scenarios and business processes.
• Review and update attribute mappings and cross-tenant access policies as needed.

Learn more: Configure cross-tenant synchronization – Microsoft Entra ID | Microsoft Learn

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

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

[Introduction]

Engage will retire live events powered by Teams Live Events effective April 27, 2026. Existing live events already scheduled will continue to be supported through February 28, 2027. We encourage customers to transition to events in Engage powered by Teams town halls, which offer an improved experience for large-scale digital and hybrid events.

[When this will happen:]

• Effective April 27, 2026: You will no longer have the option to schedule a live event in Engage powered by Teams Live Events.
• Through February 28, 2027: Engage will continue to support any live events powered by Teams Live Events that were scheduled before April 27, 2026.

[How this affects your organization:]

Who is affected: Organizations using live events in Engage powered by Teams Live Events.

What will happen:

• You will no longer be able to schedule a live event in Engage powered by Teams Live Events starting April 27, 2026.
• Engage will continue to support already scheduled live events powered by Teams Live Events through February 28, 2027.

[What you can do to prepare:]

• Migrate to events in Engage powered by Teams town halls.
• Review and update internal documentation to reflect this change.

Explore these resources:

• Organize a Live event with Teams town hall 
• Plan for Teams town halls
• Virtual Events Graph APIs
• Customer Hub events readiness sessions – recommended sessions for Teams live event users transitioning to Teams town halls:
  • What’s new in Microsoft Teams town halls and webinars
  • Migrating from Teams live events to town halls
  • Tips, tricks, and traps for town halls and webinars in Microsoft Teams

[Compliance considerations:]

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

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

[Introduction]

Microsoft is introducing Microsoft 365 Copilot Chat within Microsoft Forms, along with a new Forms Agent integration tailored to help creators design, distribute, and analyze forms more effectively. This update streamlines form creation and insights by providing AI-driven suggestions, improvements, and analysis.

This message is associated with Roadmap ID 553136.

[When this will happen:]

• General Availability (Worldwide): We’ll begin rollout early May 2026 (previously early March) and expect to complete by late May 2026 (previously late March).

[How this affects your organization:]

Who is affected: Users with an active Microsoft 365 Copilot license who create or edit forms in Microsoft Forms on the web.

What will happen:

• Users will find a new Copilot icon in Microsoft Forms.
• Forms Agent and Copilot Chat will be available directly in the form-editing experience.
• Users can perform tasks such as:
  • Getting AI‑generated suggestions to refine or improve their form or quiz.

  Screenshot 1: Select the Copilot button to chat, get suggestions, and effortlessly improve your form

  

  • Adjusting question clarity and form structure with support from Forms Agent.
  • Drafting invitation messages.
  • Analyzing survey or quiz results with AI assistance.

  Screenshot 2: Unlock quick, actionable insights from your data, and chat to dive deeper

  

• This feature will be on by default for Copilot licensed users and can be disabled by admins.
• Existing Copilot policies apply; no new admin controls are required.

[What you can do to prepare:]

No action is required.

Recommended:

• Inform helpdesk staff about new AI capabilities.
• Update internal documentation as needed.
• Review Copilot licensing and policy settings.

Learn more: 

• Welcome to Copilot in Forms – Microsoft Support
• Get started with Surveys Agent in Microsoft 365 Copilot – Microsoft Support
• Microsoft Forms Blog | Microsoft Community Hub (will be updated before rollout)

[Compliance considerations:]

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

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

[Introduction]

To streamline and modernize reporting experiences across Microsoft 365, we are retiring the Outlook for Windows Usage Report in the Exchange admin center (EAC). Admins can continue accessing Outlook usage information in the Microsoft 365 admin center (MAC), which offers a more complete and up‑to‑date reporting experience across Microsoft 365 apps.

[When this will happen]

• Retirement will begin in mid-June 2026 (previously mid‑April).
• Retirement will complete in mid-July 2026 (previously mid‑May).

[How this affects your organization]

Who is affected

• Admins who use the Exchange admin center (EAC) to view Outlook for Windows usage data.

What will happen

• The Outlook for Windows Usage Report will be removed from the EAC.
• No replacement Outlook usage reporting will remain in the EAC after this retirement.
• Admins can continue accessing Outlook for Windows usage insights through the Microsoft 365 admin center (MAC): Reports > Usage > M365 Apps > Usage > Outlook for Windows
• MAC provides consolidated usage reporting with charts and tables to help admins understand usage patterns across Outlook and other Microsoft 365 apps.
• No impact to Outlook for Windows functionality for users.
• This report retirement will occur automatically; no opt‑out or admin toggle will be available.

[What you can do to prepare]

• No admin action is required.
• If your organization references the EAC usage report in documentation or internal processes, update those materials before the retirement is complete.

Learn more: Microsoft 365 Reports in the admin center – Microsoft 365 Apps usage | Microsoft 365 | Microsoft Learn

[Compliance considerations]

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

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

[Introduction]

We’re releasing an improvement to Microsoft Teams that syncs your recently used emojis and reactions across devices. With this update, users will see the same set of “recently used” emojis when using Teams on Android, iOS, Mac, Windows desktop, and Teams for the web, creating a more consistent and seamless experience when communicating across chats and channels. This enhancement aligns with customer feedback requesting a unified emoji experience across platforms.

This message is associated with Microsoft 365 Roadmap ID 554927.

[When this will happen]

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

[How this affects your organization]

Who is affected

• All Microsoft Teams users across supported clients.

What will happen

• Recently used emojis and reactions will sync across devices.
• Users will see the same “recently used” list regardless of which Teams client they use.
• The feature will be enabled by default; no configuration is required for rollout.
• Existing Teams admin settings and messaging policies will continue to apply.
• There is no impact to message flow, data storage, compliance boundaries, or customer data pathways.

[What you can do to prepare]

No action is required. This update will roll out automatically.

Admins may optionally:

• Inform helpdesk or support teams about this user experience update.
• Update internal documentation if you reference emoji behavior or Teams UI details.
• Review your Messaging settings and Messaging policies if you manage custom emoji usage.

Learn more about emoji and reaction usage in Microsoft Teams: Send an emoji, GIF, or sticker in Microsoft Teams | Microsoft Support

[Compliance considerations]

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

This feature does not introduce new data storage, processing changes, AI/ML capabilities, communication pathways, admin reporting changes, or modifications to Purview‑governed workflows. 

• Change Agent status to DND after a notification is rejected
• Change Agent status to Inactive after a missed notification

[Introduction]

We are updating the Chat-only Copilot experience in Excel to better align with the editing experience. As part of this update, users who want to access additional Copilot agents (such as Researcher or Analyst) can do so by selecting the “…” menu in the header and choosing M365 Copilot.

[When this will happen]

• General Availability (Worldwide): Rollout starts in late April 2026 and is expected to be complete by late April 2026.

[How this affects your organization]

Who is affected

All Excel users with Microsoft 365 Copilot licenses

What will happen

• Users can continue to use the chat‑only Copilot experience in Excel to ask questions, analyze data, and receive insights without modifying workbook content.
• However, users who want to access additional Copilot agents (such as Researcher or Analyst) can do so by selecting the “…” menu in the Excel header and choosing M365 Copilot:

  

• Existing Microsoft 365 Copilot licensing and policy controls are respected.
• There is no change to workbook editing behavior or data permissions.

[What you can do to prepare]

No admin action is required.

• Inform helpdesk and support teams about the new access path to Microsoft 365 Copilot from Excel.
• Update internal documentation or training materials that describe Copilot experiences in Excel.
• Review Microsoft 365 Copilot documentation if you want to understand available agents and licensing requirements.

Learn more: Edit with Copilot in Excel | Microsoft Support

[Compliance considerations]

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

[Introduction]

To better align with Microsoft Forms branding and improve clarity for customers, the Surveys agent in Microsoft 365 Copilot is being renamed to Forms agent. This update is a naming and visual refresh only and does not introduce any functional changes. The rename helps users more easily associate the agent with Microsoft Forms capabilities.

Screenshot: The newly named agent provides the same experience:

[When this will happen:]

• General Availability (Worldwide): We will begin rolling out in late April 2026 and expect to complete by late May 2026.
• During a transitional period, users will see “Forms (formerly Surveys)” before the agent appears as “Forms.”

[How this affects your organization:]

Who is affected:

• All users who access the Surveys agent in Microsoft 365 Copilot
• A Microsoft 365 Copilot (Premium) license is required to use this feature

What will happen:

• The Surveys agent name will change to Forms agent.
• For a limited time, the agent will appear as “Forms (formerly Surveys).”
• The agent icon will update to align with Microsoft Forms branding.
• No functional changes to survey creation, distribution, or analysis.
• The feature remains enabled by default with no policy changes required.

[What you can do to prepare:]

No action is required.

We recommend the following optional steps:

• Inform helpdesk and support staff about the rename to reduce potential user confusion.
• Update any internal documentation or training materials that reference the “Surveys agent.”
• Share a brief internal notice with users highlighting that only the name and icon are changing.

[Compliance considerations:]

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

[Introduction]

To help reduce visual clutter and keep SharePoint team site homepages focused on active content, we’re introducing an automatic collapse behavior for the News web part. When a team site homepage hasn’t been edited in 30 days and no news has been published on the site, the News web part will collapse by default. This change will help surface relevant information while preserving existing News authoring and configuration capabilities.

[When this will happen]

• Targeted Release: Rollout will begin in late April 2026 and is expected to complete by late April 2026.
• General Availability (Worldwide, GCC, GCC High, and DoD): Rollout will begin in late April 2026 and is expected to complete by mid-May 2026.

[How this affects your organization]

Who is affected

• All Microsoft 365 tenants using SharePoint Online
• Team site homepages that include the News web part

What will happen

• The News web part will automatically collapse on a team site homepage if the homepage has not been edited for 30 days and no News posts have been published.
• This behavior will be enabled by default.
• Site owners and users will be able to expand the News web part at any time.
• Publishing new News posts or editing the homepage will restore normal visibility of the News web part.
• This change will not affect News authoring workflows, configuration options, or permissions.

[What you can do to prepare]

• No action will be required from administrators.
• You may want to inform site owners about this automatic behavior.
• Consider updating internal SharePoint documentation or helpdesk guidance if you describe default homepage behavior.

[Compliance considerations]

[Introduction]

Live chat in Microsoft Teams enables small and medium businesses to connect with customers through a chat widget embedded on their websites. Website visitors can chat directly with business employees, who receive and manage these conversations in Teams. Transcripts from live chats are stored in a central team and channel, which organizations can use for ticket management and follow‑up.

To better align the feature name with how customers use it, Microsoft will rename Live chat to Customer Connect. This is a name change only; there are no functional or behavioral changes.

[When this will happen]

General Availability (Worldwide): We will begin rolling out this change in late April 2026 and expect to complete the rollout by the end of May 2026.

[How this affects your organization]

Who is affected

• Microsoft 365 tenants that use Live chat in Microsoft Teams
• Teams administrators who manage Live chat settings
• Users who support customers through Live chat conversations in Teams

What will happen

• Live chat will be renamed to Customer Connect across:
  • Teams admin settings
  • In‑product references
  • Microsoft documentation
• There will be no changes to functionality, configuration, or data handling.
• If your organization already uses Live chat:
  • Existing teams and channels created for Live chat will not be renamed.
• If your organization begins using this capability after the name change:
  • The team and channel used to manage live chats will be named Customer Connect.
• The feature will remain enabled and managed the same way as before.

Learn more: Set up and manage live chat | Microsoft Teams | Microsoft Learn

[What you can do to prepare]

No action is required.

You may consider updating internal documentation or informing helpdesk and support staff of the new Customer Connect name to reduce potential confusion.

[Compliance considerations]

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

Updated April 22, 2026: We have updated the timeline and 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.

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

We’re improving how shared voicemails for Call Queues are managed in Microsoft Teams. Previously, shared voicemail messages were primarily accessed in Outlook, with limited visibility in Teams. This update brings shared voicemail management directly into the Queues app in Teams, helping queue members track and respond to missed calls more efficiently in one place.

[When this will happen]

• General Availability (Worldwide): Rollout will begin in late April 2026 and is expected to complete by late April 2026.

[How this affects your organization]

Who is affected

• Organizations using Call Queues in Microsoft Teams
• Queue members who manage missed calls
• Microsoft 365 commercial tenants (Worldwide)
• Users must be licensed with Teams Phone and Teams Premium.

What will happen

• This experience will be available to eligible users through the Queues app.
• Missed calls with associated shared voicemails will appear in the Queues app under Shared call history: 

  

• Queue members will be able to:
  • Listen to shared voicemail messages
  • Read voicemail transcripts
  • Update voicemail status (for example, In progress or Completed) to track follow-up
• Shared voicemail visibility varies by destination type:
  • Shared voicemails are visible in Outlook/Exchange for all supported destination types.
  • Shared voicemail visibility in the Teams client depends on whether a Microsoft 365 group is connected to a Teams channel.
  • Shared voicemails are visible in the Teams Queues app for all supported destination types, including:
    • Microsoft 365 groups
    • Distribution lists
    • Mail-enabled security groups
• Shared voicemail message delivery also varies by destination type:
  • When using a Microsoft 365 group, voicemails are delivered to the group mailbox.
  • When using a distribution list or mail-enabled security group, each member receives a copy in their personal Outlook inbox.
• There are no changes to the shared voicemail experience in Outlook.
• The standard Teams Calls experience continues to provide limited shared voicemail functionality outside of the Queues app.
• Shared voicemail support for Auto Attendants will be added in a future update (expected by June 2026).

[What you can do to prepare]

• No action is required if your organization already uses Call Queues with Teams Premium.
• Ensure the Queues app is available to users who manage call queues.
• Optionally, pin the Queues app for users to improve discoverability:
  • Teams admin center > Teams apps > Setup policies > select a policy > Pinned apps > Add apps > search for Queues > Add > Save
• If necessary, you can manage whether the Queues app is available org‑wide (use with caution):
  • Teams admin center > Teams apps > Manage apps > Actions > Org‑wide app settings > Microsoft apps > Off > Save

Note: Turning off Microsoft apps also affects other apps such as Insights and Tasks.

• To delegate queue management tasks (for example, managing membership or greetings), review and assign voice applications policies to authorized users.
• Consider informing queue members and helpdesk staff about the improved shared voicemail experience in Teams.

Learn more: 

• Manage Queues app for Microsoft Teams in your organization | Microsoft Teams | Microsoft Learn
• Manage Shared Voicemail for Auto Attendants and Call Queues | Microsoft Teams | Microsoft Learn
• Set the Shared call history for call queue template (optional) – Create a Call queue in Microsoft Teams | Microsoft Teams | Microsoft Learn
• Shared call history for Call queues | Microsoft Teams | Microsoft Learn

[Compliance considerations]

<

[Introduction]

Microsoft Entra ID Governance now includes Account discovery, a new capability that helps administrators identify application accounts that exist outside of Microsoft Entra ID. Account discovery finds local and orphaned accounts in connected applications and identifies accounts that can be matched to Microsoft Entra ID users. This improves visibility into existing access, simplifies application onboarding into governance, and helps organizations bring unmanaged access under centralized control.

This message is associated with Microsoft 365 Roadmap ID 559476.

[When this will happen:]

• Public Preview (Worldwide): Rollout began in mid-April 2026 and is expected to complete by late April 2026.
• General Availability (Worldwide, GCC): We expect to begin rolling out in early August 2026 and complete by late August 2026.

[How this affects your organization:]

Who is affected:

• Administrators managing application access using Microsoft Entra ID Governance.
• Tenants with provisioning configured for supported third-party applications (for example, Salesforce or Atlassian).

What will happen:

• Administrators can opt in to preview Account discovery for supported applications.
• The feature discovers local and orphaned accounts that exist outside of Microsoft Entra ID.
• Discovered accounts can be matched to Microsoft Entra ID users, improving access visibility.
• There is no impact to users and no change to existing access unless administrators take action.
• The feature is off by default and requires admin opt‑in during preview.

[What you can do to prepare:]

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

If you want to test the functionality:

• Ensure you have a provisioning configuration for a supported third‑party application (for example, Salesforce or Atlassian).
• Verify your tenant has Microsoft Entra ID Governance or Microsoft Entra Suite licenses.
• Inform identity and access management administrators about the preview to avoid confusion when reviewing access data.

Learn more: Discover identities in target applications with Account Discovery (preview) | Microsoft Learn

[Compliance considerations:]

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

[Introduction]

Microsoft Teams is introducing Efficiency Mode, a performance-optimized experience designed for hardware-constrained devices. This change improves app responsiveness and meeting quality by adjusting resource usage based on device capabilities.

This message applies to Teams for Windows desktop and Teams for Mac desktop and is associated with Roadmap ID 560055.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• Users running Microsoft Teams on hardware‑constrained devices (for example, devices with limited CPU, memory)
• 
  
• What will happen:

• Efficiency Mode is enabled by default on eligible devices.
• An Efficiency Mode indicator appears in the Teams app title bar.
• When enabled:
  • Video resolution sent from the user’s camera is dynamically adjusted in meetings.
  • The app launches without a pre-selected chat and shows a static image in the message pane.
• Users can opt out via Settings > General > “Never use efficiency mode.”

[What you can do to prepare:]

• No action is required if the default behavior works for your organization.
• Consider informing helpdesk teams about the new mode and opt-out option.
• Update internal documentation if applicable.

[Compliance considerations:]

Users can enable or disable the feature themselves. No other compliance considerations were identified.

• AI can help you fill out forms quickly by using images, files, and emails to save you time on tedious tasks.
• Model-driven app users can add a file, including images, or an email for Copilot to suggest form fields.

• ASP.NET Core is used
• Scan Cab is used to check for update compliance
• The April 2026 Scan Cab was deployed before 10:00 PM PT on April 21, 2026

• Updated Scan Cab: Download the new Scan Cab here
• CVE-2026-40372: ASP.NET Core Elevation of Privilege Vulnerability
• Announcing a smaller WSUS Scan Cab – Microsoft Tech Community: Learn more about WSUS and the Scan Cab process
• Using WUA to Scan for Updates Offline – Win32 apps | Microsoft Docs: Windows Update Agent (WUA) can be used to scan computers for security updates without connecting to Windows Update
• WSUS and the Catalog Site | Microsoft Docs: The Catalog Site used by WSUS to import updates and drivers

• Secure Boot AMA – April 23, 2026, 8:00 AM PDT
• Secure Boot AMA – May 18, 2026, 8:00 AM PDT

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

What it is

Microsoft is rolling out a new feature to streamline how app and agent availability is managed across Teams, Outlook, and Microsoft 365 Copilot. Until now, IT admins configured availability settings separately in both the Microsoft 365 Admin Center (MAC) and the Teams Admin Center (TAC), which led to mismatches. With this update, you’ll be able to unify availability policies for apps and agents across both portals, making app management more consistent and efficient.

This message is associated with Microsoft 365 Roadmap ID 393931, 485712 and 503105.

When this will happen:

We will begin rolling out this feature late September 2025 and expect to complete by August 2026 (previously end of June).

1. Phase 1 – Default Tenant Unification of App/Agent Availability

We will begin rolling out this feature at the end of September 2025. This initial phase targets tenants that have never modified their organization-wide defaults, app availability, or block/unblock in either the Microsoft 365 admin center or the Teams admin center. At the end of this phase, agent and app manageability will be unified across both Microsoft 365 admin center and Teams admin center ensuring agent and Microsoft 365 apps availability policies are in alignment for all future administrative changes. This message is associated with Microsoft 365 Roadmap ID 393931.

2.Phase 2 – Modified Tenants Unification of App/Agent Availability

This phase targets tenants that have previously modified their organization-wide defaults, app availability, or block/unblock settings in either admin center. These tenants will be transitioned to a unified management experience across both Microsoft 365 and Teams admin centers.

• For tenants with no agent or app availability differences across both admin centers, guidance will be provided to help maintain unified availability policy for all future changes. We will begin rolling out this feature in early November 2025.
  
  • This message is associated with Microsoft 365 Roadmap ID 485712 & 503105.