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

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

Prompt categories will be available in Microsoft Copilot Dashboard in Microsoft Viva Insights on the web to help you understand key Copilot use cases for your organization. In Microsoft Copilot Chat (work), which is grounded in work data, these prompt categories will include Ask and find, Catch up, Draft and brainstorm, and Other. These metrics will be added to the metrics library in the advanced insights app.

Learn more about Copilot Dashboard licensing requirements in Connect to the Microsoft Copilot Dashboard for Microsoft 365 customers | Microsoft Learn

This message is associated with Microsoft 365 Roadmap ID 486698.

Public Preview: We will begin rolling out in early September 2025 (previously mid-September) and will complete by late September 2025

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

[How this will affect your organization:]

Users enabled to view Copilot dashboard will see these updates:

1. Adoption tab: Prompt categories will be available at Viva Insights > Microsoft Copilot Dashboard > Adoption > Adoption by app > Copilot Chat (work) dropdown:

2. Impact tab: Admins can go to Viva Insights > Microsoft Copilot Dashboard > Impact > Copilot chat card > Explore more button to access the prompt categories as metrics in the Copilot impact trend section and the Comparison between groups section:

This change will be available by default.

[What you need to do to prepare:]

This rollout will happen automatically by the specified dates with no admin action required before the rollout. You may want to notify your admins and/or users about this change and update internal documentation.

Review and assess the impact for your organization. You might consider reviewing with your works council and updating your training and documentation as appropriate.

Learn more: Connect to the Microsoft Copilot Dashboard for Microsoft 365 customers | Microsoft Learn

Updated January 29, 2026: We are updating this post as a reminder. Upcoming SharePoint Online changes may impact your organization. Please review the below.

We are implementing the following changes to custom scripting and classic publishing in SharePoint Online.

1. Disablement of custom scripting

Custom scripting will be disabled by default (setting DenyAddAndCustomizePages to 1 or $true) for sites created with the following templates:

• BLANKINTERNETCONTAINER#0 = Classic Publishing Portal Site
• CMSPUBLISHING#0 = Classic Publishing Site
• BLANKINTERNET#0 = Classic Publishing Site Blank
• CSPCONTAINER#0 = SharePoint Embedded Site

NOTE:

• Existing classic publishing sites created with the templates listed above will have custom scripting disabled by default.
• Disabling custom scripting does not affect the execution of scripts that have already been added to a site or page.

Refer to this documentation to learn more about the security considerations of ungoverned scripting.

2. Ability to set site property bag valued without requiring custom scripting enablement.

Users no longer need to set DenyAddAndCustomizePages to $false or 0 (i.e. enable custom scripting) in a site to manage site property bag values. We have introduced a new AllowWebPropertyBagUpdateWhenDenyAddAndCustomizePagesIsEnabled setting at the site level and at the tenant level to allow adding/managing site property bag values. Please see documentation here for tenant level setting and here for the site level setting. 

3. Classic publishing sites creation and feature activation changes

Users will no longer be able to create new classic publishing related site collections or activate publishing features in existing site collections. This applies to both UX and API interactions.

Sites collections with the following templates cannot be created:

• BLANKINTERNETCONTAINER#0 = Publishing Portal Site
• CMSPUBLISHING#0 = Publishing Site
• BLANKINTERNET#0 = Publishing Site Blank
• ENTERWIKI#0 = Enterprise Wiki
• SRCHCEN#0 = Enterprise Search Center
• SPSSITES#0 = Site Directory
• SPSNHOME#0 = News Home Site
• PRODUCTCATALOG#0 = Product Catalog
• SPSREPORTCENTER#0 = Report Center
• SPSTOPIC#0 = Topic Area Template

Existing classic publishing enabled site collections are unaffected and can continue regular usage, including creation of sub sites.

[When this will happen]

Both changes, the extended custom scripting governance and the new classic publishing restrictions, will take effect starting September 15, 2025.

[How this will affect your organization]

• When custom scripting is disabled in classic publishing sites, users will no longer be able to use script editor web parts, create custom master pages or page layouts, and utilize several other features. More details on features affected when custom scripting is disabled can be viewed in this documentation.

• With the change to stop the creation of new classic publishing site collections and publishing feature activation, SharePoint admins will no longer be able to create new classic publishing enabled site collections or enable publishing features at site collection level.

[What you need to do to prepare]

We recommend taking the following actions to prepare for these upcoming changes.

1. Inform owners of the classic publishing sites in your organization of these upcoming changes. Promote switching to use of Modern sites. Refer to this guide.

2. The following tenant-level opt-out operation, used to allow custom scripting changes in classic publishing sites, will be retired starting March 15, 2026. Please ensure appropriate actions are taken ahead of this change.

Set-SPOTenant -DelayDenyAddAndCustomizePagesEnforcementOnClassicPublishingSites $true

3. Customers may still temporarily opt out of custom scripting enforcement for a specific site (any template) with tenant admin approval. This opt-out is effective for 24 hours and can be enabled using the following PowerShell command:

Set-SPOSite <SiteURL> -DenyAddAndCustomizePages $false

4. If you need to allow the creation of new classic publishing site collections or enable publishing feature activations, use the following PowerShell command set the flag to allow.

Set-SPOTenant -AllowClassicPublishingSiteCreation $true

NOTE:

• You need to install the latest (16.0.26211.12010 or higher) SharePoint Online Management Shell in order to run the commands above.
• The DelayDenyAddAndCustomizePagesEnforcementOnClassicPublishingSites command is scheduled to end starting on March 15, 2026, while all other commands are expected to remain functional beyond that date. 

[Compliance considerations]

There is no impact or change to compliance.

[Referenced content]

Security considerations of allowing custom script – SharePoint in Microsoft 365 | Microsoft Learn

Allow or prevent custom script – SharePoint in Microsoft 365 | Microsoft Learn

SharePoint modernization guidance | Microsoft Learn

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

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

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

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

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

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

What will happen:

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

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

Screenshot 2 – Expanded organization chart view:

What you can do to prepare

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

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

Compliance considerations

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

Updated January 28, 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 mid-February 2026 (previously end of January) and expect to complete by early March 2026 (previously mid-February).

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

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 29, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction:]

We’re introducing a visual refresh of the Access Request and Access Denied page experience across Microsoft 365, redesigned to help users quickly request access to content such as documents, SharePoint sites, or Teams meeting recordings. This update features modern Fluent illustrations, animations, and clearer messaging to make it easier to understand and resolve access issues for a more seamless collaboration experience.

This message is associated with Roadmap ID 553214.

[When this will happen:]

General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out in February 2026 (previously early January) and expect to complete by March 2026 (previously early February).

[How this will affect your organization:]

Who is affected: All users requesting access to content stored on OneDrive and SharePoint.

• Users will see a redesigned Access Request page when attempting to access restricted content: 



• The page will feature updated Fluent visuals and animations.
• Messaging will be clearer to help users understand the status of their request:



• No changes to admin policies or access controls.
• The update will be enabled by default.

[What you need to do to prepare:]

No action is required to enable this update; it will be applied automatically.

However, to ensure a smooth experience for your users, we recommend the following:

• Communicate this change to helpdesk and support staff so they can assist users who may have questions about the new visuals or messaging.
• Update internal documentation if you reference the Access Request or Access Denied experience in training materials or support guides.
• Review any custom workflows or access request processes to ensure they align with the updated experience.
• Monitor user feedback after rollout to identify any confusion or support needs related to the new design.

[Compliance considerations:] 

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

[Introduction]

As AI agents become deeply embedded in enterprise ecosystems, they are evolving beyond simple tools or workflows into an autonomous digital workforce. These agents can interpret user intent, access and manipulate enterprise data, execute actions on behalf of users, and even make real-time decisions. In many ways, they operate like human insiders only with machine-speed data processing capabilities.

To govern and protect these agents effectively, organizations require visibility into their activities, contextual understanding of their actions, and the ability to flag or block risky behavior. Now, Insider Risk Management can be extended to detect and remediate potentially risky agent activities.

Features:

• Copilot Studio & Azure AI Foundry Integration: Detect potentially risky activities of agents hosted on Copilot Studio, Azure AI Foundry, and Agent 365 platforms
• Risky AI Usage Policies: Define and enforce policies specific to AI agents accessing sensitive data or performing high-risk actions.
• IRM for Agent Users: Extend IRM in Purview to govern agent-driven workflows and protect organizational data.

This message is associated with Microsoft 365 Roadmap ID 516032.

[When this will happen:]

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

[How this affects your organization:]

On the Overview page in the Insider Risk Management solution, you will be able to access the overall risk profile of agents deployed in your organization.

The Risky Agents policy will be automatically deployed for all agents hosted on Copilot Studio and Azure AI Foundry across your organization. Alerts from this policy will be generated when an agent’s activity exceeds the thresholds configured in this automatically deployed Risky Agents policy. These alerts can be found under Agents > Alerts on the left pane.

[What you can do to prepare:]

• Review the public facing documentation to learn more about this exciting new offering: Learn about Insider Risk Management policy templates | Microsoft Learn
• Review the new Insider Risk Management interface in the Microsoft Purview portal, which now includes separate sections for Users and Agents.
• Review and tune the Risky Agents policy based on your organization’s requirements.
• If you don’t wish to track agent activities, you can delete the automatically deployed Risky Agents policy. 

Learn more:

• Help dynamically mitigate risks with Adaptive Protection | Microsoft Learn
• Create and manage Insider Risk Management policies | Microsoft Learn
• Learn about Insider Risk Management policy templates | Microsoft Learn

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

[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 threads created by that domain
  • New group 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]

We’re introducing improved support for viewing code blocks in the Microsoft Teams mobile app for iOS and Android. This update responds to customer feedback from technical and developer-focused teams who rely on accurate, readable code formatting when collaborating on the go.

[When this will happen]

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

[How this will affect your organization]

Who is affected: All users of the Microsoft Teams mobile app on iOS and Android.

What will happen:

• Users will be able to view code blocks sent from Teams desktop or web clients directly on mobile devices.
• Code blocks will appear as a message object (similar to a file preview) optimized for small screens:

   

• Tapping the preview will open a full-screen reader that includes:
  • Syntax highlighting
  • Line numbers
  • Scrollable containers for long snippets
• No admin controls are added with this update.
• This feature is enabled by default and requires no configuration.
• There is no impact to existing messaging workflows or policies.

[What you can do to prepare]

• No admin action is required. The feature will roll out automatically.
• Optional actions:
  • Notify developer or technical user groups who may benefit from this improvement.
  • Update internal documentation if you maintain guidance on using code blocks in Teams.
• Review Microsoft Teams documentation for more about code block formatting.

[Compliance considerations]

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

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

[When this will happen]

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

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

[Introduction]

We are introducing new AI workflows in the Workflows app for Microsoft Teams, powered by Microsoft 365 Copilot. These workflow templates use scheduled Copilot prompts to automate routine or complex tasks with guided setup. This update is designed to help users streamline daily operations and improve productivity through intelligent automation. Admins can control availability through existing Teams app management settings.

This feature is available only to users with a Microsoft 365 Copilot license and applies to Teams for Web and Teams for Mac.

This message corresponds to Microsoft 365 Roadmap ID 500379.

[When this will happen]

General Availability (Worldwide): Rolling out in late January 2026 and expected to complete by mid‑February 2026.

[How this affects your organization]

Who is affected:

• Users who have a Microsoft 365 Copilot license
• Users with access to the Workflows app in Microsoft Teams
• Users on Teams for Web or Teams for Mac

What will happen:

• Users will see new AI workflow templates in the Workflows app powered by scheduled Copilot prompts.
• Templates help automate recurring or complex tasks with simplified setup.
• The feature is off by default unless the Workflows app is enabled for your organization.
• Existing admin policies for Teams app availability and optional connected experiences continue to apply.
• There is no impact for users who are not assigned a Copilot license or who do not have access to the Workflows app.

Screenshot 1- Workflow setup experience:

Screenshot 2 – Workflow templates in the Workflows app:

[What you can do to prepare]

If you want users to access this feature:

• Review how scheduled prompts work in Microsoft 365 Copilot.
• Ensure the Workflows app is enabled in the Teams admin center.
• If you prefer to disable this functionality:
  • Use Cloud Policy to set Allow the use of additional optional connected experiences in Office to Disabled.
  • This also disables scheduled prompts in Microsoft 365 Copilot across apps.

Learn more:

• Manage scheduled prompts for Microsoft 365 Copilot
• Overview of optional connected experiences in Office

If you do not plan to use this feature, no action is required.

[Compliance considerations]

Introduction

Microsoft is improving the reading and review experience in Microsoft 365 Copilot by enabling PDFs to open directly within Copilot when users click them. This update streamlines content access and reduces context switching based on customer feedback.

When this will happen:

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

How this affects your organization:

   Who is affected:

• All Microsoft 365 users who interact with PDFs in Microsoft 365 Copilot.
• A Microsoft 365 Copilot license is required to use this feature.

   What will happen:

• Users who click a PDF inside Copilot will have it open directly within the Copilot interface.
• The feature is enabled by default for all tenants.
• No admin configuration changes are required.
• Existing Purview policies for PDFs continue to apply.

What you can do to prepare:

• No action is required from administrators.
• Optionally notify helpdesk/support teams of the updated PDF experience.
• Update internal documentation if it describes Copilot PDF behavior.

Compliance considerations:

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

[Introduction]

We’re introducing a new capability that enables users to open Outlook emails directly within any full‑app Microsoft 365 Copilot experience, including Copilot chat. This enhancement helps reduce context switching by allowing users to view referenced emails alongside their Copilot interaction.

[When this will happen:]

General Availability (Worldwide): rollout begins mid-February 2026 and is expected to complete by late February 2026.

[How this affects your organization:]

Who is affected:

• All users who access Microsoft 365 Copilot full‑app experiences, including Copilot chat.

What will happen:

• Users will be able to open Outlook emails directly from references or sources shown in Copilot chat.
• Emails will open side‑by‑side within the Copilot experience.
• The feature is enabled by default.
• Existing Microsoft 365 permissions and data access models remain unchanged.
• No changes are made to Outlook, Exchange Online, or Copilot admin controls.

[What you can do to prepare:]

• No administrator action is required.
• Update internal documentation if needed.

[Compliance considerations:]

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

[Introduction]

Microsoft Teams is introducing a new Drafts quick view feature to help users easily find, edit, and send draft messages. This enhancement improves productivity by making unsent drafts more accessible.

This message is associated with Roadmap ID 542789.

[When this will happen:]

• Targeted release: Rollout will begin mid-February 2026 and is expected to complete by late February 2026.
• General Availability: Rollout will begin mid-March 2026 and is expected to complete by late March 2026.

[How this affects your organization:]

• Who is affected: All Microsoft Teams users on desktop platforms (Windows, macOS, Linux).
• What will happen:
  • Users will see a new Drafts quick view option in Teams.
  • Clicking the quick view will display all unsent draft messages for easy editing and sending.
  • The feature will be ON by default; no admin configuration is required.

[What you can do to prepare:]

• No action is needed from admins.
• You may choose to inform your helpdesk or update internal documentation to reflect this new capability.

[Compliance considerations:]

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

[Introduction]

As Microsoft Teams calling adoption continues to grow across organizations, scam and phishing attempts targeting users through voice calls are increasing as well. Currently, users have no simple way to report suspicious calls, leaving organizations without visibility into these threats and without clear guidance on how users should respond. 

To address this gap, we’re introducing Report a Call in Microsoft Teams. With this feature, users can flag suspicious or unwanted one-to-one calls directly in Teams, giving your security team actionable intelligence and helping build organization-wide protection against bad actors. 

This message relates to Microsoft 365 Roadmap ID 536573.

[When this will happen]

Targeted Release: Rollout will begin in mid-March 2026 and will be completed in late March 2026.

General Availability (Worldwide): Rollout will begin in mid-April 2026 and is expected to be completed in late April 2026.

[How this will affect your organization]

Who is affected: Users who make or receive calls in Microsoft Teams on Windows, Mac, and Web.

What will happen:

• A new Report a Call option will appear in Teams call history for one-to-one calls only (ON by default on the Teams client).
• Users will be able to click more options next to any call and select Report a Call.
• Relevant call metadata and limited contextual information will be securely shared with your organization and Microsoft.
• Security teams will view detailed reported instances in the Microsoft Defender portal, which will require Defender for Office 365 (Plan 1 or Plan 2) or Defender XDR.
• Information about user-submitted reports will be available in Teams Admin Center under Protection reports > User-reported security submissions. 
• Admins will be able to investigate and take appropriate action.

[What you can do to prepare]

While the reporting option is enabled by default on Teams clients, you can configure the Microsoft Defender portal to receive and access these reports or access basic submissions data in Teams admin center.

1. For enhanced reporting, enable the setting in the Microsoft Defender portal:

• Navigate to User reporting settings.
• Ensure the Teams call reporting setting is enabled.
• Without this, detailed reported calls will not appear in the defender portal.

Alternatively, you can view reports in the Teams admin center:

• Open Teams admin center > Analytics & Reports > Protection Reports.
• Select User-reported security submissions from the drop-down.
• Select the desired time period and interaction mode (Calls).

2. Prepare user communication:

• Inform users about the new Report a Call option before rollout.
• Clarify when to use it: suspicious calls, potential scams, unwanted calls from external parties.
• Set expectations: reporting helps the organization, not just individual complaints.

To disable the experience on the Teams client:

• In the Teams admin center, under Calling settings, disable the Report a Call toggle.

[Compliance considerations]

Data Processing: 

Limited call-related metadata is processed when a user submits a report, including:

• Call timestamp and duration
• Caller ID information (if available)
• Teams user IDs for participants
• User’s reason for reporting (if provided)

• Form API: Retrieve forms by ID, manage their visibility, and interact with controls.
• List API: Access lists, toggle their visibility, and retrieve HTML elements.
• User API: Handle authentication actions like sign-in and sign-out.
• Web API: Use OData-compliant methods to create, retrieve, and query records.

• The Settings Agent now supports more languages, with expanded support for German, Portuguese, Spanish, Korean, Japanese, Hindi, Italian, and Chinese (Simplified).*
• This update expands the functionality of Cross‑Device Resume. You can continue activities from your Android phone on your PC based on the apps and services you use, including resuming Spotify playback, working in Word, Excel, or PowerPoint, or continuing a browsing session.
• This update improves MIDI on Windows with enhanced support for MIDI 1.0 and MIDI 2.0, including full WinMM and WinRT MIDI 1.0 support with built-in translation, shared MIDI ports across apps, custom port names, loopback and app-to-app MIDI, plus performance improvements and bug fixes—delivering a better experience for musicians.
• Narrator now gives you more control over how it announces on‑screen controls. You can choose which details are spoken and adjust their order to match how you navigate apps. These settings apply throughout the app to help reduce extra speech and make Narrator easier to follow.
• Windows Hello Enhanced Sign-in Security (ESS) now supports peripheral fingerprint sensors. This update extends this more secure sign-in option beyond devices with built-in fingerprint sensors to include desktops and other Windows 11 PCs, including Copilot+ PCs.

• Windows 11, versions 25H2 and 24H2: KB5074105