NetworkAdminManagementClient

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureNetworkingoauth21 EndpointsREST

For Agents

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

Connect the NetworkAdminManagementClient to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the NetworkAdminManagementClient, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

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

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 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 NetworkAdminManagementClient API.

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

Patterns agents use NetworkAdminManagementClient API for, with concrete tasks.

GET STARTED

Start building with NetworkAdminManagementClient API

Explore with Jentic

View OpenAPI Document

Use for: List admin load balancers in my Azure Stack subscription, Get an inventory of network admin load balancers for capacity planning, Retrieve admin-side load balancer details across the Azure Stack region, Find the load balancer infrastructure objects exposed to the cloud operator

Not supported: 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.

Jentic publishes the only available OpenAPI document for NetworkAdminManagementClient, keeping it validated and agent-ready.

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.

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

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.

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.

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.

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

1 endpoints — jentic publishes the only available openapi specification for the azure stack network admin load balancer surface, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Network.Admin/adminLoadBalancers

List admin load balancers in an Azure Stack region

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Network.Admin/adminLoadBalancers

List admin load balancers in an Azure Stack region

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Azure AD OAuth credentials and operator service principals are stored encrypted in the Jentic vault. Agents receive scoped bearer tokens for the Azure Stack admin endpoint at execution time; client secrets and operator credentials never enter the agent context.

Intent-based discovery

Agents search by intent (for example list azure stack admin load balancers) and Jentic returns the matching admin operation with its full input schema, so the operator agent can call the correct path without browsing the Azure Stack operator docs.

Time to first call

Direct integration with the Azure Stack admin endpoint: 1 day including AAD auth and admin endpoint configuration. Through Jentic: a few minutes to search, load, and execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Azure Network Management

Tenant-facing network resource provider for load balancers, vnets, and NSGs in Azure public cloud and Azure Stack tenant scopes.

Choose this when the agent is acting as a tenant rather than an Azure Stack operator and needs to create, update, or delete network resources.

Complementary

Azure Stack Fabric Admin

Operator-tier control plane for the Azure Stack fabric, including infrastructure roles and storage subsystems.

Use this when the operator agent needs to inspect or manage fabric-tier objects beyond network load balancers.

Complementary

Azure Stack Compute Admin

Operator-tier compute control plane for Azure Stack infrastructure VMs and quotas.

Use this when the operator agent needs to inspect or manage compute-tier infrastructure rather than network load balancers.

FAQs

Specific to using NetworkAdminManagementClient API through Jentic.

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 at https://app.jentic.com/sign-up.

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.