Microsoft Roadmap, messagecenter and blogs updates from 12-02-2026

Updated February 11, 2026: We have updated the timeline. After further review, we will not be rolling this out to GCC, GCCH, DoD, USSec, USNat during the timeline outlined below. We will communicate via Message center in dedicated posts when we are ready to proceed. Thank you for your patience.

We’re introducing the new Microsoft Teams calendar experience, designed to unify and enhance productivity across Microsoft 365. This calendar integrates familiar features with innovations like Microsoft Copilot and Microsoft Places, enabling seamless collaboration from anywhere. It works consistently across Teams, the new Outlook for Windows, Outlook on the web, and Places. As part of this update, the legacy calendar experience will be deprecated, and the toggle to switch between old and new calendars will be removed.

When this will happen

• General Availability (Worldwide): Mid-January 2026 to late February 2026 (previously end of January)

Once this update is deployed, users accessing the Calendar app in Microsoft Teams will see the new calendar experience by default. The toggle to switch between the old and new calendar will be removed, and only the new Microsoft 365 calendar will be available. This change may impact users accustomed to the legacy calendar interface.

No admin action is required. We recommend informing your users about the upcoming change and updating any internal documentation or training materials that reference the legacy calendar experience.

For more information about the new calendar experience, visit the Microsoft Teams documentation.

Compliance considerations

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

Updated February 11, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

We’re introducing Multi-Select Forward in Microsoft Teams. This feature lets users select up to five messages from a chat or channel and forward them together in one message, preserving context and order. This update addresses customer feedback for easier message sharing and supports better collaboration.

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

[When this will happen:]

• Targeted Release: We will begin rolling out early January 2026 and expect to complete by mid-January 2026.
• General Availability (Worldwide, GCC): We will begin rolling out early February 2026 (previously mid-January) and expect to complete by mid-February 2026 (previously late January).
• General Availability (GCCH, DoD): We will begin rolling out mid-February 2026 (previously early February) and expect to complete by late February 2026 (previously mid-February).

[How this affects your organization:]

Who is affected: Users of Microsoft Teams for Desktop, Mac, and web

What will happen:

• A new option will be available in the message action menu: Forward > Multiple messages.



• They can select up to five messages and forward them together. 



• Forwarded messages appear bundled in one message, preserving order and context.



• Mobile users can view these messages but cannot forward multiple messages yet. 
• This feature is ON by default.

[What you can do to prepare:]

• No admin action is required before or after rollout.
• Consider notifying your users about this change to help them understand the new behavior.
• Update any internal documentation or training materials that reference message forwarding in Teams.

Learn more: Forward a message in Microsoft Teams – Microsoft Support

[Compliance considerations:]

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

Updated February 11, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

We are bringing digital signage capabilities to Teams Rooms on Android, similar to what is available for Teams Rooms on Windows. This update allows IT admins to display dynamic content—such as announcements, news, or organizational information—on front‑of‑room displays when the room is not in a meeting. Tenant‑wide and room‑specific configuration is available through the Teams Rooms Pro Management portal. This feature supports select third‑party digital signage partners and is included with the Teams Rooms Pro license.

This message is associated with Microsoft 365 Roadmap ID 548647.

[When this will happen

• General Availability (Worldwide): Rolling out in mid-April 2026 (previously early March); expected completion by late April 2026 (previously late March).

[How this affects your organization]

Who is affected:

• Organizations using Teams Rooms on Android.
• Admins managing devices through the Teams Rooms Pro Management portal.
• Tenants with Teams Rooms Pro licenses.

What will happen:

Before the rollout, Teams Rooms on Android show a static front‑of‑room display home screen when not in use.

After the rollout:

• Admins can enable digital signage to display dynamic content when the room is idle:

 

• Supported signage sources include Appspace, XOGO, and custom web URLs.
• Digital signage is configurable at the tenant level and for individual rooms.
• Users can return to the home screen by tapping the touch console.
• Admins can:
  • Choose whether to show the Teams Rooms banner with room info and calendar preview.
  • Configure activation and deactivation timers for signage mode.
  • Determine whether signage mode respects or bypasses OS screen‑timeout settings.
• Custom URL requirements:
  • Must begin with https
  • Must be publicly accessible with no authentication
  • Must support viewing within an iframe
• SharePoint and OneDrive URLs are not supported for custom signage.

Role-based access:

• Global Admins and Teams Rooms Pro Managers can manage tenant‑wide settings.
• These roles can assign additional permissions using Role-based Access Controls (RBAC) for specific rooms or room groups.

[What you can do to prepare]

• Begin planning your digital signage deployment strategy (centralized, localized, or blended).
• Prepare content within supported signage systems.
• After devices update to the minimum required app version:
  • Enable digital signage in the Teams Rooms Pro Management portal by navigating to Settings > Digital Signage.
  • Add signage sources and apply settings to applicable rooms.
• Notify helpdesk and affected users of the upcoming capability.
• Update internal documentation and training materials as needed.

This rollout will occur automatically within the specified rollout window; no administrative action is required before rollout.

Learn more: Configure digital signage on Teams Rooms | Microsoft Teams | Microsoft Learn

[Compliance considerations]

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

[Introduction]

We are retiring the Web Search (Bing) image pivot within the SharePoint page image picker. This feature allowed authors to search the web for images using Bing and insert them into SharePoint pages. Because Microsoft has retired the underlying Bing Search API, the Web Search (Bing) image pivot will no longer function reliably and will be removed from SharePoint Pages.

[When this will happen:]

Retirement will begin in early March 2026 and is expected to be completed by late April 2026.

[How this affects your organization:]

Who is affected:

• All SharePoint Online tenants
• SharePoint page authors who insert images using the page image picker

What will happen:

• The Web Search (Bing) pivot will be removed from the SharePoint page image picker for all tenants.
• Authors will continue to have access to Stock images, Local file upload, Site and tenant assets, and Recent files.
• The change is on by default and applies automatically.
• No admin configuration or policy changes are required.

[What you can do to prepare:]

No action is required before this rollout. You may want to:

• Inform SharePoint authors that web-based image search will no longer be available.
• Update internal training or documentation to highlight supported alternatives.
• Notify help desk staff so they can assist users after the change.

[Compliance considerations:]

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

[Introduction]

To reduce confusion and align the data export experience with Viva Engage networks operating in native mode, we’re retiring two legacy options from the data export experience in the Viva Engage admin center. These options only applied to legacy Yammer networks and are not applicable to Viva Engage networks in native mode. Removing them simplifies the admin experience and aligns exports with how data is stored and accessed today.

[When this will happen:]

• March 13, 2026: The “Include attachments” and “Include external networks” options will be retired (removed) from the Viva Engage admin center data export UI.

[How this affects your organization:]

Who is affected:

• Admins who manage data exports in the Viva Engage admin center
• Organizations with legacy Yammer networks or modern external Viva Engage networks

What will happen:

• File attachments
  • Data exports will continue to include SharePoint file links for attached files.
  • Admins who need the actual files must download them directly from the SharePoint location referenced by the link in the export.
• External networks
  • Admins must sign in to each modern external network and initiate the export from within that network.
  • You can’t export data from a modern external network while signed into a different or home network.

[What you can do to prepare:]

• Review any scheduled or documented export procedures that reference:
  • “Include attachments”
  • “Include external networks”
• For attachments, ensure that teams responsible for eDiscovery, compliance, or export workflows understand that:
  • Exports contain SharePoint links for files.
  • Files must be retrieved directly from SharePoint using those links.
• For external networks, ensure admins understand they must:
  • Sign in to each modern external network individually.
  • Trigger exports separately for each network.

Learn more:

• Set up modern external Viva Engage networks | Microsoft Learn
• Network Data Export API | Microsoft Learn

[Compliance considerations:]

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

[Introduction]

We are retiring Context IQ in the new Outlook and Outlook on the web. This feature currently allows users to insert suggested files and other content by typing the “/” character while composing an email. We are retiring this capability to streamline the compose experience and reduce duplication with other supported attachment and editor workflows.

[When this will happen]

We will retire Context IQ from the new Outlook and Outlook on the web starting March 16, 2026.

[How this affects your organization]

Who is affected

• Users who compose email in the new Outlook for Windows and Outlook on the web and currently use Context IQ’s “/” suggestions.

What will happen

• Context IQ suggestions invoked with “/” during email composition will be removed.
• Users will continue to add files and content using existing methods:
  • Paste a file or URL directly into the message body.
  • Drag and drop files into the compose window.
  • Use Insert > Attach file to see suggested files, browse, and attach content.
• The Editor feature remains available via the button in the lower-right of the compose area and in the ribbon.
• There is no change to attachment storage, file handling, or Editor capabilities.

[What you can do to prepare]

No admin action is required.

To prepare for this change, we recommend the following:

• Inform your users about the retirement of Context IQ.
• Update internal training or documentation that references Context IQ or “/” suggestions.
• Share guidance on how to attach files using supported methods:
  • Paste
  • Drag and drop
  • Insert > Attach file
• Direct users to these Microsoft Support resources:
• Add pictures or attach files to email in Outlook | Microsoft Support
• Check spelling before sending a message | Microsoft Support

If you track feature usage and want to identify which users interact with compose‑related features, you can use usage reporting available in the Microsoft 365 admin center (for example, Outlook usage reports). Dedicated Context IQ usage reporting is not available.

[Compliance considerations]

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

[Introduction]

Starting in mid‑February 2026, the Microsoft 365 apps for Mac suite installer will include a shim for the Microsoft 365 Copilot app. This change helps organizations more easily deploy the Microsoft 365 Copilot Mac app by enabling users to download the full application directly from the shim.

The Microsoft 365 Copilot Mac app brings AI assistance to macOS, helping users search, analyze, and create from a single, secure desktop experience.

[When this will happen]

• General Availability (Worldwide): Rollout will begin in mid‑February 2026 and is expected to complete by mid‑March 2026.

[How this affects your organization]

Who is affected: Organizations that deploy Microsoft 365 apps for Mac using the suite installation package.

What will happen:

• The Microsoft 365 apps for Mac suite installer will include the Microsoft 365 Copilot shim app.
• Users will be able to download and install the full Microsoft 365 Copilot app by opening the shim app from the Applications folder.
• Existing installations of Microsoft 365 apps on macOS are not affected.
• Organizations that want to deploy Microsoft 365 Copilot to devices already running Microsoft 365 apps should deploy the shim app separately.

[What you can do to prepare]

If your organization deploys Microsoft 365 apps for Mac using the suite installer package:

• Ensure the Microsoft 365 Copilot shim app is not excluded during deployment.
• Confirm that Microsoft AutoUpdate (MAU) is enabled on macOS devices.
• Confirm that devices meet the minimum requirement of macOS 14.0 (Sonoma) or later.
• Ensure network connectivity is available so the shim app can download the full app.
• This guidance is applicable for all users, not specifically those who want to deploy the shim app separately.
• Review: Deployment guide for Office for Mac | Microsoft 365 | Microsoft Learn.

[Compliance considerations]

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

[Introduction]

Voice tethering builds on the recent introduction of Sign Language Mode in Microsoft Teams. When a sign language interpreter voices on behalf of a Deaf or hard‑of‑hearing (D/HH) participant, Teams will now attribute captions, transcripts, and meeting intelligence—such as Copilot notes, summaries, action items, and insights—to the D/HH participant rather than the interpreter. This update ensures accurate representation in meetings, clarifies who is contributing to the conversation, and improves downstream meeting accuracy and accountability.

This message is associated with Microsoft 365 Roadmap ID 553223.

[When this will happen]

• Targeted Release (Worldwide): We will begin rolling out in mid-March 2026 and expect to complete by late March 2026.
• General Availability (Worldwide, GCC): We will begin rolling out in early April 2026 and expect to complete by mid-April 2026.

[How this affects your organization]

Who is affected

• Organizations with meeting participants who are Deaf or hard‑of‑hearing and use sign language interpreters in Teams meetings.
• Any users who participate in meetings with Sign Language Mode enabled.

What will happen

• Voice contributions made by interpreters will be attributed to the D/HH participant across:
  
  • Live captions
  • Meeting transcripts
  • Copilot notes, summaries, action items, and insights
  • Other Teams meeting intelligence
• Meeting data becomes more accurate by ensuring the correct participant is represented.
• Interpreter identity is no longer conflated with the signer they support.
• Sign Language Mode is already available to all users; voice tethering enhances it automatically.
• The feature is on by default when sign language mode and interpreter assignment are used.
• No admin controls are required to enable or manage the feature.

[What you can do to prepare]

No action is required.

Optional preparation steps:

• Inform D/HH users and interpreters that speech attribution in meetings will change.
• Update internal training or accessibility resources if you document interpreter workflows.
• Notify helpdesk or support teams that captioning and transcript attribution will appear differently for interpreted meetings.

[Compliance considerations]

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

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

• Current Channel
• Monthly Enterprise Channel
• Semi-Annual Enterprise Channel

[When this will happen:]

We'll be gradually rolling out these updates of Microsoft 365 Apps to users on those update channels starting February 10th, 2026 (PST).

[How this will affect your organization:]

If your Microsoft 365 Apps clients are configured to automatically update from the Office Content Delivery Network (CDN), then no action is required.

If you manage updates directly you can now download these latest updates and begin deployment.

[What you need to do to prepare:]

To get more details about these updates view the following release notes:

• Current Channel
• Monthly Enterprise Channel
• Monthly Enterprise Channel
• Semi-Annual Enterprise Channel

• For Dynamics 365 customers: Glossary and synonym configuration should now be done in Copilot Studio under Agents > Copilot in D365 > Glossary/Synonyms section.
  
  Please note that any glossary entries previously configured in Power Apps will continue to work, but admins will need to update the skill name in each entry from Saleschatdvqna to Salesspecificqna to ensure functionality after this update.
  
  
• For Salesforce customers:
  Glossary/synonyms configuration is not supported yet for Salesforce environments in this release.