# OAuth provider management > OAuth provider management - How to add and manage OAuth providers. This Markdown file sits beside the HTML page at the same path (with a `.md` suffix). It summarizes the topic and lists links for tools and LLM context. Companion generated at `2026-04-24T16:03:56.640568+00:00` (UTC). ## Primary page - [OAuth provider management](https://docs.datarobot.com/en/docs/platform/acct-settings/manage-oauth.html): Full documentation for this topic (HTML). ## Sections on this page - [Configure an OAuth provider](https://docs.datarobot.com/en/docs/platform/acct-settings/manage-oauth.html#configure-oauth-provider): In-page section heading. - [Add a provider](https://docs.datarobot.com/en/docs/platform/acct-settings/manage-oauth.html#add-a-provider): In-page section heading. - [Verify a provider](https://docs.datarobot.com/en/docs/platform/acct-settings/manage-oauth.html#verify-a-provider): In-page section heading. - [Modify a provider](https://docs.datarobot.com/en/docs/platform/acct-settings/manage-oauth.html#modify-a-provider): In-page section heading. - [Remove a provider](https://docs.datarobot.com/en/docs/platform/acct-settings/manage-oauth.html#remove-a-provider): In-page section heading. - [Organization-wide consent for Microsoft OAuth](https://docs.datarobot.com/en/docs/platform/acct-settings/manage-oauth.html#organization-wide-consent-for-microsoft-oauth): In-page section heading. ## Related documentation - [Account management](https://docs.datarobot.com/en/docs/platform/index.html): Linked from this page. - [Account settings](https://docs.datarobot.com/en/docs/platform/acct-settings/index.html): Linked from this page. ## Documentation content # OAuth provider management The OAuth providers tile allows you to configure, add, remove, or modify OAuth providers for your cluster. ## Configure an OAuth provider DataRobot supports integration with several external OAuth providers. Refer to the links below for configuration options. | Provider | Client setup instructions | Callback URI | | --- | --- | --- | | GitHub | Creating an OAuth app | DATAROBOT_BASE_URL/account/oauth-providers/?providerId=PROVIDER_ID | | GitLab | Configure GitLab as an OAuth 2.0 provider | DATAROBOT_BASE_URL/account/oauth-providers/?providerId=PROVIDER_ID | | Bitbucket | Use OAuth on Bitbucket Cloud | DATAROBOT_BASE_URL/account/oauth-providers/?providerId=PROVIDER_ID | | Google | Setting up OAuth 2.0 | DATAROBOT_BASE_URL/account/oauth-providers/?providerId=PROVIDER_ID | | Box | Setup with OAuth 2.0 | DATAROBOT_BASE_URL/account/oauth-providers/?providerId=PROVIDER_ID | | Microsoft | Register an application in Microsoft Entra ID | DATAROBOT_BASE_URL/account/oauth-providers/?providerId=PROVIDER_ID | | Confluence | OAuth 2.0 (3LO) apps | DATAROBOT_BASE_URL/account/oauth-providers/?providerId=PROVIDER_ID | | Jira | OAuth 2.0 (3LO) apps | DATAROBOT_BASE_URL/account/oauth-providers/?providerId=PROVIDER_ID | | SharePoint | OAuth 2.0 and OIDC authentication flow in the Microsoft identity platform | DATAROBOT_BASE_URL/account/oauth-providers/?providerId=PROVIDER_ID | > [!NOTE] Note > In the Callback URI field, substitude the URL of your deployment in place of `DATAROBOT_BASE_URL` (e.g., `app.DataRobot.com`). The Callback URI field is configured in the external OAuth provider's settings outside of DataRobot. For Google or Box configurations, the value for `PROVIDER_ID` must be updated in the URI field after creating the OAuth provider in DataRobot. Once added, the value is the one shown in the Provider id column for the provider in the DataRobot UI. ## Add a provider To add a new OAuth provider: 1. In the top-right corner, go toUser Settings > OAuth provider management. 2. ClickAdd OAuth provider. 3. Fill in the fields. Note that all fields are required: FieldDescriptionProvider typeSpecify the provider.Provider NameSpecify a name for the provider being added.Client IDEnter theClient IDfrom the provider you want to add.Client SecretEnter theClient Secretfrom the provider you want to add. 4. To add the new provider, clickAdd. > [!NOTE] Note > Only the user who added the provider will be able to access it for modifying or removal. ## Verify a provider Before an OAuth provider can be used in the cluster, it must be authorized for the user accessing the server. To verify an OAuth provider: 1. Open theActions menuon the right-hand side of theOAuth provider managementtable in the row containing your provider and selectAuthorize on NAME(NAME will vary based on the provider of the service). 2. Click through the subsequent steps required by the service to authorize your provider. The example below demonstrates the flow for GitHub, but other providers will differ. 3. After verification, the provider row displays anauthorizedbadge below its name. ## Modify a provider To edit a configured provider: 1. Open theActions menuon the right-hand side of theOAuth provider managementtable in the row containing your provider and selectEdit OAuth provider. 2. Edit the necessary fields and clickUpdateto finish. ## Remove a provider To remove a provider: 1. Open theActions menuon the right-hand side of theOAuth provider managementtable in the row containing your provider and selectRevoke authorization. 2. ClickRevoketo proceed. The provider now displays a Not authorized icon below it. > [!NOTE] Note > The default providers cannot be removed. ## Organization-wide consent for Microsoft OAuth This feature allows administrators to grant [tenant-wide consent](https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/configure-user-consent?pivots=portal#configure-user-consent-in-microsoft-entra-admin-center) for user permissions required by the DataRobot application in Microsoft Entra ID. In Azure, by default, user permissions are not granted to individual user resources, requiring personal user consent when authorizing a [Microsoft OAuth provider](https://learn.microsoft.com/en-us/entra/architecture/auth-oauth2). When enabled, users also no longer receive consent prompts. If the list of required permissions is changed by the DataRobot application, or the administrator account who granted consent is not active anymore, the administrator must grant consent again to provide the necessary permissions for the DataRobot application. > [!NOTE] Prerequisite > Before enabling this feature in DataRobot, in Microsoft Entra ID, a Cloud Application Administrator must [grant tenant-wide consent to the DataRobot application](https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/grant-admin-consent?pivots=portal). > > Managed AI Cloud (SaaS) administrators must contact DataRobot Support to enable this feature. To enable this feature in DataRobot: **Self-managed:** A system adminstrator must perform the following steps: Click the System admin icon in the management toolbar and select Organizations . On the Profile tab, scroll down to Grant organization-wide consent for global Microsoft OAuth providers . Select the checkbox to enable global authorization for all users in the organization. The resulting window describes next steps. After closing the window, click Save . Then, an organization administrator must perform the following steps: Open User settings > OAuth provider management . Click the Actions menu next to the OAuth provider you want to authorize and select Grant user consent on behalf of organization . A window appears describing action that must be taken in Azure Entra ID. Click Grant consent and then in Azure, an application administrator must enable consent on behalf of your organization for the DataRobot application. **SaaS:** > [!NOTE] Note > Before proceeding, contact DataRobot Support to enable this feature. An organization administrator must perform the following steps: Open User settings > OAuth provider management . Click the Actions menu next to the OAuth provider you want to authorize and select Grant consent on behalf of your organization . A window appears describing action that must be taken in Azure Entra ID. Click Grant consent and then in Azure, an application administrator must enable consent on behalf of your organization for the DataRobot application.