Microsoft Roadmap, messagecenter and blogs updates from 07-02-2026

Updated February 6, 2026: We have updated the content. The scope of the change remains unchanged. Thank you for your patience.

We’re updating the output format of certain properties returned by Exchange Online PowerShell cmdlets to improve performance and align with backend service optimizations. This change reduces unnecessary data retrieval and enhances consistency across services.

[When this will happen:]

Rollout will begin in February 2026 (previously October 2025) and complete by April 2026 (previously November 2025).

[How this affects your organization:]

This update changes the string format of specific properties returned by Exchange Online cmdlets. For example, the Database property in the output of Get-Mailbox will change from:

Database : APCP153DG038-db080

to:

Database : APCP153.PROD.OUTLOOK.COM/7ad9dea1-26b7-4088-ad73-708c219faff6

This change applies only to Exchange Online. On-premises Exchange environments are not affected.

We do not expect organizations to have dependencies on these output formats. These values are informational only and not intended for admin control or automation. No changes to user workflows, admin configurations, or help desk processes are expected.

[What you can do to prepare:]

No action is required. There are no settings or controls to manage this change. If you have scripts that parse these property values, we recommend reviewing them to ensure compatibility.

The complete list of cmdlets impacted is as follows: 

The affected properties for each Output Type are as follows:

Updated February 6, 2026: We have updated the timeline. Thank you for your patience. 

Introduction

We’re introducing a new feature in Viva Connections that helps users stay informed with SharePoint news. Starting with this rollout, users will receive a weekly notification in Microsoft Teams reminding them to catch up on SharePoint news articles they haven’t read from the previous week. These articles will be accessible under the Unread pill in the News tab within Viva Connections.  

This feature is associated with Microsoft 365 Roadmap ID 498323.

When this will happen

General Availability: We will begin rolling out mid-February 2026 and expect to complete by end of February 2026. 

How this affects your organization

Once rolled out, users will receive a weekly notification in Microsoft Teams linking them to their unread SharePoint news in Viva Connections. This notification is enabled by default, but users can manage its visibility through their Teams notification settings.

What you can do to prepare

• No admin action is required. The rollout is automatic.
• Admins may wish to inform users about the new notification and how to manage it in Teams settings.

Compliance considerations

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

Updated February 6, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction:]

We’re updating Memory in Microsoft 365 Copilot to improve personalization and enhance the user experience. With this update, Copilot will personalize responses using chat history, helping users receive more relevant and contextual replies. We’re also introducing refreshed user controls in Copilot settings to make it easier to view and manage Saved Memory. This will be available to all Copilot Chat users.

Control over personalization using chat history is also available, with details for users via the settings screen. 

[When this will happen:]

• Public Preview (Frontier): Begins rolling out mid-November 2025.
• General Availability: Begins early January 2026 (previously early November 2025) and is expected to completed in March 2026.

[How this affects your organization:]

All users of Microsoft 365 Copilot in tenants where Memory is enabled.

What will happen:

• Copilot will use chat history to personalize responses, making interactions more tailored and helpful:

 

• Users will see a redesigned Memory settings page that improves visibility and control over what Copilot remembers.
• Existing admin and user-level Memory settings are respected. If Memory is toggled off, it will remain off.
• No changes to admin controls or policy enforcement.

[What you can do to prepare:]

• Review the updated Memory settings experience with your users once available.
• No admin action is required unless you wish to update internal documentation or training materials.

Learn more:

• Enhanced personalization control overview | Microsoft Graph | Microsoft Learn 
• enhancedPersonalizationSetting resource type | Microsoft Graph | Microsoft Learn

[Compliance considerations:]

Updated February 5, 2026: Agent Mode in Excel and Word are starting to roll out across web, Windows, and Mac and are expected to complete in the following weeks. Additionally, Anthropic has onboarded as a Microsoft subprocessor and we have updated the related information below.

Updated January 20, 2026: The change to Copilot Chat in Outlook to expand reasoning to include a user’s entire inbox, calendar, meetings, and other enterprise data is starting to roll out across web, new Outlook for Windows, Classic Outlook for Windows, Mac and mobile and is expected to complete in the following weeks. For more information on the data Copilot Chat in Outlook will be able to access, please see Organizational Data in our documentation. Users can learn more about this change from the Use Copilot Chat in Microsoft 365 apps article. There is no update at this time regarding Agent Mode and the Word, Excel, and PowerPoint Agents availability.

[Introduction]

We’re introducing new capabilities for Microsoft 365 Copilot Chat users (without a Microsoft 365 Copilot license) to help them better manage their day in Outlook and create and refine Word documents, Excel workbooks, and PowerPoint presentations. These updates include:

• Copilot Chat in Outlook will expand from reasoning over a single email thread to reasoning over a user’s entire inbox, calendar, meetings, and other enterprise data.
• Agent Mode in Word, Excel, and PowerPoint uses web data and referenced files to help users create and refine content in the apps.
• Word, Excel, and PowerPoint Agents allow users to create high-quality documents, workbooks, and presentations in Copilot Chat using web data and referenced files.

Please find our Microsoft Ignite announcements here.

[When this will happen:]

We will begin rolling out early January 2026 and expect to complete by late March 2026.

[How this will affect your organization:]

• Who is affected: Eligible Copilot Chat users with a Microsoft 365 or Office 365 subscription. There is no change for users with a Microsoft 365 Copilot license.
• What will happen:
  • Copilot Chat in Outlook will understand the entire inbox, calendar, meetings, and other enterprise data for a user. Additional documentation will be provided closer to rollout. Users will be able to ask Copilot to source information across their inbox, uncover action items, or manage their calendar.
  • Users will be able to access Agent Mode in Word, Excel, and PowerPoint through the Tools menu in the Copilot Chat input box in each individual app. Agent Mode lets users create and refine content as they are working. Agent Mode will use web data and referenced files but will not have access to work data.
  • Users will be able to access the Word, Excel, and PowerPoint Agents in Copilot Chat from the Tools menu in the input box or by typing “@” and selecting the agents. These agents use several models, including Anthropic’s Claude model, to help create high-quality documents, spreadsheets, and presentations. These agents will use web data and referenced files but will not have access to work data.

[What you need to do to prepare:]

• No admin action is required for Copilot Chat in Outlook. If you’d like to manage Copilot Chat in Outlook, you can use Integrated Apps in the Microsoft 365 admin center. Learn more here.
• No admin action is required for Agent Mode in Word, Excel, and PowerPoint. If you’d like to manage Copilot Chat in Word, Excel, and PowerPoint, you can use the Pin Microsoft 365 Copilot Chat setting. Learn more here.
• To provide access to Word, Excel, and PowerPoint Agents, you must connect to Anthropic’s Claude model. Learn how to connect here.

[Compliance considerations:]

The following considerations are relevant to the use of Word, Excel, and PowerPoint Agents.

• Anthropic has onboarded as a Microsoft subprocessor: Learn more here.

Updated February 6, 2026: We have added a link to a support article. Thank you for your patience. 

[Introduction:]

Managing email just got easier. Microsoft 365 Copilot now supports natural language commands to help users pin or unpin important messages, flag or unflag items, mark tasks complete, archive clutter, and mark emails as read or unread. This enhancement is designed to streamline inbox management and help users stay focused on what matters most.

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

Supported platforms: Available via Microsoft 365 Copilot Chat (Work mode). When used within Outlook, it’s supported on Classic and New Outlook for Windows, Outlook on the web, Outlook for Mac, and Outlook mobile (iOS and Android).

[When this will happen:]

• Public Preview (Worldwide): Rollout begins mid-December 2025 and is expected to complete by early January 2026.
• General Availability (Worldwide): Rollout begins mid-December 2025 and is expected to complete by mid-February 2026 (previously late January).

[How this affects your organization:]

Who is affected: Users with Microsoft 365 and Copilot licenses who use Outlook for email management.

What will happen:

• Users can use natural language to
  • Pin or unpin emails.
  • Flag or unflag messages.
  • Mark tasks as complete.
  • Archive emails.
  • Mark emails as read or unread.
• These features will be available by default for licensed users.
• No changes to existing admin policies are required.

[What you can do to prepare:]

• Ensure users have the appropriate Microsoft 365 and Copilot licenses.
• Communicate this update to helpdesk and support teams.
• Update internal documentation if you detail email management features.
• No additional configuration is required for rollout.
• Review the following support article: Triage Email with Microsoft 365 Copilot in Outlook – Microsoft Support

[Compliance considerations:]

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

Updated February 6, 2026: We have updated the content. Thank you for your patience. 

[Introduction]

Outlook is adding new Microsoft 365 Copilot capabilities that let users create and view Inbox rules using natural language. This update helps users stay organized more efficiently by allowing them to ask Copilot to set up new rules or list existing rules directly in chat, without navigating Outlook settings.

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

Supported platforms: Available via Microsoft 365 Copilot Chat (Work mode). When used within Outlook, it’s supported on Classic and New Outlook for Windows, Outlook on the web, Outlook for Mac, and Outlook mobile (iOS and Android).

[When this will happen]

General Availability (Worldwide): We began rolling out in early February 2026 (previously late January) and expect to complete by mid-March 2026 (previously early March).

[How this affects your organization]

Who is affected: Users who have access to Microsoft 365 Copilot in Outlook.

What will happen:

• Users can create new Inbox rules through natural language prompts (for example: “Create a rule to move emails from my manager to a Manager folder.”).

  

• Users can ask Copilot to show their existing Inbox rules, including rule names, conditions, actions, and status.
• Rules created with Copilot operate the same as rules created through Outlook settings:
  • Rules apply only to future incoming messages.
  • Existing messages are not automatically moved or modified.
  • All rules are visible and manageable through Outlook’s native Rules settings.
• The feature is on by default for eligible users and respects all existing Outlook and Exchange policies.

[What you can do to prepare]

No action is required from administrators.

If your helpdesk or documentation references Outlook rule creation, you may wish to update it to reflect natural‑language rule management through Copilot.

[Compliance considerations]

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

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

[Introduction]

We’re updating the feedback experience in Microsoft Planner to align with the broader Microsoft 365 feedback policy model. When the Allow users to include screenshots when they submit feedback policy is set to Not Configured, Planner will treat it the same as Enabled. This ensures consistent behavior across Microsoft 365 and gives users clearer, more predictable feedback options.

[When this will happen:]

General Availability: Rollout will begin in mid-February 2026 (previously early February) and complete by end of February 2026 (previously mid-February).

[How this affects your organization:]

Who is affected:

• Organizations using Microsoft Planner with Microsoft 365 in-product feedback not configured.
• Admins managing feedback policies in the Microsoft 365 Apps Admin Center or via Group Policy.

What will happen:

• When the feedback policy is Enabled or Not Configured, users will be able to include screenshots and file attachments in their in-product feedback.
• Explicitly Disabled policies will continue to block attachments.
• No changes will be made to other feedback functionality.
• No admin action is required for this update.

[What you can do to prepare:]

• To configure these policy settings, use the Cloud Policy service for Microsoft 365. For more information, refer to Overview of Cloud Policy service for Microsoft 365 and search for feedback or survey within Cloud Policy UI to find the policy settings to configure them.
• No action is required.
• If you want to prevent screenshot or file uploads, explicitly set the related feedback policy to Disabled.

Learn more: Manage Microsoft feedback for your organization | Microsoft Learn

[Compliance considerations:]

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

Updated February 6, 2026: We have updated the image below. Thank you for your patience. 

[Introduction]

Microsoft is introducing a unified plus (+) menu to make it easier for users to add grounding, tools, and sources when prompting in Microsoft 365 Copilot. Grounding refers to the content users connect to Copilot—such as files, sites, or other organizational data—that helps improve response relevance. This update consolidates related actions into a single menu, improving discoverability and streamlining the workflow for adding entities or updating inputs. This simplified menu will be available for Copilot Chat users (without a Microsoft 365 Copilot license) and Microsoft 365 Copilot users (with a Microsoft 365 Copilot license).

Note: The Tools menu will be consolidated under the unified plus (+) menu and no longer exist as a separate menu in the prompt box after this change.

[When this will happen:]

General Availability (Worldwide): Rollout begins in late February 2026 and is expected to complete by mid‑March 2026.

[How this affects your organization:]

  Who is affected:

  Copilot Chat and Microsoft 365 Copilot users that rely on the unified plus (+) menu.

  What will happen:

• Users will see a redesigned and unified plus (+) menu.
• Grounding options, tools, and data sources will be consolidated in one menu.
• Users will be able to add entities and update sources from this unified location.
• The feature will be enabled by default and replaces the current experience; no admin configuration is required.
• Existing admin policies related to Copilot input sources remain unchanged.

[What you can do to prepare:]

No action is required for administrators.

• Inform helpdesk and training teams about the unified plus (+) menu layout.
• Update internal documentation or screenshots that reference the previous menu.

[Compliance considerations:]

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

[Introduction]

Insider Risk Management is providing the ability to create a case without content. With this, we will introduce a new active case limit of 2000. This new functionality will allow customers to create more cases particularly when content download is unnecessary. If a case is created without content download, content download can be initiated anytime the case is active pending available content download limits. There is no change to the active content download limit of 100.

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. Insider Risk Management enables customers to create policies based on their own internal policies, governance, and organizational requirements. Built with privacy by design, users are pseudonymized by default, and role-based access controls and audit logs are in place to help ensure user-level privacy.

This message is associated with Microsoft 365 Roadmap ID 554940.

[When this will happen:]

Public Preview: We will begin rolling out late February 2026 and expect to complete by mid-March 2026.

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

[How this will affect your organization:]

Who is affected:

Admins who manage Insider Risk Management cases and alerts in Microsoft Purview.

What will happen:

• You will be able to create Insider Risk Management cases with or without content download.
• A new active case limit of 2000 will be introduced.
• There is no change to the active content download limit (100).
• Workflow updates for creating or modifying a case will follow these steps:

1. Log into Insider Risk Management.
2. Open an active alert.
3. Select Confirm alert & create case.



4. Choose whether to create the case with or without content download enabled.



5. To turn on content download later, open an active case and navigate to Content Explorer.

[What you need to do to prepare:]

• There are no prerequisites to enable this feature.

Learn more:

• Microsoft Purview: Insider risk management
• Create a case for an alert | Microsoft Support

[Compliance considerations:]

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

[Introduction]

Microsoft Defender Antivirus on Windows is updating how antivirus configuration settings, such as exclusions, are stored when Microsoft Defender for Endpoint (MDE) configuration management is enabled. Starting with platform release 4.18.25110.6, devices using MDE configuration management will no longer store readable exclusion values in the local device registry. Organizations must retrieve configuration using supported Microsoft Defender PowerShell cmdlets, such as Get-MpPreference.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• Organizations using Microsoft Defender for Endpoint configuration management.
• Admins or tools relying on registry-based monitoring of antivirus settings.

What will happen:

• Antivirus exclusion values will no longer be readable from the local device registry.
• Registry‑based extraction of exclusions will no longer be supported.
• Supported Microsoft Defender PowerShell cmdlets (such as Get-MpPreference) will become the required method to retrieve antivirus configuration settings.
• Devices not using MDE configuration management are not affected.
• The feature is on by default for tenants using MDE configuration management.

[What you can do to prepare:]

• Update monitoring workflows and scripts to use supported PowerShell cmdlets such as:
  • Get-MpPreference
  • Get-MpComputerStatus

• Review internal documentation on retrieving antivirus settings.
• Notify helpdesk or monitoring teams that registry-based queries will no longer return exclusion data.

Learn more: Troubleshoot Microsoft Defender Antivirus settings – Microsoft Defender for Endpoint | Microsoft Learn (will be updated to reflect this change)

[Compliance considerations:]

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

[Introduction]

As part of our ongoing mission to deliver a modern, secure, and scalable one-stop management portal for admins, we are transitioning Teams Android device management from the Teams admin center (TAC) to the Teams Rooms Pro Management portal (PMP).

This move consolidates management of all Teams devices, including Teams Rooms on Windows, Teams Rooms on Android, Teams phones, and Teams panels, into a single unified portal, providing IT admins a consistent and seamless experience for managing devices at scale.

[When this will happen:]

• Public Preview: We will begin rollout in early April 2026 and expect to complete by mid-April 2026. 
• General Availability (Worldwide, GCC): We will begin rollout in early June 2026 and expect to complete by mid-June 2026.
• General Availability (GCC High): We will begin rollout in early August 2026 and expect to complete by mid-August 2026.
• General Availability (DoD): We will begin rollout in early September 2026 and expect to complete by mid-September 2026.

[How this affects your organization:]

Who is affected:

Admins who manage Teams Rooms on Android, Teams phones, and Teams panels.

What will happen:

• Starting June 2026, Android device management capabilities, including inventory, updates, health monitoring, and settings will transition from TAC to PMP for the device types, Teams Rooms on Android, Teams phones, Teams panels
• The following capabilities will be available and enhanced in PMP:
• Device inventories for Android-based Teams Rooms, phones, and panels, including metadata and app information
• Remote device actions (restart, log collection, sign-in/out, provisioning, and more)
• Update management
• Device settings management
• Device health monitoring
• SIP device management
• PMP will become the primary portal for all Teams device management. By July 2026, overlapping TAC capabilities (updates, settings, restart, sign-in/out, log collection, provisioning) will begin redirecting to PMP.

[What you need to do to prepare:]

• No action is required until Android device management reaches General Availability.
• When Android device management reaches General Availability:
• Your existing Android-based Teams devices will automatically appear in PMP.
• Teams Rooms on Android and Teams panels are already visible in PMP.
• If your organization hasn’t used PMP before:
• Admins with Global, Teams, or Teams Device Administrator roles can access PMP at https://portal.rooms.microsoft.com.
• Ensure required URLs are allowlisted per guidance: Enrolling a device into the Pro Management Portal | Microsoft Learn.
• Learn more about Pro Management portal features with these Teams Rooms Pro Management short YouTube videos.
• Update internal helpdesk and IT documentation to reference PMP as the new management portal.
• Additional migration guidance, timelines, and FAQs will be published closer to the transition date.

[Compliance considerations]

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

[Introduction]

We’re adding a new PowerShell cmdlet that lets administrators change the organizer of an existing meeting or meeting series in Exchange Online. This feature supports continuity when a meeting owner changes roles, goes on leave, or is offboarded—removing the need to recreate long‑running series. After the transfer, the new organizer can update meeting properties, and attendees within the tenant won’t need to re‑RSVP.

A future release will enable users to change the organizer directly in Modern Calendar experiences in Outlook on the web, the new Outlook, and Teams. For user‑initiated transfers, the new organizer must accept the meeting before the transfer completes.

This message is associated with Microsoft 365 Roadmap ID 554937.

[When this will happen]

General Availability 

• Worldwide and GCC: We will begin rolling out in mid-May 2026 and expect to complete by late June 2026.
• GCC High and DoD: We will begin rolling out in mid-May 2026 and expect to complete by late July 2026.

[How this affects your organization]

Who is affected:

• Administrators managing Exchange Online
• Meeting organizers and attendees in your tenant may see updated organizer information when applicable.

What will happen:

• Administrators can use a new PowerShell cmdlet to change the organizer of an existing meeting or meeting series.
• The new organizer will have full control of the event, including recurrence, description, attendees, and meeting details.
• For attendees within the tenant, the existing event on attendees’ calendars will be silently updated to reflect the new organizer. These attendees won’t need to decline or reaccept the meeting.
• Attendees outside the tenant will receive 2 meeting messages – one ending the series with the previous organizer and another inviting them to a series with the new organizer. These attendees should reaccept the meeting.
• Meeting history is preserved, supporting continuity and reducing abandoned meeting series.
• This feature is enabled by default; no configuration is required.

No action is required. The feature will roll out automatically.

To prepare:

• Review upcoming public documentation for the cmdlet when it becomes available (a link will be added to this message).
• Update internal processes for organizer transitions, such as role changes or offboarding.
• You may test the cmdlet ahead of the user‑initiated organizer change experience coming to Outlook on the web, new Outlook, and Teams.

[Compliance considerations]

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

[Introduction]

We are updating Microsoft Purview’s out-of-box (OOB) sensitive information type (SIT) detection logic to improve accuracy and reduce false positives. As part of this update, the relaxed proximity matching behavior previously used in some OOB SITs will be removed. After this change, all OOB SITs will consistently use stricter proximity rules for more consistent and precise detections.

[When this will happen:]

General Availability (Production, GCC, GCC High, DoD): Available now

[How this affects your organization:]

Who is affected:

• Organizations using Microsoft Purview out-of-box sensitive information types in data classification or Data Loss Prevention (DLP) policies.

What will happen:

• OOB SITs will stop using the relaxed proximity behavior previously applied in some detection rules.
• All OOB SITs will consistently use stricter proximity matching rules going forward.
• Content that previously matched under relaxed proximity conditions may no longer trigger a detection unless it meets the stricter proximity requirements.
• This may result in fewer detections in scenarios that relied on broader proximity matching.
• Custom sensitive information types are not affected and can still be configured to use broader proximity logic if required.

[What you can do to prepare:]

• Review existing DLP and classification policies that rely on OOB SIT detections.
• Test policy behavior in a non-production environment if broader proximity matching is required for certain workflows.
• Create custom sensitive information types if your organization needs relaxed proximity logic.

Learn more: Sensitive Information Types in Microsoft Purview

[Compliance considerations:]

[Introduction]

As part of our ongoing protection investments in Microsoft Teams, we will continue expanding the ways users can report suspicious or incorrect activity. Users can already report security concerns and incorrect detections in chats and channels (MC1037768, MC1147984), and more recently in calls (MC1223828). These user‑submitted reports help identify potential malicious activity and strengthen your organization’s security posture.

Building on this foundation, we will introduce new capabilities that allow Teams administrators to review and export user‑reported security submissions directly in the Teams admin center. A new Protection reports section will be added under Analytics and reports, giving admins unified visibility into user‑reported calls, chats, and channels.

This message relates to Microsoft 365 Roadmap ID 536571.

[When this will happen]

Phase 1 – User‑reported call data

• Targeted Release: Rollout will begin in mid‑March 2026 and complete in late March 2026.
• General Availability (Worldwide): Rollout will begin in mid‑April 2026 and complete in late April 2026.

Phase 2 – User‑reported chats and channels

• This phase will add message‑level reporting for security concerns and incorrect detections.
• The timeline will be communicated in a future update to this Message center post.

[How this affects your organization]

Who is affected: Teams administrators who have access to Analytics and reports in the Teams admin center.

What will happen:

• A new Protection reports section will appear under Teams admin center > Analytics & reports:

  

• Admins will be able to view and export data about user‑submitted security reports for calls (Phase 1) and later chats and channels (Phase 2).
• Reported interactions will begin populating once users submit reports.
• Admins will be able to review reported calls or messages and take appropriate action.
• Admins will be able to view 1‑day, 7‑day, and 30‑day reporting windows.
• This feature will require that user reporting settings be enabled in the Teams admin center.

[What you can do to prepare]

To ensure reporting data is available when rollout begins, verify that end‑user reporting features are enabled:

• Enable Report a call: Teams admin center > Calling settings
• Enable Report a security concern and Report incorrect detection: Teams admin center > Messaging settings
• Once enabled and users begin submitting reports, access data at: Teams admin center > Analytics & reports > Protection reports > User‑reported security submission
• Update internal documentation if your helpdesk relies on reporting workflows.
• If you maintain training or onboarding materials about Teams security practices, consider adding guidance on how users can report suspicious interactions.

[Compliance considerations]

Model Context Protocol (MCP) based agents in Microsoft 365 Copilot Chat will now be able to surface rich, interactive UI widgets directly within chat. This enhancement enables developers to deliver more engaging and structured agent interactions. Users will experience these widgets when interacting with agents that implement them, and admins will continue to manage these agents through the Microsoft 365 Admin Center.

Screenshot 1: Rich in-line widgets in Copilot

When this will happen:

• Public Preview: Rollout will begin late February 2026 and is expected to complete by early March 2026.

How this affects your organization:

Who is affected:

• Organizations using Microsoft Copilot agents.
• Administrators responsible for agent governance and controls.

What will happen:

• MCP-based agents can now display rich interactive UI widgets in Copilot Chat.
• Widgets provide more guided, visual, and structured interactions.
• Admins can deploy agents from the Agent Store or through custom MCP packages.
• Existing Copilot extensibility controls remain unchanged.
• Access to agents can continue to be scoped via Entra ID groups.
• This functionality is enabled by default for agents that implement widgets.

What you can do to prepare:

No action is required.

• Optionally review the Agents catalog for alignment with internal policies.
• Review existing Copilot and agent governance controls.
• Update internal documentation as needed.

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

Compliance considerations:

• Add reCAPTCHA to any form using simple drag-and-drop drop in the Form Editor. No HTML edits or developer help is required.
• Configure your Site key and Secret key once in default form settings to activate reCAPTCHA across all forms.
• Protect form submissions with modern, widely trusted, accessibility-friendly bot detection.
• Reduce spam, safeguard your customer data pipelines, and maintain higher form conversion rates.
• Ensure compatibility with current security standards as HIP CAPTCHA is retired.