A laptop displays Copilot summarizing generative AI trends beside a source webpage and an organization-managed IT policy setting.
Starting in January 2027, links in the Microsoft Copilot desktop app will open inside the app for work users too, unless their IT department turns that off. Neowin called it a "major change." In practice it's a new default: for businesses, links clicked in Copilot will open next to the chat instead of in the separate browser users have set as their default. Admins have about six weeks before Microsoft flips the setting for everyone who hasn't configured it.

A laptop displays Copilot summarizing generative AI trends beside a source webpage and an organization-managed IT policy setting. What Microsoft announced​

The change appears in Microsoft 365 Message Center post MC1560922. The Message Center archive lists it as "Microsoft Copilot: In-app browsing will be enabled by default in the desktop app," filed under Microsoft Copilot (Microsoft 365) on Nov 20, 2026. A copy of the notice published by Modern Workspace Pro says Microsoft is enabling in-app browsing by default in the Microsoft Copilot desktop app for Windows and Mac.

Once the change arrives, websites shared in Copilot chat will open directly within the desktop app by default, side by side with the Copilot conversation. The notice says no action is required to enable in-app browsing, and if no changes are made, in-app browsing will remain enabled by default.

The schedule:

ItemDetail
Message Center IDMC1560922 (follows MC1474455)
PlatformsMicrosoft Copilot desktop app, Windows and Mac
Rollout startEarly January 2027 (worldwide general availability)
Expected completionEnd of January 2027
Admin action needed to enableNone
How to opt outSet the BrowsingEnabled policy to Off

These dates are Microsoft's plan. They don't confirm that the rollout has started, and Message Center dates often slip.

In short: this isn't a new feature. An existing opt-in feature becomes opt-out for organizations, and if you do nothing, it turns on.

How we got here: the September opt-in phase​

The in-app browser first came to work users in MC1474455, published in September 2026. At that point Microsoft said the feature was available now but not available by default; administrators can opt-in selected Windows and Mac devices to test this. The early-access period was meant to let organizations test in-app browsing at your organization before the broader rollout and validate deployed and in-app browsing behavior in your organization's managed environment.

Topedia's blog said much the same during that phase: the feature was in early access as an opt-in experience for admins and is turned off by default. This is expected to change in a later phase. That later phase is January.

Home users have had this for longer. WinBuzzer reported in March 2026 that a Copilot update on Windows had started opening web links in an in-app side pane, bypassing users' default browser settings without offering an opt-out. Neowin describes the situation the same way: the feature was available as the default for regular consumers, but as an optional, opt-in experience for enterprise customers. This will change in January 2027, as Microsoft is making this the default behavior for enterprise customers too.

What users will actually see​

Microsoft's September notice explains how it works. When a user clicks a link within the Copilot desktop app, the website opens in a side pane to the right of the Copilot chat. Users can:

  • Open several links, each as its own tab in the side pane, and switch between them
  • Adjust the in-app browser side pane to be smaller or larger
  • Switch to full-screen view from the side pane header
  • Close the pane when they're finished

You can still get out of the pane. The September notice lists three ways to send a page to an external browser: choose "External browser" from the three-dot menu on the link in Copilot Chat, choose "Copy the URL" and paste it into another browser, or right-click a tab in the side pane and choose "External browser." The menu wording may differ in current builds. In an Eleven Forum tutorial, the options are labeled "Open in browser" and "Open in default browser," with one route described as right clicking a tab in the browsing side pane within the Copilot app and selecting "Open in default browser". Help desks should check the labels in their own deployed version before they write user instructions.

Microsoft also says the feature isn't a new AI capability. Per the September notice, it does not add any new way to create or steer generative AI, it only lets you view websites, whether those are website on the internet or html files created generatively with copilot via other features.

The data question admins should ask​

The feature stores browsing data on the device. Eleven Forum, quoting Microsoft's notice, says browsing history, cookies, autofill information for web browsing in the Copilot app are stored on the local device in the user Data profile directory at %localappdata%\Microsoft\Copilot\User Data. Microsoft's September notice says this uses the same storage approach Edge uses.

That means a second browser-style profile on every managed endpoint, with its own cookies and autofill data. If your security baseline, DLP rules or profile-cleanup scripts only look at Edge and Chrome profile folders, add this path to your review. The new default doesn't create new legal obligations. It does put a new store of session data on your machines.

How to disable or manage it​

Microsoft's guidance in MC1560922 says to set the BrowsingEnabled policy to Off through your device management system to disable in-app browsing.

Microsoft Learn's "Configure Microsoft Copilot policies" page has the details:

  • Policy name: BrowsingEnabled (caption: "Enable browsing capabilities")
  • Supported versions: Copilot app on Windows and macOS, version 152 or later
  • Behavior: If the policy is enabled or left unconfigured, users can browse the web inside Copilot. If it's disabled, they can't.
  • Group Policy path: Administrative Templates / Microsoft Copilot / Browsing
  • ADMX file: CopilotApp.admx
  • Registry: SOFTWARE\Policies\Microsoft\Copilot, value BrowsingEnabled, type REG_DWORD
  • macOS: preference key BrowsingEnabled
  • Dynamic policy refresh: Yes

Because of how the policy works, "not configured" counts as "on." Once the default changes, devices with no setting will get the in-app browser.

Turning it off with Intune​

Topedia's walkthrough covers turning the feature on during early access, and turning it off works the same way in reverse:

  1. Import the Copilot administrative template (CopilotApp.admx) into Intune, if you haven't already.
  2. Open or create a configuration profile. The setting "Enable browsing capabilities" is now available in your configuration profile (if you used Imported Administrative Templates). Topedia added the setting to the same profile it used to deploy the Copilot app.
  3. Set "Enable browsing capabilities" to Disabled. This matches Microsoft's "Off" instruction.
  4. Assign the profile to the right users or devices, and check that it reports success before January.
  5. Restart the app if needed. Learn says the policy refreshes dynamically, but Topedia found it had to restart the Copilot desktop app to make the web browsing preferences available. Topedia also warns that if you close the Copilot desktop app window, the app keeps running in the background by default. If the policy doesn't seem to apply, quit the app fully from the system tray before you start troubleshooting.

How to tell it worked: According to Eleven Forum, with browsing disabled, clicking on links in a Copilot chat will open in the default web browser instead of in Copilot. Topedia also notes that the Web browsing page in Copilot's settings shows when the organization controls the setting.

Common problems:

  • Old app version: the policy is supported from version 152 on, so earlier builds may ignore it.
  • Policy not appearing: make sure CopilotApp.admx was imported. For GPO, also check that the template is in your central store.
  • App still running in the background: close it fully and relaunch.

More detailed controls​

MC1560922 says admins can configure the new in-app browsing policies as needed to manage security, privacy, access, authentication and network behavior, downloads, and permissions. Microsoft hasn't yet published a complete list of those settings for this notice. It says it will update the message with documentation. The September notice pointed admins to the Microsoft Edge policy documentation along with the Copilot policies page. Until Microsoft publishes the details, don't assume a particular setting exists.

The Edge question​

Neowin raises a competition concern: some will be displeased that the only embedded browser allowed inside the Copilot app is Microsoft Edge. Microsoft's notices don't say which engine the pane uses, and neither does the policy documentation. WinBuzzer's March report on the consumer version described an embedded side pane built on Edge's rendering engine, regardless of whichever browser a user has set as their system default.

For a company that has standardized on Chrome or Firefox, the bigger issue is everything the pane doesn't share. WinBuzzer noted that the pane does not inherit their browsing environment – not their stored passwords, not their extensions, not their preferred security configurations. Users would be clicking links in a separate browser profile with no password manager, no security extensions and none of the settings their main browser has.

There's a reasonable argument for Microsoft's approach. Keeping a source open next to the AI answer that cited it is useful, and Neowin points out that Teams and Outlook already open links in a similar way. Organizations also get a supported off switch before the change lands. The concern is the default: features that are on unless someone turns them off tend to stay on. Microsoft's statement that the change has no compliance considerations doesn't remove the need to check data storage and browser policy yourself.

Bottom line​

For Windows and Mac shops running the Copilot desktop app, here's what to do before the January rollout:

  • Decide whether you want in-app browsing.
  • If you don't, deploy BrowsingEnabled = Disabled, confirm devices are on app version 152 or later, and check that links open in the default browser.
  • If you do, add %localappdata%\Microsoft\Copilot\User Data to your data-handling review, update help desk instructions, and watch MC1560922 for the promised policy documentation.

Doing nothing also counts as a decision, since unconfigured devices will get the in-app browser.

 

References

  1. Microsoft Copilot app is getting a "major change" Neowin 2026-11-20T08:24:02+00:00
  2. Windows 11: Microsoft Copilot Will Bypass Your Default Browser winbuzzer.com
  3. MC1560922: Microsoft Copilot In-App Browsing mwpro.co.uk