What is happening is the difference between a normal Copilot query and a query that uses browsing context inside Microsoft Edge.
In Edge, Microsoft states that it decides what data to send to Copilot based on the query and consent settings.
- For prompts that do not need browsing context, Edge sends only:
- the query
- the URL
- the page title
- previous conversation history
- For prompts that do need browsing context—such as summarizing a page or answering about what is open in the browser—Edge asks for permission to access page information.
Microsoft defines browsing context as the URL and page content open in the active tab. It also defines page information as the content of the webpage or document open in the active tab.
That means the Edge-integrated experience is designed around the current active tab, not an arbitrary URL pasted into the prompt. If the request is treated as needing browsing context, Edge asks for permission to use the active tab’s page information. That is why the permission prompt can appear unrelated to the URL mentioned in the request.
Microsoft also states that for questions needing browsing context, Edge sends the full browsing context only for public pages that are on the Bing index. For page context-based conversations, Edge and Copilot do not store or train on the context used for grounding. Conversation history, however, stores Copilot queries and responses until deleted.
If the goal is to prevent Copilot in Edge from reading the current page, the documented control is:
- Settings > Copilot and sidebar > Copilot
- turn off Allow Copilot to read context clues on the web
For Actions in Edge, there is a separate permissions model under:
- Settings > AI innovations
That area controls whether Copilot can act on sites with Light, Balanced, or Strict permissions, and whether sites are allowed or blocked.
So the behavior is not that Copilot needs unrelated bank or medical content to answer every URL question. The documented behavior is that the Edge integration uses the active tab as its context source when a request is classified as needing browsing context, and permission is required for that. The standalone Copilot experience differs because it is not tied to the active Edge tab in the same way.
References: