Microsoft Azure NetworkManagementClient
Browse all Azure APIs★ Only Publicly Available OpenAPI DocumentCloud InfrastructureNetworkingoauth297 EndpointsREST
For Agents
Provision and manage Azure virtual networks, NSGs, load balancers, public IPs, application gateways, and ExpressRoute circuits via 97 ARM operations on the Microsoft.Network provider.
Use for: I need to create a virtual network with two subnets in West Europe, List all network security groups in a resource group and their inbound rules, Allocate a static public IP and attach it to a load balancer frontend, Set up an application gateway in front of three backend VMs
Not supported: Does not handle Azure Front Door, Traffic Manager, or DNS zone records — use for Microsoft.Network resource provisioning (VNets, NSGs, load balancers, ExpressRoute) only.
Jentic publishes the only available OpenAPI specification for NetworkManagementClient, keeping it validated and agent-ready. The Azure Network management API exposes 97 operations across the Microsoft.Network resource provider for managing virtual networks, subnets, network interfaces, public IP addresses, network security groups, load balancers, application gateways, route tables, ExpressRoute circuits, and VPN gateways. It supports the full lifecycle of Azure networking primitives — provisioning, configuration changes, peering setup, security rule updates, and traffic inspection — at subscription and resource group scope.
Install Jentic One Beta
Connect the NetworkManagementClient to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the NetworkManagementClient, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: 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 instanceJentic 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 NetworkManagementClient API.
Provision virtual networks and subnets and attach network interfaces to virtual machines
Configure network security groups with inbound and outbound rules to restrict traffic
Allocate and assign static or dynamic public IP addresses to load balancers and NICs
Create application gateways with backend pools, listeners, and HTTP routing rules
Set up internal and external load balancers with health probes and load balancing rules
Establish ExpressRoute circuits with peerings and authorisations for hybrid connectivity
Inspect ARP and route tables on ExpressRoute circuits for connectivity troubleshooting
Use Cases
Patterns agents use NetworkManagementClient API for, with concrete tasks.
★ Multi-Tier Application Networking
Build the network plane for a multi-tier web application — a virtual network with web, app, and database subnets, an application gateway in front of the web tier, network security groups locking traffic to expected ports, and a public IP for ingress. The 97 endpoints cover every primitive needed, from the VNet itself down to individual NSG rules. End-to-end provisioning of this topology takes around 10-20 ARM calls and completes in a few minutes.
Create a virtual network 'app-vnet' with three subnets, attach an NSG to each subnet allowing only the expected ports, and provision an application gateway with a public IP frontend
Hybrid Connectivity with ExpressRoute
Connect an on-premises datacentre to Azure over ExpressRoute. The flow is: list available service providers and peering locations, create the ExpressRoute circuit, configure private and Microsoft peering, generate authorisations for partner organisations, and verify connectivity by inspecting the ARP and route tables. The API exposes circuit stats and peering state so an agent can confirm the link is up before VMs depend on it.
Create an ExpressRoute circuit with a 1 Gbps SKU at the London peering location, configure private peering with the supplied ASN and IP ranges, and confirm the circuit reports Provisioned status
Network Security Hardening Audit
Audit and tighten network security across a subscription. List every network security group, inspect each rule, identify rules that allow inbound traffic from 0.0.0.0/0 on sensitive ports, and replace them with tighter CIDR-restricted rules. The flat list endpoints at subscription scope let an agent walk every NSG without enumerating resource groups individually, making this practical to run on a schedule.
List all NSGs in the subscription, identify rules allowing TCP/22 or TCP/3389 from Any source, and update each to restrict source to the corporate IP range
AI Agent Cloud Networking Operator
An AI agent supporting a platform team can provision and inspect Azure networks through Jentic. The agent searches by intent ('create an azure virtual network'), Jentic returns the VirtualNetworks_CreateOrUpdate operation with its schema, and the agent executes the call with managed Azure credentials. The same flow handles NSG updates, public IP allocation, and load balancer reconfiguration without the agent learning the Microsoft.Network namespace.
Search Jentic for 'create an Azure virtual network', load the VirtualNetworks_CreateOrUpdate schema, and execute it with the supplied address space and subnet definitions
Key Endpoints
97 endpoints — jentic publishes the only available openapi specification for networkmanagementclient, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Network/loadBalancers
List all load balancers in a subscription
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Network/networkInterfaces
List all network interfaces in a subscription
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Network/networkSecurityGroups
List all network security groups in a subscription
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Network/publicIPAddresses
List all public IP addresses in a subscription
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Network/applicationGateways
List all application gateways in a subscription
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Network/expressRouteCircuits
List all ExpressRoute circuits in a subscription
POST
/subscriptions/{subscriptionId}/providers/Microsoft.Network/locations/{location}/CheckDnsNameAvailability
Check if a DNS name is available in a region
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Network/loadBalancers
List all load balancers in a subscription
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Network/networkInterfaces
List all network interfaces in a subscription
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Network/networkSecurityGroups
List all network security groups in a subscription
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Network/publicIPAddresses
List all public IP addresses in a subscription
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Network/applicationGateways
List all application gateways in a subscription
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Network/expressRouteCircuits
List all ExpressRoute circuits in a subscription
POST
/subscriptions/{subscriptionId}/providers/Microsoft.Network/locations/{location}/CheckDnsNameAvailability
Check if a DNS name is available in a region
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Azure service principal credentials are encrypted in the Jentic vault. Agents receive scoped ARM bearer tokens at execution time and never see the underlying client secret.
Intent-based discovery
Agents search by intent ('create an azure virtual network' or 'list network security groups') and Jentic returns the matching operation, avoiding the need to learn 97 endpoints across the Microsoft.Network namespace.
Time to first call
Direct ARM integration: 1-2 days for AAD app registration, MSAL token handling, and async-operation polling. Through Jentic: under 1 hour.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using NetworkManagementClient API through Jentic.
Why is there no official OpenAPI spec for NetworkManagementClient?
Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call NetworkManagementClient 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 Network Management API use?
It uses Azure Active Directory OAuth 2.0 against https://management.azure.com/ with the user_impersonation scope. The caller needs Network Contributor or a custom role with Microsoft.Network/* permissions. Jentic stores service principal credentials encrypted and issues short-lived bearer tokens at execution time.
Can I create a virtual network and its subnets through this API?
Yes. PUT to /subscriptions/{id}/resourceGroups/{rg}/providers/Microsoft.Network/virtualNetworks/{name} with the address space and subnet definitions in the request body. The call returns 201 with an Azure-AsyncOperation header you poll until the VNet reports Succeeded.
What are the rate limits for the Azure Network Management API?
Azure Resource Manager applies subscription-level throttling at roughly 1,200 reads per hour and 1,200 writes per hour. Long-running provisioning operations return 202 Accepted with an Azure-AsyncOperation URL to poll for completion.
How do I provision an application gateway through Jentic?
Run pip install jentic and search for 'create an azure application gateway'. Jentic returns the ApplicationGateways_CreateOrUpdate operation; load its schema and execute it with the listener, backend pool, and routing rule definitions.
Does this API cover Azure Front Door or Traffic Manager?
No. NetworkManagementClient covers Microsoft.Network primitives (VNets, NSGs, load balancers, application gateways, ExpressRoute). Azure Front Door lives under Microsoft.Network/frontDoors in a separate namespace and Traffic Manager under Microsoft.Network/trafficManagerProfiles.
GET STARTED