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

Updated January 14, 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 January 2026 (previously mid-January) and expect to complete by end of January 2026 (previously end of December 2025).

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

Introduction

We’re introducing enhancements to the focus area experience in Viva Glint to improve how organizations track and act on employee feedback. With this update, focus areas will now be tied to survey cycles, and goal periods will be retired. This change simplifies reporting and aligns focus areas more closely with survey insights.

This update is associated with Microsoft 365 Roadmap ID 498922.

General availability: We will begin rolling out mid-February 2026 (previously mid-January) and expect to complete by mid-February 2026 (previously late January).

After the update, focus areas will be organized by survey cycle instead of goal periods. Glint users will be able to create and report on focus areas based on survey cycles. Goal periods will be retired. Focus areas not linked to a survey cycle (for example, if the cycle has been deleted) will be labeled No survey cycle and remain accessible in the platform. No focus areas will be deleted as part of this change. This update will be enabled by default. 

• No admin action is required for the transition, but we recommend communicating this change to Glint users in your organization.
• Review and update any internal documentation or training materials that reference goal periods. 

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

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

Introduction

We’re updating the default behavior of Microsoft Teams Copilot in meetings. Copilot without transcription will become the default mode for newly scheduled Teams meetings where Copilot is allowed. Additionally, conversation history will now persist during meetings, improving multitasking and continuity of insights.

This update is associated with Microsoft 365 Roadmap ID 478611.

When this will happen

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

[What’s changing?]

Who is affected:

• Affected tenants: If your TeamsMeetingPolicy was created or modified before the Copilot without transcription policy option was introduced (June 2024), your tenant will be affected by this change.
• Not Affected: If your TeamsMeetingPolicy was created or modified after June 2024 when the Copilot without transcription option was introduced, your tenant will not be affected.

What will happen:

• The default Copilot policy will change from EnabledWithTranscript to Enabled for both new and existing Teams meetings where Copilot is allowed.
• Copilot and Facilitator will no longer automatically start transcription for meetings in affected tenants.
• Users must manually enable transcription to use post-meeting Copilot or Facilitator queries.
• Conversation history will persist during meetings for Copilot without transcription.
• Tenants with TeamsMeetingPolicy created or modified after June 2024 are not affected.

If adopting the new defaults:

• Review TeamsMeetingPolicy for transcription dependencies.
• Update internal documentation and training.
• Communicate to users how to enable transcription when needed.

Optional admin steps to retain current behavior:

• Update Global and Custom TeamsMeetingPolicy settings via TAC or PowerShell.
• TAC UI Portal: Navigate to Teams Admin Center and set the Copilot policy default value as required. For example, if the current default value is desired, update it to a different value, then set it back. Please ensure both TeamsMeetingPolicy and all Custom Policies are updated.
• PowerShell example to set Copilot policy to EnabledWithTranscript for all relevant meeting policies:

  get-csteamsmeetingpolicy | ? {
    $_.Identity -ne "Tag:AllOn" -and
    $_.Identity -ne "Tag:AllOff" -and
    $_.Identity -ne "Tag:Default" -and
    $_.Identity -ne "Tag:Kiosk" -and
    $_.Identity -ne "Tag:RestrictedAnonymousAccess" -and
    $_.Identity -ne "Tag:RestrictedAnonymousNoRecording"
  } | % {
    $_.Identity;
    set-csteamsmeetingpolicy -identity $_.Identity -Copilot EnabledWithTranscript
  }
      

Learn more: 

• Manage Microsoft 365 Copilot in Teams meetings and events | Microsoft Teams | Microsoft Learn
• Use Copilot without recording a Teams meeting | Copilot in Teams | Copilot | Microsoft Support

Compliance considerations

Updated January 15, 2026: We are canceling a proposed change related to renaming the existing Calling and Meetings executable.

No action is required from administrators. This change did not introduce a new binary. It involved renaming the existing executable used for Calling and Meetings as a workaround for a Windows compatibility issue. 

What Happened? 

To reduce administrative effort, we partnered with the Windows team to deliver the fix for a Windows compatibility issue. With the Windows fix now fully rolled out in Windows 24H2 and 25H2, the executable name change is no longer required and has been rolled back. 

Was this a security, reliability, or compliance issue? 

• This was not a security or compliance issue. 
• It was a platform compatibility issue in Windows. 
• No customer data, identity, or tenant configuration was at risk. 

Was my tenant impacted? 

Only organizations participating in our Technology Adoption Program (TAP) were affected. Specifically, the change applied only to the TAP Admin earlyadopter subset (Ring 1.5). 

If your organization does not participate in the Microsoft Technology Adoption Program, you were not impacted in any way. The change has been fully rolled back for TAP participants, with no lasting configuration or behavioral changes on client machines. No administrator action is required. 

What if we haven’t deployed recent Windows updates yet? 

We understand that many enterprises deploy Windows cumulative updates on managed timelines. 

• There is no risk or degradation if the referenced Windows KBs are not installed. 
• New features that depend on these Windows updates will explicitly check for the presence of the required KBs and will only enable when they are available. 
• If the KBs are not installed, those features simply remain disabled—no functionality breaks and no admin action is required. 

Windows updates that include the fix 

The Windows compatibility fix is included in Windows updates for versions 24H2 and 25H2, delivered through KB5068861. 

What to expect next? 

• No changes to admin configuration or tenant settings 
• No service disruption 

—Original message—

[Introduction]

We’re improving the performance and startup time of calling features in the Microsoft Teams Desktop Client for Windows. To achieve this, we’re introducing a new child process named ms-teams_modulehost.exe that will handle the calling stack separately from the main application process (ms-teams.exe). This change optimizes resource usage and enhances meeting experiences.

Rollout will begin early January 2026 and complete by late January 2026.

Note: Timelines may shift due to year-end feature flag rollout freeze.

• Who is affected: All users running the Teams Desktop Client on Windows.
• What will happen:
  • A new process (ms-teams_modulehost.exe) will appear in Task Manager under the main Teams process (ms-teams.exe).
  • This process is dedicated to calling features and improves performance.
  • No changes to user workflows or UI; however, admins should ensure endpoint and security software allow this new process.

• Update endpoint management and security software to allowlist ms-teams_modulehost.exe alongside ms-teams.exe.
• Communicate this change to helpdesk staff to avoid confusion during troubleshooting.
• Update internal documentation if you reference Teams process names.
• Make sure the same QoS settings applied to ms-teams.exe are also applied to ms-teams_modulehost.exe. Refer to this page for details: Implement Quality of Service (QoS) in Microsoft Teams
  • DO NOT remove QoS settings of ms-teams.exe. Only add QoS settings for ms-teams_modulehost.exe.

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

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

[Introduction]

We’re adding scheduled prompt capabilities in Microsoft 365 Copilot to help users automate recurring tasks and improve productivity.

A Microsoft 365 Copilot license is required.

This message is associated with Microsoft 365 Roadmap IDs 531912, 531911, 531913, and 531759.

[When this will happen]

• Public Preview (Worldwide): Mid-November 2025 to mid-December 2025
• General Availability (Worldwide): Mid-January 2026 (previously Mid-December 2025) to mid-February 2026 (previously mid-January)

[How this affects your organization]

• Who is affected: Users in organizations enrolled in the Frontier program.
• What will happen:
  • Users can schedule recurring prompts for declarative agents like Analyst and Idea Coach.
  • Users can schedule prompts in the Web tab.
  • Users can edit existing scheduled prompts without deleting and recreating them.
  • Natural language scheduling is available in the Work tab (such as “Help me prepare for my day every Monday at 9 AM”).
  • Feature will be ON by default for eligible tenants.
  • Some agents and tabs may not support scheduled prompts yet; updates will be posted on the Microsoft 365 Roadmap.
  • Editing email notifications and prompt text is coming soon.

Feature Highlights & How to try them

Scheduled prompts for agents

What it does: Allows users to schedule recurring prompts to declarative agents like Analyst, Idea Coach, and more.

Try it: In the Copilot app, navigate to your favorite agent, run a prompt (or find one you’ve run before), hover over the prompt text, and select Schedule this prompt. Fill out scheduling details and hit Save.

Note: Not every agent supports scheduled prompts yet; updates will be posted on the M365 Roadmap.

Scheduled prompts for the Web tab

What it does: Allows users to schedule a prompt in the Web tab.

Try it: In the Copilot app, navigate to the Web Tab, run a prompt (or find one you’ve run before), hover over the prompt text, and select Schedule this prompt. Fill out scheduling details and hit Save.

Edit scheduled prompts

What it does: Allows users to update existing schedules without deleting and recreating them.

Try it: Navigate to the Scheduled prompts management pop-up in the Copilot app. Select your preferred scheduled prompt, click Edit schedule, make your changes, and click Update.

Note: Users can currently only update the schedule of the prompt; support for editing email notifications and the prompt text itself is coming soon.

Natural language support for scheduled prompts

What it does: Allows users to create scheduled prompts directly in chat.

Try it: In the Copilot app, navigate to the Work tab and add a time and recurrence for a prompt you’d like to schedule (such as “Help me prepare for my day every Monday at 9 AM”).

Note: Natural language support is currently only enabled in the Work tab in mainline M365 chat. Support for agents and the Web tab is coming soon.

[What you can do to prepare]

• Ensure your organization is enrolled in the Frontier program via Microsoft admin center.
• Ensure that intended users have a Microsoft 365 Copilot license.
• Communicate this change to helpdesk staff.
• Update internal documentation if you detail Copilot features.

[Compliance considerations]

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

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

[Introduction]

Microsoft 365 Copilot declarative agents are upgrading to the GPT-5.1 model, which uses an “auto” architecture. The orchestrator will automatically select the best model for each scenario, either the fast “chat” model or the advanced reasoning model, based on the user prompt.

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

Who is affected: All tenants using Microsoft 365 Copilot declarative agents.

What will happen:

• Declarative agents will upgrade to GPT-5.1.
• The advanced reasoning model will be available for complex queries.
• No admin configuration changes are required.
• Feature will be enabled by default for all applicable tenants.

No action is required.

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

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

[Introduction]

We’re improving scheduled channel meetings in Microsoft Teams by reducing automatic meeting updates in channel conversations. This change helps keep channels cleaner and focused on real user replies, while meeting details remain accessible when you open the meeting thread.

[When this will happen:]

• Targeted Release: Rolling out mid-January 2026, expected to complete by late January 2026.
• General Availability (Worldwide): Rolling out early February 2026, expected to complete by late February 2026.
• General Availability (GCC, GCCHigh, DoD): Rolling out early March 2026, expected to complete by late March 2026.

[How this affects your organization:]

• Who is affected: All Microsoft Teams users participating in scheduled channel meetings.
• What will happen:
  • Automatic meeting updates in channel conversations will be reduced.
  • Channel threads will appear cleaner and reply counts will reflect actual user responses.
  • Meeting details remain accessible by opening the meeting thread.
  • No admin configuration changes are required; the feature is enabled by default.

[What you can do to prepare:]

• No action is required. This update will roll out automatically.
• Optional: Communicate this change to helpdesk staff to reduce potential confusion.
• For more information on channel meetings, visit: Channel meetings in Teams.

[Compliance considerations:]

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

We are updating Microsoft Loop so that any Entra ID user with OneDrive or SharePoint storage will be able to create Loop workspaces, unless blocked by Cloud Policy. This change aligns workspace creation permissions with existing permissions to create Loop components and pages, simplifying the overall experience.

General Availability (Worldwide): We will begin and complete rollout in mid-February 2026.

Who is affected: This change applies to all Microsoft 365 tenants.

What will happen:

• Users blocked by Cloud Policy (“Create Loop workspaces in Loop” = Disabled): These users will continue to be unable to create Loop workspaces. Cloud Policy will remain the only method to prevent workspace creation.
• Users with Microsoft 365 E3/E5/A3/A5, Business Standard, Business Premium, or Microsoft 365 Copilot licenses: No change. These users can already create Loop workspaces.
• Users without OneDrive or SharePoint storage (for example, Exchange Online Plan 1 or Plan 2): No change. These users still cannot create Loop workspaces because they have no storage location.
• All other users (for example, Office 365 E1/E3/E5, Microsoft 365 F1/F3): These users will be able to create Loop workspaces. This message replaces MC1184645.

No action is required. However, you may want to:

• Review your organization’s Cloud Policy settings to ensure that users who should not create Loop workspaces have the “Create Loop workspaces in Loop” policy disabled.
• Note that assigning or removing the Microsoft Loop service plan will no longer control workspace creation.
• Communicate this change to your help desk or support staff.
• Update internal documentation related to Loop usage.

Learn more:

• Admin policies for Loop components and Loop workspaces | Microsoft 365 | Microsoft Learn
• Summary of governance, lifecycle, and compliance capabilities for Loop | Microsoft 365 | Microsoft Learn

Loop workspaces may require data lifecycle management workflows. Review the Summary of governance, lifecycle, and compliance capabilities for Loop to confirm your policies meet your organization’s needs.

[Introduction]

Microsoft Teams will soon automatically remove hidden metadata (EXIF) from images shared in chats and channels. This helps protect sensitive details such as photo location and device information from being shared without user awareness, improving privacy and security.

This message applies to Teams for Windows desktop, Teams for Mac desktop, and Teams for the web and is associated with Microsoft 365 Roadmap ID 542795.

[When this will happen:]

• Targeted Release: Rollout begins in late January 2026 and completes by early February 2026.
• Worldwide and GCC: Rollout begins in mid-February 2026 and completes by early March 2026.
• GCC High: Rollout begins in late February 2026 and completes by mid-March 2026.
• DoD: Rollout begins in early March 2026 and completes by late March 2026.

[How this affects your organization:]

• Who is affected: All users sharing images in Microsoft Teams chats and channels.
• What will happen:
  • EXIF metadata (e.g., GPS location, camera model, manufacturer info) will be automatically removed from images shared in Teams conversations.
  • The visible image content remains unchanged.
  • No admin action is required; this feature is enabled by default.
  • If users need to retain EXIF data, they can upload images to OneDrive and share a link via Teams.

[What you can do to prepare:]

• Inform end users, security, and compliance stakeholders that EXIF data will no longer be available in Teams-shared images.
• Update internal documentation or training that references sharing metadata via images.
• Review workflows, diagnostics, or integrations that rely on EXIF data and plan alternatives.

[Compliance considerations:]

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

[Introduction]

We are introducing structured document generation with Microsoft Forms in SharePoint. This capability will help organizations generate standardized, compliant documents through simple form-driven experiences. It will reduce manual effort, improve template consistency, and support governance across high-volume document workflows. Creating and configuring structured document forms will require a Microsoft 365 Copilot license.

This message is associated with Microsoft Roadmap ID 545896.

[When this will happen]

General availability (Worldwide): Rollout will begin in early February 2026 and will complete by late February 2026.

[How this affects your organization]

Who is affected:

• All Microsoft 365 tenants using SharePoint Online
• Users with a Microsoft 365 Copilot license who will create structured document forms

What will happen:

• Users with a Microsoft 365 Copilot license will be able to create structured document forms linked to approved SharePoint templates.
• Business teams will be able to maintain and enforce template governance while enabling document generation across the organization.
• Users will be able to generate consistent, compliant documents by completing a form.
• Existing SharePoint permissions, governance policies, and information management controls will continue to apply.
• Document generation through published forms will be available based on standard SharePoint permissions.
• The feature will be on by default; no admin action will be required.

Screenshot 1 – Review and refine AI-suggested fields before publishing:

Screenshot 2 – Edit content and apply advanced template customizations, including conditional sections in Word:

[What you can do to prepare]

No admin action is required. You may choose to:

• Inform business stakeholders who manage templates and document workflows.
• Review opportunities to streamline document processes with form-driven generation.
• Update internal documentation or training materials if needed.

Watch the video: Generate documents by filling in the form (18 seconds)

[Compliance considerations]

No compliance considerations identified. Review as appropriate

We’re introducing the ability to save meeting events as drafts in Outlook on iOS. This update helps users start a meeting invitation, pause, and return to it later, providing more flexibility when scheduling on mobile devices.

This message is associated with Microsoft Roadmap ID 545895.

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

Who is affected:

• All users creating calendar events in Outlook on iOS connected to Exchange Online.

What will happen:

• Users will see a new option to save an in-progress meeting as a draft when dismissing an event with at least one attendee:





• Draft events will appear on the calendar with a “[Draft]” label in the title:



• The feature is on by default and requires no admin configuration.
• No changes are made to existing policies or settings.

No admin action is required. You may choose to:

• Inform users about the new “Save as Draft” option in Outlook for iOS.
• Update internal training materials or documentation as needed.

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

• Usage over the last 30 days
• Activity success rates with visual breakdowns
• Interactive charts with monthly success trends