Yes, this is by design so that you can access your web apps privately rather than over the public Internet. What is it that you are trying to achieve?
https://learn.microsoft.com/en-us/azure/app-service/networking/private-endpoint
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
After enabling the azure web app private endpoint I am not able to access web applications publically.
Yes, this is by design so that you can access your web apps privately rather than over the public Internet. What is it that you are trying to achieve?
https://learn.microsoft.com/en-us/azure/app-service/networking/private-endpoint
Yes, PE is the most secure method to connect your source (App Service, Database etc.). I guess you want to secure your application via using 'Private Endpoints' but there is a critical mistake because PE is only accessible with host settings and credentials. So, if you want to access your application publically, you can't use PE.
Scenario :
Let's say, you have an application and API. So you can configure PE between your API and application with VN and Bastion Host. You can configure your application settings by PE and connect your API only with PE (not publically). At the end of the day, if you want to access your application publically you can't use PE, because PE ignores any public access. (such as Database with PE)
Best Practices :
If your application is not able to access publically, but also you want to access your application, you can use 'Virtual Network' in Azure. If you're not working on 'Production Environment' I don't recommend using private endpoints.
Bests,
Atakan ATALI