The firewall rule exists and looks correct, but traffic still reaches the service.
There are no obvious misconfigurations, yet enforcement doesn’t match expectations.
I’m trying to understand whether this is a rule priority issue or something else.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
The firewall rule exists and looks correct, but traffic still reaches the service.
There are no obvious misconfigurations, yet enforcement doesn’t match expectations.
I’m trying to understand whether this is a rule priority issue or something else.
Most cloud firewalls evaluate rules in a defined order, and earlier allow rules can override later deny rules. Direction also matters—outbound rules are evaluated separately from inbound ones.
It’s common to focus on the presence of a rule without checking how it’s evaluated in context. Overlapping rules, defaults, or inherited policies can all affect the outcome.
Takeaway: Firewall behavior depends on evaluation order, not just rule intent.