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

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

We’re introducing an enhanced organization chart experience in the Profile Card in Microsoft Teams for Windows Desktop, Mac, and Teams on the web. This update improves the user interface and navigation while maintaining the core browsing functionality. These changes are based on user feedback to streamline org chart exploration and reduce friction in navigating team structures.

This feature is associated with Microsoft 365 Roadmap ID: 500696.

Targeted Release: We will begin rolling out in mid-March 2026 (previously early February) and expect to complete in late March 2026 (previously mid-February).

General Availability (Worldwide): We will begin rolling out in late March 2026 (previously mid-February) and expect to complete in late April 2026 (previously early April).

Who is affected: All users of Microsoft Teams on Windows Desktop, Mac, and web platforms.

What will happen:

• The organization chart in the Profile Card will receive UI/UX enhancements to improve navigation and usability.
• The focused individual remains centered when the manager chain is collapsed, improving visual clarity.
• Fewer clicks are needed to view another person’s Profile Card from the current view, reducing navigation effort.
• New navigation buttons allow users to scroll through previously viewed individuals within the same Profile Card instance, streamlining org chart exploration.
• The feature is enabled by default and requires no configuration changes.

Screenshot 1 – Updated Profile Card with centered individual and collapsed manager chain:

Screenshot 2 – Expanded organization chart view:

What you can do to prepare

• No admin action is required at this time.
• We recommend informing users about the improved navigation experience to help them take full advantage of the update.
• Update internal documentation or training materials if they reference the Profile Card experience.

Learn more (to be updated closer to rollout): Profile cards in Microsoft 365 | Microsoft Support 

Compliance considerations

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

Updated April 15, 2026: We have updated the timeline, added known limitations, and confirmed private channel support. Thank you for your patience.

[Introduction]

We’ve extended the migration deadline to give organizations more time to transition. The following capabilities are now supported with Workflows webhooks:

1. Posting messages using MessageCard‑formatted payloads (no reformatting required; however, button rendering will not be supported)
2. Posting messages to shared channels

These updates significantly reduce migration friction for customers currently using Office 365 Connectors.

New — April 2026: Private channels are now supported for Workflows webhooks through the Power Automate portal. Selection of private channels directly within the Workflows app in Teams is rolling out fully by April 20, 2026.

Office 365 Connectors will be permanently disabled on the following schedule: 

• Deprecation rollout starts: May 18, 2026
• Deprecation rollout completes: May 22, 2026

This is the final deprecation timeline. All connector-based webhooks must be migrated to Workflows before May 18, 2026.

[How this affects your organization:]

Who is affected: Organizations using Office 365 Connectors in Microsoft Teams

[Known Limitations:]

When using Workflows webhooks, please be aware of the following limitations:

• Bot icon and name customization is not available when posting Adaptive Cards via webhook. Messages will display with the default Workflows bot (Flow bot) identity. Custom icons and display names are not supported for Adaptive Card payloads.
• Interactive cards are not supported for MessageCard-formatted payloads. If your scenario requires interactive elements such as actionable buttons or input fields, you will need to use Adaptive Cards instead of MessageCards. MessageCard-formatted payloads will render content but will not support button rendering or other interactive components.

If you are currently using Office 365 Connectors in Microsoft Teams:

• Review your existing Office 365 Connector usage.
• Begin migrating to Workflows webhooks as soon as possible.
• Complete migration before May 18, 2026 to avoid service disruption.
• If your workflows rely on interactive card elements, update your payloads to use Adaptive Cards.
• Test your migrated workflows to ensure they function as expected.

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

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

[Introduction]

Starting in March 2026, Microsoft Entra ID will introduce passkey profiles and synced passkeys to General Availability (GA). This update allows administrators to opt in to a new passkey profiles experience that supports group-based passkey configurations and introduces a new passkeyType property.

Important: Only tenants that already have Passkeys (FIDO2) enabled are affected by this update. 

The passkeyType property enables admins to configure:

• Device-bound passkeys
• Synced passkeys
• Both

If your tenant already has Passkeys (FIDO2) enabled and you do not opt in to passkey profiles during the initial rollout window, your tenant will be automatically migrated to the passkey profiles schema at the date range specified below. When this occurs: 

• Existing Passkey (FIDO2) authentication method configurations will be moved into a Default passkey profile. 
• The passkeyType value will be set based on the tenant’s current attestation settings. Synced passkeys will be enabled for tenants with attestation enforcement disabled. 
• No new authentication methods are enabled as part of this migration. 
• This migration also impacts Authentication methods registration campaign set to “Microsoft managed” state, which uses passkey configuration settings to determine which registration prompts are shown to users.

Authentication Methods Registration Campaign changes (Microsoft-Managed Only)

Tenants are impacted when all the following conditions are met:

• The Passkeys (FIDO2) authentication method policy is Enabled
• Authentication methods registration campaign is set to “Microsoft managed” state
• Allow self-service setup is Enabled
• Target specific AAGUIDs is not selected (no AAGUID restrictions configured)
• The Authentication Methods Registration Campaign state is set to Microsoft-managed
• The tenant has at least one user enabled for both synced passkeys and device‑bound passkeys
  • Only users who are enabled for both synced passkeys and device‑bound passkeys, with no passkey profile restrictions configured (i.e. attestation enforcement, AAGUID restrictions), will receive a passkey registration nudge during sign‑in.

For these tenants, Microsoft-managed registration campaign settings will be updated after passkey profile automatic migration is complete. We will roll out changes incrementally to in-scope tenants according to the timeline outlined below. 

[When this will happen]

Passkey profile and Synced passkeys General Availability

• Public cloud Worldwide: Rollout begins in early March 2026 and is expected to complete by late March 2026 
• GCC, GCC High, DoD clouds: Rollout begins in early May 2026 and is expected to complete by late May 2026 
• USNat, USSec: Rollout begins in early July 2026 and is expected to complete by late July 2026 

Automatic migration for existing passkeys (FIDO2) enabled tenants

• Public cloud Worldwide: Rollout begins in early May 2026 and is expected to complete by late June 2026
• GCC, GCC High, DoD clouds: Rollout begins in early August 2026 and is expected to complete by late August 2026
• USNat, USSec: Rollout begins in early August 2026 and is expected to complete by late August 2026

Authentication Methods registration campaign changes in Microsoft-Managed state (for in-scope tenants):

• Public cloud Worldwide: Rollout begins in early May 2026 and is expected to complete by late June 2026 

[How this affects your organization]

Automatic migration for existing passkeys (FIDO2) enabled tenants 

What will happen:

If you have not opted in to passkey profiles by your automatic enablement period, your tenant will be migrated to passkey profiles.

• Your existing Passkey (FIDO2) configurations will be migrated into a Default passkey profile
• New passkeyType property will be auto-populated
  • If enforce attestation is enabled, then device-bound allowed
  • If enforce attestation is disabled, then device-bound and synced allowed
• Any existing key restrictions will remain intact
• Any existing user targets will be assigned to the Default passkey profile

Authentication Methods registration campaign changes in Microsoft-Managed state (for in-scope tenants)  

What will happen:

Microsoft-managed registration campaign settings will be updated: 

• “Targeted authentication method” will change from Microsoft Authenticator to “passkeys (FIDO2)”. 
• “Days allowed to snooze” setting will change from 3days to “1 day”. This setting will no longer be configurable. 
• “Limited number of snoozes” setting will change from Enabled to “Disabled”. This setting will no longer be configurable. 
• The default user targeting will be updated from voice call or text message users to all multifactor authentication (MFA) capable users.  

What is the end user impact: 

Once the above changes have taken effect, users targeted in the registration campaign will begin to receive passkey registration nudges during sign-in flows after they have completed multifactor authentication. 

[What you can do to prepare]

If you want a configuration different from the migration defaults, review the timeline above and opt in to passkey profiles before your tenant’s automatic enablement window begins. Then configure the Default passkey profile’s passkeyType to your preferred values.

We also recommend:

• Review your registration campaign configuration, especially if its set to Microsoft-managed. If you do not want registration campaign to target passkeys, you can: 
  • Switch the registration campaign state to Enabled and continue targeting Microsoft Authenticator, or 
  • Set the registration campaign state to Disabled.
• Update runbooks and help content so your help desk and end users understand any changes in passkey availability or behavior. 

Learn more:

• Enable passkeys for your organization – Microsoft Entra ID | Microsoft Learn 
• How to Enable Passkey (FIDO2) Profiles in Microsoft Entra ID (preview) – Microsoft Entra ID | Microsoft Learn
• How to Enable Synced Passkeys (FIDO2) in Microsoft Entra ID (preview) – Microsoft Entra ID | Microsoft Learn
• Synced passkeys FAQ – Microsoft Entra ID | Microsoft Learn

[Compliance considerations]

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

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

[Introduction]

We’re introducing ad-hoc room reservation directly from the Microsoft Teams Rooms on Windows console. This update enables users to reserve an available room on the spot without relying on a personal device or hallway panel, supporting quick, spontaneous meetings and helping reduce scheduling conflicts. This feature requires a Teams Rooms Pro license. 

This message is associated with Microsoft 365 Roadmap ID 548648.

[When this will happen]

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

[How this will affect your organization]

Who is affected

• Users and admins of Teams Rooms on Windows with Teams Rooms Pro licenses.

What will happen

• After this feature becomes available on room devices, users can reserve an available room directly from the Teams Rooms calendar by choosing Reserve and selecting an end time: 

  

• End times appear in 15-minute increments for up to the end of the day or until the next scheduled meeting, whichever comes sooner:

   

• The feature is enabled by default.
• Admin controls will be available on the Teams Rooms Pro Management portal: Rooms > Settings > Meetings > Allow ad-hoc room reservation.

[What you can do to prepare]

• No action is required before rollout.
• Notify users of the new reservation workflow.
• Update internal training or documentation.
• Use Teams Rooms Pro Management portal or device settings if you want to restrict ad-hoc reservations.

[Compliance considerations]

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

Updated April 14, 2026: After further review, we have decided not to move forward with this change at this time. You can refer to MC1279092 for updates. We apologize for any inconvenience this may cause and appreciate your understanding.

[Introduction]

As previously announced in MC1221452, Microsoft Registration Campaigns will support Passkeys (FIDO2) as an additional authentication method starting in early April 2026. This update helps organizations accelerate adoption of phishing‑resistant credentials by allowing administrators to opt users into Passkeys and deliver Passkey registration nudges during sign‑in.

Please refer to MC1279092 for updates. 

[When this will happen] 

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

[How this affects your organization]

Who is affected

• Microsoft 365 tenants using Microsoft Registration Campaigns
• Tenants configured in either Microsoft‑managed or Enabled states
• Users who are MFA‑capable and eligible for Passkeys (FIDO2)

What will happen

Microsoft‑managed state

Your tenant will be impacted when all of the following conditions are met:

• The Passkeys (FIDO2) authentication method policy is enabled.
• Allow self‑service setup is enabled.
• Target specific AAGUIDs is not selected (no AAGUID restrictions configured).
• The Authentication Methods Registration Campaign state is set to Microsoft‑managed.

When these conditions are met, the following settings will update automatically:

• The targeted authentication method will change from Microsoft Authenticator to Passkeys (FIDO2).
• Days allowed to snooze will change from three days to one day. (This setting will no longer be configurable.)
• Limit number of snoozes will be disabled. (This setting will no longer be configurable.)
• Targeting will expand to all MFA‑capable users. (This setting will no longer be configurable.)
• Default user targeting will change from voice call or text message users to all multifactor authentication (MFA)–capable users.

Affected users will receive Passkey registration nudges at sign‑in after completing MFA.

We will roll out these changes incrementally over time to in‑scope tenants.

Enabled state

Passkey (FIDO2) can be selected as the Targeted Authentication Method when Microsoft Registration Campaigns are in the Enabled state. 

Note: Registration Campaigns support targeting only one authentication method at a time—either Microsoft Authenticator or Passkeys (FIDO2), but not both simultaneously.

[What you can do to prepare]

Opting into Passkey Registration Nudges:

• The user is MFA‑capable
  • They have at least one registered MFA method
  • They can successfully complete MFA at sign‑in
• Under Authentication methods > Policies, the user is in scope for Passkeys (FIDO2)
• Under Authentication methods > Policies > Passkeys (FIDO2) > Configure, make sure you have Allow self-service set up checked. 

Important Guidance:

We will roll out these changes incrementally to in-scope tenants starting in early April. This rollout will take time, and even if your tenant meets the eligibility criteria, you may not see the changes immediately. 

Enabled State 

Over time, we will incrementally refine the logic for Passkeys nudges in Microsoft Registration Campaigns to guide users toward the appropriate passkey registration experience based on their passkey profile scope. Initially, the logic may not account for every edge‑case scenario, but we are actively expanding and improving it on an ongoing basis. When users have passkey profile restrictions (for example, AAGUID restrictions), the registration experience triggered by the nudge may not be optimal.   

Using Passkeys Despite Restrictions

You can still set Passkeys as the target authentication method in Microsoft Registration Campaigns. However, users may encounter a poor or confusing experience if they have passkey profile restrictions.

Example: 

If a user is scoped into specific AAGUID synced passkeys only, they may see a Passkey nudge at sign‑in. If they attempt to register a device‑bound passkey, the registration will fail because they are not in scope for that passkey type. 

Recommended next steps

• Review your Registration Campaign state by early April 2026.
• Communicate this change to helpdesk or support teams.
• Update internal documentation on authentication method enrollment.
• If you prefer to continue targeting Microsoft Authenticator, verify this configuration before rollout.

Learn more: How to enable passkey (FIDO2) profiles in Microsoft Entra ID (preview) | Authentication | Microsoft Entra ID | Microsoft Entra | Microsoft Learn

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

[Introduction]

We are adding new Copilot metrics across Microsoft 365 apps to help you better understand how users engage with Copilot. These metrics include actions taken in the Microsoft 365 Copilot app, Microsoft Edge, and OneNote, and intent-based usage across Outlook, Word, Excel, and PowerPoint. This update expands visibility into how users adopt Copilot and supports improved insights in the Copilot Dashboard and Advanced Analysis in Copilot Analytics. 

This message is associated with Microsoft 365 Roadmap ID 557981.

[When this will happen]

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

[How this affects your organization]

Who is affected

• This capability is available to users who are licensed for Microsoft 365 Copilot.
• All Microsoft 365 tenants with access to Copilot Dashboard or Copilot Analytics in Viva Insights

What will happen

• New metrics will appear in the Copilot Dashboard and Advanced Analysis.
• You will be able to track Copilot usage in the Microsoft 365 Copilot app, Microsoft Edge, and OneNote:

   

  

• Additional intent-based scenarios will be measured in Outlook, Word, Excel, and PowerPoint. These scenarios include suggested replies, translation, coaching, and clean data.
• The feature will be enabled automatically for all tenants.
• No configuration changes or policy updates are required.

[What you can do to prepare]

• No action is required before rollout.
• You may choose to notify relevant teams about the new metrics.
• Update internal documentation if your organization tracks Copilot usage analytics.
• Review updated online documentation when it becomes available in early May.

[Compliance considerations]

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

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

[Introduction]

Intelligent summaries in Copilot Dashboard help you quickly understand what’s driving Copilot adoption in your organization. These AI‑generated insights highlight key usage trends, areas of success, and opportunities where focused attention can accelerate value. Suggested prompts guide deeper exploration of underlying drivers and adoption patterns.

This message is associated with Microsoft 365 Roadmap ID 557681.

[When this will happen]

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

[How this will affect your organization]

Who is affected

• Admins using the Microsoft 365 Copilot Dashboard in Microsoft Viva and Microsoft 365

What will happen

• Intelligent summaries will appear automatically in the Copilot Dashboard:

   

• Admins will see AI‑generated insights that highlight adoption trends and key usage patterns.
• Suggested prompts will be available to help admins drill into specific drivers and areas of opportunity.
• No configuration changes are required; the feature is on by default for eligible tenants.
• Existing admin controls and permissions remain unchanged.
• There is no user workflow impact.

[What you can do to prepare]

No action is required before rollout.

If helpful for your organization, you may:

• Notify helpdesk or training teams about the new summaries.
• Update internal documentation that references the Copilot Dashboard.
• Review updated online documentation, which will be refreshed as rollout begins in late April.
• If you choose not to use this feature, you can roll back by disabling intelligent summaries using available admin controls.

[Compliance considerations]

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

• Updated Scan Cab: Download the new Scan Cab here
• Announcing a smaller WSUS Scan Cab: Learn more about WSUS and the Scan Cab process
• Using WUA to Scan for Updates Offline: Windows Update Agent (WUA) can be used to scan computers for security updates without connecting to Windows Update
• WSUS and the Catalog Site: The Catalog Site used by WSUS to import updates and drivers

We've released updates to the following update channels for Microsoft 365 Apps:

• Current Channel
• Monthly Enterprise Channel
• Semi-Annual Enterprise Channel

[When this will happen:]

We'll be gradually rolling out these updates of Microsoft 365 Apps to users on those update channels starting April 14th, 2026 (PST).

[How this will affect your organization:]

If your Microsoft 365 Apps clients are configured to automatically update from the Office Content Delivery Network (CDN), then no action is required.

If you manage updates directly you can now download these latest updates and begin deployment.

[What you need to do to prepare:]

To get more details about these updates view the following release notes:

• Current Channel
• Monthly Enterprise Channel
• Semi-Annual Enterprise Channel

The In development for Microsoft Intune page in our documentation has been updated.

[How this will affect your organization:]

The In development page provides a list of features in upcoming releases of Microsoft Intune to assist in your readiness and planning. The list has now been updated. You will start seeing these changes in the next month or in a subsequent release.

[What you need to do to prepare:]

You can inform your IT staff and helpdesk of the upcoming changes listed on this page. Plan to update your user guidance, if you feel any of these features would be important to your users.

Apple has released new Terms and Conditions for Apple Business. An IT admin will need to accept these terms when using Apple School Manager, Apple Business, Apple Volume Purchasing Program, or Automated Device Enrollment to ensure that the managed devices can continue communicating with Microsoft Intune. 

[How this will affect your organization:]

This will only affect you if you use Apple Automated Device Enrollment, Apple School Manager, Apple Business, or Apple Volume Purchase Program. You will need to accept the new terms and conditions to ensure your Intune service is not interrupted. If you do not accept the new terms and conditions the Intune service will receive the error – “T_C_NOT_Signed” from Apple.

[What you need to do to prepare:]

Simply login to the appropriate URL listed in the support article from Apple here: https://support.apple.com/102069. Once you have logged in and accepted the new terms and conditions, managed Apple devices will once again be able to communicate with Apple’s device management servers.

Note, Apple Business Manager is now Apple Business, learn more from Apple here: https://support.apple.com/guide/business/intro-to-apple-business-axm7909096bf/web 

[Introduction]

Microsoft 365 is introducing a new organizational data export capability for tenant administrators to improve data portability and transparency. This enhancement allows authorized admins to securely export raw organizational data uploaded into Microsoft Organizational Data Ingestion Service (MODIS) in a documented and auditable manner.

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

• Tenant administrators with Global Administrator or Organizational Data Source Administrator roles

What will happen:

• Authorized Admins can export raw organizational data that has been uploaded to MODIS using manual uploads or automated connectors.
• Only data that is retained within the 30‑day retention window is eligible for export.
• Export is initiated directly within the MODIS user experience.
• Exported data is downloaded in CSV format.
• The capability applies only to data your organization has directly uploaded and that remains within the 30‑day retention window.
• The capability is enabled by default and requires no admin configuration.
• There is no impact to users.

Learn more: Understand how organizational data is used and retained in Microsoft 365 | Microsoft Learn (will be updated soon)

[What you can do to prepare:]

No action is required at this time.

After rollout, consider reviewing your data ingestion and retention practices to determine whether exporting ingested data supports compliance, migration, or archival needs.

[Compliance considerations]

[Introduction]

We’re announcing expanded visibility for the Teams Reader role in the Microsoft Teams admin center. With this update, Teams Readers can view Teams and channel management information across the Teams admin center, as well as through PowerShell and Microsoft Graph APIs. This update expands read-only visibility without granting edit permissions.

[When this will happen:]

• General Availability (Worldwide, GCC): Rollout begins in late April 2026 and is expected to complete by early May 2026.

[How this affects your organization:]

Who is affected:

• Organizations that assign the Teams Reader role
• Global admins managing role-based access control (RBAC)
• Tenants using the Teams admin center, PowerShell, or Microsoft Graph APIs

What will happen:

Teams users assigned the Teams Reader role will be able to:

• View Teams management pages, including individual Team and channel details.
• View the Teams tab on the User details page in the Teams admin center.

Role limitations (not included in this release):

• No access to Meetings & Calls user details (planned for a future update)
• No access to Notifications & Rules management (planned for a future update)
• No access to Frontline worker deployment management
• No access to the Collaboration activity dashboard

Note: This update does not grant any new edit or management permissions.

[What you can do to prepare:]

• No admin action is required before rollout.
• Review Teams Reader role assignments for alignment with your access strategy.
• Notify Global admins of the expanded visibility.
• Update internal documentation or training materials that describe Teams admin roles.

Learn more: Use Microsoft Teams administrator roles to manage Teams – Microsoft Teams | Microsoft Learn (will be updated before rollout)

[Compliance considerations:]

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

[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 early May 2026 and is expected to complete by late May 2026.

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

[Introduction]

We’re introducing the ability to submit agents built with Agent Builder for administrator review and approval before publishing to the organization’s catalog in the Agent Store—making it easier to scale distribution of high-quality internal agents while maintaining IT admin control. Once approved, agents appear in the Built by your org section of the Agent Store, where users across the org can discover and install them.

This message is associated with Microsoft 365 Roadmap ID 557173.

[When this will happen:]

General Availability (Worldwide): Rollout will begin in mid‑May 2026 and is expected to complete by late May 2026.

[How this affects your organization:]

Who is affected:

• Users of Agent Builder.
• Microsoft 365 administrators responsible for reviewing and publishing agents.
• Users who discover and install organization‑approved agents from the Agent Store.

What will happen:

There is no impact to users unless an agent is submitted, approved, and published by an administrator. Here is how it works:

• Submission: Agent Builder users can request org publishing of their agents by selecting Submit to your org catalog, including in tenants with sharing controls.

Screenshot 1: Agent Builder menu showing the Submit to your org catalog option for requesting administrator review and approval:

>

• Review: Submitted agents create a review request in the Microsoft 365 admin center. Using the existing publishing and approval workflow, admins have full control over which agents are published, who can access them, and how they are deployed (for example, scoping access to specific users or security groups, preinstalling, or pinning agents).

Screenshot 2: Microsoft 365 admin center showing the agent publishing workflow, where administrators can review submissions and control deployment settings such as user access and installation options.



• Distribution: Users can discover and install approved agents directly from the Agent Store.

Management and Updates:

Once published, the agent appears as a separate entry in the Agent Registry under Agents > All agents. Agent updates require a new admin submission, and each one triggers a new review cycle before the updated version becomes available in the Agent Store.

[What you can do to prepare:]

• No action is required before rollout.
• Admins can familiarize themselves with the agent review experience in the Microsoft 365 admin center under Agents > All agents > Requests.
• Consider communicating this capability to internal agent makers so they understand the submission and approval process.
• Review internal guidance or documentation related to agent governance, if applicable.

Learn more: Publish agents | Microsoft Learn

[Compliance considerations:]

[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-May 2026 and is expected to complete by late May 2026.

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

[Introduction]

We’re improving breakout room setup in Microsoft Teams by adding support for CSV import of breakout room assignments. This update helps organizers reduce manual setup time and prepare structured meetings—such as trainings, workshops, and large collaboration sessions—more efficiently.

This message is associated with Roadmap ID 559387.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• Meeting organizers who use Breakout rooms in Microsoft Teams meetings

What will happen:

• Organizers can import a CSV file to:
  • Create breakout rooms in bulk
  • Assign participants to specific rooms before the meeting starts
• Imported assignments can still be modified using existing breakout room controls during or before the meeting
• The feature is enabled by default and does not require admin configuration
• Existing breakout room policies and controls are respected

[What you can do to prepare:]

No action is required from administrators.

• Inform meeting organizers about this new capability
• Update internal documentation or training materials as needed

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

[Compliance considerations:]

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

[Introduction]

Data Governance Admins and Data Stewards can use a built‑in migration tool in Microsoft Purview Unified Catalog to migrate classic glossary terms, associated term templates, and asset and column relationships into Unified Catalog. After migration, glossary terms can be managed in Unified Catalog and associated with business concepts and data assets.

This message is associated with Microsoft 365 Roadmap ID 558683.

[When this will happen]

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

[How this affects your organization]

Who is affected

• Data Governance Admins
• Data Stewards
• Organizations using classic glossary terms in Microsoft Purview, along with Unified Catalog

What will happen

• Admins can choose to use the built‑in migration tool to migrate classic glossary terms to Unified Catalog.
• Migration includes:
  • Classic glossary terms
  • Associated term templates
  • Asset and column relationships
• Admins who do not need migration can skip the process and use glossary terms only in Unified Catalog.
• In both cases, classic glossary terms will become read‑only.
• After migration or switching, Unified Catalog glossary terms can be used to curate assets and columns.

[What you can do to prepare]

• Determine whether your organization uses classic glossary terms.
• Decide whether to:
  • Migrate classic glossary terms to Unified Catalog, or
  • Abandon classic glossary terms and use Unified Catalog glossary terms only.
• If you choose migration:
  • Review the detailed migration documentation.
  • Plan and execute the migration when your organization is ready for all required steps.

Links to detailed migration documentation will be added to the Unified Catalog glossary terms overview documentation when the feature enters public preview.

[Compliance considerations]

• Settings Features – AI form fill assistance
• Settings Features – Natural language grid and view search
• Settings Features – AI insight cards

• Form fill assistance
• Row summaries
• Find data
• Visualize data