Skip to content
← All insights

How-to4 min read

Stop Copy-Pasting Company Files into ChatGPT: Run a Controlled SharePoint Pilot

Plan a controlled company-file pilot with scope, licensing, consent, access tests and human verification.

Plan a controlled company-file pilot with scope, licensing, consent, access tests and human verification.
Original conceptual illustration; not a product screenshot or evidence of a real incident.

A manager needs the latest leave policy, a project lead wants the approved scope, and Finance is looking for a supplier procedure. The usual response is to download files from SharePoint and upload them into a new AI chat. That works, but it creates unnecessary copies and makes it harder to know whether the answer came from the current document.

A better pilot is to connect ChatGPT to an approved SharePoint source and let staff search information they already have permission to view. The useful outcome is faster retrieval with source links, controlled access and a clear owner.

What you need before starting

You need an eligible ChatGPT workspace where the SharePoint app or plugin is available, plus a Microsoft organisational account that can access the intended SharePoint content. Availability can vary by plan, rollout, administrator settings and role. OpenAI’s current guidance says plugins and apps are generally enabled by default for ChatGPT Business, while Enterprise and Edu administrators control availability more tightly.

This is a ChatGPT-to-SharePoint integration, not Microsoft 365 Copilot. Confirm the organisation’s actual ChatGPT entitlement and Microsoft 365 access instead of assuming a Copilot add-on is required.

Assign two owners before touching the settings: a ChatGPT workspace administrator and a Microsoft 365 administrator. They may be different people. If Microsoft Entra requires administrator consent, the Microsoft administrator must review the requested permissions rather than approving them as a formality.

1. Choose a narrow document set

Start with one SharePoint site containing low-risk, useful material such as staff procedures, approved templates or product information. Avoid payroll, disciplinary records, customer secrets and unrestricted commercial folders in the first pilot.

Define one measurable question, such as: “Can employees find the current travel-claim rules and cite the source in under two minutes?”

2. Fix SharePoint access first

A connector does not repair poor permissions. If an employee can already open an overshared SharePoint folder, a personal connection may retrieve that content. Review site membership, broad sharing links and obsolete access before connecting anything.

Use SharePoint or Microsoft 365 groups where possible, align permissions with job roles and confirm that every pilot site has an owner. Do not create a powerful shared account simply to make search easier. OpenAI documents that personal connections use the employee’s source permissions, while shared connections may have broader access.

3. Enable and connect the approved app

In ChatGPT, the workspace administrator should review the SharePoint plugin or app, make it available only to the intended pilot group and examine its actions and requested permissions. OpenAI separates several controls: plugin availability, app access, permitted actions, the authenticated Microsoft identity and the external service’s own permissions.

The pilot user can then install the approved plugin if required and complete the Microsoft sign-in. If the tenant blocks user consent, follow the Entra admin-consent process. Microsoft advises inspecting the application, publisher and exact permissions before granting tenant-wide consent.

For an information-retrieval pilot, keep the scope read-only wherever the available controls support it. Installing a plugin does not automatically connect an account or approve every action.

4. Test with questions that expose mistakes

Start a new chat and invoke the approved SharePoint plugin with an @ mention, or describe the task directly where automatic tool selection is supported. Ask for the document title and source link with every answer.

Run four tests:

  • Find a known current document and summarise only what it says.
  • Compare two approved versions and identify the newer source.
  • Ask for a document the pilot user should not be able to access; retrieval must fail.
  • Ask an ambiguous question and check whether the answer admits uncertainty instead of inventing a policy.

Hypothetical example: A 40-person Malaysian consultancy connects only its Operations Procedures site. A staff member asks, “What receipts are required for a local travel claim?” ChatGPT returns a short answer with a link to the approved procedure. The same user asks for a directors-only remuneration file and receives no result. This is an illustrative scenario, not an AXO client case.

5. Train staff to verify, not merely trust

Require users to open the cited document before acting on HR, financial, contractual or security instructions. Connected search reduces hunting time; it does not turn an AI response into the official record. If a source is outdated, correct or archive the SharePoint document rather than repeatedly correcting the prompt.

OpenAI notes that retrieved app content is not automatically saved as a Library file, but information placed into a conversation or generated file follows that location’s retention rules. Copying an answer into a widely shared page can expose it beyond the original audience.

6. Review the pilot after two weeks

Measure successful searches, failed searches, stale documents discovered, access exceptions and time saved on repeat questions. Review the application permissions in Microsoft Entra and confirm the pilot group still needs access. Remove the connection if the business purpose has ended.

For ChatGPT Business, Enterprise and Edu, OpenAI states that workspace data is encrypted in transit and at rest and is not used to train its models by default. That is an important control, but it does not replace document classification, least privilege, retention decisions or human review.

Keep the first deployment small: one useful site, a defined user group, read-oriented use, test evidence and a named owner. Expand one site at a time only after the pilot consistently returns current sources without crossing permission boundaries.

For help planning a governed AI and Microsoft 365 integration roadmap, contact AXO Technologies: Contact AXO Technologies

Sources

← Explore all insightsDiscuss your priorities with AXO ↗