Microsoft Copilot Is Getting In-App Web Browsing on Windows and Mac

Microsoft is expanding the capabilities of its Copilot desktop app with in-app web browsing, allowing users to open websites directly alongside their Copilot conversations instead of switching to a separate browser window.

The feature is available now for organizations that choose to enable it on selected Windows and Mac devices, according to Microsoft’s September 2026 announcement. A broader rollout is scheduled to begin in late November 2026.

The change gives Copilot a more browser-like role inside its desktop application. When users click a website link shared in a Copilot conversation, the page can open in a side pane next to the chat, keeping the conversation and web content in the same workspace.

Microsoft’s current documentation also confirms that the Copilot app supports web browsing within the application and that administrators can control the capability through the BrowsingEnabled policy.

How Copilot’s In-App Browser Works

The basic experience is straightforward.

When a user clicks a link in Copilot, the website opens in a panel on the right side of the conversation. The Copilot chat remains visible, so users can move between the AI conversation and the website without opening another application or browser window.

Users can also open multiple websites as separate tabs within the side pane. That makes the feature particularly relevant for research-heavy tasks where several sources need to be reviewed at once.

The browsing panel can be resized, allowing users to give more screen space to the website or return more room to the Copilot conversation.

There is also a full-screen option for users who want to temporarily focus on the webpage itself.

Microsoft’s support documentation describes a similar workflow in which web content opens beside the Copilot conversation, with tabs saved alongside the conversation so users can return to them later.

What users can do

The updated experience allows users to:

Open links from Copilot directly inside the app
Keep multiple websites open as tabs
Resize the browsing pane
Switch the webpage to full-screen mode
Close the browsing pane when finished
Continue using the Copilot conversation alongside the web content
Open a website in an external browser when preferred

That last point is important. Microsoft is not forcing users to abandon their existing browser workflow.

Users can select the External browser option from the three-dot menu associated with a Copilot link. They can also copy the URL and paste it into another browser.

Microsoft’s supplied announcement also says that right-clicking a tab and selecting External browser is being added as another way to move content outside Copilot.

Why Microsoft Is Adding Browsing to the Copilot App

The change reflects a broader shift in how Microsoft is positioning Copilot: less as a standalone chat window and more as a workspace where AI assistance, information retrieval and web content can coexist.

Until now, a typical Copilot workflow could involve asking a question, receiving a link and then leaving the Copilot interface to inspect the linked page.

In-app browsing removes one of those boundaries.

A user researching a topic, for example, can ask Copilot for information, open a source in the side pane and continue asking questions while keeping the source visible.

Microsoft’s support documentation specifically points to use cases such as viewing web content without leaving the conversation and working across multiple opened tabs.

The distinction matters because web search and web browsing are not exactly the same thing.

Copilot can use web content to ground responses, but an embedded browser gives users a direct way to inspect the underlying webpages themselves. Microsoft’s documentation separately describes controls for web search, which allow organizations to determine whether Copilot can incorporate real-time web content into responses.

Administrators Get Control Over the Feature

For IT departments, the most important part of the update may be the policy controls rather than the interface itself.

Microsoft’s current Copilot policy documentation lists a dedicated BrowsingEnabled policy for controlling browsing capabilities.

The policy is supported on Windows and macOS starting with Copilot version 152 or later. Administrators can enable or disable the capability, and Microsoft identifies it as a mandatory policy that can be refreshed dynamically.

On Windows, Microsoft documents the policy under:

Administrative Templates/Microsoft Copilot/Browsing

The corresponding registry configuration uses:

SOFTWARE\Policies\Microsoft\Copilot

On Mac, Microsoft documents BrowsingEnabled as a preference key.

This gives organizations a way to introduce the feature selectively rather than treating the broader rollout as an all-or-nothing change.

Why the opt-in phase matters

Microsoft’s early-access approach gives organizations time to:

Test browsing on managed devices
Review how websites behave inside the Copilot environment
Evaluate compatibility with internal policies
Prepare help-desk and support teams
Communicate the change to employees
Review privacy and data-storage implications

That testing period could be particularly relevant for companies with strict browser controls, security requirements or regulated workflows.

The Privacy Question: Browsing Data Is Stored Locally

The addition of a browser inside Copilot also introduces an important data-storage consideration.

According to the supplied Microsoft announcement, browsing history, cookies and autofill information are stored locally on the device, using storage mechanisms similar to Microsoft Edge.

The specified Copilot data profile directory is:

%localappdata%\Microsoft\Copilot\User Data

That does not mean the feature should simply be treated as identical to an ordinary browser installation. Organizations will still need to examine their own endpoint-management, browser and data-retention policies before enabling the capability broadly.

Microsoft’s current Windows support documentation also says users can open web content directly inside Copilot and, where enabled, sync passwords and form data.

For businesses, that makes policy review an important part of deployment rather than an afterthought.

Copilot Is Becoming More Like a Workspace

The significance of the update goes beyond the ability to open a webpage.

Microsoft’s current Copilot app documentation describes the application as a desktop experience available on both Windows and macOS, alongside web and mobile versions. The app can contain several Copilot experiences depending on the account and licensing environment.

In that context, embedded browsing fits naturally into Microsoft’s larger effort to keep users inside the Copilot environment while they research, read and work.

It also creates an interesting overlap with Microsoft’s existing browser-based AI experiences.

For example, Microsoft Edge has its own Copilot browsing capabilities, including policies that control how Copilot interacts with web content. Those Edge controls are separate from the BrowsingEnabled policy documented for the Copilot application.

That distinction will matter to IT administrators managing both products.

What This Means for Windows and Mac Users

For everyday users, the practical change is relatively simple: clicking a link from Copilot no longer has to mean leaving the Copilot workspace.

A researcher could keep source material open beside the conversation. A professional could compare several webpages while asking Copilot questions about them. Someone working through a long online document could keep the AI conversation visible instead of repeatedly switching between windows.

The feature also preserves an important escape hatch: users can still send webpages to their normal external browser.

That means Microsoft’s approach is less about replacing the browser outright and more about making browsing part of the Copilot workflow.

What Organizations Should Do Before the Broader Rollout

Organizations preparing for the wider rollout can use the current opt-in period to establish their own policies.

A sensible checklist includes:

Confirm the Copilot version deployed across managed Windows and Mac devices.
Review the BrowsingEnabled policy and determine whether browsing should be available, restricted or disabled.
Test websites used in normal business workflows.
Review local browser-data storage requirements, particularly for cookies, history and autofill.
Check existing endpoint and browser policies for possible conflicts.
Prepare users for the new interface so support teams are not dealing with unexpected workflow changes after rollout.
Review privacy requirements before enabling the feature across a larger device population.

Microsoft’s documentation provides the policy framework administrators need to control browsing within the Copilot application.

What Comes Next

The immediate story is the controlled rollout. Organizations can test the feature now, while Microsoft plans to begin the broader rollout in late November 2026, according to the supplied announcement.

The more consequential question is how far Microsoft takes the concept.

Once an AI assistant can keep a conversation, web pages and multiple sources in one desktop workspace, the boundary between chatbot and browser becomes less important to the user.

For Microsoft, that could make the Copilot desktop app a more central destination for research and everyday computer work.

For IT departments, however, the next phase will be about governance as much as convenience. The combination of embedded web access, locally stored browsing data and increasingly capable AI features means organizations will need to decide not only whether users can browse inside Copilot, but also which policies should govern that browsing experience.

The late-November rollout will therefore be worth watching not simply as another Copilot interface update, but as a further step in Microsoft’s effort to make Copilot a persistent working environment on Windows and Mac.