Organizational Microsoft Copilot sends information to cloud services to answer your request, but this is not the same as allowing your documents to train a foundation model. Microsoft’s enterprise data protection commitments say that prompts, responses and organizational data are not used to train foundation models.
This article covers a work or school account. Do not apply its organizational controls to a personal Copilot account. There is no verified universal “Data sharing” opt-out in the Copilot pane or admin-center menu described in the earlier version of this article.
Official documentation checked: October 14, 2026.
What Information Is Used to Answer a Request?
A request can include the prompt, relevant conversation context and content retrieved or provided for the task. Microsoft’s architecture documentation explains that organizational access is scoped to the signed-in user’s permissions. The exact retrieval behavior depends on the app, feature and available work-data access.
Do not assume that Copilot sees only files currently open on your screen. Equally, having Copilot does not grant a user permission to read every file in a tenant. Review the source citations to establish what supported a particular answer; a general explanation of the service is not evidence about one request.
File names, calendar details and other business information are not categorically excluded from useful context. Avoid supplying information that your organization has not approved for that workflow.
Separate Web Search and External Integrations
When web grounding is used, Copilot can derive a search query and send it to Bing. Microsoft distinguishes that query from the entire prompt and documents its separate handling. A short prompt can itself be the query, and referenced content can influence search terms. Read Microsoft’s web-search privacy guidance rather than assuming that no business words can reach search.
Administrators can manage the documented Allow web search in Copilot policy. Disabling search is a feature decision, not a training opt-out, and can affect answers that need current public information. Test with non-sensitive prompts after an approved policy change.
Agents and other integrations need their own review. Before enabling one, record its requested permissions, receiving service and terms. Do not treat a Copilot logo as proof that every external endpoint follows identical processing rules.
Control Optional Feedback Through Real Policies
Feedback is distinct from the data needed to answer a request. Microsoft documents policies that govern submitting feedback and including screenshots, attachments, logs or content samples. Samples can include Copilot interactions. The supported administrative route is the Microsoft feedback policy guidance, including Cloud Policy service.
- Decide whether the requirement concerns feedback submission, attached content, web search, retention or access to source files.
- Ask the responsible administrator to inspect the corresponding effective policy and its user/group scope.
- For feedback controls, search the Cloud Policy interface for feedback or survey policies and review each relevant setting before changing it.
- Use a pilot group and a harmless example to confirm the intended behavior. Record the result and any lost support functionality.
A feedback restriction does not convert Copilot into an offline product. It also does not prove that all required service or diagnostic data has stopped.
Retention Is Not a Model-Training Switch
Interaction history can be stored and subject to organizational retention and investigation requirements. Microsoft documents retention for Copilot and AI apps separately. Visible chat history is not a reliable test of whether a compliance copy exists.
If you need a deletion outcome, specify what must be deleted and what holds or legal obligations apply. Do not promise “no storage after opting out,” and do not use browser-cache clearing as a compliance deletion procedure.
Practical Review for a New Copilot Workflow
Start with one real task, such as summarizing an internal project document. Note which account and app are used, which source is attached or retrieved, whether web search is allowed, and whether an agent is involved. Then identify what happens to the resulting chat and final document.
Resolve each control with its owner: information permissions with the content owner, retention with the records team, external processing with security or privacy, and feedback with the device or Microsoft 365 administrator. This produces an auditable decision instead of an unsupported “data sharing off” claim.