Copilot in Microsoft Edge

What it does

Copilot in Microsoft Edge is the browser assistant, historically a sidebar and now also the fuller Copilot Mode, that can read the page or PDF you're on, summarise it, answer questions, and take actions across tabs. Its data terms and admin controls depend on whether you're signed in with a personal or an Entra work account.

Key facts

Copilot in Edge can use the content of the current page or PDF as context, so it can summarise or answer against what you're reading.
Copilot Mode (launched 2025) is a broader AI-browser experience: a chat-first new tab, multi-tab context, voice, Journeys that organise history by topic, and Copilot Actions for agentic tasks.
Page context and browsing-history use are permission-based; history is opt-in via Page Context in settings and can be turned off.
With an Entra work profile, the sidebar gets enterprise/commercial data protection, shown by a shield, isolating prompts from model training and applying your DLP and access policies.
Admins control page-context access with policies such as EdgeEntraCopilotPageContext and the CDP page-context policy, which apply to Entra ID profiles.
Edge for Business enforces org DLP: if a site or document is protected, Copilot will say it can't access the page.
IT can set allow/block lists governing which sites Copilot in Edge may access.
Copilot Mode is available in Copilot markets on Edge for Windows and Mac, with mobile coming; consumer and work experiences differ in governance.

When to use / skip

Good for quick page summaries, comparing across tabs, and research clean-up where the content is non-sensitive or you're on a governed work profile. On an Entra work account with data protection, it's reasonable for day-to-day browsing help. Be cautious feeding sensitive pages to it on a personal account, where none of the commercial protections or DLP apply. Copilot Mode's agentic Actions are worth a careful look before you let them loose on real accounts and forms.

Configuration decisions

Decide whether Copilot in Edge / Copilot Mode is enabled at all on managed devices, and for which account types.
Set the page-context policy: allow or block Copilot reading webpage and PDF content for Entra profiles.
Configure site allow/block lists so Copilot only touches sanctioned domains.
Choose whether browsing-history use and Journeys are permitted, given they read history with consent.
Confirm DLP labelling is in place so protected content is actually blocked from Copilot rather than assumed to be.

Gotchas

Data protection follows the signed-in Entra work profile; a personal account in Edge means consumer terms and no DLP, even on a corporate device.
Page-context and history policies apply to Entra ID profiles, so personal-account browsing sits outside those admin controls.
Copilot Mode changes the browsing experience noticeably (chat-first new tab, Actions); roll it out with some user comms or expect confusion.
Copilot Actions can act on your behalf, filling forms, unsubscribing, booking; scope and test before trusting it on live sessions.
The shield indicator is the quick check for whether protection is active; teach users to look for it.

Consultant notes

Same rule as the rest of the family: commercial data protection tracks the Entra account, not the browser or the machine, so profile hygiene is the control that matters.
For regulated clients, the allow/block lists and page-context policies are the real governance surface; walk through them rather than just toggling Copilot on.
Treat Copilot Mode and Copilot Actions as newer and more agentic; pilot them before a broad rollout, especially where Actions touch accounts.
If a client uses Edge for Business, tie Copilot's behaviour into their existing DLP and sensitivity labels rather than treating it as a separate thing.

Verify the current Edge policy names and whether Copilot Mode is default-on for the client's channel before you write the config guide.