Your company offices in Montreal, Seattle, and Paris each send outbound traffic from fixed public IP addresses. Front Door FD1 uses a WAF policy Policy1 that contains Rule1 enforcing a rate limit of 100 requests for traffic originating from Montreal. You must enforce the same 100-request rate limit for traffic that originates from each of the other offices as well. What should you change to apply the rate limit for each office?

Modifying the conditions of Rule1 is the correct approach because rate limits in Azure Front Door WAF policies are applied based on matching conditions. To apply the same rate limit to traffic from Seattle and Paris, you need to add their respective fixed public IP addresses (or IP ranges) to the existing conditions of Rule1. This ensures that the single rate limit rule applies to all specified source locations. Modifying the rate limit threshold would change the 100-request limit itself, not expand its scope. Creating two additional associations would be for associating the WAF policy with different Front Door frontends or routing rules, not for modifying the scope of a specific rule within the policy. Modifying the rule type would change whether it's a rate limit rule, a custom rule, or a managed rule, which is not the goal here.