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

het nieuws van Microsoft message center roadmap en blogs - KbWorks - SharePoint and Teams Specialist

25-January-2026 Below you will find a collection of news published yesterday. This news consists of Microsoft’s Roadmap when it is updated it will be below with items. Then there will be a section with the message center, if there is anything new there, this will be automatically included. And it contains a piece from blogs that I follow myself and would like to share with you. If I miss something in the blogs that do have an RSS feed, please let me know.

This entire post was automated via Microsoft Flow
have fun reading!

Items from the MessageCenter in Microsoft 365

(Updated) Microsoft Viva Engage: Smarter delivery of Community Announcement notifications
Category:Microsoft Viva
Nummer:MC1143276
Status:planForChange

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

Introduction

We hear your feedback about ways we can improve the notifications experience in Viva Engage. It’s always a fine balance between ensuring your users are notified of relevant content without notifications feeling too overwhelming or noisy. In response to your feedback, we’re rolling out an intelligent notifications experience. Specifically, this change will improve how Community Announcement notifications are delivered. This smarter delivery approach optimizes notifications delivery based on a user’s engagement behavior, helping to reduce notifications fatigue while ensuring timely visibility of announcements. 

When this will happen

General Availability (Worldwide): We will begin rolling out this change in mid-September 2025 and expect the rollout to reach GA (General Availability) by February 6, 2026 (previously end of January).

How this affects your organization

Previously, when an admin created a new Community Announcement, this would send a notification in Teams and Mobile Push immediately, followed by an email notification two hours later if the announcement was not opened already in Teams and/or Mobile Push.  With this new update:

  • Users will now receive the notification in one channel only—either Teams, Mobile Push, or Email. This notification channel may differ by user and is selected based on where a user has engaged with Engage notifications most frequently in the past 30 days. 
  • If the announcement is not opened within two hours in the first notification channel, a secondary notification channel will be sent, also determined by where a user engages with Engage notifications most frequently. 

We will continue to respect all user notification preferences and settings where applicable. If a notification channel is disabled or the app is not installed, it will not be selected as a potential notification channel for the Community Announcement delivery.

Note that this change applies only to regular Community Announcements in Viva Engage and does not affect the “immediate” Community Announcement feature (where admins can still select the checkbox to send emails immediately —this functionality remains unchanged).

Can I still notify Community users via email immediately (along with other notification channels)? 

Yes! In Viva Engage, we offer an option to send an “immediate” Community Announcement. With this feature, Community admins can choose to send email notifications immediately after posting a Community Announcement, even if a user has opted out of receiving emails. All other notification channels will also send immediately along with email, including Teams and Mobile Push. Therefore, we recommend admins to use this feature when there is a Community Announcement that requires immediate attention from users. 

Community Admins can find this “immediate” Community Announcement option by firstly navigating to the announcement publisher and selecting the hyperlinked “option to send emails immediately” at the bottom of the publisher. Upon clicking this option, an additional pop-up box will open called “Immediate email delivery”. By selecting this checkbox, this will ensure that all three notification channels – Email, Teams, and Mobile Push – will send to customers immediately after a Community Announcement is made. 

 What you can do to prepare

No admin action is required. However, we recommend:

  • Informing your users about the new notifications change to reduce confusion
  • Monitoring user feedback and engagement with Community Announcements’ notifications delivery
  • Reviewing internal communication strategies to align with the new notification’s behavior

Compliance AreaExplanation
Does the change alter how existing customer data is processed, stored, or accessed?Yes. Notification delivery logic now uses user behavior data (last 30 days of notification engagement) to determine delivery channels. This data is used to personalize delivery but is not stored permanently.
Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data?Yes. The system uses behavioral data to determine the most effective notification channel, which is a form of machine learning-based personalization.
Does the change provide a new way of communicating between users, tenants, or subscriptions?Yes. The change modifies how users receive communications (Community Announcements) by introducing a dynamic, behavior-based delivery method.
(Updated) Microsoft Word, Excel, and PowerPoint agents: A new Copilot experience for content creation
Category:Microsoft 365 apps Microsoft Copilot (Microsoft 365) Microsoft 365 Copilot Chat
Nummer:MC1187799
Status:stayInformed

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

[Introduction]

We’re introducing new Word, Excel, and PowerPoint agents in Microsoft 365 Copilot to help users create documents, workbooks, and presentations more efficiently in Copilot Chat within the Frontier program. These agents assist with creating documents, workbooks, and presentations by using web and enterprise grounding. Each agent supports multi-turn chat, enabling user to refine content through an interactive back-and-forth conversation.

[When this will happen:]

  • General Availability: We will begin rolling out on January 29, 2026.

[How this affects your organization:]

If your organization is part of the Frontier program and has enabled Anthropic usage in your tenant, users will be able to access Word, Excel, and PowerPoint agents via the navigation pane in the M365 Copilot app or within the Tools menu in Copilot chat across Word, Excel and PowerPoint. Additionally, users can invoke these agents by typing “@” followed by the agent name (for example, @PowerPoint).

user settings

Who is affected:

  • Copilot Chat users in the Microsoft 365 Copilot app in the Frontier Program.

What will happen:

  • Users will have access to the following Copilot agents:
    • Word agent: Assists with research, formatting, layout, and content refinement for documents such as strategic plans, policy documents, and technical papers.
    • Excel agent: Supports data analysis, formula generation, trend identification, and summarization of insights.
    • PowerPoint agent: Helps generate presentations from outlines or documents, suggests layouts, and refines visual storytelling.
  • Each agent supports multi-turn chat for iterative content development.
  • Users can perform high-level iterations on the generated files via chat directly in the Word, Excel, and PowerPoint agents. For more extensive or granular editing, users can open their documents in the respective applications.
  • user settings

  • The feature will be ON by default for tenants with Copilot access, Frontier enabled, and for tenants who have opted into Anthropic usage. If Anthropic usage is disabled by the admin, the agents will not appear in the user experience. Learn more: Connect to Anthropic’s AI models | Microsoft Learn.

[What you can do to prepare:]

  • No action is required at this time.
  • Communicate availability to helpdesk or content teams.
  • If desired, review internal documentation or training materials to reflect the new capabilities.

Learn more: Get started with Word, Excel, and PowerPoint Agents in Microsoft 365 Copilot (Frontier)

[Compliance considerations:]

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

(Updated) Microsoft Defender for Office 365: Admins can block external users in Microsoft Teams from Defender Portal
Category:Microsoft Teams Microsoft Defender XDR
Nummer:MC1200058
Status:stayInformed

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

[Introduction]

We’re introducing an integration between Microsoft Teams and Microsoft Defender for Office 365 that allows security admins to manage blocked external users in Teams through the Tenant Allow/Block List (TABL) in the Microsoft Defender portal. This centralized approach enhances security and compliance by enabling organizations to control external user access across Microsoft 365 services.

This message is associated with Roadmap ID 542189.

[When this will happen:]

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

[How this affects your organization:]

Who is affected: Organizations using Microsoft Teams and Microsoft Defender for Office 365 Plan 1 or Plan 2.

What will happen:

  • Security admins (with Teams admin permission) can add, delete, and view blocked external users and domains for Teams in the Microsoft Defender portal.
  • Screenshot 1: Image showcasing the teams block sender and block domain list in Microsoft Teams

    user settings

  • Incoming communications (chats, channels, meetings, and calls) from blocked users will be prevented.
  • Existing communications from blocked users will be automatically deleted.
  • Audit logs will track actions taken to block users for compliance monitoring.
  • Entry limits: Up to 4,000 blocked domains and 200 email addresses can be configured for Teams.
  • This applies to all Teams clients and the Defender XDR web portal.
  • Existing federation configurations and domain blocks in the Teams admin center remain unaffected.

[What you can do to prepare:]

  • Enable the setting “Block specific users from communicating with people in my organization” in the Teams admin center (default: Off).
  • Screenshot 2:  Image showing the teams toggle for blocking sender email addresses in Microsoft Teams

    user settings

  • Enable the setting “Allow my security team to manage blocked domains and blocked users” in the Teams admin center (default: Off).
  • Grant security team access to manage blocked domains and users in the Teams admin center.
  • Review internal documentation and inform helpdesk staff about this change.
  • Learn more: Tenant Allow/Block List documentation.

[Compliance considerations:]

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

Dynamics 365 Contact Center – Customize transfers and consults for queues, representatives
Category:Dynamics 365 Apps
Nummer:MC1221931
Status:stayInformed
We are announcing the ability to customize transfers and consults for queues and customer service representatives in Dynamics 365 Contact Center. This feature will reach general availability on January 26, 2026.

How does this affect me?
This feature allows administrators to manage the queues or customer service representatives who are available during a consult or transfer action. On the Consult and transfer page in the Copilot Service admin center, administrators can configure FetchXML queries for the following scenarios:
  • Consult to queue
  • Consult with a representative
  • Transfer to a queue
  • Transfer to a representative
The system dynamically tailors the queues or customer service representatives that can be consulted with or transferred to according to your configuration options.

What action do I need to take?
This message is for awareness, and no action is required.
Message Trace support on Graph API is now in Public Preview
Category:Exchange Online Microsoft 365 suite
Nummer:MC1221939
Status:planForChange

[Introduction]

We’re introducing Message Trace support on Microsoft Graph to provide a modern, REST‑based API experience for tracing email across your Exchange Online organization. This update aligns with our ongoing effort to move message trace support from the legacy Reporting Web Service to Microsoft Graph. Public Preview is now available, and General Availability roll-out begins January-end.

[When this will happen]

Public preview (worldwide): Available now.

General availability (worldwide): Rollout begins in late January 2026 and is expected to complete by early February 2026.

[How this affects your organization]

Who is affected: Admins and developers who use automated or programmatic message trace capabilities in Exchange Online. Admins and developers who use Reporting Web Service for message trace.

What will happen:

  • Message trace and message trace detail functionality is now available through Microsoft Graph API.
  • The API provides a modern, RESTful experience for querying message trace data.
  • This feature will replace the message trace and message trace detail endpoints in the legacy Reporting Web Service.
  • Retirement of the Reporting Web Service message trace endpoints begins April 6, 2026.
  • New Exchange Online organizations already do not have access to message trace support via the Reporting Web Service.
  • No user impact: this change affects admin and developer tooling only.

[What you can do to prepare]

[Compliance considerations]

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

Take Action: Out-of-band update to address cloud‑backed storage application issues
Category:Windows
Nummer:MC1222123
Status:preventOrFixIssue
Microsoft released today a resolution for an issue observed after installing the January 2026 Windows security update. This issue may cause applications that open or save files stored in cloud‑backed locations to become unresponsive or display errors. Some installations of Outlook may also become unresponsive and fail to open when PST files are stored in cloud‑backed storage such as OneDrive.
 
An out-of-band (OOB) update was released today, January 24, 2026, to address this issue. This cumulative update includes all protections and improvements from the January 2026 Windows security update released January 13, 2026, as well as from the OOB update released on January 17, 2026 (which introduced fixes for two known issues: remote desktop connections and hibernation failures). 

This OOB update is available through Windows Update for Windows 11 devices running the updates released this month. To install it, open Settings > Windows Update, and select Download and install. Note that this update will show up in Windows Update only if you have installed one of the updates released in January that caused this issue. Some devices may install the update automatically. For supported versions of Windows Server and Windows 10, the OOB update is available from the Microsoft Update Catalog. Refer to the KB articles below for detailed information and installation steps.

  • Windows 11, versions 25H2 and 24H2: KB5078127
  • Windows 11 Enterprise versions 25H2 and 24H2: Hotpatch KB5078167
  • Windows 11, version 23H2: KB5078132
  • Windows 10 ESU (22H2) and Windows 10 Enterprise LTSC 2021: KB5078129
  • Windows Server 2025: KB5078135
  • Windows Server 2025 Datacenter: Azure Edition: Hotpatch KB5078239
  • Windows Server, version 23H2: KB5078133
  • Windows Server 2022: KB5078136
  • Windows Server 2022 Datacenter: Azure Edition: Hotpatch KB5078238
  • Windows Server 2019 and Windows 10 Enterprise LTSC 2019: KB5078131

IT administrators using Microsoft Intune or Windows Autopatch should follow the guidance below for installing the OOB update via Windows Update.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top