Microsoft Azure WebApplicationFirewallManagement

Name: WebApplicationFirewallManagement API
Brand: WebApplicationFirewallManagement
Availability: InStock

★ Only Publicly Available OpenAPI DocumentSecurityThreat Detectionoauth25 EndpointsREST

For Agents

Manage Azure Front Door Web Application Firewall policies and list available managed rule sets so agents can lock down web traffic against OWASP-style threats.

Use for: Create a Front Door WAF policy with the default managed rule set, List all WAF policies in resource group prod-rg, Get the current rules on WAF policy app-waf-prod, Delete an unused Front Door WAF policy

Not supported: Does not handle Application Gateway WAF, network DDoS protection, or backend application code - use for Front Door WAF policy and managed rule set management only.

The Azure WebApplicationFirewallManagement API manages Azure Front Door Web Application Firewall (WAF) policies and inspects the managed rule sets that Microsoft maintains for blocking common web exploits. It exposes five management plane operations across three resource paths under Microsoft.Network, covering policy create-or-update, policy retrieval and deletion, listing policies in a resource group, and listing managed rule sets globally for a subscription. Use it to script WAF policy lifecycle, attach policies to Front Door endpoints, and audit which managed rule set versions are available before assigning them.

Install Jentic One Beta

Connect the WebApplicationFirewallManagement to your agent

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

Create or update Front Door WAF policies with custom rules and managed rule set assignments

Retrieve a Front Door WAF policy by name to inspect its current rule configuration

List all Front Door WAF policies within a resource group for audit and reporting

Delete a WAF policy when an application is decommissioned or migrated

GET STARTED

Start building with WebApplicationFirewallManagement API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use WebApplicationFirewallManagement API for, with concrete tasks.

★ Standardise WAF policy across environments

Define a single WAF policy template and roll it out consistently across dev, staging, and production resource groups using Policies_CreateOrUpdate. Agents can list managed rule sets, choose a specific Microsoft rule set version, and apply it to every Front Door instance so security posture stays consistent without manual portal clicks.

Create a WAF policy named app-waf-prod in resource group prod-rg with the latest Microsoft Default Rule Set in Prevention mode and verify the response status.

WAF policy audit and drift detection

Inventory all Front Door WAF policies in a subscription by listing policies per resource group, then read each one to compare its custom rules and managed rule set versions against an approved baseline. This makes it possible to surface drift and unauthorised rule disables before they affect production traffic.

List all Front Door WAF policies in resource group prod-rg, fetch each by name, and report any policy where mode is set to Detection instead of Prevention.

Decommission unused WAF policies

When an application is retired, an agent can delete its associated WAF policy with Policies_Delete after confirming no Front Door endpoint references it. The API supports straightforward lifecycle removal so operators can keep their security configuration tidy and avoid orphaned policies that drift out of date.

Delete the WAF policy named legacy-app-waf in resource group archive-rg and confirm the long-running operation succeeds.

Agent-driven web edge hardening

Allow an AI agent to harden a new web application by discovering managed rule sets, applying the recommended one, and attaching the resulting policy to a Front Door deployment, all through Jentic-mediated calls. This turns WAF setup into a tool an agent can invoke as part of a broader provisioning runbook.

Search Jentic for 'list azure front door waf managed rule sets', load the schema, execute it for the target subscription, and pick the latest stable rule set.

Key Endpoints

5 endpoints — the azure webapplicationfirewallmanagement api manages azure front door web application firewall (waf) policies and inspects the managed rule sets that microsoft maintains for blocking common web exploits.

METHOD

PATH

DESCRIPTION

PUT