Need JA4 enabled on our Front Door WAF

Hi @ EricInIT-1,

Welcome to the Microsoft Q&A Platform.

The “JA4/ClientFingerprint” flag isn’t something you can flip on directly in the portal today, it’s part of an internal preview feature for Bot Manager and client fingerprinting.

To move this forward, we’ll need a bit more info so we can either enable it on our side or steer you to the right process:

1. Which Front Door tier are you on—Standard or Premium?
2. Are you configuring WAF via the Azure portal, ARM template/CLI?
3. Can you share the exact WAF policy JSON (or screenshots) where you’re expecting the Client Fingerprint setting?
4. What region is your Front Door deployed in, and do you have a support ticket opened for this feature?
5. Have you already enabled Bot Protection (Bot Manager 1.1) and tried the JavaScript Challenge action under that rule set?

Hi Vellpu,

I appreciate your response and will answer but one of my engineers upgraded our support to Production and opened a ticket. It is unfortunate that this feature is effectively behind a support paywall.

1. Premium
2. We typically use the portal and CLI. I understand we may need to use an ARM template and are OK should we need to.
3. We havent defined that yet. We also use AWS CloudFront and have had much more success blocking scrapers using JA3/4 fingerprinting so we want this functionality or will have to migrate.
4. FrontDoor is Global but the resources we are protecting are in West 2 and East. We opened a ticket, but the response is that we need to schedule a call. We will follow through on that route.
5. Yes.