ChatGPT Enterprise and Edu: individual sync connections disabled from 14 August 2026
OpenAI has disabled individual-user sync connections in ChatGPT Enterprise and Edu. Admins must migrate to admin-managed sync or plugins now.
From 14 August 2026, OpenAI disabled all individually authorised sync connections in ChatGPT Enterprise and Edu workspaces. If your organisation has users who connected their own Google Drive, SharePoint, GitHub, GitLab Issues, or Azure DevOps accounts to ChatGPT using their personal credentials, those connections are now off, and deletion of the associated synced data has begun. If your workspace admins have not already acted, users will have lost access to knowledge that was previously surfaced through those connections.
This is a hard cut, not a soft deprecation with a long runway. New individual sync connections stopped being available from 10 August 2026, and the existing ones followed four days later.
What changed, and why it matters
ChatGPT Enterprise has supported data connectors since late 2025, allowing ChatGPT to query approved external sources such as SharePoint, Google Drive, and GitHub rather than requiring manual file uploads. These connectors could be set up in two ways: an admin could configure a connection centrally for the whole workspace, or an individual user could authorise their own connection using their personal OAuth credentials.
OpenAI has now closed the second path entirely. Only admin-managed sync connections remain supported. The reasoning is straightforward from a governance perspective: user-level OAuth connections are harder for IT teams to audit, revoke, and control. Centralising sync under admin management brings it in line with how enterprise software is typically governed.
Administrator-managed sync is completely unaffected by this change. If your workspace was already running on admin-configured connectors, nothing has changed for your users.
What you need to do if you haven’t already
If your workspace relied on individually authorised sync, you have a few routes depending on which service is involved.
Google Drive. Enable the Google Drive plugin from Admin settings. If you need synced knowledge (rather than just plugin-based access), configure admin-managed Google Drive sync using domain-wide delegation. The OpenAI Help Center guide for Google Drive walks through the setup.
SharePoint. Enable the SharePoint plugin and, if synced knowledge is required, configure admin-managed SharePoint sync. OpenAI notes a useful transition path here: go to Admin settings, then Apps, then SharePoint, then “Deploy to team”. This adds admin-managed sync without immediately removing the user-authenticated app, which means you can avoid a hard outage for users while you migrate. The SharePoint app guide covers this in detail. Note that from 30 April 2026, the SharePoint app moved from delegated Microsoft scopes to application scopes for the “Deploy to your team” sync option, so check your Microsoft Entra ID permissions if you configured this before that date.
GitHub. Enable the non-synced GitHub plugin. There is no admin-managed sync option for GitHub; plugin-based access is the supported path.
GitLab Issues and Azure DevOps (Azure Boards). OpenAI has said replacement plugins for these services will be communicated separately. Keep an eye on the Enterprise and Edu release notes for updates.
A note on synced data deletion
OpenAI has confirmed that deletion of synced data from disabled individual connections has begun. This is worth taking seriously. Data that was pulled into ChatGPT from a user’s personal Google Drive or SharePoint authorisation is being removed from OpenAI’s systems. If any of that data was the primary or only copy held in ChatGPT’s knowledge layer, it is gone once deletion completes. The original files in Google Drive or SharePoint are not affected, but any knowledge built up through the sync will need to be reconstructed through admin-managed sync if you want it back.
The broader direction of travel
This change fits a clear pattern. Over 2025 and into 2026, OpenAI steadily tightened the governance model around ChatGPT Enterprise. Connectors were renamed to apps in December 2025, and in July 2026 the app directory moved into the plugin directory, making plugins the primary way users and admins discover integrations. The direction is towards centralised admin control, role-based access controls, and auditable data flows rather than ad-hoc user-level connections.
For IT and security teams, this is broadly a good thing. Admin-managed sync means you can see exactly what data sources are connected to your ChatGPT workspace, control who can access them through RBAC, and revoke access centrally when someone leaves the organisation. The Microsoft Purview sensitivity label integration is also relevant here: files protected by labels that enforce encryption or access control are not synced by ChatGPT, which is the kind of guardrail enterprise security teams need.
For end users, the change is largely invisible if their admin has already configured admin-managed sync. If it hasn’t been done, they will notice their previously available knowledge has disappeared.
What this means for you
If you are a ChatGPT Enterprise or Edu admin and you have not yet reviewed your connector settings, do it now. The deadline has passed and data deletion is under way. Check Admin settings and look for any connectors that were set up at the user level rather than the admin level. For each affected service, follow the migration steps above or in the OpenAI Help Center.
If you are a user who has lost access to synced knowledge, the right move is to raise it with your workspace admin rather than trying to reconnect at the individual level. That option no longer exists.
The shift to admin-managed sync is the right call for enterprise governance, but it does require admins to take deliberate action. If your organisation has not done that yet, the time is now.