In July 2026, Microsoft began rolling out an update to the Teams desktop app that lets users open links inside chat and channel messages in a separate window—instead of navigating away from the active conversation. Available on Windows and Mac, the feature arrives through a simple Ctrl+click (or Cmd+click on macOS) shortcut, plus a new option in the “More actions” menu. For a collaboration tool used by hundreds of millions, this tiny interface change targets one of the most persistent and expensive forms of digital friction: losing the thread of a discussion just to inspect a linked file, task, or webpage.

What Changed: A Simple Shortcut and a Long-Awaited Menu Option

Microsoft didn’t redesign Teams to achieve this. The core change is behavioral: when a user hovers over a link in a Teams message—whether in a one-on-one chat, group chat, or channel post—they’ll now have two ways to open it without leaving the current view.

On Windows, holding the Ctrl key and clicking the link opens the destination in a new Teams window. On Mac, it’s the Cmd key. If keyboard shortcuts aren’t your thing, clicking the “More options” (…) menu on the message and selecting “Open link in new window” does the same job.

The update is part of Microsoft 365 Roadmap item ID 565220, which first appeared on June 10, 2026, and was last updated on July 6, 2026. According to the roadmap, the rollout covers the Teams desktop client on both Windows and macOS. It’s shipping to all commercial tenants (worldwide standard multi-tenant) as well as government clouds: GCC, GCC High, and DoD. Both General Availability and Targeted Release rings are included, meaning organizations set to receive early updates may see it slightly before the broader July 2026 GA window.

What It Means for You: Preserving Context Across Every Click

For everyday Teams users, the immediate benefit is practical: no more mentally reconstructing a conversation after clicking away. Imagine a colleague shares a SharePoint link and says, “Review the Q3 budget figures I just updated—we need to cut 5%.” In the old model, clicking that link replaces the chat with the document, burying the instruction. The new model keeps both visible: the chat on one side, the budget spreadsheet on the other.

For power users and multi-monitor warriors, the shortcut muscle memory from browsers finally translates into Teams. Ctrl+click already means “open in new tab” in Edge, Chrome, and Firefox. Now Teams honors that same action, reducing the learning curve for those who live in front of multiple screens. An ultrawide monitor user can park a channel discussion on the left and a linked Planner task on the right without minimizing, resizing, or digging through the backstack.

IT professionals and administrators gain a small but meaningful win: a feature that reduces help-desk noise. Users regularly complain about “lost” windows or confusing navigation; a predictable, window-based link behavior can preempt those tickets. Because the feature is client-side and doesn’t introduce new permissions or data access patterns, it’s unlikely to trigger compliance alarms. Still, admins should verify that screen-sharing sessions don’t accidentally expose private chats when a new window pops up—a prudent check for any window-management change.

A particular highlight for cross-platform organizations: macOS support is arriving simultaneously. Mac users are often wary of UI inconsistencies, and the explicit mention of Cmd+click in Microsoft’s roadmap reassures that Teams on Mac is getting the same first-class treatment. Those using Spaces, Stage Manager, or multiple desktops will benefit just as much as their Windows counterparts.

How We Got Here: Teams’ Slow March Toward Desktop Norms

Teams hasn’t always been a poster child for multitasking. For years, the product tried to contain everything inside one shell: chats, channels, meetings, files, apps, and later, Loop components and Copilot. The “single pane of glass” philosophy sounded elegant, but in practice, it forced constant context-switching.

Microsoft started chipping away at that constraint back in 2021, when it added the ability to pop out individual chats into separate windows. That was a revelation for users managing multiple conversations concurrently. In 2023, the company extended window support to channels, allowing a dedicated channel view to float independently. TechRadar and other outlets noted at the time that these moves signaled a recognition that teams workflow was inherently multi-window.

The message-link addition is the latest and most granular step. It acknowledges that not every piece of information needs to be swallowed into Teams’ main frame. Sometimes, the best collaboration interface is two windows side by side: the discussion and the artifact under discussion. This aligns with how knowledge workers actually operate—comparing, cross-referencing, and verifying across sources.

The change also reflects the maturity of the “new Teams” client architecture. After Microsoft rebuilt Teams from the ground up in late 2023 to be faster and more resource-efficient, the client could finally support multiple windows without the performance penalty that plagued the old version. That foundation made separate-window experiences viable at scale.

The rollout doesn’t demand a policy overhaul, but a few proactive steps will keep your organization ahead of the curve.

  • Test link types thoroughly. On a test machine (or a Targeted Release device), try Ctrl+click (or Cmd+click) on common link types: a SharePoint file, a OneDrive document, a channel post link, a Planner task, a Loop component link, and a plain external URL. Document which destinations open inside a new Teams window and which might still trigger a browser or native app. Inconsistent behavior could confuse users if some links open in Teams while others launch Edge or Chrome.
  • Brief your support staff. Even a one-line internal announcement (“Teams now lets you right-click or Ctrl+click message links to open in a new window”) can deflect dozens of “why did my Teams layout change?” tickets. Include the tip in any updated user guides or Teams tips channels.
  • Watch out for browser defaults. Microsoft has a history of steering Teams and Outlook links toward Edge, triggering complaints when users expect their system default browser. While this feature doesn’t directly involve browser choice, it adds another layer to the link-handling puzzle. If your organization has configured policies about which browser handles M365 links, test that those policies don’t interfere with the new in-Teams window behavior.
  • Check accessibility. Confirm that the More options menu works cleanly with keyboard navigation and screen readers. The Ctrl+click shortcut is a mouse-driven action; the menu is the fallback for assistive tech users, and it must be discoverable.

Outlook: Windows Everywhere—but Will Context Stick?

This feature won’t be the last of its kind. Microsoft is increasingly treating Teams as a workspace operating layer, not a bounded app. We’re likely to see more window-aware behaviors—like opening a meeting chat alongside the meeting window, or launching a Copilot pane detached from the main thread.

The challenge ahead is window sprawl. Users can already pop out chats, channels, meetings, and now linked content. Without sensible defaults—such as automatic window grouping in the taskbar, clear titles that echo the source conversation, and predictable focus switching—the productivity gains could be offset by clutter.

Another open question is how this interacts with Teams’ new link-unfurling capabilities. When a link expands into a rich preview card inside a message, does Ctrl+click still open the full linked destination in a new window, or does it expand in place? Early testing will reveal the nuances.

But for now, the July 2026 update is a straightforward win. It doesn’t require a policy change, a license upgrade, or a training module. It simply gives users a way to keep their conversation in view while they inspect the thing the conversation is about. In the real world of enterprise work, that small victory is often the difference between a productive session and a frustrating detour.