M365 Copilot uses the Bing service to obtain information from the internet. Many customers have questions about M365's interaction with Bing. Although Bing is a Microsoft-managed consumer service, it is not managed within the M365 security and accreditation boundary. Security is paramount for both M365 and Bing, but each is governed by different terms and conditions.
The simplest way to describe the interaction is this: M365 Copilot reviews a user's prompt and determines whether web-grounded data is needed. If so, Copilot creates one or more short, intent-based keyword queries; it does not forward the original prompt to Bing. User identity, tenant ID, cookies, and tracking identifiers are removed before the query leaves Copilot's orchestration layer. All web data is then returned to the M365 service boundary for processing. The biggest misconception is that M365 sends all of its data to Bing; this does not happen. Only the derived queries are sent.
Only the sanitized, derived web query is sent to commercial Bing, over an encrypted Microsoft service-to-service connection. Bing searches its web index and returns public results to M365, where Copilot synthesizes the response. Without ZQL, Bing retains a log of the derived query by default. The full M365 Copilot prompt, files, response, and tenant interaction records are not transmitted to Bing as the search payload. However, words drawn from the prompt or from a referenced or open file can appear in the derived query, and removing identity metadata does not guarantee that the query's subject matter is nonsensitive. For this reason, Microsoft created the ZQL feature so that queries to the commercial Bing index are not logged.
ZQL is a customer-implemented control that provides enhanced privacy and compliance when web grounding is enabled in Microsoft 365 Copilot. It removes query retention in Bing, which reduces compliance risk and lets organizations that turned off web search because of data retention concerns enable web grounding with confidence. When ZQL is enabled, Bing does not retain a log of query data or identifiers from web grounding through Microsoft 365 Copilot.
Even though Bing does not keep logs, the organization’s own records inside the Microsoft 365 boundary are unchanged. Prompts, responses, and the web search keywords Copilot used continue to be recorded in the Microsoft Purview Audit log, and Copilot prompts and responses are stored in hidden folders in each user’s mailbox. These in-boundary records remain available for eDiscovery, retention policies, and legal hold, can be reviewed with DSPM for AI, and remain protected by enterprise data protection.
Additionally, Microsoft Purview DLP for Microsoft 365 Copilot lets customers define which sensitive information Copilot can process and when it can use the web. Policies can detect sensitive information types (SITs), such as credit card, passport, and Social Security numbers, as well as custom SITs the organization defines. DLP can be configured at several points in the Copilot process to protect against sensitive information appearing in a derived query.
In short, customers who need additional control over how M365 Copilot interacts with Bing should first implement Copilot DLP capabilities, and then consider whether ZQL is needed.
Reference: https://learn.microsoft.com/en-us/microsoft-365/copilot/microsoft-365-copilot-zero-query-logging
No comments:
Post a Comment