Control 2.6: Copilot Web Search and Web Grounding Controls
Control ID: 2.6 Pillar: Security & Protection Regulatory Reference: GLBA §501(b), Data Residency Considerations Last Verified: 2026-09-24 Governance Levels: Baseline / Recommended / Regulated
Objective
Govern the web search and web grounding capabilities within Microsoft 365 Copilot to control whether Copilot can retrieve information from the public internet (via Bing) when responding to user queries. For financial institutions, web search in Copilot raises data privacy, data residency, and regulatory concerns that must be evaluated against the productivity benefits. This control provides a risk-based framework for enabling, restricting, or disabling web search across different user populations.
Why This Matters for FSI
- GLBA §501(b) requires safeguards for customer information — when web search is enabled, Copilot-generated search queries may be sent to Bing's search infrastructure, and firms must understand this data flow to assess risk to customer information
- Data residency requirements may be impacted if generated search queries (which can be informed by business context) are processed through web search services located in different regions than the firm's M365 tenant
- SEC Reg S-P requires protection of customer NPI — if generated search queries derived from prompts contain customer information and are routed to web search services, this may constitute disclosure to a third-party processor
- FINRA Rule 3110 (Supervision) requires supervision of registered representatives' communications — web search queries from Copilot may not be captured in standard supervision workflows
- Vendor risk management expectations from OCC Bulletin 2023-17 and FFIEC guidance require due diligence on data processing by third-party services — web search in Copilot involves Bing's infrastructure as an additional processing layer
Control Description
Microsoft 365 Copilot can optionally use web search to augment its responses with current public information. When enabled, Copilot sends a search query derived from the user's prompt to Microsoft Bing and incorporates web results into the response.
Web Search Data Flow
User Prompt → Copilot Service → Query Extraction
│
┌───────┴───────┐
│ │
Web Search OFF Web Search ON
│ │
M365 Data Bing Search API
Only │
│ ├─ Generated query sent
│ ├─ Web results returned
│ ├─ Results integrated
│ └─ Query available to
│ audit / eDiscovery /
│ DSPM for AI
│ │
└───────┬───────┘
│
Response
to User
Privacy and Data Handling for Web Search
| Data Element | When Web Search is ON | When Web Search is OFF |
|---|---|---|
| User prompt | Processed by Copilot; a generated search query is derived and sent to the Bing search service. The prompt and response stay within the Microsoft 365 service boundary | Processed by Copilot only |
| Generated search query | A few words derived from the prompt — not the entire prompt (unless the prompt is very short, for example "local weather"), not entire files, and not entire web pages summarized in Edge | Not applicable |
| Bing search results | Returned to Copilot for response integration | Not applicable |
| User and tenant identity | Microsoft states user and tenant identifiers are removed before the generated query is sent to the Bing search service; no identifying information based on the user's Microsoft Entra ID is included | Not applicable |
| Microsoft's stated commitments on generated queries | Per the Product Terms: no Microsoft rights beyond providing the service; not used to improve Bing; not used for advertising profiles or behavior tracking; not shared with advertisers; not used to train generative AI foundation models; treated as customer confidential information | Not applicable |
| Contractual position for generated queries | Microsoft states it acts as a data controller for generated web search query data, that the Data Protection Addendum (DPA) does not apply to generated web search queries, and that the Product Terms supersede the Microsoft Services Agreement and Microsoft Privacy Statement in the event of conflict. HIPAA and the EU Data Boundary do not apply to generated search queries | Not applicable (prompts and responses remain under enterprise data protection and the DPA, with Microsoft acting as a data processor) |
| Query visibility for governance | Generated web search queries are available to admins through audit log search, eDiscovery, and Microsoft Purview DSPM for AI activity explorer | Not applicable |
Web Search Risk Assessment for FSI
| Risk Factor | Low Risk | Medium Risk | High Risk |
|---|---|---|---|
| Data in prompts | General business questions | Industry-specific queries | Prompts containing customer names/data |
| User population | Back-office, administrative | Front-office, general | Registered reps, trading, compliance |
| Regulatory sensitivity | General operations | Moderate (internal controls) | High (MNPI, customer data, regulatory) |
| Data residency | Single-country operation | Multi-country, same region | Cross-border, multiple jurisdictions |
| Recommendation | Enable web search | Enable with monitoring | Disable web search |
Web Search Configuration Options
| Setting | Description | Admin Control |
|---|---|---|
| Tenant web search policy | Enable or disable web search for Microsoft Copilot and Microsoft Copilot Chat users | Cloud Policy service for Microsoft 365 policy: Allow web search in Copilot |
| Group-based web search | Enable web search for specific user groups only | Cloud Policy service policy configuration scoped to Microsoft Entra security groups |
| Work/Web mode split | Disable web search in Microsoft Copilot Work mode while allowing Microsoft Copilot Web mode and Microsoft Copilot Chat. Microsoft states this option also disables web search in Researcher and Cowork | Cloud Policy service policy option |
| Unconfigured (default) state | If the Allow web search in Copilot policy is not configured, Microsoft states web search is available to users in both Microsoft Copilot and Microsoft Copilot Chat, unless Allow the use of additional optional connected experiences in Office is set to Disabled (which also restricts many other Microsoft 365 experiences) | Configure the policy explicitly rather than relying on the default |
| Optional web content toggle | Users can turn web content off. Microsoft states this toggle is available to both Microsoft Copilot and Microsoft Copilot Chat users, is on by default when the admin enables web search, and that the preference persists across sessions and applies across supported Copilot clients and devices | User-level Web content toggle (surfaced as the Web search toggle under Settings > Personalization > Advanced in the Microsoft Copilot app) |
| Mandatory disable | Web search disabled with no user override — Microsoft states the Web content toggle is turned off and dimmed | Cloud Policy service policy set to disabled |
| Sensitive-data web search block | Block external web search for a specific prompt when the prompt text contains selected sensitive information types (SITs) | Microsoft Purview DLP policy on the Microsoft 365 Copilot and Copilot Chat location with the Prevent Copilot from processing content > Performing Web Searches action |
Graph Beta Policy Verification Boundary
Microsoft Learn documents a Microsoft Graph beta copilotPolicySetting resource for microsoft.copilot.allowwebsearch, available at GET https://graph.microsoft.com/beta/copilot/admin/policySettings/microsoft.copilot.allowwebsearch. The endpoint is tenant-level only: Microsoft documents that user-level and group-level policies are not supported, and that group-scoped settings return 422 with groupScopedSettingNotSupported. The endpoint is documented for the Global service; this commercial-cloud framework treats the Graph beta response as corroborating tenant evidence only.
Use this beta endpoint only as corroborating tenant evidence. Public Microsoft documentation describes the value property as a setting-specific string that might be a digit representing a state, but it does not publish a value map for the three Allow web search in Copilot policy options. Capture the raw value and policyId from the tenant and reconcile them to the Cloud Policy UI before documenting a value-to-policy mapping.
Selective Web Grounding Controls
Beyond the binary enable/disable decision, Microsoft currently documents the following selective controls. Organizations should verify which of these are available in their tenant before relying on them in a governance design.
| Mechanism | What it does | Where it is configured |
|---|---|---|
| Group-scoped Cloud Policy | Applies the Allow web search in Copilot setting to specific Microsoft Entra security groups only | Cloud Policy service for Microsoft 365 (config.office.com) |
| Work/Web mode split | Turns web search off in Microsoft Copilot Work mode while leaving it on in Web mode and Microsoft Copilot Chat | Cloud Policy service for Microsoft 365 |
| Purview DLP web search block | Blocks external web search as a grounding source for prompts that contain selected SITs; Copilot still answers from permitted internal Microsoft 365 sources | Microsoft Purview portal > Data Loss Prevention > Policies (Custom policy, Microsoft 365 Copilot and Copilot Chat location) |
| Per-agent scoped web search | For declarative agents, web search can be enabled per agent and scoped to up to four public websites (an allowlist, configured by the agent author) | Agent Builder Knowledge section, or the WebSearch capability with the sites property in the declarative agent manifest (schema v1.3 or later) |
Tenant-wide domain exclusion is not a documented capability
Current Microsoft documentation for Microsoft 365 Copilot does not describe a tenant-wide setting that excludes specific domains from Copilot web grounding, and the Microsoft 365 admin center Copilot settings do not include a "Web Content" node. The nearest documented domain-level control is the per-agent scoped web search allowlist described above, which is an allow list rather than a block list. Microsoft Edge policies such as BrowsingWithCopilotAllowList govern browsing with Copilot in Edge and are a separate product surface. Organizations that require domain-level blocking should verify current capability with Microsoft rather than assuming it exists.
FSI relevance of selective controls:
- Sensitive-prompt containment: DLP-based web search blocking helps keep prompts that carry customer identifiers or other regulated SITs from reaching external web search, without removing web grounding from the whole population
- Population scoping: Group-scoped Cloud Policy supports different postures for front-office, back-office, and supervised populations
- Agent-level restriction: Per-agent scoped web search limits an approved agent's web grounding to a small set of vetted public sources
Selective Web Grounding Governance Tiers:
| Level | Requirement | Rationale |
|---|---|---|
| Baseline | Review the available selective web grounding controls listed above; document which are in use and which are deliberately not used | Awareness of the available capability and an initial assessment of whether selective control is appropriate |
| Recommended | Maintain documented business justification for each selective control in use — Cloud Policy group scoping, DLP web search rules, and any per-agent scoped-site allowlists; review quarterly; assign ownership to a designated governance role | Active management with documented rationale supports examination readiness |
| Regulated | All Recommended requirements plus: require compliance approval before changing group scoping, DLP web search rules, or agent scoped-site allowlists; conduct at least quarterly review against the firm's vendor risk and content governance standards; retain change history | Comprehensive governance with approval workflows and audit trail |
Copilot Surface Coverage
| M365 Application | Web Search Available | Admin Controllable | User Toggle | Notes |
|---|---|---|---|---|
| Microsoft Copilot Chat | Yes | Yes | Yes (if enabled) | Primary web search surface; web search query citations are shown here only |
| Word | Limited | Yes | Yes (if enabled) | Web search for research/drafting; query citations are not shown in the in-app Copilot pane |
| Excel | No | N/A | N/A | Data analysis does not use web search |
| PowerPoint | Limited | Yes | Yes (if enabled) | Web content for presentations; query citations are not shown in the in-app Copilot pane |
| Outlook | Limited | Yes | Yes (if enabled) | Web context for email drafting |
| Teams | Yes | Yes | Yes (if enabled) | Web search in Teams Copilot |
| OneNote | No | N/A | N/A | Not applicable |
| Loop | Limited | Yes | Yes (if enabled) | Web content in Loop components |
| Copilot Pages / Notebooks (Copilot Cowork) | Yes | Yes | Yes (if enabled) | Include Pages and Notebooks co-authoring in web-grounding scope decisions |
| Researcher in Microsoft Copilot | Yes | Yes | Yes | Microsoft recommends enabling web search to get the most value from Researcher; Researcher has its own Web search toggle in the input box |
| Analyst in Microsoft Copilot | Yes | Yes | No | Microsoft states Analyst does not have a Web content toggle for users |
| SharePoint (Agents) | Configurable | Yes | No | Per-agent web search setting; the tenant policy overrides the agent setting |
How the user-level toggle applies
Microsoft documents a single user-level Web content preference (surfaced as the Web search toggle under Settings > Personalization > Advanced in the Microsoft Copilot app). Microsoft states the preference persists across sessions and is applied across supported Copilot clients and devices, rather than being set separately in each application. When the admin disables web search, the toggle is turned off and dimmed.
Governance Levels
| Level | Requirement | Rationale |
|---|---|---|
| Baseline | Disable web search org-wide during initial Copilot deployment; document the decision and rationale; review quarterly | Reduces web search data-flow risk by removing public-web grounding during initial AI adoption |
| Recommended | Enable web search for non-regulated user groups (HR, marketing, general operations) via group-based policy; disable for registered representatives, traders, compliance, and executive leadership; monitor web search usage via Copilot analytics; quarterly review of group assignments | Balanced approach that provides web search value where risk is low while maintaining restrictions for high-risk user populations |
| Regulated | Disable web search org-wide; if business need arises, require formal risk assessment and CISO approval before enabling for any group; document exceptions with business justification and compensating controls; annual review of web search policy | Maximum data containment — appropriate for firms where any external data flow from user prompts is unacceptable based on regulatory posture |
Setup & Configuration
Step 1: Access the Copilot Control System
Portal: Microsoft 365 admin center > Copilot
Use the Copilot Control System as the centralized admin surface to review Copilot license status, security and compliance controls, agent management, and the Copilot scenario settings. The web search entry point appears under Copilot > Settings > Data Access > Web search for Microsoft Copilot and Microsoft Copilot Chat. Microsoft states this entry point is a shortcut only — the setting itself is not configured in the Microsoft 365 admin center, and the link opens the Microsoft 365 Apps admin center (Cloud Policy service) where the policy is created.
Step 2: Configure the Cloud Policy Web Search Control
Portal: Cloud Policy service for Microsoft 365 (config.office.com), or the Microsoft Intune admin center under Apps > Policy > Policies for Office apps
Roles: Microsoft documents Office Apps Administrator (recommended), Security Administrator, or Entra Global Admin for the Microsoft 365 Apps admin center
- Under Customization, select Policy Management, then create or update the policy configuration for the intended tenant, pilot, or exception scope
- On the Choose the scope page, select all users or specific Microsoft Entra security groups (policies apply to user objects only; nested groups are supported up to three levels)
- On the Configure Settings page, search for Allow web search in Copilot
- Select the governance-approved option:
- Enabled in Microsoft Copilot and Microsoft Copilot Chat
- Disabled in Microsoft Copilot and Microsoft Copilot Chat
- Disabled in Microsoft Copilot Work mode; Enabled in Microsoft Copilot Web mode and Microsoft Copilot Chat
- Review and publish, then allow policy propagation before user testing. Microsoft documents that Click-to-Run checks in with the Cloud Policy service roughly every 90 minutes for users covered by a policy configuration (24 hours for users who are not), and that policies take effect the next time the Office app is restarted
- If using Graph beta evidence, query
microsoft.copilot.allowwebsearchand record the returned rawvalue/policyId, but treat the value encoding as tenant-observed unless Microsoft publishes a value map for this setting
Do not rely on the default
Microsoft states that if the Allow web search in Copilot policy is not configured, web search is available to users in both Microsoft Copilot and Microsoft Copilot Chat unless Allow the use of additional optional connected experiences in Office is set to Disabled. Firms intending a disabled posture should create the policy explicitly.
Step 3: Configure Group-Based Web Search (Recommended Level)
If enabling web search for specific groups:
- Create a security group for web-search-enabled users (e.g., "Copilot-WebSearch-Enabled")
- Add appropriate users (non-regulated populations)
- Assign the Allow web search in Copilot Cloud Policy configuration to this group
- Verify that users outside the group cannot access web search in Copilot
Step 4: Configure Sensitive-Data Web Search Restrictions
Portal: Microsoft Purview portal > Data Loss Prevention > Policies
- Create a Custom policy and turn on the Microsoft 365 Copilot and Copilot Chat location (Microsoft states this location is available only in the Custom template, and that selecting it disables all other locations for that policy)
- Add a rule with the Content contains > Sensitive information types condition covering the SITs that represent regulated or customer data
- Set the action to Prevent Copilot from processing content > Performing Web Searches
- Save and turn on the policy. Microsoft states DLP policy updates can take up to four hours to take effect in the Copilot experience, and that DLP does not scan the contents of files uploaded directly into prompts — only the typed prompt text
- Record the tenant's web search entry point status in the Copilot Control System alongside the Cloud Policy decision, and document how the two relate
Step 5: Configure Agent Web Search
For declarative agents, including agents created from SharePoint:
- Web search is a per-agent capability; agent authors can enable it and optionally scope it to up to four public websites (Agent Builder Knowledge section, or the
WebSearchcapability with thesitesproperty in the declarative agent manifest, schema v1.3 or later) - Set the governance default to "disabled" for all new agents and require approval for agents with web search enabled
- Account for the documented interaction with tenant policy: Microsoft states that when administrators disable web search, agents with web search enabled do not report an error and simply do not include web results, while developer-mode debug cards may still show web search as enabled. Verification should therefore test agent responses rather than rely on the agent's own configuration display
- For scoped web search, note Microsoft's documented limitation that grounding relies on Bing-indexed content for those sites, so dynamically rendered or frequently changing content may be missing or stale
Step 6: Monitor Web Search Usage
Microsoft documents that generated web search queries are available to admins through audit log search, eDiscovery, and Microsoft Purview DSPM for AI activity explorer. Copilot interactions are recorded as CopilotInteraction events (RecordType 261) in the unified audit log, and Bing-backed web search appears in the CopilotEventData.AISystemPlugin collection.
# Search audit logs for Bing-backed web search activity in Copilot interactions
Search-UnifiedAuditLog -StartDate (Get-Date).AddDays(-30) -EndDate (Get-Date) `
-RecordType CopilotInteraction -ResultSize 5000 |
Where-Object {
($_.AuditData | ConvertFrom-Json).CopilotEventData.AISystemPlugin.Id -contains 'BingWebSearch'
}
Step 7: Document the Decision
Regardless of setting chosen, document:
- Cloud Policy configuration and assigned groups
- Copilot Control System web search entry-point status and any Purview DLP web search rules
- Any per-agent scoped web search allowlists
- Risk assessment summary
- Business justification
- Approver (CISO or equivalent)
- Review cadence
- Date of last review
Financial Sector Considerations
- Registered Representatives: Web search should be disabled for registered representatives. Their Copilot queries may contain client names, ticker symbols, or investment context that should not flow to external search services, even in anonymized form.
- Trading Desks: Proprietary trading information and strategies must never be exposed through web search queries. Disable web search for all trading personnel.
- Compliance Teams: Compliance staff working on regulatory matters, examinations, or investigations should not have web search enabled, as their queries may contain sensitive regulatory context.
- Research Analysts: Consider the implications of enabling web search for research analysts. While public market information is valuable, analyst queries may inadvertently reveal research coverage changes or opinion shifts.
- Vendor Risk Assessment: If enabling web search, document Bing's data processing practices in the firm's third-party vendor risk assessment. Note Microsoft's documented position that it acts as a data controller for generated web search queries and that the Data Protection Addendum does not apply to those queries — a different contractual posture from Copilot prompts and responses, where Microsoft acts as a data processor. Microsoft's commitments regarding generated query handling should be evaluated against the firm's vendor management standards.
- Data Residency Impact: Evaluate whether web search processing locations align with the firm's data residency requirements. Microsoft states the EU Data Boundary does not apply to generated search queries, and that the Bing search service operates separately from Microsoft 365 with different data-handling practices.
- Supervision and Records: Microsoft documents that generated web search queries can be searched, audited, and collected through eDiscovery alongside prompts and responses, and can be viewed in Purview DSPM for AI activity explorer. Firms should verify whether these query records fall within their supervision and recordkeeping procedures.
- Examination Preparedness: Be prepared to explain the web search configuration decision to examiners. Whether enabled or disabled, having a documented, risk-based rationale demonstrates sound governance.
Verification Criteria
- Web Search Status: Verify the Allow web search in Copilot Cloud Policy selection matches the intended governance level, and confirm the policy exists rather than relying on the unconfigured default
- Graph Beta Evidence Boundary: If collecting API evidence, verify
GET https://graph.microsoft.com/beta/copilot/admin/policySettings/microsoft.copilot.allowwebsearchreturns the tenant-level setting, retain the rawvalueandpolicyId, and reconcile the raw value to the Cloud Policy UI in the tenant rather than assuming a public 0/1/2 mapping - Group Scoping: If using group-based web search, verify that only assigned Cloud Policy groups can access web search functionality in Copilot
- User Experience Test (Disabled): As a user with web search disabled, ask Copilot a question that would require web data — confirm no web results appear, that the Web content toggle is turned off and dimmed, and that the response is based solely on M365 data
- User Experience Test (Enabled): As a user with web search enabled, ask a current events question in Microsoft Copilot Chat — confirm web results are integrated and that the web search query citations appear in the linked citation section (Microsoft states these citations are available in Microsoft Copilot Chat only, and remain in the chat thread for 24 hours)
- Regulated User Exclusion: As a registered representative or trading desk user, verify web search is not available in Copilot
- Agent Configuration: Verify the default web search setting for new declarative and SharePoint agents is "disabled", and verify agent behavior by testing responses — Microsoft states agents with web search enabled do not report an error when administrators have disabled web search tenant-wide
- Audit Trail: Confirm
CopilotInteractionevents are captured in the unified audit log and that generated web search queries are retrievable through audit log search, eDiscovery, or Purview DSPM for AI activity explorer - DLP Web Search Restriction: If a Purview DLP rule with the Performing Web Searches action is in place, verify it is enabled on the Microsoft 365 Copilot and Copilot Chat location and test with a prompt containing an in-scope SIT
- Decision Documentation: Verify that a documented risk assessment, Cloud Policy assignment, Copilot Control System setting record, and approval record exist for the web search configuration
- Review Cadence: Confirm quarterly (Baseline/Recommended) or annual (Regulated) review of web search policy is scheduled
- Vendor Risk Assessment: Verify that Bing/web search data processing is included in the firm's third-party vendor risk assessment (if web search is enabled for any users)
Additional Resources
- Data, privacy, and security for web search in Microsoft Copilot and Microsoft Copilot Chat
- copilotPolicySetting resource type
- Get copilotPolicySetting
- Manage Microsoft Copilot settings in the Microsoft 365 admin center
- Overview of Cloud Policy service for Microsoft 365
- Learn about using Microsoft Purview DLP to protect interactions with Microsoft 365 Copilot and Copilot Chat
- Add knowledge sources to your declarative agent (web and scoped web search)
- Copilot interaction events overview (audit schema)
- Set up Microsoft 365 Copilot and assign licenses
- Microsoft 365 Copilot privacy and data protection
- GLBA §501(b) and Interagency Guidelines Establishing Information Security Standards
- Related Controls: 2.5 Data Minimization, 2.7 Data Residency, 2.14 Declarative Agents, 4.1 Admin Settings & Feature Management
- Playbooks: Portal Walkthrough, PowerShell Setup, Verification & Testing, Troubleshooting