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

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

Introduction

You can now deploy, manage, and measure a frontline worker (FLW) pilot directly from Teams Admin Center. This new capability enables Teams administrators to define pilot users and owners, configure workloads, and monitor adoption—all in one place. It’s designed to help IT admins and business leaders streamline the rollout of Teams features tailored for frontline teams.

This message is associated with Microsoft 365 Roadmap ID 498226

When this will happen

Public Preview: Rolling out early November 2025; expected completion by mid-November 2025.

General Availability: Rolling out late February 2026 (previously mid-November 2025); expected completion by end of February 2026 (previously late November 2025).

How this affects your organization

This feature provides a simplified experience for piloting Teams capabilities for frontline workers. Admins can:

• Select and configure workloads such as Chat, Channels, Shifts, Walkie Talkie, Viva Engage, and Tasks.
• Assign pilot users and owners.
• Share access to the Teams mobile app via QR code.
• Monitor adoption and usage insights directly in Teams Admin Center.

What you can do to prepare

To prepare for this rollout:

• Identify frontline worker pilot participants and the workloads you want to enable.
• Review your Teams Admin Center settings to ensure you have the necessary permissions.
• Plan communications with pilot users to support adoption.
• Learn more: [Link to be provided]

Compliance considerations

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

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

Expected with Intune’s March (2603) release, all guided scenarios, except Windows 365 Boot, will be removed from the Intune admin center.

[How this will affect your organization:]

Admins will no longer have access to the guided scenario wizards in the Intune admin center. However, any Intune objects previously created by these wizards, such as policies and apps, will remain and can continue to be managed as usual.

[What you need to do to prepare:]

No action is required, only awareness. This change will not impact existing configurations or require admin intervention.

For alternative solutions and step-by-step guidance, refer to the following resources:

• Microsoft Intune product and capabilities documentation | Microsoft Learn
• Intune prescriptive guides
• Intune administration guides: https://setup.cloud.microsoft/intune
• Securing apps for mobile | Android
• Securing apps for mobile | iOS
• Configuring Intune and Configuration Manager to co-manage devices
• Manage and secure devices for Windows
• Microsoft Copilot in Intune | Microsoft Learn

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

[Introduction]

Coming soon to SharePoint: Tenant admins will be able to centrally manage site branding using PowerShell. This update supports consistent branding across all SharePoint sites by enabling enforcement of enterprise themes, disabling custom branding on specific sites, and auditing branding changes. These capabilities help organizations maintain a unified brand experience and improve governance.

This message is associated with Roadmap ID 526794.

[When this will happen:]

• Targeted Release (Worldwide): Begins late November 2025, completes mid-December 2025
• General Availability (Worldwide, GCC, GCC High, DoD): Begins end of February 2026 (previously mid-January), completes end of February 2026 (previously late January)

[How this affects your organization:]

Who is affected: Tenant admins managing SharePoint Online branding and governance.

What will happen:

• Admins can disable or enable custom site branding per site using PowerShell.
• When site branding is disabled, site managers lose access to Site branding page in Site Settings.
• Admins can apply enterprise themes (including multi-color themes) to specific sites via PowerShell.
• Branding changes made via PowerShell are tracked for audit and accountability.
• New site creation scripts can include branding settings to ensure consistency from launch.
• Admins can remove existing Brand Center via PowerShell.
• Theme management via PowerShell is transitioning to a centralized model:
  • The primary geo will act as the central location for organization-wide theme creation and management.
  • Satellite geos will be able to view and apply themes from the primary geo using Get-SPOTheme and Set-SPOWebTheme cmdlets.
  • Themes previously created in satellite geos will remain available, but creating new themes in satellite geos will no longer be supported.

[Here’s what’s new:]

• Consistent branding enforcement: Admins can disable or enable custom branding per site. When disabled, site managers lose access to Site branding page in Site Settings.
• Automated theme application: Apply approved enterprise themes (including multi-color themes) to specific sites using PowerShell.
• Audit and transparency: All branding changes made via PowerShell are tracked, enabling visibility into who made updates.
• Automated site creation with branding: Embed theme settings directly into site creation scripts to ensure new sites launch with consistent branding.
• Easier Brand Center management: Admins can remove an existing Brand Center via PowerShell to reset or update branding controls.
• Centralized theme management across geos: Themes created in the primary geo are visible and applicable in satellite geos. Satellite geos can apply but not create new themes going forward.

[What you can do to prepare:]

• Review PowerShell documentation:
  • Set-SPOSite
  • Get-SPOTheme
  • Set-SPOWebTheme
• Upgrade your SharePoint Online Management Shell to the latest version after rollout.
• Communicate branding governance changes to your SharePoint admin team.
• Update internal documentation to reflect new PowerShell capabilities and theme management model.

[Compliance considerations:]

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

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.

• Data processing outside of Microsoft: Anthropic’s Claude model is hosted outside Microsoft. Data processed by Claude is outside Microsoft-managed environments and audit controls.
• Microsoft agreements do not apply: Microsoft’s Product Terms, Data Processing Addendum, data residency commitments, audit and compliance requirements, SLAs, and Customer Copyright Commitment do not apply when using Anthropic services.
• Third-party integration: Use of Anthropic services is governed by Anthropic’s Commercial Terms of Service and Data Processing Addendum.

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

We’re introducing the ability for organizations to customize Microsoft 365 profile cards by adding up to 10 custom properties sourced from external systems such as HR platforms. This enhancement helps enrich user profiles with relevant organizational details, improving discoverability and context for collaboration.

This message is associated with Microsoft 365 Roadmap ID 529851.

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

Who is affected: Microsoft 365 tenant admins managing user profile cards

What will happen:

• You can add up to 10 custom properties to profile cards using Microsoft Graph People connectors.
• Properties can be sourced from external systems (such as HR platforms).
• This feature is OFF by default and requires admin configuration to enable.
• Admins can configure visibility, display name, and icon for each property in Microsoft 365 admin center under: Settings > Org settings > People settings > Profile > Person info on profile cards 

  

• Once enabled, properties appear in the Contact Information section of profile cards in Outlook Web:



• Changes may take up to 24 hours to propagate across profile cards.
• Future updates will include direct ingestion from SAP SuccessFactors and Workday connectors.

• Review external systems for properties you want displayed on profile cards.
• Ingest these properties using a Microsoft Graph People connector.
• Configure visibility and enable properties in the Microsoft 365 admin center.
• Communicate this change to helpdesk staff and update internal documentation if needed.

Learn more: Microsoft 365 Copilot connectors for people data | Microsoft Learn

Compliance considerations

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

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

[Introduction]

Express voice enrollment in Microsoft Teams makes registering your voice profile quick and seamless. A voice profile enables features such as voice isolation, speaker recognition, identification in meeting rooms, improved transcripts, and enhanced meeting recaps and insights powered by Microsoft 365 Copilot. If you haven’t enrolled, you’ll receive an in-product prompt to opt in and enroll simply by speaking during a meeting. Admins can enable or disable this feature for their organization.

This message is associated with Roadmap ID 537269.

[When this will happen:]

• Targeted Release: Rollout begins early March 2026 (previously early February) and is expected to complete by mid-March 2026 (previously mid-February).
• General Availability: Rollout begins mid-March 2026 (previously mid-February) and is expected to complete by end of March 2026 (previously end of February).

[How this will affect your organization:]

Who is affected:

• All enterprise Microsoft Teams customers except Education (EDU) tenants.

What will happen:

• A new voice enrollment experience will be available in Teams.
• Users will receive an in-product prompt to enroll their voice profile by speaking during a meeting.
• The feature will be ON by default for enterprise tenants.
• EDU tenants are excluded from this rollout.
• If your organization previously disabled voice enrollment policies, this feature will not apply.
• Admins can manage this setting using new PowerShell cmdlets under the PassiveVoiceEnroll configuration in the csTeamsAIPolicy policy.

[What you can do to prepare:]

• Review your organization’s Teams AI policy settings before rollout.
• If you want to disable this feature, update the PassiveVoiceEnroll configuration using PowerShell.
• Communicate this change to your helpdesk and end users as needed.
• Update internal documentation to reflect this new capability.

[Compliance considerations:]

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

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

[Introduction]

We’re introducing Viva Engage communities in Microsoft Teams to make it easier for employees to connect, share, and learn across your organization. This new experience brings discoverable, asynchronous conversations and leadership engagement into Teams—helping employees explore ideas and perspectives beyond project-based collaboration.

This message is associated with Microsoft 365 Roadmap ID 513274.

[When this will happen]

• General Availability (Worldwide): April 2026 (previously March) to May 2026 (previously April)

[How this affects your organization]

Who is affected: All Microsoft Teams users with access to Viva Engage.

What will happen:

• This feature is available to all Microsoft Teams customers with a standard Microsoft 365 and Teams license and access to Viva Engage. No additional Teams license is required.
• Communities will appear in Teams navigation:
  • Unified view: New section in the Chat app.
  • Split view: New section in the Chats and Channels app.
• Existing Viva Engage community memberships will sync into Teams.
• Favorited communities in Engage will appear in Teams favorites.
• Notifications for announcements and mentions will surface in Teams Activity feed and deep link to the new experience.
• Rich engagement features include:
  • Posting discussions, questions, praise, polls, and announcements (admins only).
  • Reactions, delegated posting (requires setup in Viva Engage), and scoped search.
  • Event participation: ask questions, upvote, view live or replay.
• Admins can manage community settings, membership, and roles directly in Teams.
• Default setting: ON for all tenants.

[What you can do to prepare]

• No immediate action required unless you want to disable this feature.
• To turn off communities in Teams:
  • Go to Teams admin center > Viva Engage settings > Toggle OFF.
• Ensure prerequisites:
  • Viva Engage IPs and URLs are not blocked.
  • Sign-ins for Viva Engage are enabled in Microsoft Entra ID.
  • Users have Microsoft 365 and Teams licenses.
• Consider sharing best practices and customization options with users.
• Coordinate with Viva Engage admins for internal change communications.

Learn more:  

• Getting started with Viva Engage Communities in Microsoft Teams | Microsoft Support
• Manage Viva Engage experiences in Microsoft Teams | Microsoft Teams | Micosoft Learn

[Compliance considerations]

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

We’re expanding the ability for users to report suspicious Microsoft Teams messages to customers with Microsoft Defender for Office 365 Plan 1. Previously available only to Plan 2, this update helps security teams identify and investigate potential phishing, malware, and spam across internal and external Teams chats, channels, and meeting chats. This enhancement strengthens protection by incorporating user-reported signals into existing Defender detections.

Users will be able to report messages in two ways:

• Report as security risk — for messages suspected to contain phishing, malware, or other malicious content.
• Report as not a security risk — for messages that were incorrectly identified as threats (false positives).

This message is associated with Microsoft 365 Roadmap ID 531760.

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

Who is affected:

• Microsoft 365 tenants using Microsoft Defender for Office 365 Plan 1
• Users across Microsoft Teams
• Security admins reviewing reported messages

What will happen:

• Users will see options to report messages as security risks or not security risks. 
• Reports will appear on the User reported page in the Defender portal and/or your configured mailbox.
• This feature is opt-in and respects your existing User reported settings.
• Teams admin center toggles for reporting will be automatically enabled when User reported settings are turned on.

• Enable and configure User reported settings in the Defender portal.
• Review message reported destination preferences for reported messages.
• Communicate reporting guidance to users.
• Review supporting documentation.
• Update internal documentation as needed.

Learn more: 

• How your submissions to Defender for Office 365 are processed behind-the-scenes | Microsoft Defender for Office 365 Blog
• Turn off or turn on user reporting of Teams messages in the Defender portal | Microsoft Learn
• User reported message settings in Microsoft Teams | Microsoft Defender for Office 365 | Microsoft Learn

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

To support broader reporting needs and customer feedback, the Queues app will soon allow users to view up to 45 days of historical data for call queues, auto attendants, and agents. This update expands reporting options without changing how users access or create reports.

This message is associated with Microsoft 365 Roadmap ID 547825.

[When this will happen]

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

[How this affects your organization]

Who is affected:

• Users with access to historical reports in the Queues app.

What will happen:

• Users can view up to 45 days of historical data.
• The default 7-day range remains unchanged.
• No changes to report access, permissions, or workflows.

[What you can do to prepare]

• No action is required.
• Optional: Inform users of the expanded range and update internal documentation.
• Learn more about historical reporting: Auto attendant and Call queue historical reports | Microsoft Teams | Microsoft Learn.

[Compliance considerations]

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

[Introduction]

To help administrators troubleshoot Data Loss Prevention (DLP) and Information Protection issues more efficiently, we’re introducing new diagnostics in Microsoft Purview. These enhanced tools provide deeper visibility into why specific DLP or labeling policies are triggered for files and emails.

This message is associated with Roadmap ID 547833.

[When this will happen:]

• Public Preview: We will begin rolling out mid-January 2026 and expect to complete by mid-February 2026.
• General Availability (Worldwide): We will begin rolling out early April 2026 and expect to complete by early May 2026.

[How this affects your organization:]

Who is affected:

Microsoft 365 administrators managing DLP, Information Protection labels, and Purview compliance operations.

What will happen:

• As part of this update, administrators will gain insights into:
• Sensitive Information Types detected in a document or email
• Labels applied to a file
• DLP policies triggered based on content analysis
• The following diagnostics experiences will become available:
• DLP SharePoint Diagnostics – Analyze policy matches for SharePoint Online content
• DLP Exchange Online (EXO) Diagnostics – Validate DLP triggers for email scenarios
• Auto-Labeling Diagnostics for SharePoint and OneDrive – Review label assignment and policy alignment for stored files
• No impact to user workflows.
• No changes to existing configurations or policy enforcement.
• Diagnostics are enabled by default.

[What you can do to prepare:]

No action is required.

• Review the diagnostics experience at:
  • Microsoft Purview Data Loss Prevention Diagnostics
  • Microsoft Purview Information Protection Diagnostics
• Share these resources with compliance, helpdesk, or security teams.
• Update internal documentation if needed.

[Compliance considerations:]

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

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

[Introduction]

Agent Mode in PowerPoint for Microsoft 365 Copilot introduces a conversational way for users to edit presentations while maintaining existing formatting, structure, and branding. This enhancement enables users to guide Copilot to update slides, refine layouts, and iterate on content using enterprise data. This capability is available in PowerPoint for the web.

Screenshot – Entry point for PowerPoint Agent Mode

This message is associated with Roadmap IDs 548520 and 548646.

[When this will happen:]
General Availability (Worldwide): Rollout will begin mid-February 2026 and complete by mid-March 2026.

[How this will affect your organization:]

Who is affected:
Users in your organization who use the PowerPoint web application and have Microsoft 365 Copilot licenses.

What will happen:

• Users will gain access to Agent Mode in Microsoft 365 Copilot for PowerPoint for the web.
• Users can interact with Copilot Chat to edit and refine presentation content.
• Formatting, structure, and branding will be preserved.
• Users can use Enterprise assets to further enhance the presentation.
• Agent mode is available to all eligible users by default; no action is needed by Admins.
• Note: Agent Mode is part of Copilot Chat within PowerPoint for the web and is not a standalone feature.

[What you need to do to prepare:]
No action is required.

• Communicate availability of Agent Mode to helpdesk staff and users.
• Encourage users to explore the feature to improve presentation workflows.
• Review and update internal documentation if you provide guidance on PowerPoint for the web or Copilot usage.

[Compliance considerations:]

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

[Introduction]

Brand Impersonation Protection for Teams Calling adds proactive safeguards against fraudulent or deceptive external callers who attempt to appear as trusted organizations. This helps reduce social-engineering risks and improves tenant security when users receive first-contact external calls. This update aligns with Microsoft’s ongoing investments in caller identity protection and secure collaboration.

This message is associated with Microsoft 365 Roadmap ID 543239.

[When this will happen:]

Targeted Release: Rollout will begin mid-February 2026 and is expected to complete by late February 2026.
General Availability: Timelines will be communicated in a future message.

[How this affects your organization:]

Who is affected:

• All organizations using Microsoft Teams Calling that receive inbound VoIP calls from first-contact external callers.

What will happen:

• Teams will evaluate inbound calls for signs of brand impersonation.
• Users will see high-risk call warnings before answering suspicious calls.
• Warnings may continue during the call if risk signals persist.
• Users can accept, block, or end the call.
• The feature will be enabled by default.
• Existing Teams Calling policies remain unchanged.

[What you can do to prepare:]

No admin action is required at this time.

• Inform helpdesk staff that users may begin seeing high-risk call warnings.
• Update internal training materials if applicable.
• Review Microsoft documentation on caller ID security when available.

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

[Compliance considerations:]

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

[Introduction]

To help admins detect unusual or potentially risky interactions with external organizations, Microsoft Teams is introducing the External domains anomalies report. This report analyzes cross-tenant communication patterns for your tenant and highlights sudden spikes or abnormal engagement activity. These insights support proactive investigation and help protect your organization while enabling secure external collaboration.

This message is associated with Microsoft 365 Roadmap ID 536572.

[When this will happen]

• General Availability (Worldwide): Rolling out in late February 2026 and expected to complete in March 2026.

[How this affects your organization]

Who is affected:

• Teams administrators can view this report for their Microsoft 365 tenant if their organization collaborates with external organizations.

What will happen:

• A new External domains anomalies report will be available in the Microsoft Teams admin center under Protection reports.
• Admins can select Communication anomalies, choose a date range, and run the report to view results:
• Insights include external domains with unusual communication activity:
  • External domain name
  • Total anomalies detected
  • New 1:1 chat threads created by that domain
  • New group chat threads created by that domain
• A Block option is available directly in the report for managing external domains:

[What you can do to prepare]

No action is required to access the report.

To receive proactive alerts:

• Enable External domains anomalies alerts in the Teams admin center:
  • Go to Notifications & alerts > Rules.
  • Select External domains anomalies.
  • Set status to Active.
• Specify a Teams channel for notifications if desired.



• Daily alerts will summarize the top five domains with unusual activity.

[Compliance considerations]

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

[Introduction]

With this release, users with a Microsoft 365 Copilot license will be able to set up custom calendar instructions so that Copilot will proactively RSVP to new meeting requests and remove canceled meetings on their behalf. For example, users will be able to instruct Copilot to “Always accept meetings from /name if my calendar is free,” “Always follow meetings after 5pm,” or “Always remove canceled meetings from my calendar,” helping keep their calendars up to date and clutter free. After instructions are set, Copilot will monitor relevant calendar events and take the appropriate action. All actions will appear in notifications in the Copilot button on the Outlook calendar, helping reduce calendar clutter, resolve untriaged invites, and keep users focused on the meetings that matter. This feature will be available only in the new Outlook and Outlook for web.

The first-run experience for calendar instructions will roll out later and will be the primary way users discover this feature.

[When this will happen]

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

[How this will affect your organization]

Who is affected:

• Users with a Microsoft 365 Copilot license using the new Outlook or Outlook for web.

What will happen:

• Users can set custom calendar instructions that allow Copilot to automatically respond to incoming meeting invites.
• Users can create an instruction for Copilot to always remove canceled meetings from their calendars.
• Copilot will monitor relevant calendar events and perform actions proactively after instructions are set.
• Users will receive notifications and activity logs for all calendar actions Copilot completes.
• No admin policies will change; the feature is available to licensed users as part of Copilot’s calendar capabilities.
• A first-run experience that introduces users to calendar instructions will roll out later to help users discover the feature.

[What you can do to prepare]

• Ensure users who need this capability have a Microsoft 365 Copilot license.
• Inform helpdesk staff or update internal documentation as needed.
• No additional admin configuration is required.

[Compliance considerations]

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

As communicated in MC1125485 and Configure Microsoft Entra multifactor authentication – Microsoft Entra ID | Microsoft Learn, we will retire the Custom greetings feature in Voice call authentication on February 28, 2026. This feature allowed organizations to customize voice call greetings for multifactor authentication (MFA). After this date, voice call authentication messages will use Microsoft’s default recordings.

How this affects your organization

Starting February 28, 2026, the custom greeting feature will no longer be available. Voice call authentication will revert to Microsoft’s default voice recordings. If your organization relies on custom greetings for branding or user recognition during MFA, this change may impact the user’s experience.

What you need to do to prepare

• This retirement will happen automatically on the specified dates. If your organization is still using the Custom greetings feature, begin preparing users for the transition to Microsoft’s default voice greetings.
• Review your multifactor authentication configuration and ensure users are aware of the upcoming change: Authentication methods – Microsoft Entra admin center
• For guidance on planning and implementing Microsoft Entra multifactor authentication, see: Deployment considerations for Microsoft Entra multifactor authentication – Microsoft Entra ID | Microsoft Learn

[Introduction]

Viva Glint Reporting users like managers and leaders will be able to retrace their navigation flow i.e. drill down and drill up in reports rather than lose their navigation flow within reports. Navigation improvements will replace “Go Back” to Reporting home page with an alternative clickable UX to enable users to go back to the last page of reporting they were in. In other words, this feature will cater to Back navigation improvements in Reporting.

This message is associated with Roadmap ID 547836.

[When this will happen:]

General Availability (Worldwide, GCC): Rollout will begin in early February 2026 and complete by mid-February 2026.

[How this affects your organization:]

• Who is affected: Managers and leaders who use Viva Glint Reporting.
• What will happen:
  • The “Go Back” link at the top of reports will be replaced with a new navigation option.
  • Users will be able to return to the previous state of the report rather than the Reporting home page.
  • This enables drill-down and drill-up navigation within reports.
  • The feature will be ON by default for all tenants.
  • No admin configuration is required.

Screenshot: “Go back” in reports has been replaced by a new navigation experience enabling drill-down and drill-up.

[What you can do to prepare:]

• No action is required from admins.
• You may want to inform managers and leaders about this improved navigation experience.

[Compliance considerations:]

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

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

• Current Channel

[When this will happen:]

We'll be gradually rolling out this update of Microsoft 365 Apps to users on that update channel starting January 21st, 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 this latest update and begin deployment.

[What you need to do to prepare:]

To get more details about this update view the following release notes:

• Current Channel