When you open the Copilot sidebar in Microsoft Edge, you may see a message that Copilot cannot access the current page. This stops Copilot from summarizing, answering questions about, or taking actions on the web page you are viewing. The root cause is usually a browser permission setting, a site restriction, or a conflict with another extension. This article explains why Copilot loses page access and provides step-by-step fixes to restore its ability to read the active tab.
Key Takeaways: Fixing Copilot Sidebar Page Access in Microsoft Edge
- Edge settings > Site permissions > Copilot: Controls whether Copilot can read the current page URL and content.
- Copilot pane > three-dot menu > Reload: Refreshes the sidebar connection to the active tab.
- Browser extensions like ad blockers: Can block Copilot from accessing page content by interfering with Edge’s internal APIs.
Why Copilot Cannot Access the Current Page
Copilot in the Microsoft Edge sidebar uses a browser permission called site access to read the URL and content of the current tab. This permission is granted by default when you first open the Copilot sidebar. However, several conditions can revoke or block that permission.
The most common cause is a change in Edge’s site permissions for the specific domain you are visiting. If you previously denied site access for Copilot on a particular page, Edge remembers that choice and blocks the sidebar. Another frequent cause is a browser extension that restricts script injection or content reading. Extensions such as content blockers, privacy tools, or script managers can intercept the API calls Copilot relies on. A third cause is a corrupted Copilot session state within the browser, which can happen after an Edge update or a crash. Finally, some corporate or school-managed devices may have group policies that disable the Copilot sidebar entirely or restrict its page access.
Steps to Restore Copilot Page Access in Edge
Follow these steps in order. After each step, test Copilot by asking a question about the current page. If the issue persists, move to the next step.
- Check site permissions for the current page
In Microsoft Edge, click the lock icon in the address bar to the left of the URL. In the dropdown, look for Copilot under Permissions. If it shows Blocked, click the dropdown and change it to Allow. Reload the page and open the Copilot sidebar again. - Reset Copilot permissions for all sites
Open Edge settings by clicking the three-dot menu in the top right and selecting Settings. Go to Cookies and site permissions > Site permissions > Copilot. Click Manage permissions. Under Block, you will see a list of sites where Copilot is blocked. Click the trash icon next to each blocked site to remove the restriction. Under Allow, ensure the sites you want to use Copilot on are listed. Click Add and enter the full URL of a site if needed. - Reload the Copilot sidebar
In the Copilot pane, click the three-dot menu near the top right. Select Reload. This refreshes the sidebar without reloading the entire page. Wait a few seconds and try asking a question about the page again. - Disable conflicting browser extensions
Click the three-dot menu > Extensions > Manage Extensions. Turn off extensions one by one. After disabling each extension, test Copilot. Pay special attention to ad blockers, script blockers, privacy tools, and VPN extensions. If a specific extension causes the problem, leave it off or add an exception for the Copilot sidebar. - Clear Edge browsing data for the current site
Click the lock icon in the address bar. Select Cookies and site data > Manage cookies and site data. Click the trash icon to remove all cookies for that site. Reload the page. This clears any stored permission conflicts that may block Copilot. - Reset Edge settings to default
Go to Edge settings > Reset settings > Restore settings to their default values. Click Reset. This will not delete your bookmarks, history, or passwords. It will reset site permissions, including Copilot permissions, to the factory state. After the reset, reopen Copilot and test page access.
If Copilot Still Cannot Access the Page
If the problem persists after the main steps above, check for these additional issues.
Copilot sidebar shows a blank or generic response
This can happen when the page uses a strict Content Security Policy that blocks the Copilot sidebar from injecting its script. Examples include banking portals, email clients, and internal corporate web apps. In this case, Copilot cannot access the page by design. There is no browser-level fix. You can copy the page text and paste it into the Copilot sidebar manually using the Compose or Chat input box.
Copilot is disabled by group policy on a work or school device
If you use a Microsoft 365 work or school account, your IT administrator may have disabled the Copilot sidebar using Microsoft Intune or group policy. In this case, the Copilot icon will not appear in the Edge toolbar, or the sidebar will show a message that Copilot is unavailable. Contact your IT help desk to request access. You can verify this by opening edge://policy in the address bar and looking for a policy named CopilotPageContext or HubsSidebarEnabled set to 0 or false.
Copilot works on some pages but not others
This indicates a per-site permission issue. Revisit Step 2 above and check the blocked sites list. Also verify that the page is not a restricted protocol page such as edge:// settings pages, chrome:// pages, or about:blank. Copilot cannot access those pages. It also cannot access local file URLs (file://) by default.
| Item | Copilot Sidebar with Page Access | Copilot Sidebar without Page Access |
|---|---|---|
| Description | Copilot can read the URL and visible text content of the active tab | Copilot cannot read any data from the active tab |
| User experience | You can ask for a summary, translation, or action based on the page | Copilot responds with generic answers or says it cannot access the page |
| Required permission | Site permission set to Allow for the current domain | Site permission set to Block or not granted |
| Common cause | None — this is the normal working state | User denied permission, extension conflict, or group policy restriction |
| Fix | No action needed | Reset site permissions, disable conflicting extensions, or clear cookies |
You can now restore Copilot sidebar page access by checking site permissions, disabling conflicting extensions, and resetting Edge settings if needed. If you work on a managed device, confirm with your IT team that the Copilot sidebar is enabled. As an advanced tip, you can use the edge://settings/content/copilot URL to jump directly to the Copilot permissions page and manage all blocked and allowed sites from one place.