Connect a service

A connector scans one service, such as SharePoint, Power BI or ChatGPT Enterprise, into your inventory. To connect one, you turn it on in your Environment and give Rencore Governance access to the service. Most Microsoft 365 connectors only need an administrator’s consent. Others need a dedicated account, an app in your own tenant, or API keys. What each kind of access means is explained in Connectors, modules and Preview.

Before you begin

• The Admin or Owner role in Rencore Governance. Admins manage Environment settings such as connectors and consent.
• A connected tenant. See Set up Rencore Governance.
• An administrator of each service you connect. Connecting a service needs an admin of that service, for example a SharePoint administrator for SharePoint or the primary owner of your Claude organization for Claude Enterprise.
• The module that holds the connector in your Subscription. Apps, Automation & BI and AI & Agents are add-on modules on the Premium and Enterprise Plans. See Add-ons.

Steps

Turn on the connector

1. Go to Settings > Environment Settings > Manage Services.
2. Toggle the selector for the connector.
3. Click Save.

Give access

1. Go to Settings > Environment Settings.
2. On General Settings, click the ellipses menu ([…]) and select Manage consent.
3. On the Scan tab, click Give Consent on the connector.
4. Follow the steps for that connector in the table below: sign in with an administrator account, or enter the app details or keys.
5. When Connection Successful! is shown, click Save and Close, where the dialog offers it.

If you do not have the administrator account yourself, click Ask admin for consent and send the link to your administrator. Built-in actions and automations that change objects can need their own consent, given on the Automations/Actions tab or the first time you use them.

Notes for each connector

Copilot Studio and Azure

Copilot Studio reads its Daily Costs data through the Azure scan. To see Daily Costs, connect Azure as well and give the Azure app the Reader role on the subscription.

Microsoft Foundry

Microsoft Foundry is scanned through the Azure consent, the same one the Azure and Copilot Studio connectors use. It fills the inventory with AI hubs, AI projects, AI services, AI agents, LLM deployments and fine-tuning jobs. It has no policies, automations or actions.

To turn it on, toggle Azure AI Services in Manage Services. That is the name of the Microsoft Foundry connector in the settings.

The Azure app needs these Azure roles:

• Reader on the subscriptions that hold your Foundry resources. With it, Rencore Governance lists AI hubs, AI projects, AI services and LLM deployments.
• A role that can list the keys of your Azure AI services accounts (the action Microsoft.CognitiveServices/accounts/listKeys/action), such as Cognitive Services User. Rencore Governance uses the account keys to read AI agents and fine-tuning jobs. Reader alone does not allow this, so without such a role these two object types are not collected.

Claude Enterprise

Claude Enterprise does not use a Microsoft consent. An owner of your Claude organization turns on the Anthropic APIs and creates the keys in claude.ai, and you enter them on the Scan tab. Each key is optional and covers a different part of the inventory. The full steps are in Anthropic consent.

ChatGPT Enterprise

To turn it on, toggle ChatGPT (Preview) in Manage Services and click Save.

ChatGPT Enterprise does not use a Microsoft consent either. Rencore Governance reads the workspace through the ChatGPT Compliance API, the Codex analytics API and the workspace log streams. It lists conversations as objects, such as who, when, how many messages and which models, and never reads their content. The ChatGPT Enterprise connector page lists every permission it uses.

What you see

After you give access, the next scan of the connector fills the inventory. To check it, click Inventory and look at the connector’s tile, or open Inventory Options ([…]) > All scans. If a consent stops working later, the Environment shows a consent warning. See Re-consent permissions.