Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Cloud Infrastructure / Azure / ExpressRouteCrossConnection REST APIs
ExpressRouteCrossConnection REST APIs logo

Microsoft Azure ExpressRouteCrossConnection REST APIs

Browse all Azure APIs
40
AI ReadinessNon-Ready (F)40/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticCloud InfrastructureNetworkingoauth212 EndpointsREST

Know of an official OpenAPI document? Contribute it →

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.

Jentic One on GithubView OpenAPI Document

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.

1

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
2

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

Fetch the currently advertised ARP table for a peering device

Fetch the currently advertised routes table and route table summary for a peering device

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

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

Read the route table summary on a peering device

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

E

ExpressRouteCrossConnection REST APIs

- Non-Ready (F)
40/100
73
Foundational Compliance
56
Developer Experience & Jentic Compatibility
18
AI-Readiness & Agent Experience
94
Agent Usability
35
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
73

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4
93%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

56

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: CSignals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

18

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
72%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

0%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

0%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

35

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1
35%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

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.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Azure Network Management Client

→

Provides the surrounding virtual networks, gateways, and ExpressRoute circuit resources this cross connection peers with.

Use the network management client to manage VNets, gateways, and circuits; use this API for provider-side cross connection objects.

Complementary

Azure Monitor Management Client

→

Collects metrics and diagnostic logs for ExpressRoute peerings.

Use Monitor for BGP and traffic metrics; use this API for the cross connection configuration that produces them.

Alternative

AWS Direct Connect

→

AWS dedicated network connection equivalent to ExpressRoute for hybrid networking.

Choose Direct Connect for AWS hybrid links. Stay with ExpressRoute Cross Connection for Azure hybrid circuits.

Alternative

Google Cloud Compute (Interconnect)

→

Manages Google Cloud Interconnect attachments as a private connectivity option.

Choose Cloud Interconnect for GCP. Stay with ExpressRoute Cross Connection for Azure private circuits.

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.

GET STARTED

Start building with ExpressRouteCrossConnection REST APIs

Explore with Jentic One
View OpenAPI Document