App Service Environments now support 2 new features that have been very highly requested. They now support both the ability to be deployed to resource manager (v2) virtual networks and also support the ability to be created with internal load balancer (ILB) instead of requiring a public IP.
Previously ASEs were only available on classic ASM based virtual networks and this is something that customers have been asking for.
Creating App Service Environment on ARM VNet
From the Portal when you create an ASE you will now have the option to select ARM VNets during the creating of the ASE.
Figure 1 – App Service Environment creation
In the following picture you can see that both ARM and Classic VNets are selectable with classic VNets clearly marked.
Figure 2 – App Service Environment ARM VNet
Creating App Service Environment on ARM ILB
After you have selected the VNet and subnet the next option that is available is whether or not you want to use an External or Internal Virtual IP (VIP).
When you select an Internal VIP you also need to specify a subdomain value, and once the App Service Environment
Figure 3 – App Service Environment Select VIP type
ASEs still require that premium instances are used and at least 2 Front End instances and 2 Worker instances are created.
Figure 4 – App Service Environment scale settings
Configuring certificate for Internal Load Balancer
After the ASE has finished deploying using an Internal Load Balancer (ILB), you will need to upload a certificate that is used for HTTPS traffic.
Figure 5 – App Service Environment ILB Certificate
After the certificate is loaded the ASE will finish scaling out and you will see that both the Front End and Worker Pools will have a status of Scaling.
After it has finished scaling the status will change to Ready.