Apps in the workspace or file search in your own application?
Options
- 1Apps and Company Knowledge in ChatGPT
- 2The Responses API with file search in an application of your own
- 3Both: the workspace for people, the application for the workflow
Our recommendation: Apps when people work with their documents in ChatGPT and the sources sit in SharePoint, Outlook and GitHub anyway; the person's rights apply, and nothing is copied. File search when a workflow without a chat should answer from a fixed set of documents, for instance an agent that answers questions about policies, with citations and a test set in the pipeline. Often the team works in the workspace, and the workflow behind it uses the application.
What we advise against: Loading documents into a vector store that sit in SharePoint with permissions. The store does not know the permissions of the source; whoever asks the application gets what the store contains.
Which apps and connectors do we enable?
Options
- 1Every app the vendor offers
- 2The apps of the first case, by data class
- 3None until the directive exists
Our recommendation: The apps of the first case, with the data class they reach: SharePoint and Outlook for documents and emails, GitHub for code, line-of-business systems through apps of your own only after review. The approval sits in the admin console, in Enterprise in the Connector Registry, and the directive says which confidentiality level may go into which app. Every further app comes with the case that needs it.
What we advise against: Opening every app because the sign-in checks the person's rights anyway. The rights check the source, but not whether the content may reach the workspace.
Build an MCP server yourself or take a ready one?
Options
- 1The server of the system's vendor
- 2A server of your own in your Azure subscription
- 3Both, depending on the system
Our recommendation: The vendor's server where one exists and it handles sign-in on behalf of the person, for instance for Dataverse and Business Central. A server of your own for systems without one or with writes that need an approval: it runs in your Azure subscription, checks the token of the sign-in and provides only the tools the case needs. The same server serves Copilot Studio, Foundry and OpenAI.
What we advise against: A server that offers every table of a system as a tool. An agent uses what it sees, and so does an attack through a hidden instruction.
What do we clean up before the first app reads?
Options
- 1Nothing, the app only sees what is allowed anyway
- 2The sources of the first case
- 3The whole tenant
Our recommendation: The sources of the first case, completely: correct sharing with everyone and open links, superseded versions into the archive, set labels, check guests, write the source map. The rest of the tenant follows case by case, with the same reports; what is cleaned up in Microsoft 365 applies to Copilot and ChatGPT alike.
What we advise against: Cleaning up the whole tenant before a case exists. Without a case there is no measure of which sharing disturbs and which is intended.