@devries-cameron20 / composio Mirror · read-only
Fork 0

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

next
md 6.33 KB

How do I set up custom OAuth credentials for Microsoft Entra ID?

Microsoft Entra ID has no Composio-managed app, so you need your own app registration to connect it.

Create the Microsoft Entra app

  1. Sign in to the Azure portal, open App registrations, and click New registration.
  2. 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).
  3. Under Redirect URI, select the Web platform, enter https://backend.composio.dev/api/v1/auth-apps/add, and click Register.
  4. On the app's Overview page, copy the Application (client) ID.

Entra app Overview page with the client, object and tenant IDs censored

  1. 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.

Add a client secret panel with a description and the 180-day expiry

  1. 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.

Client secrets list with the Value and Secret ID columns censored

  1. Open API permissions, click Add a permission, select Microsoft Graph, and choose Delegated permissions so the app acts as the signed-in user. Add User.Read and offline_access, plus the directory permissions your workflow needs, then click Add permissions.

API permissions page with the Add a permission button

Request API permissions panel with Microsoft Graph under Microsoft APIs

Microsoft Graph permission type choice with Delegated permissions

Configured Microsoft Graph permissions with the User.Read delegated permission details

  1. 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

  1. In the Composio dashboard, go to Auth Configs, click Create, and select Microsoft Entra ID. Enter a config name and click Next.

Composio Auth Configs page with the Create button

Create Auth Config dialog with Microsoft Entra ID selected

Auth config name field with the Next button

  1. 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 to global for commercial Microsoft 365, or set gcc_high for Microsoft 365 US Government GCC High. The app registration must live in that cloud.

Composio auth config form with OAuth 2.0 selected and empty Client id and Client secret fields

Composio auth config with the v1 redirect URI, Microsoft cloud environment set to global, and the User.Read and offline_access scopes

  1. Under Scopes, select the same permissions you added in Azure, then click Create Auth Config.
  2. Open the auth config and click Connect Account. Sign in to the tenant that holds the directory you want to use and review the consent prompt. Directory administration also needs the matching Entra roles on the signed-in account. 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.

Microsoft Entra ID auth config panel with the Connect Account button

Microsoft Pick an account page with the accounts censored

Composio page confirming the Microsoft Entra ID connection

  1. 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.

Connected Accounts tab with the Microsoft Entra ID account showing Active

For the general flow, see custom auth configs.

Scopes

The default auth config requests User.Read and offline_access. Directory operations need operation-specific Graph permissions and roles. See Microsoft's get user 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)

Microsoft Entra ID 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 (issuer) 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. In this mode the tenant field also accepts a verified tenant domain.