Microsoft Azure DataLakeStoreAccountManagementClient
Browse all Azure APIs★ Only Publicly Available OpenAPI DocumentStorageObject Storageoauth226 EndpointsREST
For Agents
Provision, configure, and delete Azure Data Lake Store Gen1 accounts and manage their firewall rules, virtual network rules, and trusted identity providers.
Use for: Provision a new Azure Data Lake Store account in a resource group, Delete a Data Lake Store account that is no longer needed, List all Data Lake Store accounts in a subscription, Add a firewall rule to a Data Lake Store account
Not supported: Does not read or write files in the lake, manage U-SQL jobs, or handle billing — use for Data Lake Store Gen1 account lifecycle and network configuration only.
Jentic publishes the only available OpenAPI specification for DataLakeStoreAccountManagementClient, keeping it validated and agent-ready. The API manages the lifecycle of Azure Data Lake Store accounts under the Microsoft.DataLakeStore resource provider, covering account creation and deletion, firewall and virtual-network rule configuration, trusted identity providers, and per-region capability or usage queries. It is the control-plane surface for Data Lake Store Gen1 — file-level reads and writes live in a separate filesystem API.
Install Jentic One Beta
Connect the DataLakeStoreAccountManagementClient to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DataLakeStoreAccountManagementClient, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with DataLakeStoreAccountManagementClient API.
Provision and delete Data Lake Store accounts in a resource group
Configure firewall rules and virtual network rules on a Data Lake Store account
Register and manage trusted identity providers for an account
Check Data Lake Store account name availability per region
Retrieve regional capability and usage information for Data Lake Store
Update encryption configuration and account-level settings
Use Cases
Patterns agents use DataLakeStoreAccountManagementClient API for, with concrete tasks.
★ Automated Data Lake Store provisioning
Platform teams provision Data Lake Store Gen1 accounts as part of an analytics environment template. The management API lets an automation flow create the account, configure firewall and virtual network rules, register trusted identity providers, and verify the account is ready before downstream U-SQL jobs are scheduled.
Create a Data Lake Store account named 'analytics-dev01' in resource group 'analytics-rg' in East US 2 with default encryption and a single firewall rule allowing the corporate egress range
Network access lockdown
Security teams routinely tighten access to Data Lake Store by restricting which IP ranges and virtual networks can reach an account. The firewall and vnet rule endpoints support adding, listing, and removing rules on an existing account so a controller can converge configuration to a desired state.
Replace the firewall rule list on Data Lake Store account 'analytics-dev01' with the approved CIDR ranges from the security catalogue and remove any rule not in the approved list
Account name availability check
Before a self-service portal lets an analyst pick a name for a new Data Lake Store account, the portal calls the name-availability endpoint. This avoids a failed provisioning attempt and gives the user immediate feedback on whether the chosen name is taken in the target region.
Check whether the Data Lake Store account name 'salesanalytics2026' is available in West Europe and return the conflict reason if it is not
Agent-driven environment provisioning
An AI agent owning an analytics workspace template uses Jentic to assemble Data Lake Store account creation alongside related steps. The agent searches for the create operation, supplies the resource group and configuration, then waits for the long-running provisioning to complete before signalling readiness to the rest of the workflow.
Provision a Data Lake Store account 'agent-test01' with the encryption-at-rest default and confirm the long-running operation reaches Succeeded provisioning state
Key Endpoints
26 endpoints — jentic publishes the only available openapi specification for datalakestoreaccountmanagementclient, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/subscriptions/{subscriptionId}/providers/Microsoft.DataLakeStore/accounts
List Data Lake Store accounts in a subscription
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataLakeStore/accounts/{accountName}
Create or update a Data Lake Store account
DELETE
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataLakeStore/accounts/{accountName}
Delete a Data Lake Store account
POST
/subscriptions/{subscriptionId}/providers/Microsoft.DataLakeStore/locations/{location}/checkNameAvailability
Check Data Lake Store account name availability
GET
/subscriptions/{subscriptionId}/providers/Microsoft.DataLakeStore/locations/{location}/usages
Get Data Lake Store usage in a region
GET
/subscriptions/{subscriptionId}/providers/Microsoft.DataLakeStore/operations
List Microsoft.DataLakeStore provider operations
GET
/subscriptions/{subscriptionId}/providers/Microsoft.DataLakeStore/accounts
List Data Lake Store accounts in a subscription
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataLakeStore/accounts/{accountName}
Create or update a Data Lake Store account
DELETE
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataLakeStore/accounts/{accountName}
Delete a Data Lake Store account
POST
/subscriptions/{subscriptionId}/providers/Microsoft.DataLakeStore/locations/{location}/checkNameAvailability
Check Data Lake Store account name availability
GET
/subscriptions/{subscriptionId}/providers/Microsoft.DataLakeStore/locations/{location}/usages
Get Data Lake Store usage in a region
GET
/subscriptions/{subscriptionId}/providers/Microsoft.DataLakeStore/operations
List Microsoft.DataLakeStore provider operations
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Azure AD OAuth 2.0 client credentials are stored encrypted in the Jentic vault. Agents receive a scoped bearer token at execute time; client secrets and refresh tokens never reach the agent's context.
Intent-based discovery
Agents search by intent (e.g., 'provision azure data lake store account') and Jentic returns the matching create or update operation with its required resource-group and account-name parameters resolved from the spec.
Time to first call
Direct integration with Azure Resource Manager for Data Lake Store, including AAD app registration and long-running operation polling, typically takes 1-2 days. Through Jentic: under 1 hour to first successful call.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using DataLakeStoreAccountManagementClient API through Jentic.
Why is there no official OpenAPI spec for DataLakeStoreAccountManagementClient?
Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call DataLakeStoreAccountManagementClient via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
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.
GET STARTED