Microsoft Azure DataLakeStoreAccountManagementClient

What authentication does the Data Lake Store Account API use?

The API is part of Azure Resource Manager and uses OAuth 2.0 bearer tokens issued by Azure Active Directory. Through Jentic, the AAD client secret or managed identity refresh token is held in the encrypted vault and a short-lived access token is supplied at execute time so the bearer token never enters the agent's context.

Can I provision a Data Lake Store account with this API?

Yes. PUT /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataLakeStore/accounts/{accountName} creates or updates an account. The call returns immediately with a long-running operation; poll the resource until provisioningState reaches Succeeded before treating the account as ready.

What are the rate limits for the Data Lake Store Account API?

Azure Resource Manager applies subscription-level read and write throttles (commonly 12,000 reads per hour and 1,200 writes per hour per region per subscription) and returns 429 with a Retry-After header when exceeded. Batch list calls and avoid tight provisioning loops to stay within the writes budget.

How do I add a firewall rule to a Data Lake Store account through Jentic?

Search Jentic for 'add firewall rule data lake store', load the schema for the firewall rules CreateOrUpdate operation under Microsoft.DataLakeStore/accounts/{accountName}/firewallRules/{firewallRuleName}, then execute with the start and end IP range. The pip install jentic Python SDK uses the async search, load, execute pattern.

Is the Data Lake Store Account API free?

There is no per-call charge for the management API itself; you pay only for the Data Lake Store Gen1 storage and transactions on accounts that you create. Note that Data Lake Store Gen1 has been retired in favour of Gen2 - new workloads should target ADLS Gen2.

Can I limit what my agent is allowed to do with the Microsoft Azure Data Lake Store API?

Yes. Jentic One runs self-hosted, so your own rules decide which Data Lake Store operations the agent may call and which Azure credential it uses. Because the account name sits in the URL path, you can pin the agent to a single account and its firewall and virtual-network rules, granting only what it needs such as FirewallRules_CreateOrUpdate. A destructive operation like Accounts_Delete stays out of reach unless you explicitly add it.