Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Storage / Azure / DataLakeStoreAccountManagementClient
DataLakeStoreAccountManagementClient logo

Microsoft Azure DataLakeStoreAccountManagementClient

Browse all Azure APIs
42
AI ReadinessFoundational (D-)42/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticStorageObject Storageoauth226 EndpointsREST

Know of an official OpenAPI document? Contribute it →

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.

Jentic One on GithubView OpenAPI Document

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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fdatalakestoreaccountmanagementclient" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fdatalakestoreaccountmanagementclient" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

D

DataLakeStoreAccountManagementClient

- Foundational (D-)
42/100
69
Foundational Compliance
56
Developer Experience & Jentic Compatibility
21
AI-Readiness & Agent Experience
94
Agent Usability
35
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
69

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: B+Signals: 4
77%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

56

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: CSignals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

26%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

21

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
83%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

0%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

0%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

35

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1
35%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Azure Data Lake Store account management by hand means registering an Azure AD app, handling OAuth 2.0 bearer tokens against management.azure.com, and polling long-running ARM operations for account create and delete yourself. Through Jentic you install once, import Data Lake Store Account Management from the API Directory, store the Azure service principal credential once, and your agent calls it.

Permission scoping

Data Lake Store puts the account name in the URL path (/subscriptions/{id}/resourceGroups/{rg}/providers/Microsoft.DataLakeStore/accounts/{accountName}/...), so a rule can pin your agent to one account and its firewall and virtual-network rules. You choose the operations it may call, so a destructive one like Accounts_Delete is not included unless you add it alongside operations such as FirewallRules_CreateOrUpdate that it actually needs.

Credential isolation

Your Azure service principal credential is stored once, encrypted, by your own Jentic One instance and injected as a scoped ARM bearer token at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'provision an Azure Data Lake Store account' or 'add a firewall rule to Data Lake Store', and Jentic returns the matching operation with its input schema so the agent supplies the resource group and IP range without reading the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

DataLakeStoreFileSystemManagementClient

→

File-level operations on the data inside a Data Lake Store account

Pick this when the agent needs to read or write files in the lake rather than provision the account.

Complementary

DataLakeAnalyticsCatalogManagementClient

→

Manages the U-SQL catalog of an analytics account that consumes Data Lake Store data

Pick this when the agent needs to inspect U-SQL catalog metadata layered on top of Data Lake Store.

Alternative

DataShareManagementClient

→

Shares datasets across Azure tenants without provisioning a Data Lake Store account

Pick this when the agent's goal is dataset sharing rather than provisioning storage.

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 with Jentic One, the self-hosted execution layer.

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.

GET STARTED

Start building with DataLakeStoreAccountManagementClient API

Explore with Jentic One
View OpenAPI Document