• Documentation
    • Search documentation
    karat

    +

    K

    API Reference ↗
    Data connectivity & integrationAvailable connectorsAzure Active Directory

    Azure Active Directory

    The Azure Active Directory connector is a Palantir-provided driver for Azure Active Directory.

    To create a new Azure Active Directory source, follow the standard setup flow for Palantir-provided drivers, then use the sections below for Azure Active Directory-specific configuration and networking. For the complete property reference, see the official Azure Active Directory driver documentation ↗.

    Configuration

    The properties below are mandatory or recommended.

    PropertyRequired?DescriptionDefault
    DefaultGroups ↗MandatoryDetermines whether to use the /me/memberOf or /groups endpoint for user authentication.AllGroups
    DefaultUser ↗MandatoryDetermines whether to use the /me or /users endpoint for user authentication.AllUsers
    AuthScheme ↗RecommendedSpecifies the type of authentication to use when connecting to Azure Active Directory. If this property is left blank, the default authentication is used.AzureServicePrincipal
    AzureTenant ↗RecommendedIdentifies the Azure Active Directory tenant being used to access data. Accepts either the tenant's domain name (for example, contoso.onmicrosoft.com ) or its directory (tenant) ID.—
    GroupId ↗RecommendedSpecify a default GroupId.—
    InitiateOAuth ↗RecommendedSpecifies the process for obtaining or refreshing the OAuth access token, which maintains user access while an authenticated, authorized user is working.GETANDREFRESH
    OAuthClientId ↗RecommendedSpecifies the client ID (also known as the consumer key) assigned to your custom OAuth application. This ID is required to identify the application to the OAuth authorization server during authentication.—
    OAuthClientSecret ↗RecommendedSpecifies the client secret assigned to your custom OAuth application. This confidential value is used to authenticate the application to the OAuth authorization server. (Custom OAuth applications only.)—
    UserId ↗RecommendedSpecify a default UserId.—

    Networking

    The table below lists the domains that the source needs to be able to access in order to successfully run.

    For each domain, add a corresponding egress policy. If the source is hosted on-premises and not directly reachable from Foundry, use an agent proxy egress policy instead; the agent host itself must also be able to reach the listed domains. See using an agent as a proxy for details.

    DomainRequired
    <Server>:<Port>Always. Server and Port connection properties