Control 2.6: Copilot Web Search and Web Grounding Controls — Portal Walkthrough
Step-by-step portal configuration for controlling Copilot's ability to search the web and use web content for response grounding.
Prerequisites
- For the Microsoft 365 admin center review: Entra Global Admin or AI Administrator role
- For the Cloud Policy configuration: Office Apps Administrator (Microsoft's recommended role), Security Administrator, or Entra Global Admin
- Microsoft 365 Admin Center and Microsoft 365 Apps admin center (config.office.com) access
- Governance committee decision on web search policy for Copilot
Steps
Step 1: Review Web Search Settings
Portal: Microsoft 365 Admin Center Path: Admin Center > Copilot > Settings > Data Access > Web search for Microsoft Copilot and Microsoft Copilot Chat
Review the current web search configuration for Copilot. The admin control is the Allow web search in Copilot policy in the Cloud Policy service for Microsoft 365 Apps; Microsoft states the Microsoft 365 admin center Data Access page is a shortcut only and that the scenario is not configured there. In commercial tenants, if the policy is not configured, web search is on by default (unless Allow the use of additional optional connected experiences in Office is set to Disabled) and may use the Bing search service to supplement responses with public web content. For FSI environments, this behavior requires careful governance.
Step 2: Disable or Restrict Web Search
Portal: Microsoft 365 Cloud Policy service (Microsoft 365 Apps admin center)
Path: https://config.office.com > Customization > Policy Management > Allow web search in Copilot (reachable via the web search shortcut on Admin Center > Copilot > Settings > Data Access)
For most FSI deployments, configure the Allow web search in Copilot policy and set it off to prevent Copilot from: - Grounding responses on unverified external content - Potentially sending generated search queries informed by organizational context to the Bing search service - Generating responses that mix internal and external data without clear distinction
Set the policy to off for all users, or scope it to specific Microsoft Entra security groups based on governance policy. In commercial tenants, web search stays on until this policy is configured to off, so create the policy explicitly rather than relying on defaults. Microsoft documents that Click-to-Run checks in with the Cloud Policy service roughly every 90 minutes for users covered by a policy configuration, and that policies take effect the next time the Office app is restarted.
Step 3: Restrict Web Search for Sensitive Prompts
Portal: Microsoft Purview portal Path: Purview > Data Loss Prevention > Policies > Create policy (Custom) > Microsoft 365 Copilot and Copilot Chat location
If web search is selectively enabled, add a DLP rule that blocks external web search for prompts containing regulated data: - Add a rule with the Content contains > Sensitive information types condition - Set the action to Prevent Copilot from processing content > Performing Web Searches - Microsoft states DLP policy updates can take up to four hours to take effect in the Copilot experience
Step 4: Set Up Third-Party Plugin Web Access Controls
Portal: Microsoft Teams Admin Center Path: Teams Admin > Teams Apps > Permission Policies
Review third-party plugins that may access web content or external data sources. Block plugins that: - Send organizational data to external services without governance approval - Retrieve web content that could introduce unvetted information into Copilot responses
Step 5: Document Web Grounding Policy
Document the organization's web grounding policy including: - Whether web search is enabled, disabled, or selectively enabled - Which user groups have web search access and business justification - Data handling requirements for web-sourced content - Review cadence for web grounding policy
FSI Recommendations
| Tier | Recommendation |
|---|---|
| Baseline | Disable web search for all Copilot users |
| Recommended | Disable web search by default; enable for specific approved use cases with user training |
| Regulated | Web search disabled organization-wide; any exceptions require formal risk assessment and governance approval |
Next Steps
- Proceed to PowerShell Setup for web control automation
- See Verification & Testing to validate web controls
- Review Control 2.5 for overall grounding scope management
- Back to Control 2.6