<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>WAF on The David Page</title><link>https://thedavidpage.pages.dev/tags/waf/</link><description>Recent content in WAF on The David Page</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sun, 02 Aug 2026 09:00:00 +0700</lastBuildDate><atom:link href="https://thedavidpage.pages.dev/tags/waf/index.xml" rel="self" type="application/rss+xml"/><item><title>"Policy ArmResourceId has incorrect formatting" Has Nothing to Do With ARM Resource IDs</title><link>https://thedavidpage.pages.dev/posts/cloud/azure/front-door/waf-policy-arm-resource-id-formatting-error/</link><pubDate>Sun, 02 Aug 2026 09:00:00 +0700</pubDate><guid>https://thedavidpage.pages.dev/posts/cloud/azure/front-door/waf-policy-arm-resource-id-formatting-error/</guid><description>&lt;p&gt;&lt;strong&gt;&lt;code&gt;Policy ArmResourceId has incorrect formatting&lt;/code&gt; — an Azure CLI error message that cost me a whole debugging session, when the real reason was just a hyphen in the policy name.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Hi everyone 👋&lt;/p&gt;
&lt;p&gt;Setting up an Azure Front Door WAF Policy through the CLI, I ran into an error that — as it turns out — a lot of other people have been hitting for over three years, ever since it was first reported back in December 2022.&lt;/p&gt;</description></item></channel></rss>