Azure Table Storage

The Azure Table Storage connector is a Palantir-provided driver for Azure Table Storage.

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

Configuration

The properties below are mandatory or recommended.

PropertyRequired?DescriptionDefault
AccountMandatoryThe Windows Azure Storage account name.
UseSSLMandatoryThis field sets whether SSL is enabled. The default is true.TRUE
AccessKeyRecommendedThe key for the storage account.
AuthSchemeRecommendedThe scheme used for authentication. Accepted entries are AccessKey, SharedAccessSignature, AzureAD, AzureServicePrincipal, AzureServicePrincipalCert and AzureMSI. The default value is SharedAccessSignature.AccessKey
BackendRecommendedThe backend where data is stored.Storage
InitiateOAuthRecommendedSpecifies the process for obtaining or refreshing the OAuth access token, which maintains user access while an authenticated, authorized user is working.REFRESH
OAuthClientIdRecommendedSpecifies the client Id that was assigned when the custom OAuth application was created. (Also known as the consumer key.) This ID registers the custom application with the OAuth authorization server.
OAuthClientSecretRecommendedSpecifies the client secret that was assigned when the custom OAuth application was created. (Also known as the consumer secret). This secret registers the custom application with the OAuth authorization server.
TablesRecommendedThis property restricts the tables reported to a subset of the available tables. For example, Tables=TableA,TableB,TableC.

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
<Account>.table.core.windows.netIf Backend=Storage (default)
<Account>.table.cosmosdb.azure.comIf Backend=CosmosDB
<Account>If Backend=AzureStack or Emulator, specify the full URL in Account
login.microsoftonline.comIf AuthScheme=AzureAD AND AzureEnvironment=GLOBAL (default)
login.chinacloudapi.cnIf AuthScheme=AzureAD AND AzureEnvironment=CHINA
login.microsoftonline.usIf AuthScheme=AzureAD AND AzureEnvironment=USGOVT or USGOVTDOD