Azure Front Door

Azure Front Door Service enables you to define, manage, and monitor the global routing for your web traffic. The REST API supports configuring routing rules, backend pools, health probes, caching policies, and WAF rules for secure and performant application delivery at the edge.

Azure Front Door is listed with 2 APIs on the APIs.io network: Operations API and Profiles API. Tagged areas include CDN, Edge, Global Routing, Load Balancing, and WAF.

The Azure Front Door catalog on APIs.io includes 1 Spectral governance ruleset.

Azure Front Door’s developer surface includes authentication, developer portal, pricing, support, and 13 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

38.5/100 thin ▬ flat Agent 20/100 agent aware saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessPaidSelf serve

2 APIs

CDN EdgeGlobal RoutingLoad Balancing WAF

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Information Technology Management

BC-600

Profiles

PUT /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Cdn/profiles/{name}

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 38.5/100 · thin

Contract Quality 8.3 / 19

Developer Ergonomics 5.4 / 15

Access Clarity 4.7 / 15

Operational Transparency 1.0 / 10

Contract Governance 1.2 / 9

Discoverability 5.5 / 8

Regulatory Posture 4.4 / 15

Create-or-Update Ergonomics 2.2 / 10

Agent readiness — 20/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/microsoft-azure-front-door/"><img src="https://apis.io/badge/microsoft-azure-front-door/card.svg" alt="Azure Front Door on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

9 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 44.1 — up to +14.0 composite points
Access Clarity scores 31.6 — up to +13.7 composite points
Developer Ergonomics scores 35.7 — up to +12.9 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/microsoft-azure-front-door/apis.yml: open an issue on github.com/api-evangelist/microsoft-azure-front-door to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Azure Front Door is an area vendor: providers adopt it to run part of their developer surface. This is the Kin Score checks its features can move for a provider that adopts it, what each one really earns, and what it earns nothing for.

cdncapability map1 features checked 2026-09-25 · rubric v0.22.0

Azure Front Door moves no Kin Score check. It accelerates and protects delivery with edge TLS, caching, L3–7 DDoS protection, WAF bot-manager rules and a rules engine. The fetched documentation describes no AI-crawler consent signal, Web Bot Auth, agent monetization, security.txt or llms.txt. A provider behind Front Door scores exactly what its own published artifacts earn.

Nothing the Kin Score reads. Azure Front Door's features serve the provider's operations, not the published surface the score measures.

Across 8977 providers that publish a contract, adopting Azure Front Door would move 0. Median lift: composite +0.0 (90th percentile +0.0), agent readiness +0.0 (+0.0). Conditional rows excluded.

What Azure Front Door ships that earns nothing (1)

Azure Front Door delivery and WAF — Delivery, TLS, DDoS and bot filtering change nothing any check reads.

A model, not a score. Adopting this vendor changes a provider's Kin Score only when the provider publishes the resulting artifacts on its own surface; nothing here writes a score, and no sponsorship or partnership can. The rating is not for sale → · Full vendor facets artifact

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Network Edge (CDN, networking, peering, edge compute)	undeclared	-	-	-
Cisco DevNet Ecosystem (builders on Meraki, Catalyst, ISE, ThousandEyes, Splunk)	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

Azure Front Door Operations API

Operations operations

Azure Front Door Profiles API

Profiles operations

Open Collections 3

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Azure Front Door REST Operations API

OPEN COLLECTION

Azure Front Door REST Operations Profiles API

OPEN COLLECTION

Azure Front Door REST API

OPEN COLLECTION

Azure Front Door API pricing

Rate limits

Free Tier Default: 10 requests per minute
Free Tier Monthly Quota: 1000 requests per month
Professional Tier Default: 100 requests per minute

Compiled by API Evangelist, not yet checked against Azure Front Door's documentation. All 5 limits →

Pricing Plans 1

Published pricing tiers and plan structures.

Microsoft Azure Front Door Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Microsoft Azure Front Door Rate Limits

5 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Microsoft Azure Front Door Finops

FINOPS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Azure Front Door API Rules

47 rules · 45 errors 1 warnings 1 info

SPECTRAL

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Microsoft Azure Front Door Authentication

oauth2 · 1 scheme

SECURITY

Microsoft Azure Front Door Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Microsoft Azure Front Door Scopes

1 scope · implicit

1 scopes

SCOPES

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Microsoft Azure Front Door Agentic Access

7 operations · 3 acting

AGENTIC

Resources

Get Started 1

Portal, sign-up, and the first successful call

Portal

Portal

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

LlmsText

LlmsText

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

OAuthScopes

OAuthScopes

Operate 2

Status, limits, changes, and where to get help

RateLimits

RateLimits

Support

Support

Commercial 5

Pricing, plans, and the legal terms of use

FinOps

Plans

Pricing

TermsOfService

PrivacyPolicy

Company 1

The organization behind the API

Website

Website

Other 2

Properties that don't map to a standard resource type

VendorFacets

VendorFacets

CapabilityMap

CapabilityMap

Source (apis.yml)

aid: microsoft-azure-front-door
name: Azure Front Door
description: Azure Front Door Service enables you to define, manage, and monitor the global routing for your web traffic.
  The REST API supports configuring routing rules, backend pools, health probes, caching policies, and WAF rules for secure
  and performant application delivery at the edge.
type: Index
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: paid
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Paid · Self-serve signup
  confidence: medium
  source:
  - finops
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/microsoft-azure-front-door.png
tags:
- CDN
- Edge
- Global Routing
- Load Balancing
- WAF
url: https://raw.githubusercontent.com/api-evangelist/microsoft-azure-front-door/refs/heads/main/apis.yml
created: '2026-03-13'
modified: '2026-05-19'
specificationVersion: '0.23'
apis:
- aid: microsoft-azure-front-door:microsoft-azure-front-door-operations-api
  name: Azure Front Door Operations API
  description: Operations operations
  humanURL: https://learn.microsoft.com/en-us/rest/api/frontdoor/
  baseURL: https://management.azure.com/
  tags: []
  tags_raw:
  - Operations
  properties:
  - type: OpenAPI
    url: openapi/microsoft-azure-front-door-operations-api-openapi.yml
  - type: Documentation
    url: https://learn.microsoft.com/en-us/rest/api/frontdoor/
- aid: microsoft-azure-front-door:microsoft-azure-front-door-profiles-api
  name: Azure Front Door Profiles API
  description: Profiles operations
  humanURL: https://learn.microsoft.com/en-us/rest/api/frontdoor/
  baseURL: https://management.azure.com/
  tags:
  - Profiles
  properties:
  - type: OpenAPI
    url: openapi/microsoft-azure-front-door-profiles-api-openapi.yml
  - type: Documentation
    url: https://learn.microsoft.com/en-us/rest/api/frontdoor/
common:
- type: RateLimits
  url: rate-limits/microsoft-azure-front-door-rate-limits.yml
- type: FinOps
  url: finops/microsoft-azure-front-door-finops.yml
- type: VendorFacets
  url: vendor-facets/microsoft-azure-front-door-vendor-facets.yml
- type: Plans
  url: plans/microsoft-azure-front-door-plans-pricing.yml
- type: Website
  url: https://www.microsoft.com/
- type: CapabilityMap
  url: capabilities/microsoft-azure-front-door-capability-edges.yml
  name: Azure Front Door Business Capability Map
- type: AgenticAccess
  url: agentic-access/microsoft-azure-front-door-agentic-access.yml
- type: DomainSecurity
  url: security/microsoft-azure-front-door-domain-security.yml
- type: Authentication
  url: authentication/microsoft-azure-front-door-authentication.yml
- type: OAuthScopes
  url: scopes/microsoft-azure-front-door-scopes.yml
- type: GitHubOrganization
  url: https://github.com/Azure
- type: Portal
  url: https://portal.azure.com/
- type: Pricing
  url: https://azure.microsoft.com/en-us/pricing/
- type: TermsOfService
  url: https://www.microsoft.com/en-us/legal/terms-of-use
- type: PrivacyPolicy
  url: https://privacy.microsoft.com/en-us/privacystatement
- type: Support
  url: https://support.microsoft.com/
- type: LlmsText
  url: https://portal.azure.com/llms.txt
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
x-parent: microsoft-azure
x-relationship: product

Azure Front Door API — frequently asked questions

Does Azure Front Door have an API?

Yes. APIs.io lists 2 APIs from Azure Front Door, including Azure Front Door Operations API and Azure Front Door Profiles API.

Is there an OpenAPI specification for the Azure Front Door API?

Yes. APIs.io indexes 2 OpenAPI specifications for Azure Front Door, each linked for download from this page.

How do I authenticate with the Azure Front Door API?

Azure Front Door uses bearer-token authentication (oauth2 · 1 scheme). The details are profiled on APIs.io as Microsoft Azure Front Door Authentication.

Is the Azure Front Door API ready for AI agents?

Azure Front Door has a Kin Score of 38.5 out of 100 (thin) and an Agent Readiness score of 19.6 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/microsoft-azure-front-door"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/microsoft-azure-front-door/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/microsoft-azure-front-door/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

Azure Front Door

What this lets a business do 1

What adopting Azure Front Door moves on the Kin Score 0

Markets this provider is in provisional

Standards implemented 2

APIs 2

Open Collections 3

Azure Front Door API pricing

Rate limits

Pricing Plans 1

Rate Limits 1

FinOps 1

Spectral Rules 1

Security Posture 2

Scopes 1

Agentic Access 1

Get Started 1

Agent Surfaces 2

Build 1

Access & Security 3

Operate 2

Commercial 5

Company 1

Other 2

Source (apis.yml)

Azure Front Door API — frequently asked questions

Does Azure Front Door have an API?

Is there an OpenAPI specification for the Azure Front Door API?

How do I authenticate with the Azure Front Door API?

Is the Azure Front Door API ready for AI agents?

MCP server

Tools for providers

Call it yourself

Get an API key