I spent a great deal of time working with ChatGPT in a project in my business account where I am the admin to automate data entry into a spreadsheet we use. When I finally got all of the rules correct for the workflow and created a custom GPT so people could easily use this, I could not connect SharePoint so it could grab the source file. I have SharePoint enabled everywhere in the business account that the settings allow. In the Project, it can grab the source file and make updates. If it can't do it in the GPT, it kind of makes custom GPTs useless for automation of documents.
#Connecting SharePoint to a Custom GPT
midnight fjord
pine marshBOT
Hi @midnight fjord. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
You’ve run into a real limitation of how SharePoint works in ChatGPT today.
From the docs, there are two different integration paths:
-
SharePoint app / synced connector in ChatGPT (what you’re using in the Project)
- Once enabled, ChatGPT can automatically reference OneDrive/SharePoint files in normal chats and Projects, honoring permissions and sync scope. [SharePoint apps]
- Admins can enable this at the workspace level (Business/Enterprise/Edu) and users can then connect via OAuth and/or enable sync. [Business setup]
- This is what allows your Project to “grab the source file and make updates.”
-
Custom GPTs with Actions (developer-defined APIs)
- For SharePoint, OpenAI provides cookbook examples showing how to build a custom Action that talks to SharePoint/Graph via your own Azure Function. [SharePoint Actions doc; SharePoint Actions text]
- In these examples, the Custom GPT does not use the built‑in SharePoint connector; instead, it calls your API, which then searches/retrieves files from SharePoint and returns either base64 files or extracted text.
The knowledge sources do not state that the built‑in SharePoint app/connector can be attached directly to a Custom GPT as a selectable “tool” the way Actions are. They only describe:
- Using SharePoint in regular ChatGPT / Projects once the app or synced connector is enabled. [SharePoint apps; Add files from connected apps]
- Using custom Actions if you want a GPT that programmatically interacts with SharePoint (e.g., automation workflows). [SharePoint Actions doc]
So, based on the docs:
- Your observation is correct: the built‑in SharePoint connector that works in Projects is not documented as something you can “attach” to a Custom GPT for automation.
- To get a Custom GPT that reliably pulls a specific SharePoint file and updates it (automation scenario), the documented path is to build a SharePoint Action (via Azure Function + Microsoft Graph) and wire that into your Custom GPT. [SharePoint Actions doc]
Because the knowledge sources don’t describe any way to bridge “Project + SharePoint connector” directly into a Custom GPT, I can’t confirm that what you want is currently supported via the native connector. The supported, documented approach for Custom GPT–based document automation with SharePoint is to:
- Implement the SharePoint API logic in your own backend (e.g., Azure Function using Microsoft Graph, as in the cookbook). [SharePoint Actions doc]
- Expose it as an OpenAPI Action and attach it to your Custom GPT. [SharePoint Actions text]
If you’d like, I can summarize how to adapt the cookbook example to your “update a specific spreadsheet” workflow, but I can’t point to any official method to make the built‑in SharePoint connector behave inside a Custom GPT the same way it does in your Project—there’s no such capability described in the provided documentation.
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
midnight fjord
@pine marsh This was helpful, but it requires getting an Azure subscription. Why is it that I can access our SharePoint files in other parts of our workspace, but I cannot attach the connector to the custom GPT?
@pine marsh This was helpful, but it requires getting an Azure subscription. Why is it that I can access our SharePoint files in other parts of our workspace, but I cannot attach the connector to the custom GPT?
pine marshBOT
Let me check the knowledge base for you again. One moment! :books:
You’ve run into a real product gap, and the docs don’t give a “why” beyond what’s implied by how things are structured.
From the knowledge we have:
-
SharePoint in the workspace is a “connector/app with sync” feature
- Admins enable SharePoint at the workspace level; users (in Business) or admins (in Enterprise/Edu) then configure sync. [Business setup; Enterprise setup]
- Once enabled, ChatGPT can automatically reference your OneDrive/SharePoint content in chats and Projects, honoring permissions and sync scope. [SharePoint overview; Add files from connected apps]
-
Custom GPTs use a different mechanism: Actions / custom apps (MCP)
- For SharePoint automation, the official examples use your own backend (e.g., Azure Functions + Microsoft Graph) exposed as an Action, not the built‑in connector. [SharePoint Actions docs; SharePoint Actions text]
- Admin controls for “apps” and “custom apps” (MCP) are described separately from the synced connectors like SharePoint/Drive. [Admin controls]
- What’s missing in the docs
- There is no documentation saying that the SharePoint connector/app with sync can be attached as a tool to a Custom GPT.
- There is also no explanation in the docs for why that limitation exists (e.g., technical vs. security vs. roadmap). The docs simply treat:
- Connectors/apps with sync (SharePoint, Google Drive, etc.) as something ChatGPT itself uses to enrich conversations and Projects. [Apps with sync overview]
- Custom GPT automation against SharePoint as something you do via your own Action/backend. [SharePoint Actions docs]
So, based on the available information:
- You can access SharePoint files in chats/Projects because the SharePoint app with sync is a first‑party connector that ChatGPT uses internally once enabled. [SharePoint overview]
- You cannot “attach the connector” to a Custom GPT because that capability is simply not documented or exposed—Custom GPTs are expected to use Actions or MCP-based custom apps for this kind of automation, and the official SharePoint examples assume you’ll host your own integration (e.g., on Azure). [SharePoint Actions docs]
The knowledge sources do not provide an official rationale for this design choice, only the behavior and the supported patterns.
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
midnight fjord
@pine marsh So, it's probably best just to do automations as a project and just treat the project like a custom GPT
pine marshBOT
Let me check the knowledge base for you again. One moment! :books:
Yes—given what’s documented today, using a Project is the most “native” way to run SharePoint‑backed automations without standing up your own Azure/Graph integration.
From the docs:
- Once the SharePoint app / synced connector is enabled, ChatGPT can automatically reference your SharePoint and OneDrive files in conversations and Projects, respecting permissions. [SharePoint apps]
- Projects are designed as a “live context hub” where teams share files, chats, and instructions, and ChatGPT can use that shared context for recurring workflows. [Projects vs GPTs]
The knowledge sources do not describe any way to attach the built‑in SharePoint connector directly to a Custom GPT, while they do show Projects working with connected apps and synced content. [Add files from connected apps]
So for your use case (automating updates to a SharePoint‑hosted spreadsheet) and avoiding Azure:
- Treat a Project as your “automation hub”:
- Put your workflow instructions in the Project’s custom instructions. [Projects FAQ]
- Let ChatGPT access the SharePoint file via the connector inside that Project.
- Reserve Custom GPTs + Actions only if/when you’re ready to host your own SharePoint integration (e.g., Azure Function + Graph), which is the pattern shown in the cookbook. [SharePoint Actions]