home

Advantage Platform Administration

Adobe Sign ServicesAdvantage Platform AdministrationApprovals for Advantage PlatformApprovals for SalesforceBilling for Advantage PlatformBilling for SalesforceCLM for Advantage PlatformCLM for SalesforceContracts for SalesforceCollaborateComposer for Advantage PlatformComposer for SalesforceContractsConga for Google DocsConga Upgrade ProgramContract Intelligence (Standalone)Conga CopilotCPQ for Advantage PlatformCPQ for SalesforceDeal MaximizerDigital Commerce for Advantage PlatformDigital Commerce for SalesforceDiscovery AI for Advantage PlatformDiscovery AI for SalesforceDocusign ServiceseSignature Integration with Advantage PlatformGridInvoice GenerationMix FormsOrchestrateOrder Management for Advantage PlatformOrder Management for SalesforcePartner Commerce for Advantage PlatformPartner Commerce for SalesforceQuote GenerationSign for Advantage PlatformSign for SalesforceSmart SearchTest AuthorTurboEnginesX-Author for Contracts 1.0 (Classic)X-Author for ContractsX-Author for Contracts Advanced for Advantage PlatformX-Author for Contracts Advanced for SalesforceX-Author for ExcelX-Author for Migration Manager for Advantage PlatformX-Author for Migration ManagerRelease NotesGeneral
Adobe Sign ServicesAdvantage Platform AdministrationApprovals for Advantage PlatformApprovals for SalesforceBilling for Advantage PlatformBilling for SalesforceCLM for Advantage PlatformCLM for SalesforceContracts for SalesforceCollaborateComposer for Advantage PlatformComposer for SalesforceContractsConga for Google DocsConga Upgrade ProgramContract Intelligence (Standalone)Conga CopilotCPQ for Advantage PlatformCPQ for SalesforceDeal MaximizerDigital Commerce for Advantage PlatformDigital Commerce for SalesforceDiscovery AI for Advantage PlatformDiscovery AI for SalesforceDocusign ServiceseSignature Integration with Advantage PlatformGridInvoice GenerationMix FormsOrchestrateOrder Management for Advantage PlatformOrder Management for SalesforcePartner Commerce for Advantage PlatformPartner Commerce for SalesforceQuote GenerationSign for Advantage PlatformSign for SalesforceSmart SearchTest AuthorTurboEnginesX-Author for Contracts 1.0 (Classic)X-Author for ContractsX-Author for Contracts Advanced for Advantage PlatformX-Author for Contracts Advanced for SalesforceX-Author for ExcelX-Author for Migration Manager for Advantage PlatformX-Author for Migration ManagerRelease NotesGeneral

Conga Product Documentation

Welcome to the new doc site. Some of your old bookmarks will no longer work. Please use the search bar to find your desired topic.

Show Contents

Show Page Sections

Advantage Platform Administration

SAML 2.0 Identity Provider as an External Integration

Microsoft Entra (Azure AD) as a SAML Identity Provider

To configure Microsoft Entra ID (formerly Azure Active Directory) as a SAML 2.0 external integration, you must register a new application within the Microsoft Entra portal. This registration establishes trust between Microsoft Entra and the Conga Revenue Lifecycle Platform, enabling secure single sign-on (SSO) through SAML.

During the setup process, Microsoft Entra acts as the Identity Provider (IdP), while Conga Advantage Platform functions as the Service Provider (SP). The Conga Advantage Platform also supports IdP-initiated flow.

Once the application is created, you must collect such key configuration values as the Tenant ID, Metadata URL, and the claim type used to represent the user's organization ID to complete integration to the Conga platform.

This setup allows users to authenticate through Microsoft Entra using their enterprise credentials, ensuring secure and centralized identity management for access to Conga services.

Step 1: Register an app in Microsoft Entra (Azure AD)

  1. Log in to portal.azure.com.
  2. Select Microsoft Entra ID and go to Enterprise Applications.
  3. Click New Application, then click the Create your own application option.
  4. Enter the app name.
  5. Select the Integrate any other application you don't find in the gallery (Non-gallery) option.
  6. Click Create.
  7. Select the registered app.
  8. Go to Single Sign-on and select SAML.
  9. Click Upload metadata file and select the service provider metadata file. You can download the service provider metadata file either using the following URL or from the Add New External Integration screen > Download SP Metadata File button (refer to Step 3):

    • NA: https://login.congacloud.com/api/v1/auth/Saml2

      EU: https://login.congacloud.eu/api/v1/auth/Saml2

      AU: https://login.congacloud.au/api/v1/auth/Saml2

  10. After uploading the metadata file, you can see the Basic SAML Configuration screen, where all metadata settings get auto-filled.
  11. Click Save.
  12. Click Done.

Step 2: Get the Tenant ID, Metadata Location URL, and Organization ID Claim Type details

  1. Go to Enterprise Applications and select the registered app.
  2. Go to Single Sign-on and select SAML 2.0.
  3. Metadata Location URL: Under the SAML Certificate option, copy the App Federation Metadata Url which is the metadata location URL.
  4. Open the App Federation Metadata Url in any of the web browsers.
    • External ID: Get the value of the entityId attribute from the root node of the XML. Copy the last ID (tenant ID) value which is the external organization ID.

      For example, if the entityId value is https://sts.windows.net/8831e6d9-dc6c-4cd1-9cc6-1dc2d4133195/, the tenant ID is 8831e6d9-dc6c-4cd1-9cc6-1dc2d4133195.

    • Organization ID Claim Type: Search for the tenantid claim; if it is available, use the URI attribute in the XML tag as the organization ID claim type. For example, http://schemas.microsoft.com/identity/claims/tenantid.
      Note:

      If you don't see the TenantId, leave the Organization ID Claim Type field blank.

Step 3: Add Microsoft Entra (Azure AD) as an external integration

  1. Log in to the Conga Advantage Platform as an admin user.
  2. Click the App Launcher () icon from the top-left corner; then Admin Console > Organization.
  3. Go to the External Integrations tab.
  4. Click Add New and choose the SAML 2.0 from the list.
    The Add New External Integration screen appears.
  5. Enter values in the following fields as per your SAML 2.0 external integration:

    Field

    Description

    Download SP Metadata File

    Click this button to download the SP metadata file that can be used in Step 1.

    Choose IDP Metadata Setup

    You can either enter the metadata location URL or upload the XML file.

    • URL Input: Select this option and enter the App Federation Metadata Url that you copied in Step 2.
    • XML File Upload: Select this option and upload your metadata XML file.

    External Organization ID

    Enter the external organization ID that you copied in Step 2.

    Type

    Enter the type of this integration. It is a free-form text field. You can add types such as Dev, QA, UAT, Prod, etc.

    Organization ID Claim Type

    Enter the organization ID claim type that you copied in Step 2.

    Description

    Add the description.

    Email Domain

    Enter the email domain you want to associate with designated IdP. It can be added for administrative purposes.

    Display Name

    Enter the display name for the identity provider.

    Default IDP

    Enable the toggle to make it a Default External Integration IDP.

    A user will be created for the external integration set as the Default IdP for the organization. For example, if you have set Microsoft Entra (Azure AD), a SAML Identity Provider, as the Default IdP, all the new users will be created with Microsoft Entra (Azure AD).

  6. Click Save.

Review the step 4 if you want to configure the Single Sign-On (IdP-initiated flow).

You can edit the external integration. Perform the following steps to edit the existing external integration:

  1. Click the More () icon and select Edit.

  2. Update the Choose IDP Metadata Setup, External Organization ID, Type, Organization ID Claim Type, Description, Email Domain, Display Name, and Default IDP fields per your business needs.

    Note: You should change the External Organization ID if the Single Sign-On (SSO) external ID changes.

Step 4: Configure Single Sign-On (IdP-initiated flow)

  1. Go to Enterprise Applications.
  2. Select the registered app and navigate to Single Sign-on.
  3. Go to the Attributes and Claims section and add the following attribute as per your environment:

    Attribute

    Details

    redirect_uri
    Enter the Conga Advantage Platform App Url where the user should be redirected after authentication. Use the following URL per your environment:
    • Preview Environment:

      NA: https://rls-preview.congacloud.com

      EU: https://rls-preview.congacloud.eu

      AU: https://rls-preview.congacloud.au

    • Production Environment:

      NA: https://rls.congacloud.com

      EU: https://rls.congacloud.eu

      AU: https://rls.congacloud.au

    client_id

    The SPA Client ID for logging in. Use the following client ID per your environment:

    • Preview Environment:

      NA: rls-preview-spa

      EU: rls-previeweu-spa

      AU: rls-previewau-spa

    • Production Environment:

      NA: rls-prod-spa

      EU: rls-prodeu-spa

      AU: rls-prodau-spa

  4. Click Save.
Administrator Guide
Conga Advantage Platform Administration

September 8, 2025