Why Edge Copilot Refuses to Summarize Pages Behind Logged-in Areas

Quick fix: Edge Copilot can’t summarize pages it can’t access publicly — behind-login content (private Notion docs, paywalled articles, internal SharePoint) isn’t passed to the cloud Copilot. Use Copilot with the page DOM context option (the small button in the Copilot pane) or paste the page text directly into Copilot.

You’re reading a logged-in page — an internal documentation site, a paywalled article, your private notes — and you click Copilot to summarize. Copilot returns “I can’t access this page” or summarizes only what’s visible publicly (the title, marketing copy). It can’t see what’s behind your login.

How Copilot accesses page content

Copilot has two modes for page content: Server-side fetch (it loads the URL itself from Microsoft’s servers, without your cookies) and Client-side DOM (it reads the rendered page from your browser, with your login state). The default is server-side fetch, which fails for logged-in content. Switching to client-side DOM lets Copilot see what your browser sees.

Method 1: Use Copilot’s page-context toggle

1. Open the logged-in page in Edge.
2. Click the Copilot icon (top-right of Edge).
3. In the Copilot pane, look for a small icon or toggle near the input box labeled Use page context or showing the current page’s URL.
4. Toggle it on. Copilot now reads the rendered DOM.
5. Ask “Summarize this page”.

Method 2: Paste the text directly

1. Select the page content you want summarized.
2. Copy (Ctrl+C).
3. Open Copilot. Paste the text and ask for a summary.
4. Copilot summarizes the pasted text without needing access to the page.

Method 3: Use Copilot in Microsoft 365 for documents

1. For SharePoint or OneDrive documents, open them in the matching M365 app (Word, OneNote).
2. Copilot inside the app has access to the document content.
3. Ask for a summary; it works because the access is M365-authenticated.

How to verify the fix worked

• Copilot returns a summary referencing actual content from the logged-in page.
• The summary mentions specific details that are only visible when logged in.

If none of these work

If Copilot still can’t see logged-in content even with page-context on, the site may use JavaScript-heavy rendering that doesn’t expose text to the DOM cleanly — manual paste (Method 2) is the workaround. For corporate-managed Copilot tenants, IT may restrict the page-context feature; coordinate with admin.

Bottom line: Copilot’s default fetch is server-side without cookies. Toggle page-context, or paste text manually, for behind-login summaries.