Microsoft Copilot
What is ChatGPT Enterprise governance?
Governing ChatGPT Enterprise means knowing which custom GPTs, projects, connectors and seats exist in your workspace, who each is shared with, what data it can reach and who owns it. It uses metadata and a join to your Microsoft identity, without reading conversations. Coverage in Rencore is in Preview.
In short
- ChatGPT Enterprise keeps its own users, GPTs and projects, outside the Microsoft 365 policies you already run.
- The first risks are sharing and reach: GPTs open to the whole workspace and projects wired to company data.
- Govern from metadata. You do not need to read conversations to answer who owns what and who can open it.
- Join every user to your identity provider, so seats and spend read by department.
Step by step
Five steps bring ChatGPT Enterprise under the same operating model as the rest of your digital workplace.
-
Confirm the plan and connect the workspace
Check that the workspace is ChatGPT Enterprise, since ChatGPT Business is outside OpenAI's Compliance Platform. The workspace owner creates the key for the connection, one key and one connection per workspace.
Tip: Ask the workspace owner to create the key rather than sharing an admin login.
-
Inventory GPTs, projects and connectors
List every custom GPT, project, connector, workspace agent and service account with its owner and configuration. Include the connector scopes, such as the SharePoint sites and repositories a project can reach.
-
See who each one is shared with
For each GPT and project, record who it is shared with: individuals, groups or the whole workspace. Flag anything shared workspace-wide and anything that reads a company data source through a connector.
-
Join users to your Microsoft identity
Relate every ChatGPT Enterprise user to their Entra ID account, with department and country. This is how you spot users who hold both a ChatGPT Enterprise seat and a Copilot licence, and seats held by people who have left.
-
Isolate before you delete
Where a GPT or project is shared too widely, remove the sharing and keep it with its owner, then ask whether others still need it. Delete only what nobody claims, and keep a record of each step.
Why ChatGPT Enterprise needs its own governance
Employees build custom GPTs and projects the way they once built Teams and Power Apps: quickly, for a real need and with nothing recording who owns the result. A project connector can wire SharePoint, Slack, Google Drive or Linear into a project. A GPT shared with the whole workspace reaches everyone in it. Each is a small decision, and nobody sees them added up.
The workspace also sits beside Microsoft 365 with a separate user list. Without a join to Entra ID, a seat cannot be read by department or country, and nobody can check it against the Copilot licence the same person holds. OpenAI's own compliance log window is 30 days, which is short for any question about last quarter.
Connectors in this How-to
Each connector page in the Rencore docs lists the objects, policies, reports and actions behind these steps.
Last updated 11 November 2026
