After a waf policy deployed on a exchange service, it interrupts. Some users complain that we can not connect to exchange server and outlooks are disconnected. Any experience with this issue?
Have you checked the ASM Event Logs (Request Logs) to see why the requests are being rejected? A little more info is needed to help with a possible explanation.
Was a full policy activated, or did you do tuning on an already existing policy?
In the first case, Traffic Learning suggestions might help you understand which signatures/attack vectors are frequently matched and you might need to disable some Blocking feature on those requests.
In the second case, reviewing policy audit log might help you understand what edit triggered service disruption and you can do some fine tuning.
