Mr. Brooks' Blog

There’s a unique identifier under the trackingReference that shows all the matches that have increased the anomaly score eventually causing it to be blocked. https://learn.microsoft.com/en-us/azure/web-application-firewall/ag/web-application-firewall-troubleshoot#understanding-waf-logs More details on how.

There are scenarios where a reboot of the underlying instance may be required to recover the state of the OS or application for issues such as temp worker space.

I often come across issues where we need to inspect the request headers that an app services is receiving. Without code modifications its often difficult to achieve these results..