canonical: https://jentic.com/apis/azure.com/azure-data-lake-analytics-account-management

# Microsoft Azure DataLakeAnalyticsAccountManagementClient

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.

## For AI 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.

## Scope

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.

## Capabilities

- 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

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

| 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 |

## Key resources

- **Accounts** — Provision and manage Data Lake Analytics accounts and check name availability
- **DataLakeStoreAccounts** — Attach, list, get, and detach Data Lake Store sources on an Analytics account
- **StorageAccounts** — Attach, list, get, and detach Azure Storage sources on an Analytics account
- **ComputePolicies** — Define per-user and per-group parallelism and job-count limits
- **FirewallRules** — Control which IP ranges can submit jobs to the account
- **Locations** — Query per-region Data Lake Analytics capabilities and quotas

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Data Lake Analytics Catalog Management** — Manage U-SQL catalog objects (databases, tables, credentials) within a Data Lake Analytics account.
- **Data Lake Store Account Management** — Provision the Data Lake Store accounts that Data Lake Analytics queries.
- **Databricks Management** — Spark- and Delta-Lake-based analytics workspaces instead of U-SQL on Data Lake Analytics.

## FAQ

### 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.