Microsoft Azure ManagedNetworkManagementClient

Name: ManagedNetworkManagementClient API
Brand: ManagedNetworkManagementClient
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureNetworkingoauth219 Endpoints

Install Jentic One Beta

Connect the ManagedNetworkManagementClient to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ManagedNetworkManagementClient, 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.

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

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

Create and manage ManagedNetwork resources that group VNets and scopes under one boundary

Define ManagedNetworkGroups that collect virtual networks for shared connectivity rules

Configure ManagedNetworkPeeringPolicies that automate hub-and-spoke or mesh peering

GET STARTED

Start building with ManagedNetworkManagementClient API

Explore with Jentic

View OpenAPI Document

For Agents

Define managed networks, group memberships, scope assignments, and peering policies for centralised Azure VNet topology management. Use for managed network configuration, not for VNet creation or per-NIC operations.

Use for: Create a managed network that groups all production VNets under one peering policy, Add a list of VNets to the 'prod-spokes' managed network group, Apply a hub-and-spoke peering policy to the 'prod-network' managed network, List all managed networks in my subscription

Not supported: Does not create virtual networks, subnets, or network interfaces, and does not manage Azure Firewall or NSG rules — use only for Microsoft.ManagedNetwork grouping, peering policy, and scope assignment resources.

Use Cases

Patterns agents use ManagedNetworkManagementClient API for, with concrete tasks.

★ Centralised Hub-and-Spoke Topology

Enterprises with dozens of VNets across business units use ManagedNetworkManagementClient to declare a hub VNet and spoke groups, then attach a peering policy that produces the right peerings automatically. New VNets added to a spoke group inherit peering without per-VNet configuration. This replaces hand-maintained peering scripts with a declarative ARM resource graph.

Create managed network 'prod-network', a ManagedNetworkGroup 'spokes' containing 12 spoke VNet IDs, and a ManagedNetworkPeeringPolicy of type HubAndSpokeTopology with the hub VNet ID, then verify the peerings appear under each VNet.

Scope-Driven Network Governance

Cloud platform teams attach a managed network to a subscription or management group via ScopeAssignment so that any VNet created under that scope is governed by the managed network's policies. This shifts VNet connectivity policy from a per-resource concern to a platform concern, simplifying landing zone enforcement.

Create a ScopeAssignment that attaches managed network 'prod-network' to the 'prod-mg' management group, then list ScopeAssignments to confirm the binding exists.

Topology Migration from Mesh to Hub-Spoke

Operations teams reducing east-west traffic costs migrate a fully meshed VNet group to a hub-and-spoke topology. Updating the ManagedNetworkPeeringPolicy from Mesh to HubAndSpokeTopology causes Azure to remove the redundant peerings and create the hub-routed ones. The migration is declarative and auditable through ARM activity logs.

PATCH the peering policy 'prod-policy' on managed network 'prod-network' to set type=HubAndSpokeTopology with the chosen hub VNet ID, then list peerings on each spoke to verify the new topology.

AI Agent Network Topology Operations

Network platform agents use Jentic to discover managed network operations on demand. Searching for 'apply azure peering policy' returns the matching ManagedNetworkPeeringPolicies operation; the agent loads the schema and executes against management.azure.com using a token from the Jentic vault, so topology automation does not require bundling the Network Manager SDK.

Use Jentic to search 'create azure managed network peering policy', load the ManagedNetworkPeeringPolicies_CreateOrUpdate schema, and PUT the policy with the requested topology and hub VNet ID.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

PUT