PeeringManagementClient

Name: PeeringManagementClient API
Brand: Azure Peering Management
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureNetworkingoauth226 EndpointsREST

For Agents

Provision and manage Azure Internet peerings, peer ASNs, peering services, and customer prefixes through 26 ARM operations on the Microsoft.Peering provider.

Connect the PeeringManagementClient to your agent

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

List peering locations and exchange peering facilities by region and SKU

Provision direct and exchange peerings between an ISP and Microsoft's network

GET STARTED

Start building with PeeringManagementClient API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for PeeringManagementClient, keeping it validated and agent-ready. The Azure Peering Service management API exposes 26 operations on the Microsoft.Peering resource provider for managing Internet peerings between ISPs and Microsoft's global network. Use it to register peer ASNs, list peering locations, provision direct and exchange peerings, register and validate peering services and prefixes, and check service provider availability for a specific customer location.

Use Cases

Patterns agents use PeeringManagementClient API for, with concrete tasks.

★ ISP Peering Onboarding

An ISP onboarding to Azure Peering registers its ASN, lists peering facilities where it has presence, and provisions direct peerings with the Microsoft AS at those facilities. The management API automates the registration and provisioning steps that previously required manual coordination through the Azure Peering portal. Once provisioned, BGP sessions establish at the agreed facility and bandwidth.

Register peer ASN 64512 with the supplied contact details, list peering facilities in Frankfurt, and provision a direct peering at the chosen facility with a 10 Gbps SKU

Enterprise Peering Service Setup

An enterprise enrolling in Azure Peering Service for higher-quality Internet routing to Microsoft 365 registers a peering service at each customer site, provides the prefixes it wants Microsoft's partners to announce, and validates each prefix before going live. The provider availability check confirms which Peering Service partner serves a given postcode so the enterprise can choose the right one for each location.

Check service provider availability for postcode 'WC2N 5DU', register a peering service for London office with the available provider, and add prefix 198.51.100.0/24 with prefix validation

Peering Inventory Audit

Audit peering posture across a subscription. List every peer ASN, every direct and exchange peering, every legacy peering inherited from before the current API generation, and every peering service location. Group by facility and SKU to confirm capacity and identify duplicates or stale entries that should be deprovisioned.

List every direct peering and legacy peering in the subscription, group by facility, and report any peerings still in Provisioning state for more than 24 hours

AI Agent Peering Operator

An AI agent in a network operations workflow can provision and audit Azure peerings through Jentic. The agent searches by intent ('register an azure peer asn'), Jentic returns the PeerAsns_CreateOrUpdate operation with its schema, and the agent executes the call with managed Azure credentials. Peering creation, prefix validation, and service provider lookup follow the same intent-driven flow.

Search Jentic for 'register an Azure peer ASN', load the PeerAsns_CreateOrUpdate schema, and execute it for ASN 64512 with the supplied contact information

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Peering/peerAsns

List peer ASNs in a subscription

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Peering/peerAsns/{peerAsnName}

Get a peer ASN registration

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Peering/peeringLocations

List peering locations available for direct or exchange peering

POST

/subscriptions/{subscriptionId}/providers/Microsoft.Peering/CheckServiceProviderAvailability

Check which Peering Service providers serve a customer location

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Peering/peeringServiceLocations

List Peering Service locations

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Peering/peeringServiceProviders

List Peering Service providers

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Peering/legacyPeerings

List legacy peerings

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Peering/peerAsns

List peer ASNs in a subscription

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Peering/peerAsns/{peerAsnName}

Get a peer ASN registration

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Peering/peeringLocations

List peering locations available for direct or exchange peering

POST

/subscriptions/{subscriptionId}/providers/Microsoft.Peering/CheckServiceProviderAvailability

Check which Peering Service providers serve a customer location

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Peering/peeringServiceLocations

List Peering Service locations

Why though 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 ('register an azure peer asn' or 'list azure peering locations') and Jentic returns the matching operation, avoiding the need to learn the 26 endpoints under Microsoft.Peering.

Time to first call

Direct ARM integration: half a day for AAD app registration, MSAL token handling, and peering payload modelling. Through Jentic: under 30 minutes.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Azure Network Management

Manages ExpressRoute circuits and core VNet networking alongside Internet peerings.

Use Network Management for ExpressRoute (private connectivity); use this API for Internet peering (public BGP sessions).

Complementary

Azure DNS Management

Publish DNS records for resources reachable via the peering paths configured here.

Use DNS Management to point names at IPs that are routed efficiently thanks to Peering Service.

Complementary

Azure Monitor

Collect metrics on peering throughput and BGP session health.

Use Monitor to alert on peering session drops or unexpected drops in announced prefix counts.

FAQs

Specific to using PeeringManagementClient API through Jentic.

Why is there no official OpenAPI spec for PeeringManagementClient?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call PeeringManagementClient 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 Peering 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.Peering/* permissions on the subscription. Jentic stores service principal credentials encrypted and issues short-lived bearer tokens at execution time.

Can I provision a direct peering through this API?

Yes. PUT to /subscriptions/{id}/resourceGroups/{rg}/providers/Microsoft.Peering/peerings/{name} with the peering kind set to Direct, the peer ASN reference, the chosen peering location, and the bandwidth SKU. The call kicks off provisioning and you poll the resource until it reaches Succeeded.

What are the rate limits for the Peering management API?

Azure Resource Manager applies subscription-level throttling at roughly 1,200 reads and 1,200 writes per hour. Peering provisioning is an asynchronous operation that returns 202 Accepted with an Azure-AsyncOperation header to poll until the BGP session is established.

How do I check Peering Service provider availability through Jentic?

Run pip install jentic and search for 'check azure peering service provider availability'. Jentic returns the CheckServiceProviderAvailability operation; load its schema and execute it with the customer's country and postcode to get the list of Peering Service partners serving that location.

Does this API cover ExpressRoute peerings?

No. ExpressRoute peerings live under Microsoft.Network/expressRouteCircuits in the Network management API. This API covers Internet peerings (direct, exchange, Peering Service) under Microsoft.Peering only.