Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 04:45 UTC
How do I set up custom OAuth credentials for SharePoint Graph?
SharePoint Graph has no Composio-managed app, so you need your own Microsoft Entra ID app registration to connect it.
Create the Microsoft Entra app
- Sign in to the Azure portal, open App registrations, and click New registration.
- Enter a Name. Under Supported account types, choose an organizational option: Accounts in this organizational directory only (single tenant) or Accounts in any organizational directory (multitenant). Personal Microsoft accounts can't use these site operations.
- Under Redirect URI, select the Web platform, enter
https://backend.composio.dev/api/v1/auth-apps/add, and click Register. - On the app's Overview page, copy the Application (client) ID.

- Open Certificates & secrets and click New client secret. Add a description, choose an expiry that fits your rotation policy (for example, 180 days), and click Add. Rotate the secret before it expires.

- Copy the secret Value right away. Use the Value, not the Secret ID. Azure shows the full value only once; if you lose it, create a new secret.

- Open API permissions, click Add a permission, select Microsoft Graph, and choose Delegated permissions so the app acts as the signed-in user. Add the delegated permissions that match the scopes you'll select in Composio (see Scopes below), then click Add permissions.





- If your tenant restricts user consent, have a tenant admin click Grant admin consent for your tenant on the API permissions page. Adding a permission to the app registration doesn't grant consent by itself.
The redirect URI you register must exactly match the oauth_redirect_uri field in your Composio auth config (default https://backend.composio.dev/api/v1/auth-apps/add).
Create the auth config in Composio
- In the Composio dashboard, go to Auth Configs, click Create, and select SharePoint Graph. Enter a config name and click Next.



- Select OAuth 2.0 and Your Own Credentials. Paste the Application (client) ID into Client id and the secret value into Client secret. Leave Redirect URI as shown. Keep Microsoft cloud environment (
microsoft_cloud) set toglobalfor commercial Microsoft 365, or setgcc_highfor Microsoft 365 US Government GCC High. The app registration must live in that cloud.


- Under Scopes, select the same permissions you added in Azure, then click Create Auth Config.
- Open the auth config and click Connect Account. Sign in with a work or school account that can access the SharePoint sites you need, review the requested site access, and click Accept. Leave Consent on behalf of your organization unchecked unless you're an admin granting tenant-wide consent. An unverified label is expected for a custom app without a verified publisher.



- Back on the auth config's Connected Accounts tab, confirm the account shows Active. The Enabled label at the top of the page describes the auth config, not the account.

For the general flow, see custom auth configs.
Scopes
The default auth config requests Sites.ReadWrite.All, Sites.Manage.All, Sites.FullControl.All, Files.ReadWrite.All, SensitivityLabels.Read.All, offline_access, and User.Read. These allow edits and deletions. Creating list items needs only Sites.ReadWrite.All, and read-only site access can use Sites.Read.All. See Microsoft's create listItem reference.
Restrict sign-in to one tenant
The connection's tenant field (issuer) defaults to common. To restrict sign-in to one tenant, set it to your Directory (tenant) ID from the app's Overview page or a verified tenant domain.
App-only access (client credentials)
SharePoint Graph also supports an app-only auth mode (S2S_OAUTH2) that runs without a signed-in user. It takes the Client id, the Client secret value, and your Microsoft Entra tenant ID (generic_id) as a GUID, found under Microsoft Entra ID > Overview > Tenant ID. For this mode, add Application permissions instead of delegated permissions on the app registration, and have an admin grant admin consent.