Microsoft Roadmap, messagecenter and blogs updates from 14-01-2026

Updated January 12, 2026: We have updated the timeline. Thank you for your patience.

[Introduction]

We are introducing two new Microsoft Graph APIs that enable admins to programmatically access and manage agents and apps within their organization. These APIs provide greater flexibility for reporting and integration scenarios without relying on manual UI workflows.

This message is associated with Microsoft 365 Roadmap ID 502875.

[When this will happen:]

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

[How this affects your organization:]

Who is affected: Admins managing Copilot agents and apps within Microsoft 365 environments.

What will happen:

• New Graph API endpoints will be available:
  • GET graph.microsoft.com/copilot/admin/catalog/packages – Retrieves a complete inventory of all agents and apps (Microsoft, External, Shared, and Custom).
  • GET graph.microsoft.com/copilot/admin/catalog/packages/{id} – Fetches detailed metadata for a specific agent or app, including properties and manifest details.

• These APIs allow for automated reporting and integration workflows.
• No changes to existing UI workflows or admin policies.
• These Graph API endpoints are available to users with an existing Microsoft 365 license; no additional license or add-on is required.

[What you can do to prepare:]

• Review the Microsoft Graph API documentation to familiarize yourself with usage and capabilities at this time.

[Compliance considerations:]

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

Updated January 13, 2026: We have updated the content. Thank you for your patience. 

[Introduction]

We’re introducing new capabilities in Copilot Pages and Copilot Chat that enable improved connection and interactions between these two experiences. There are four main elements included in this update:

1. Page creation via Chat, where an intent to create a Copilot Page in a Chat prompt will automatically create that page.
2. Page updates via Chat, where a prompt to modify or add to the currently-open Page will make those changes directly on the Page.
3. Chat can now answer questions based on the content of the open Page.
4. Improved on-Page Copilot interactions, including Ask Copilot for selecting content and the use of Page-level improvements via the Copilot Shortcuts experience.

General Availability (Worldwide): We will begin rolling out in early October 2025 and expect to complete by early February 2026 (previously early November 2025).

• Who is affected: Users with access to Copilot in Microsoft 365 who use Copilot Pages and Copilot Chat in side-by-side mode.
• What will happen:
  • Users will be able to create new pages in Chat when they use language that implies that a new Page is desired (e.g., “Create a Page to help me…”)
  • If a Page is already open, they can use Chat to request updates to the page (e.g., “Update the introduction to be more formal”)
  • Users will be able to ask questions in Copilot Chat about the currently open page in Copilot Pages and Copilot will respond using the content of the open page to provide contextual answers.
  
  • Copilot will respond using the content of the open page to provide contextual answers.
  • Users can use on-Page experiences like Ask Copilot (available by selecting content and either right-clicking or using the floating menu experience) and Copilot Shortcuts (available in the bottom corner of the Page)
  • The feature will be ON by default for eligible tenants to configure.
  • Existing admin policies are respected; no policy changes are required.

• Communicate this change to helpdesk and support staff.
• Update internal documentation or training materials that reference Copilot Pages or Chat functionality.
• Review user guidance to ensure users understand how to use Copilot effectively in side-by-side mode.

Learn more:  Manage Copilot Pages and Copilot Notebooks in your organization | Microsoft Learn

No compliance considerations identified, all compliance capabilities will be the same as the Microsoft 365 Copilot Pages experience.

Updated January 13, 2026: We have updated the timeline. Thank you for your patience. 

Microsoft is introducing the ability to start, stop, and restart meeting recording and transcription directly from Microsoft Teams Rooms on Android devices. This enhancement supports a more seamless meeting experience by removing the need for a companion device to initiate these actions. Spoken language for the meeting can also be changed during the session. This functionality is available with Teams Rooms Pro licensing.

General Availability (Worldwide and GCC): We will begin rolling out end of January 2026 (previously mid-January) and expect to complete by mid-February 2026 (previously late January).

General Availability (GCCH and DoD): We will begin rolling out end of February 2026 (previously early February) and expect to complete by mid-March 2026 (previously mid-February).

Who is affected:

• Users joining Teams meetings from Microsoft Teams Rooms on Android devices.
• Organizations with Teams Rooms Pro licensing.

What will happen:

• Users can start, stop, and restart recording and transcription directly from a Teams Rooms device running Android. To do this, they can select More on the meeting interface, then choose Record and transcribe to initiate or stop the recording and transcription.
• The spoken language for the meeting can be changed during the session.
• Previously, users needed a companion device to initiate recording or transcription.
• Recording and transcription are supported in meetings where a participant belongs to the same tenant as the organizer.
• For Meet now or Whiteboard sessions initiated from a Teams Rooms on Windows device, users must invite themselves to the meeting to access the recording file via Teams desktop or mobile app.
• To use the start and stop recording and transcription feature, both the meeting organizer and the room account must have permission to record and transcribe. If either party lacks the required permissions, the button to initiate or stop recording and transcription will not appear.
• If the meeting organizer removes recording or transcription permissions from the room account using meeting options, the button will also be unavailable.

• Limitations – Recording and transcription are not supported in the following scenarios:
  • Peer-to-peer (P2P) calls: Direct one-on-one calls between two users.
  • Group calls: Ad-hoc calls involving multiple participants that are not scheduled meetings.
  • PSTN calls: Calls made through the Public Switched Telephone Network using Teams Calling Plans or Direct Routing.
  • External or cross-tenant meetings and calls: Meetings involving participants from outside the organizer’s tenant.
  • Third-party meetings and calls: Including Direct Guest Join and SIP-based meetings, which use the Session Initiation Protocol to connect external video conferencing systems (such as Cisco or Polycom) to Microsoft Teams. These integrations do not support native Teams recording and transcription features.

Screenshot – New recording and transcription controls in Teams Rooms on Android:

• Ensure room accounts and meeting organizers have permissions to record and transcribe meetings.
• Communicate this change to helpdesk and support teams.
• Update internal documentation to reflect the new functionality.
• Review meeting options to confirm room account permissions are correctly configured.

Compliance considerations:

Updated January 13, 2026: We have updated the timeline. Thank you for your patience. 

Outlook mobile users can now prepare for their meetings using Copilot chat with a single tap. This feature is available on Android and iOS platforms and requires a Microsoft 365 Copilot license. It helps users quickly access relevant meeting information, making preparation more efficient and personalized.

This message is associated with Microsoft 365 Roadmap ID 516568.

[When this will happen:]

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

[How this affects your organization:]

• Who is affected: Users of Outlook mobile on Android and iOS who have a Microsoft 365 Copilot license.
• What will happen:
  • Eligible users will see a new Copilot chat option to prepare for meetings directly within Outlook mobile.
  • The feature will be ON by default for licensed users. To turn off Copilot in Outlook review Turn off Copilot in Microsoft 365 apps | Microsoft Support.
  • No admin configuration is required.
  • Existing policies and permissions are respected.

Screenshots 1-3 provide a view of the previous experience:

Screenshots 4-5 provide a view of the new experience – Selecting Prepare will take users to Copilot Chat, enabling users to ask follow-up questions:

[What you can do to prepare:]

• No admin action is required at this time.
• If desired, communicate this feature to helpdesk staff.
• Update internal documentation if you detail this feature.
• Ensure users have the appropriate Microsoft 365 Copilot license to access this feature.

[Compliance considerations:]

Updated January 13, 2026: We have updated the timeline. Thank you for your patience. 

Microsoft is introducing a new capability in Teams that enables Channel Agent to orchestrate tasks with select third-party Model Context Protocol (MCP) servers, including GitHub, Asana, and Atlassian (JIRA). This integration supports collaborative workflows that reflect real human teamwork, allowing agents to transparently reason through tasks and gather information across tools. This change helps reduce manual switching between apps and improves task completion efficiency—all within the familiar Teams environment.

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

This message is associated with Microsoft 365 Roadmap ID 515466.

• Targeted Release (Worldwide): Begins in mid-November 2025 and is expected to complete by late January 2026 (previously mid-December 2025).

Who is affected: Microsoft 365 tenants using Teams and Channel Agent integrations.

What will happen:

• Channel Agent will be able to collaborate with Model Context Protocol (MCP) servers like GitHub, Asana, and Jira.
• Users can ask Channel Agent questions and receive coordinated responses across tools:

          Screenshot 1

Screenshot 2



• The feature will be available in preview and requires admin enablement.
• A Microsoft 365 Copilot license is required.
• There is no impact unless enabled by tenant admins.

What you can do to prepare

• Enable Channel Agent usage in Teams for your tenant.
• Allow apps that integrate with Model Context Protocol (MCP) servers such as GitHub, Asana, or Jira.
• Ensure users who need access have a Microsoft 365 Copilot license.
• Review internal documentation and update helpdesk guidance as needed.

Compliance considerations

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

Updated January 13, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

To improve collaboration and streamline meeting workflows, Microsoft Teams is introducing the ability to consult and merge Public Switched Telephone Network (PSTN) callers into active meetings—even when those callers are behind auto-attendants or Interactive Voice Response (IVR) systems that require Dual-Tone Multi-Frequency (DTMF) navigation. This enhancement allows users to reach subject matter experts via dial-in and seamlessly bring them into the broader conversation.

This message is associated with Microsoft 365 Roadmap ID 518218.

• Targeted Release: Rolling out early March (previously early February), expected to complete by mid-March 2026 (previously mid-February).
• General Availability:  Rolling out late March (previously mid-February), expected to complete by early April 2026 (previously end of February).

[How this affects your organization:]

• Who is affected: All Microsoft Teams users who initiate or manage meetings with PSTN participants. Administrators overseeing Teams meeting policies and call configurations.
• What will happen:
  • Users can consult with PSTN or Voice over Internet Protocol (VoIP) participants via the Participants panel.
  • A new interface will allow users to access a dialpad to navigate IVR systems and auto-attendants using DTMF tones.
  • Once the external party is reached, users can merge them into the ongoing meeting.
  • No changes to existing administrator policies; feature is enabled by default.

[What you can do to prepare:]

• No administrator action is required for this rollout.
• If your organization uses custom training or helpdesk documentation, consider updating it to reflect this new capability.
• Before rollout, we will update this post with new documentation.

[Compliance considerations:]

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

Updated January 13, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction:]

To help users declutter their calendars, Outlook Mobile now supports hiding declined meetings. This aligns with existing functionality in New Outlook and Outlook for the Web, where users can choose to show or hide declined events. With this update, users can enjoy a simplified calendar experience across devices.

[When this will happen:]

General Availability (Worldwide, GCC, GCCH, and DoD): Rollout begins in early February 2026 (previously mid-January) and is expected to complete by mid-February 2026 (previously late January). 

[How this affects your organization:]

Who is affected: Users of Outlook Mobile who have enabled “Show declined meetings” in New Outlook or Outlook for the Web.

What will happen: 

• Users will see a new setting in Outlook Mobile to hide declined meetings: 



• This setting provides a cleaner calendar view by removing declined events.
• The feature respects existing preferences set in New Outlook or Outlook for the Web.
• No changes to admin policies or configurations are required.

Learn more: What is the Hide Declined Events Setting? | Microsoft Support

[What you can do to prepare:] 

No admin action is required at this time.

You may choose to inform helpdesk staff or update internal documentation to reflect this new setting.

[Compliance considerations:]

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

Updated January 13, 2026: We have updated the timeline and content. Thank you for your patience. 

[Introduction:]

Microsoft Edge for Business is introducing a “What’s New” webpage to inform and educate users about the latest features and enhancements in Edge and Microsoft 365 Copilot. After a major browser version update, this page will automatically open in a new tab the first-time users launch the updated browser. This one-time experience provides an overview of new capabilities, allowing users to explore and try out these features directly or simply close the tab and continue working as usual.

This message is associated with Microsoft 365 Roadmap ID 526798.

[When this will happen:]

General Availability (Worldwide): Rollout will begin in mid-February 2026 (previously mid-January) and is expected to complete by late February 2026 (previously late January).

[How this will affect your organization:]

• Who is affected: All users signed in with their Entra ID using Microsoft Edge for Business.
• What will happen:
  • After a major browser update, the “What’s New” page will open automatically in a new tab the first time the browser launches.
  • This feature will be on by default.
  • Admins can disable this experience using the WhatsNewPageForEntraProfilesEnabled policy, which will be available once the feature rolls out.

[What you need to do to prepare:]

No admin action is required before rollout. However, you may:

• Review your current configuration to determine the impact on your organization.
• Notify your users about this change.
• Update any relevant internal documentation.

[Compliance considerations:]

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

Updated January 13, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

Microsoft Planner will soon support Microsoft Information Protection (MIP) sensitivity labels at the content level. This enhancement enables encryption, restricts unauthorized actions such as copying, printing, or exporting plan contents, and adds visual markings like watermarks for clear sensitivity awareness. By enforcing content-level protections, Planner helps organizations prevent data leaks, maintain compliance, and enable secure collaboration without impacting productivity. This update aligns Planner with Microsoft Purview standards for consistent enforcement of security and data protection policies.

This message is associated with Microsoft 365 Roadmap ID 523819.

[When this will happen:]

General Availability (Worldwide): Rollout will begin in early December 2025 and is expected to complete by late January 2026 (previously mid-December 2025).

[How this affects your organization:]

Who is affected: Admins and users of Microsoft Planner across Microsoft 365 tenants.

What will happen:

• Planner will support Microsoft Information Protection (MIP) sensitivity labels at the content level.
• Container-level labels (already supported) control who can join a plan and enforce restrictions like guest access and sharing limits.
• Content-level labels (new):
  • Block copy, print, and export actions.
  • Enforce read-only access for highly confidential plans.
  • Restrict duplicating or exporting plans.
• Feature will be enabled by default and progressively available across all tenants by December 15, 2025.

Screenshot 1: Label Picker

Screenshot 2: Label Details

Screenshot 3: Label induced restrictions

[What you can do to prepare:]

• No changes are required for existing labels.
• Review Purview label protection settings (copy/print/export restrictions) and confirm RMS usage rights align with expected Planner behaviors.
• Update governance guidance and user training for label behaviors in Planner.
• Update help and user training for label behaviors in Planner.

Learn more: Learn about sensitivity labels (updates in progress)

FAQ

Question: What label types does Planner support now?
Answer: Planner has long supported container‑level labels (Teams/M365 Group/roster access controls). With this release, Planner adds enforcement for content‑level labels (block copy/print/export, read‑only, etc.) on plans and tasks consistent with Microsoft Purview policies and RMS usage rights.

Question: Which plan types are covered and when?
Answer: Rollout begins with Roster Plans followed by Group‑backed Plans.

Question: Do I need to change any Purview policies or configurations?
Answer: No changes are required for existing labels; however, you should review label protection settings (e.g., copy/print/export restrictions) and confirm RMS usage rights align with expected Planner behaviors. Update governance guidance accordingly.

Question: How does this interact with Loop and Teams meeting notes/TLC?
Answer: Loop meeting notes apply a single content label across the page and its components (including Task List components (TLC)). Planner now inherits and enforces those restrictions on the corresponding roster plan, preventing prior sync breaks when restrictive labels were applied.

Question: What happens to guest/external users under different label combinations?
Answer: Container labels determine who can be added; content labels determine what actions are permitted. For example, guests can be added when the container allows it, but content‑level restrictions may prevent plan access or actions (copy/export/print).

Question: Who can change a plan’s sensitivity label?
Answer: Typically, owners/editors with the appropriate rights can change labels. Permissions are enforced service‑side and reflected in the UI according to RMS usage rights.

[Compliance considerations:]

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

Updated January 13, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

We are introducing a new dashboard in Teams Admin Center (TAC) that gives admins new visibility into user voice and face enrollment data to help organizations better understand usage of AI-dependent capabilities such as speaker attribution, voice isolation, and face-based room experiences. Dashboard data includes enrollment status, counts, and aggregate metrics

This update also adds the ability for admins to view and delete end-user voice and face enrollment data directly from TAC. These controls strengthen compliance posture and provide more direct management of sensitive data.

This message is associated with Roadmap ID 506750.

[When this will happen:]

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

[How this will affect your organization:]

• Who is affected: Admins managing Microsoft Teams in Teams Admin Center.
• What will happen:
  • A new voice and face enrollment dashboard will appear in Teams Admin Center.

  

  • Admins will gain data deletion capabilities, allowing removal of voice or face enrollment data for individual users or batches of users.
  • Deleted data is permanently removed, and users will need to re-enroll to continue benefiting from features such as speaker attribution or personalized AI meeting experiences.
  • There is no change to default enrollment behavior. Existing policies and user controls remain unchanged.

[What you need to do to prepare:]

• No action is required to enable this feature. It will appear automatically as part of the rollout.

[Compliance considerations:]

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

Updated January 13, 2026: Anthropic as a subprocessor is rolling out to the Researcher agent in phases, so the Anthropic option in Researcher may not be available for all tenants yet. Broad availability is expected by the end of January 2026. Use Claude with Researcher in Microsoft 365 Copilot

[Introduction:]

In September, Anthropic models became available in certain Copilot experiences through an opt-in setting, where use was subject to Anthropic’s commercial terms and data processing agreement. On January 7, 2026, Anthropic models will be enabled by default for many customers and now offered under the Microsoft Product Terms and Data Protection Addendum. To enable this change, Anthropic has been onboarded as a Microsoft subprocessor. This transition extends Microsoft’s contractual commitments and data protection standards to the use of Anthropic models in Copilot experiences.

[How this affects your organization:]

Who is affected:

• Admins managing Microsoft 365 Copilot and Microsoft Copilot Studio.
• Microsoft 365 Copilot licensed customers participating in select Frontier features such as Word, Excel, PowerPoint, and Researcher agents, as well as Agent Mode in Excel.

Key changes

• Dec 8, 2025: New admin toggle for Anthropic models appears in the Microsoft 365 admin center (MAC). For most commerical cloud customers, it will be enabled ON by default (except customers in EU/EFTA and UK will be OFF by default). See “customer and region exclusions” section below for more details.
• January 7, 2026: Anthropic as a Microsoft subprocessor becomes enabled on your tenant; the legacy admin toggle to opt-in to Anthropic’s commercial terms and data processing agreement is deprecated.
  • If you previously opted in to the legacy Anthropic toggle, and you’re in an excluded region, you would need to opt in to the new subprocessor toggle.
• Admins can opt out in MAC now – no need to wait until January.

Some features are only available when Anthropic models are enabled. If you turn off this option, certain features may no longer be accessible.

Customer and region exclusions:

The following customers and regions will not have the toggle set to default on:

• Customer tenants in EU/EFTA and UK: The toggle will be set to default off. You will need to opt in to use Anthropic models as a subprocessor.
• Government clouds (GCC, GCC High, DoD) or sovereign clouds: Anthropic models are not yet available in government or sovereign clouds. No toggle will be present for those clouds.

What does it mean that Anthropic is now a Microsoft subprocessor?

As a subprocessor for Copilot experiences, Anthropic will operate under Microsoft’s direction and contractual safeguards. This includes coverage under the Microsoft Data Protection Addendum (DPA) and Product Terms. In addition, use of Anthropic models in Microsoft 365 Copilot falls under our Enterprise Data Protection as described here. Note that Anthropic models are currently excluded from EU Data Boundary and when applicable, in-country processing commitments. 

Learn more:

• Integrate and manage Anthropic’s AI models in Microsoft 365 Copilot
• Enterprise data protection in Microsoft 365 Copilot and Microsoft 365 Copilot Chat
• Use Claude with Researcher in Microsoft 365 Copilot
• Get started with Word, Excel, and PowerPoint Agents (Frontier) in Microsoft 365 Copilot
• Choose an external model as the primary AI model – Microsoft Copilot Studio

Updated January 13, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

We’re introducing a new Slack to Microsoft Teams migration tool to help organizations seamlessly transition collaboration from Slack to Teams. This tool enables administrators to migrate content from Slack public and private channels into Teams shared, public, and private channels, reducing complexity and improving continuity.

• Targeted Release: Rollout begins in late January (previously early December) and completes by late January 2026.
• General Availability (Worldwide): Rollout begins in late January 2026 and completes by early March 2026.

Who is affected: Microsoft 365 administrators managing Teams and Slack migrations.

What will happen:

• A new Slack to Teams migration tool will appear in the Migration and imports page of the Microsoft admin center.

Screenshot 1: On the setup page, users can specify a Slack export file and select a workspace to migrate.



Screenshot 2: On the migration page, users can run migration tasks and monitor their execution status.



• Admins can:
  • Review Slack channels eligible for migration.
  • Migrate Slack channel content to Teams channels.
• Initial release supports Slack channel content only; future updates will expand to other Slack content types.
• No changes to existing Teams functionality.
• Feature is available by default; no opt-in required.

• No action is required before rollout.
• If planning a migration:
  • Review Slack channels for migration readiness.
  • Communicate this change to IT and helpdesk teams.

Learn more: Migrating from Slack to Microsoft Teams – Microsoft Teams | Microsoft Learn

[Compliance considerations:]

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

[Introduction]

We’re updating the retention period for direct export download containers in Microsoft Purview eDiscovery to improve storage efficiency and security. Starting February 16, 2026, direct export packages created from eDiscovery cases will expire after 14 days. 

[When this will happen:]

This change will take effect on February 16, 2026.

[How this affects your organization:]

• Who is affected: eDiscovery users who create and download direct export packages from eDiscovery cases in Microsoft Purview.
• What will happen:
  • Direct export download containers will expire 14 days after export process creation.
  • After expiration, the container will no longer be available for download.
  • This applies only to exports created after February 16, 2026. Existing exports created before this date are not affected.
  • The eDiscovery interface will display a clear banner when an export has expired.
  • Exports from Review Sets are not impacted by this change.

[What you can do to prepare:]

• No action is required if your organization typically downloads exports within 14 days.
• If needed:
  • Ensure eDiscovery users download required exports within 14 days of creation.
  • Communicate this change to your eDiscovery team and update internal documentation.
  • Expired exports can be regenerated by re-running the export from the original search using the same sources and conditions.
• Learn more: Export search results in eDiscovery | Microsoft Learn

[Compliance considerations:]

[Introduction]

We’re updating the default behavior of the tenant setting Capacities can be designated as Fabric Copilot capacities. Beginning on or after February 12, 2026, this setting will be enabled by default for all tenants.

This update affects only the tenant setting itself. It will not modify an existing capacity configuration. If your organization has not enabled any capacities for Fabric Copilot, this default change will have no impact on your current setup.

[When this will happen]

This change will begin rolling out on or after February 12, 2026.

[How this affects your organization]

Who is affected:

• All tenants
• Fabric capacity admins

What will happen:

• The tenant setting Capacities can be designated as Fabric Copilot capacities will be automatically enabled by default.
• Capacity admins will see the setting turned on in the Fabric Admin portal.
• If your current capacities are not enabled for Fabric Copilot (FCC), this update will not alter or impact them.
• Tenants that proactively opt out before rollout will be excluded from the default-on update.

[What you can do to prepare]

No action is required unless you prefer not to adopt this default-on behavior at rollout.

If your organization wants to opt out of the automatic default-on update:

1. Turn the Copilot capacity designation setting on in the Fabric admin portal.
2. Then turn the setting off immediately.

This action signals that your organization plans to enable Copilot capacities later, and we will skip applying the automatic change to your tenant.

Learn more: 

• Capacities can be designated as Fabric Copilot capacities – Copilot tenant settings | Microsoft Fabric | Microsoft Learn
  
• Fabric Copilot capacity | Microsoft Fabric | Microsoft Learn

[Compliance considerations]

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

[Introduction]

We’re enhancing Activity Explorer in the Microsoft Purview compliance portal to provide better visibility into sensitive data detected in Exchange Online. Today, admins can only view email message bodies when investigating Data Loss Prevention (DLP) or Information Protection events. With this update, admins will be able to preview flagged email attachments directly within Activity Explorer—without downloading the email—simplifying investigations and reducing risk exposure.

This message is associated with Microsoft Roadmap ID 543969.

[When this will happen]

General Availability (Worldwide) rollout will begin in early February 2026 and complete by early February 2026.

[How this affects your organization]

Who is affected: Admins who use Microsoft Purview Activity Explorer to investigate Data Loss Prevention (DLP) or Information Protection events in Exchange Online.

What will happen:

• Admins will be able to preview email attachments flagged for sensitive data directly within Activity Explorer:



• A preview pane will appear for supported file types.
• Email downloads will no longer be required for most investigations.
• The feature will be enabled by default; no configuration changes will be required.
• Existing DLP and Information Protection policies will remain unchanged.

[What you can do to prepare]

• No action is required. This update will take effect automatically after rollout.
• (Optional) Communicate this improvement to your security and compliance teams.
• (Optional) Update internal investigation workflows or documentation.

[Compliance considerations]

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

[Introduction]

We’re introducing the Data Security Posture Agent, available in public preview December 24, 2025. This agent helps data security admins proactively discover sensitive data across your organization’s data estate and assess associated risks. By leveraging large language models (LLMs), it goes beyond traditional keyword-based analysis to understand the purpose and context of content, enabling more accurate risk identification and actionable insights.

This message is associated with Roadmap ID 542188.

[When this will happen:]

• Public Preview (Worldwide): Rollout begins mid-December 2025 and completes by late December 2026.
• General Availability (Worldwide): Rollout begins mid-March 2026 and completes by late March 2026.

[How this affects your organization:]

Who is affected: Admins managing data security and compliance in Microsoft Purview.

What will happen:

• A new Data Security Posture Agent will be available in Microsoft Purview under the Explore Agent tab.



• The agent uses LLM-powered natural language discovery to:
  • Search documents, emails, and messages for sensitive data.
  • Assess risks based on context and intent, not just keywords.
• Provides:
  • GenAI-generated summaries.

  

  • LLM-assisted job completion tasks.
  • Actionable recommendations to improve security posture.
• Default setting: The feature requires admin setup; it is not enabled automatically.

[What you can do to prepare:]

• Set up the agent in Microsoft Purview > Explore Agent using the required admin roles.
• Review your organization’s data security policies and ensure admins have appropriate permissions.
• Communicate this change to your security and compliance teams.

Learn more: 

• Security Copilot Agents in Microsoft Purview overview (preview) | Microsoft Learn (will be updated before rollout)

[Compliance considerations:]

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 January 13th, 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
• Current Channel
• Current Channel
• Current Channel
• Monthly Enterprise Channel
• Monthly Enterprise Channel
• Monthly Enterprise Channel
• Monthly Enterprise Channel
• Monthly Enterprise Channel
• Monthly Enterprise Channel
• Monthly Enterprise Channel
• Monthly Enterprise Channel
• Semi-Annual Enterprise Channel
• Semi-Annual Enterprise Channel
• Semi-Annual Enterprise Channel
• Semi-Annual Enterprise Channel

• This security update includes improvements that were a part of update KB5072033 (released December 9, 2025).
• This update makes quality improvements to the servicing stack, which is the component that installs Windows updates.
• This update addresses an issue where you might experience RemoteApp ​​​​​​​connection failures in Azure Virtual Desktop environments. This might occur after installing KB5070311.
• This update addresses an issue where devices with a Neural Processing Unit (NPU) might stay powered on when idle.

• Windows 11, versions 25H2 and 24H2: KB5074109
• Windows 11, version 23H2: KB5073455
• Windows 11 Enterprise LTSC 2024: Hotpatch Baseline
• Windows 10, versions 22H2 and 21H2: KB5073724
• Windows 10 Enterprise LTSC 2019 and Windows Server 2019: KB5073723
• Windows 10 LTSB 2016 and Windows Server 2016: KB5073722
• Windows Server 2025: KB5073379
• Windows Server 2025 Datacenter: Azure Edition: Hotpatch Baseline
• Windows Server 2022: KB5073457
• Windows Server 2022 Datacenter: Azure Edition: Hotpatch Baseline
• Windows Server 2012 R2: Monthly Rollup: KB5073696
• Windows Server 2012: Monthly Rollup: KB5073698
• Windows Server 2008 R2 Service Pack 1: Monthly Rollup: KB5073695 / Security Only: KB5073699
• Windows Server 2008 SP2: Monthly Rollup: KB5073697 / Security Only: KB5073700