It's working all fine except in web server logs it's showing ForitWeb internal IP, not Client Public IP. I have tried enabling the option from Server Policy, but after enabling that I can't connect to the WebServer. Is the issue related to Azure Load Balancer which is doing the NAT? Wondering anyone deployed FortiWeb in Azure and can share something.
If you are enabling the client real IP option in the server policy, then you need to set FortiWeb as the default gateway on the backend server. Instead, you could configure FortiWeb to include X‑Forwarded-For in the HTTP header before traffic is generated to the backend server. for more information and configuration, please refer the following link: