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 / Analytics / Azure / DataLakeAnalyticsAccountManagementClient
DataLakeAnalyticsAccountManagementClient logo

Microsoft Azure DataLakeAnalyticsAccountManagementClient

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

Know of an official OpenAPI document? Contribute it →

For Agents

Provision and manage Azure Data Lake Analytics accounts and their Data Lake Store sources, Storage account links, firewall rules, and compute policies through 31 ARM operations on the Microsoft.DataLakeAnalytics namespace.

Use for: I need to provision a new Data Lake Analytics account in North Europe, List all Data Lake Analytics accounts in a subscription, I want to attach an additional Data Lake Store to an existing Analytics account, Find all compute policies on a given Analytics account

Not supported: Does not submit U-SQL jobs, query catalog metadata, or run analytics workloads - use for Data Lake Analytics account, source-attachment, and compute-policy management only.

Jentic publishes the only available OpenAPI specification for DataLakeAnalyticsAccountManagementClient, keeping it validated and agent-ready. The Azure Data Lake Analytics management API exposes 31 operations across 17 paths to provision and configure Data Lake Analytics accounts, attach Data Lake Store and Azure Storage data sources, define compute policies that govern user job concurrency and parallelism, and check name availability and capability quotas in a region. Use it to stand up Data Lake Analytics accounts for U-SQL workloads, control how analysts share cluster capacity, and inventory accounts at the subscription level.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the DataLakeAnalyticsAccountManagementClient to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DataLakeAnalyticsAccountManagementClient, 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%2Fazure-data-lake-analytics-account-management" | 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%2Fazure-data-lake-analytics-account-management" | 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 DataLakeAnalyticsAccountManagementClient API.

Create, list, update, and delete Data Lake Analytics accounts in any subscription

Attach and detach Data Lake Store and Azure Storage account data sources to an Analytics account

Define compute policies that limit per-user maxDegreeOfParallelism and maxJobCount

Check Data Lake Analytics account name availability before creation

Query region capability and quota information for Data Lake Analytics

Manage firewall rules controlling which IPs can submit jobs to an account

Use Cases

Patterns agents use DataLakeAnalyticsAccountManagementClient API for, with concrete tasks.

★ Provision Data Lake Analytics Accounts

Create Data Lake Analytics accounts to run U-SQL jobs over data stored in Data Lake Store. Accounts_CreateOrUpdate accepts the default Data Lake Store, additional Data Lake Stores and Storage accounts, firewall rules, and tier configuration. Provisioning typically completes in a few minutes; once created the account exposes a job submission endpoint that the data-plane SDK uses to run U-SQL.

Create a Data Lake Analytics account named 'analytics-prod' in resource group 'rg-data' with default Data Lake Store 'dls-prod' and northeurope as location

Multi-Tenant Compute Policies

Define compute policies on a Data Lake Analytics account so each user or service principal has a capped maxDegreeOfParallelism and maxJobCount. ComputePolicies_CreateOrUpdate accepts an objectId, objectType (User, Group, ServicePrincipal), and the two limits. This prevents a single team from saturating the account during peak load and gives platform teams predictable cost profiles.

Create a compute policy 'team-marketing' on account 'analytics-prod' for objectId {guid} with maxDegreeOfParallelismPerJob=20 and minPriorityPerJob=100

Source Account Attachments

Attach additional Data Lake Stores and Azure Storage accounts to a Data Lake Analytics account so U-SQL jobs can read across multiple stores without copying data first. The DataLakeStoreAccounts and StorageAccounts endpoints support attach, list, get, and detach. Storage attachments require a key reference at the time of attach. Useful for federated analytics across business units.

Attach Storage account 'logs-archive' to Data Lake Analytics account 'analytics-prod' using the supplied access key

Account Inventory and Decommissioning

List Data Lake Analytics accounts at subscription or resource group level to inventory accounts and feed governance reports. Combine with Accounts_Delete and Accounts_CheckNameAvailability for tear-down and stand-up workflows. The Locations_GetCapability call reports per-region quotas so the agent can plan provisioning across regions.

List all Data Lake Analytics accounts in subscription /subscriptions/{id} and report each account's state and default Data Lake Store

AI Agent Analytics Provisioning

An AI agent supporting a data engineering team can manage Data Lake Analytics accounts through Jentic. The agent searches by intent ('create data lake analytics compute policy'), Jentic returns the ComputePolicies_CreateOrUpdate operation with its schema, and the agent executes the call with managed Azure credentials. The same flow handles account lifecycle, source attachment, and firewall management.

Search Jentic for 'create data lake analytics compute policy', load the ComputePolicies_CreateOrUpdate schema, and execute it with the user-supplied objectId, objectType, and parallelism limits

Key Endpoints

31 endpoints — jentic publishes the only available openapi specification for datalakeanalyticsaccountmanagementclient, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/subscriptions/{subscriptionId}/providers/Microsoft.DataLakeAnalytics/accounts

List all Data Lake Analytics accounts in a subscription

POST

/subscriptions/{subscriptionId}/providers/Microsoft.DataLakeAnalytics/locations/{location}/checkNameAvailability

Check whether a Data Lake Analytics account name is available

GET

/subscriptions/{subscriptionId}/providers/Microsoft.DataLakeAnalytics/locations/{location}/capability

Get region capability information

DELETE

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataLakeAnalytics/accounts/{accountName}

Delete a Data Lake Analytics account

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataLakeAnalytics/accounts/{accountName}/computePolicies

List compute policies on a Data Lake Analytics account

GET

/providers/Microsoft.DataLakeAnalytics/operations

List Microsoft.DataLakeAnalytics operations

GET

/subscriptions/{subscriptionId}/providers/Microsoft.DataLakeAnalytics/accounts

List all Data Lake Analytics accounts in a subscription

POST

/subscriptions/{subscriptionId}/providers/Microsoft.DataLakeAnalytics/locations/{location}/checkNameAvailability

Check whether a Data Lake Analytics account name is available

GET

/subscriptions/{subscriptionId}/providers/Microsoft.DataLakeAnalytics/locations/{location}/capability

Get region capability information

DELETE

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataLakeAnalytics/accounts/{accountName}

Delete a Data Lake Analytics account

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataLakeAnalytics/accounts/{accountName}/computePolicies

List compute policies on a Data Lake Analytics account

GET

/providers/Microsoft.DataLakeAnalytics/operations

List Microsoft.DataLakeAnalytics 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

DataLakeAnalyticsAccountManagementClient

- Foundational (D-)
42/100
69
Foundational Compliance
56
Developer Experience & Jentic Compatibility
20
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
76%

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.

20

AI-Readiness & Agent Experience

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

Grade: FSignals: 4
81%

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 Analytics account management by hand means registering an Azure AD app, handling MSAL bearer tokens against management.azure.com with the user_impersonation scope, and polling the Azure-AsyncOperation header for account provisioning yourself. Through Jentic you install once, import Data Lake Analytics Account Management from the API Directory, store the Azure service principal credential once, and your agent calls it.

Permission scoping

Data Lake Analytics puts the account name in the URL path (/subscriptions/{id}/resourceGroups/{rg}/providers/Microsoft.DataLakeAnalytics/accounts/{accountName}/...), so a rule can pin your agent to one account and its compute policies and source attachments. You choose the operations it may call, so destructive ones like Accounts_Delete or DataLakeStoreAccounts_Delete are not included unless you add them.

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; storage keys passed at attach stay server-side and the credential never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a Data Lake Analytics compute policy' or 'list Data Lake Analytics accounts', and Jentic returns the matching operation with its input schema so the agent sets the parallelism limits without learning the 31 paths under Microsoft.DataLakeAnalytics.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Data Lake Analytics Catalog Management

→

Manage U-SQL catalog objects (databases, tables, credentials) within a Data Lake Analytics account.

Use Catalog Management for U-SQL metadata; use Account Management for account lifecycle and policies.

Complementary

Data Lake Store Account Management

→

Provision the Data Lake Store accounts that Data Lake Analytics queries.

Use to set up the underlying Data Lake Store before attaching it as the default source on an Analytics account.

Alternative

Databricks Management

→

Spark- and Delta-Lake-based analytics workspaces instead of U-SQL on Data Lake Analytics.

Choose Databricks for modern Spark-based analytics; choose Data Lake Analytics when teams already invest in U-SQL pipelines.

FAQs

Specific to using DataLakeAnalyticsAccountManagementClient API through Jentic.

Why is there no official OpenAPI spec for DataLakeAnalyticsAccountManagementClient?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call DataLakeAnalyticsAccountManagementClient 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 Analytics management API use?

It uses Azure Active Directory OAuth 2.0 against https://management.azure.com/ with the user_impersonation scope. The caller needs Contributor or a custom role with Microsoft.DataLakeAnalytics/* permissions on the resource group. Jentic stores service principal credentials encrypted and issues short-lived bearer tokens at execution time.

Can I attach a Storage account at account-creation time?

Yes. The Accounts_CreateOrUpdate body accepts a storageAccounts array where each entry includes the storage account name and access key. You can also attach later via StorageAccounts_Add.

What are the rate limits for the Data Lake Analytics management API?

Azure Resource Manager applies subscription-level read and write throttling (around 1,200 requests per hour). Long-running operations such as account creation return 202 Accepted with an Azure-AsyncOperation header you poll for completion.

How do I create a compute policy through Jentic?

Run pip install jentic and search for 'create data lake analytics compute policy'. Jentic returns the ComputePolicies_CreateOrUpdate operation; load its schema and execute it with the subscriptionId, resourceGroupName, accountName, computePolicyName, and a body specifying objectId, objectType, maxDegreeOfParallelismPerJob, and minPriorityPerJob.

Does this API submit U-SQL jobs?

No. This is the management plane only - it provisions accounts and policies. U-SQL job submission uses the Data Lake Analytics job API at https://{accountName}.azuredatalakeanalytics.net/ with a separate SDK.

Can I limit what my agent is allowed to do with the Data Lake Analytics Account Management API?

Yes. Because you run Jentic One yourself, your own rules decide which of the 31 operations the agent may call and which Azure service principal credential it uses. Since the account name sits in the request path (/subscriptions/{id}/resourceGroups/{rg}/providers/Microsoft.DataLakeAnalytics/accounts/{accountName}/...), a rule can pin the agent to a single account together with its compute policies and source attachments. You choose the operations it can reach, so destructive calls like Accounts_Delete or DataLakeStoreAccounts_Delete are excluded unless you add them.

GET STARTED

Start building with DataLakeAnalyticsAccountManagementClient API

Explore with Jentic One
View OpenAPI Document