Microsoft Azure ExpressRouteCrossConnection REST APIs

Name: ExpressRouteCrossConnection REST APIs
Brand: Azure ExpressRoute Cross Connection REST APIs
Availability: InStock

Browse all Azure APIs

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureNetworkingoauth212 EndpointsREST

For Agents

Manage Azure ExpressRoute cross connections and their peerings, and read the live ARP, route, and route-summary tables from peering devices.

Use for: List all ExpressRoute cross connections in subscription 1111-2222-3333-4444, Get the cross connection named cc-london-1 in resource group network-rg, Update the tags on cross connection cc-london-1 to set environment=prod, Create a peering on cross connection cc-london-1 for AzurePrivatePeering

Not supported: Does not provision ExpressRoute circuits, virtual network gateways, or VNets, and does not establish BGP sessions itself - use only to manage provider-facing cross connections, their peerings, and read the live ARP and route tables on peering devices.

Jentic publishes the only available OpenAPI specification for the Azure ExpressRoute Cross Connection REST APIs, keeping it validated and agent-ready. This API manages ExpressRoute cross connections that providers create on behalf of customers to extend on-premises networks into Azure over a private circuit. It exposes operations to read cross connections, update tags, configure peerings, and inspect the live ARP table, route table, and route table summary on a peering device.

Install Jentic One Beta

Connect the ExpressRouteCrossConnection REST APIs to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ExpressRouteCrossConnection REST APIs, 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fexpressroute-cross-connection-rest-apis" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fexpressroute-cross-connection-rest-apis" | 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 ExpressRouteCrossConnection REST APIs.

List ExpressRoute cross connections in a subscription or resource group

Read the configuration of a specific ExpressRoute cross connection

Update tags on an ExpressRoute cross connection

Configure peerings (primary, secondary, Microsoft) on a cross connection

GET STARTED

Start building with ExpressRouteCrossConnection REST APIs

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use ExpressRouteCrossConnection REST APIs for, with concrete tasks.

★ Provisioning Cross Connections for Customers

Connectivity providers configure ExpressRoute cross connections on behalf of their enterprise customers to land circuits into Azure regions. PUT /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/expressRouteCrossConnections/{crossConnectionName} updates the cross connection definition; the matching list endpoints support inventory automation across many customer subscriptions.

Update cross connection cc-london-1 in resource group network-rg with the production tag and verify the response shows the new tags

Configure Peerings on a Cross Connection

Network engineers configure peerings (typically AzurePrivatePeering or MicrosoftPeering) on a cross connection so that on-premises routers can exchange BGP sessions with Azure. The peerings sub-resource supports list, get, create or update, and delete so engineers can iterate on VLAN ids, ASNs, and IP allocations without recreating the parent cross connection.

Create AzurePrivatePeering on cross connection cc-london-1 with peer ASN 65001 and primary peer subnet 192.168.10.0/30

Diagnose BGP State on a Peering Device

When a peering session misbehaves, NetOps inspect the live ARP table, advertised routes, and routes summary directly from the peering device. POST endpoints under peerings/{peeringName}/arpTables, routeTables, and routeTablesSummary return the current state, which is far more actionable than the static configuration when troubleshooting BGP next-hop or MAC issues.

Fetch the ARP table for peering AzurePrivatePeering on device primary for cross connection cc-london-1 and report any missing neighbour

Agent-Driven Cross Connection Audit

An AI agent running monthly network audits can list every cross connection, read each peering, and pull the live route table summary through Jentic. Intent search returns the cross connection and peering operations with their schemas, while the AAD token used to call ARM is held in your Jentic One instance so the agent never sees the service principal secret.

Search Jentic for 'list Azure ExpressRoute cross connections', execute against the production subscription, and emit a report of peering states and route table summaries

Key Endpoints

12 endpoints — jentic publishes the only available openapi specification for the azure expressroute cross connection rest apis, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Network/expressRouteCrossConnections

List cross connections in a subscription

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/expressRouteCrossConnections/{crossConnectionName}

Create or update a cross connection

PATCH

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/expressRouteCrossConnections/{crossConnectionName}

Update cross connection tags

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/expressRouteCrossConnections/{crossConnectionName}/peerings/{peeringName}

Create or update a peering

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/expressRouteCrossConnections/{crossConnectionName}/peerings/{peeringName}/arpTables/{devicePath}

Read the live ARP table on a peering device

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/expressRouteCrossConnections/{crossConnectionName}/peerings/{peeringName}/routeTablesSummary/{devicePath}

Read the route table summary on a peering device

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Network/expressRouteCrossConnections

List cross connections in a subscription

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/expressRouteCrossConnections/{crossConnectionName}

Create or update a cross connection

PATCH

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/expressRouteCrossConnections/{crossConnectionName}

Update cross connection tags

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/expressRouteCrossConnections/{crossConnectionName}/peerings/{peeringName}

Create or update a peering

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/expressRouteCrossConnections/{crossConnectionName}/peerings/{peeringName}/arpTables/{devicePath}

Read the live ARP table on a peering device

POST

Read the route table summary on a peering device

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the ExpressRoute Cross Connection API by hand means minting Azure AD OAuth 2.0 tokens against management.azure.com, assembling the Microsoft.Network cross connection and peering ARM paths, and handling the POST table reads that can take several seconds to return from the peering device. Through Jentic you install once, import the ExpressRouteCrossConnection REST APIs from the API Directory, store the Azure AD client credentials once, and your agent calls it.

Permission scoping

The API puts the subscription, resource group, and cross connection name in the URL path (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/expressRouteCrossConnections/{crossConnectionName}/...), so a rule can pin your agent to one cross connection and its peerings. You choose the operations it may call, so mutating ones like the peering create-or-update or peering delete are not included unless you add them.

Credential isolation

Your Azure AD client credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time as a scoped bearer token. The service principal secret never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list Azure ExpressRoute cross connections' or 'read the ARP table for a peering', and Jentic returns the matching cross connection or peering operation with its input schema so the agent calls the right endpoint without memorising the long ARM path layout.

FAQs

Specific to using ExpressRouteCrossConnection REST APIs through Jentic.

Why is there no official OpenAPI spec for ExpressRouteCrossConnection REST APIs?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call ExpressRouteCrossConnection REST APIs 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 ExpressRoute Cross Connection API use?

The API uses Azure Active Directory OAuth 2.0 bearer tokens (the azure_auth scheme) on management.azure.com. Through Jentic, the AAD service principal secret is stored in your Jentic One instance and exchanged for a short-lived bearer token per call.

Can I configure a peering on an ExpressRoute cross connection with this API?

Yes. Call PUT /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/expressRouteCrossConnections/{crossConnectionName}/peerings/{peeringName} with the peering body (peer ASN, VLAN id, primary and secondary peer subnets) to create or update peerings such as AzurePrivatePeering.

How do I read the live ARP and routes table for a peering?

Call POST under the peering with arpTables/{devicePath}, routeTables/{devicePath}, or routeTablesSummary/{devicePath}. The devicePath identifies the primary or secondary device; the response is the current advertised state, which is what you want for BGP troubleshooting.

What are the rate limits for the ExpressRoute Cross Connection API?

Azure Resource Manager applies subscription-level throttling. Mutation calls are throttled more strictly than reads; on HTTP 429 back off using the Retry-After header. ARP and routes table reads are POST operations against the device and may take several seconds to return.

How do I audit ExpressRoute cross connections through Jentic?

Run pip install jentic, then search Jentic with 'list Azure ExpressRoute cross connections'. Load ExpressRouteCrossConnections_List, execute against your subscription, and chain into ExpressRouteCrossConnectionPeerings_List for each. Credentials are sourced from the vault on every call.

Can I limit what my agent is allowed to do with the Microsoft Azure ExpressRoute Cross Connection API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. The subscription, resource group, and cross connection name all sit in the ARM URL path, so a rule can pin the agent to a single cross connection and its peerings. You also choose which operations are enabled, so read-only calls like listing cross connections or fetching the ARP and route tables can be allowed while mutating calls such as peering create-or-update and peering delete stay excluded unless you add them.

Microsoft Azure ExpressRouteCrossConnection REST APIs

Connect the ExpressRouteCrossConnection REST APIs to your agent

Capabilities

Start building with ExpressRouteCrossConnection REST APIs

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs