When you click to open a link in Copilot, the content now appears in a sidepane next to your conversation instead of a separate browser window, so you don't lose context. It sounds straightforward enough. A productivity tweak. A quality-of-life improvement for people who use Copilot for research, drafting, and multi-tab work.
But Microsoft's latest Copilot update for Windows Insiders has triggered something far more fraught than a routine interface refinement. What appears to be a simple UX decision sits at the intersection of product design, market competition, privacy risk, and regulatory scrutiny. The feature reveals the genuine tension between user convenience and the preservation of open digital markets.
The underlying mechanism is neither secret nor particularly novel. With your permission, Copilot will have access to the context of tabs you open in that conversation, and only in that conversation, so you can ask clarifying questions, summarize information across tabs, or ask Copilot's help in drafting exactly the right words needed for the task. Additionally, if you choose to enable it, you can sync passwords and form data so it's easier to work within Copilot.
For Copilot users specifically, the appeal is real. Research workflows do fragment across browser tabs and chat windows. The friction of switching contexts has a genuine cognitive cost. Keeping a conversation and web content visible simultaneously, with the ability to ask an AI to synthesise across multiple open pages, reflects how people actually work today.
What has provoked concern is the mechanism underneath the convenience. The Copilot update embeds web browsing directly into the assistant, opening links in a side panel rather than launching your default browser. This is not a trivial distinction. For a quarter-century, users have expected that clicking a link opens their chosen browser with their preferred security settings, stored passwords, and chosen extensions. Bruce Lawson of Vivaldi noted that people have become accustomed to clicking links to open their default browser with their preferred settings, stored passwords, preferred font size, and preferred security settings. "Pulling that rug from under users' feet is impertinent and discourteous. Whether it circumvents DMA or other competition regulations is for lawyers and regulators to decide, but the eternal arrogance of gatekeepers is self-evident."
The regulatory question is not trivial. Microsoft was identified as a gatekeeper under the EU's Digital Markets Act, and some consultants have suggested the only DMA obligation affecting Microsoft was to enable end-users to delete any software applications pre-installed. The European Commission closed its investigation into Microsoft's Edge browser, finding that Edge does not qualify as a gatekeeper core platform service. Yet the question of whether embedding Edge's rendering technology into Copilot circumvents the spirit of browser choice remedies remains genuinely unresolved. It is precisely the sort of technical end-run that regulatory frameworks struggle to address.
From a centre-right perspective, the core tension deserves honest acknowledgement. Microsoft has built Copilot into Windows with considerable market leverage. Embedding Edge into the assistant is not predatory in its implementation; password sync is optional, tab access requires permission, and Microsoft is iterating in preview rather than forcing the feature on all users immediately. These are reasonable guardrails.
Yet the underlying pattern is clear. Finding a corner of Microsoft's software that Copilot hasn't reached is increasingly difficult, and disabling it across the company's productivity suite has become a game of Whac-A-Mole for enterprise administrators, particularly given that Copilot surfacing suggestions based on email content could run afoul of data security policies.
Microsoft's market position is legitimate. The company earns its dominance through product quality and integration depth that users often prefer. But dominance also carries responsibility. When a single company controls the operating system, the default email client, the dominant office suite, and now increasingly the AI assistant embedded in all of them, the company faces a genuine accountability burden that goes beyond what smaller competitors face.
This update works as intended for willing users. The productivity gains are real. But a reasonable policy framework should ensure that opting into Copilot does not become a soft requirement to cede browser choice, credential control, and tab context access to a single vendor. Transparency about where data is processed, strong administrative controls for enterprises, and genuine optionality rather than friction-based defaults would represent pragmatic middle ground.
The update is currently a preview and therefore subject to change. That window provides an opportunity for Microsoft to address legitimate regulatory and competitive concerns before the feature reaches all Windows users. It would be fiscally prudent and strategically wise to do so.