Avoid default 403 when IP Restrinctions are configured on App Services
Currently, when you configure ip restrinctions on App Services, the App Service is able to return the 403 default error page. It could be a proxy, I think. But many IT managers (clients, because I am an Azure consultant) gave me this idea.
It could be better if our web applications does not return the 403 default page when the ip source does not in the whitelist
This is the default 403 web page generated by Microsoft, when we have configured ip restrictions:
Error 403 - This web app is stopped.
The web app you have attempted to reach is currently stopped and does not accept any requests. Please try to reload the page or visit it again soon.
If you are the web app administrator, please find the common 403 error scenarios and resolution here. For further troubleshooting tools and recommendations, please visit Azure Portal.