canonical: https://jentic.com/apis/azure.com/azure-stack-network-admin-load-balancers

# Microsoft Azure NetworkAdminManagementClient

Jentic publishes the only available OpenAPI specification for the Azure Stack network admin load balancer surface, keeping it validated and agent-ready. NetworkAdminManagementClient is the operator-facing control plane for an Azure Stack Hub deployment, exposing the cloud admin view of physical infrastructure objects rather than tenant resources. The 2015-06-15 slice covers the admin load balancers endpoint, which lists the load balancer resources active across the Azure Stack region. The base URL adminmanagement.local.azurestack.external is reached only from inside an Azure Stack environment with operator credentials.

## For AI agents

Read the list of admin load balancers in an Azure Stack Hub region. Single endpoint that exposes operator-level network infrastructure objects.

## Scope

Does not handle tenant load balancer creation, public-cloud Azure networking, or non-network admin resources - use for the Azure Stack network admin load balancer list endpoint only.

## Capabilities

- List admin-scoped load balancer infrastructure resources in an Azure Stack region
- Surface load balancer state for Azure Stack operator dashboards
- Provide an inventory feed for Azure Stack health and capacity tooling

## Use cases

### Azure Stack operator dashboards

Cloud operators running Azure Stack Hub need a single inventory of physical-tier network load balancers across a region. Calling the admin load balancers list endpoint returns the operator-visible objects with location and resource group, which feeds capacity, patch, and health dashboards. The endpoint runs against the admin management plane reachable only from within the Azure Stack deployment, so it is appropriate for trusted operator tooling.

Example prompt: List admin load balancers for subscription abc on the Azure Stack admin endpoint and return the count grouped by resource group.

### Capacity planning for Azure Stack regions

Capacity planners running Azure Stack want to track the number and distribution of admin load balancer objects to inform expansion decisions. The admin endpoint provides a stable inventory feed that can be sampled on a schedule, joined against tenant-side metrics, and surfaced in capacity reports. Combined with operator-level tools for compute, storage, and updates, it forms part of the operational data fabric.

Example prompt: Sample admin load balancers daily for one week and record the count and resource group distribution to a capacity log.

### Health monitoring integration

Operations teams integrate Azure Stack admin endpoints into their wider monitoring stack to surface infrastructure-tier issues. The list response can be parsed for unexpected entries or missing items relative to a known baseline, alerting the operator that the load balancer fleet has changed in a way that needs investigation.

Example prompt: Compare the current admin load balancer list against a baseline file and emit an alert if any expected entry is missing or any new entry has appeared.

### Agent-driven Azure Stack inventory

AI agents with operator credentials can use Jentic to discover NetworkAdminManagementClient operations by intent, load the structured input schema, and execute the call against the Azure Stack admin endpoint without browsing the Azure Stack docs. An inventory agent answering a natural-language question about Azure Stack infrastructure can fetch the load balancer list as a first step in a broader trace of operator-tier resources.

Example prompt: Search Jentic for list azure stack admin load balancers, load the schema, and execute it on the admin endpoint, returning the JSON response unchanged.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /subscriptions/{subscriptionId}/providers/Microsoft.Network.Admin/adminLoadBalancers | List admin load balancers in an Azure Stack region |

## Key resources

- **Admin Load Balancers** — Operator-visible inventory of load balancer infrastructure objects in an Azure Stack region.

## Why Jentic

- **Setup:** Wiring Azure Stack's NetworkAdminManagementClient by hand means acquiring an Azure AD token from login.microsoftonline.com, reaching the private operator host adminmanagement.local.azurestack.external from inside the Stack deployment, and threading the api-version into every admin call. Through Jentic you install once, import NetworkAdminManagementClient from the API Directory, store the Azure AD credential once, and your agent calls it.
- **Permission scoping:** This API puts the subscription id in the URL path (/subscriptions/{subscriptionId}/providers/Microsoft.Network.Admin/adminLoadBalancers), so a rule can pin your agent to one Azure Stack subscription. You choose the operations it may call, and since the exposed slice is only the admin load balancer list, the agent stays a read-only inventory reader unless you add more.
- **Credential handling:** Your Azure AD credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list Azure Stack admin load balancers', and Jentic returns the matching admin operation with its input schema so the operator agent calls the correct path without browsing the Azure Stack operator docs.

## Related APIs

- **Azure Network Management** — Tenant-facing network resource provider for load balancers, vnets, and NSGs in Azure public cloud and Azure Stack tenant scopes.
- **Azure Stack Fabric Admin** — Operator-tier control plane for the Azure Stack fabric, including infrastructure roles and storage subsystems.
- **Azure Stack Compute Admin** — Operator-tier compute control plane for Azure Stack infrastructure VMs and quotas.

## FAQ

### Why is there no official OpenAPI spec for NetworkAdminManagementClient?

Microsoft does not publish a single OpenAPI specification for the Azure Stack admin Network resource provider. Jentic generates and maintains this spec from the Azure Stack operator contracts so that AI agents and developers with operator credentials can call NetworkAdminManagementClient 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 Azure Stack network admin API use?

The API uses Azure Active Directory OAuth 2.0 with the user_impersonation scope against https://login.microsoftonline.com/common/oauth2/authorize. The caller must be an Azure Stack operator and must reach the admin management endpoint adminmanagement.local.azurestack.external from inside the Azure Stack network. Jentic stores the AAD client secret encrypted in its vault and issues scoped bearer tokens at execution time.

### What does the admin load balancers endpoint actually return?

GET /subscriptions/{subscriptionId}/providers/Microsoft.Network.Admin/adminLoadBalancers returns the list of load balancer infrastructure objects visible to the cloud operator across the Azure Stack region. The response includes resource IDs, locations, and resource groups; tenant-facing load balancers are managed through the standard Azure Resource Manager network APIs.

### What are the rate limits for this Azure Stack admin endpoint?

Azure Stack admin endpoints inherit ARM-style throttling, but practical limits depend on the deployed Azure Stack scale unit. Inventory pulls should run on a paced schedule, typically no more than once per minute, to avoid contention with operator workloads on the same admin tier.

### How do I list admin load balancers through Jentic?

Search Jentic for list azure stack admin load balancers, load the schema for GET /subscriptions/{subscriptionId}/providers/Microsoft.Network.Admin/adminLoadBalancers, and execute it with the operator subscription ID. The agent must be running in an environment that can reach the Azure Stack admin endpoint.

### Can this API create or delete load balancers?

The 2015-06-15 admin slice modeled here exposes only the list operation. Creating, updating, or deleting load balancers on Azure Stack is done through the tenant-facing network management API, while admin-tier mutations on infrastructure objects are restricted to internal operator tooling.

### Can I limit what my agent is allowed to do with the Azure Stack Network Admin Load Balancers API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. Since this API carries the subscription ID in the URL path (/subscriptions/{subscriptionId}/providers/Microsoft.Network.Admin/adminLoadBalancers), you can pin the agent to a single Azure Stack subscription. The only exposed operation is listing admin load balancers, so the agent stays a read-only inventory reader that cannot create, update, or delete infrastructure unless you grant more.