canonical: https://jentic.com/apis/azure.com/azure-peering-management

# Microsoft Azure PeeringManagementClient

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.

## For AI agents

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

## Scope

Does not handle ExpressRoute private peerings, VPN gateways, or VNet peerings - use for Microsoft.Peering Internet peerings (direct, exchange, Peering Service) only.

## Capabilities

- Register peer ASNs and validate them before creating peerings
- List peering locations and exchange peering facilities by region and SKU
- Provision direct and exchange peerings between an ISP and Microsoft's network
- Register peering services for a customer site to use Azure Peering Service
- Add and validate IP prefixes that Peering Service announces on behalf of a customer
- Check service provider availability at a specific customer location
- Inspect legacy peerings inherited from earlier peering arrangements

## Use cases

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

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

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

## Key resources

- **PeerAsns** — Register and manage peer ASNs
- **Peerings** — Provision direct and exchange peerings between an ISP and Microsoft
- **PeeringLocations** — List facilities where direct or exchange peering is available
- **PeeringServices** — Register peering services for customer sites
- **PeeringServicePrefixes** — Add and validate IP prefixes announced through Peering Service
- **PeeringServiceProviders** — List Peering Service partner providers
- **CheckServiceProviderAvailability** — Check which providers serve a customer location
- **LegacyPeerings** — Inspect legacy peerings inherited from earlier arrangements

## Why Jentic

- **Setup:** Wiring the PeeringManagementClient by hand means acquiring an Azure AD token from login.microsoftonline.com, sending every call to management.azure.com with the correct preview api-version, and mapping Microsoft.Peering objects like peer ASNs, peering locations, and Peering Service providers yourself. Through Jentic you install once, import PeeringManagementClient 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.Peering/...), so a rule can pin your agent to one subscription. You choose the operations it may call, so registering or deleting a peer ASN is not included unless you add them, letting the agent list peering locations and service providers as a read path.
- **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 'register an Azure peer ASN' or 'list Azure peering locations', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without learning the Microsoft.Peering namespace.

## Related APIs

- **Azure Network Management** — Manages ExpressRoute circuits and core VNet networking alongside Internet peerings.
- **Azure DNS Management** — Publish DNS records for resources reachable via the peering paths configured here.
- **Azure Monitor** — Collect metrics on peering throughput and BGP session health.

## FAQ

### 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 with Jentic One, the self-hosted execution layer.

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

### Can I limit what my agent is allowed to do with the Azure Peering Management API?

Yes. Because you run Jentic One yourself, your own rules decide which Microsoft.Peering operations and which Azure AD credential the agent may use. Since this API carries the subscription id in the URL path, you can pin the agent to a single subscription, and you choose the operations it can call, so read paths like listing peering locations and service providers stay available while write actions such as registering or deleting a peer ASN are excluded unless you add them. The credential is stored by your own instance and injected only at execution time.