Creating/using app service environment both internally and externallly

Question

I noticed internal and external access options while creating app service envriuonment.

what if I want to access both internal and external as well, how can achieve that?

Answer 1

To achieve both internal and external access in an Azure App Service Environment (ASE), you can:

1. Set up an External ASE to ensure it's accessible over the internet.
2. Configure a Private Endpoint for internal access, enabling secure access within your Virtual Network (VNet).

This setup allows the ASE to be accessible externally while also providing a private, secure pathway for internal access, leveraging Azure's networking capabilities to manage both access paths efficiently.

Answer 2

@Varma Thanks for your follow-up questions on this. sorry for the confusion here.

Yes, you can have only either internal or external access when you are creating ASE

• External: This type of deployment exposes the hosted apps by using an IP address that is accessible on the internet.
• Internal load balancer: This type of deployment exposes the hosted apps on an IP address inside your virtual network. The internal endpoint is an internal load balancer.

Regardless of the deployment type, all App Service Environments have a public virtual IP (VIP). This VIP is used for inbound management traffic, and as the address when you're making calls from the App Service Environment to the internet. Such calls leave the virtual network through the VIP assigned for the App Service Environment.

Refer to this Networking consideration for App service documentation for more information.