App Service Environment reference for DoD customers connected to the DISA CAP
This article explains the baseline configuration of an App Service Environment (ASE) with an internal load balancer (ILB) for customers who use the Defense Information Systems Agency (DISA) Cloud Access Point (CAP) to connect to Azure Government.
You've deployed an ASE with an ILB and have implemented an ExpressRoute connection to the DISA CAP.
When you create the ASE via the Azure Government portal, a route table with a default route of 0.0.0.0/0 and next hop “Internet” is created. However, since DISA advertises a default route out of the ExpressRoute circuit, the User Defined Route (UDR) should either be deleted, or you should remove the default route to Internet.
You'll need to create new routes in the UDR for the management addresses to keep the ASE healthy. For Azure Government ranges, see App Service Environment management addresses.
- 126.96.36.199/32 -> Internet
- 188.8.131.52/32 -> Internet
- 184.108.40.206/32 -> Internet
- 220.127.116.11/32 -> Internet
- 18.104.22.168/32 -> Internet
- 22.214.171.124/32 -> Internet
- 126.96.36.199/32 -> Internet
- 188.8.131.52/32 -> Internet
Make sure the UDR is applied to the subnet your ASE is deployed to.
Network security group (NSG)
The ASE will be created with the following inbound and outbound security rules. The inbound security rules must allow ports 454-455 with an ephemeral source port range (*). The following images describe the default NSG rules generated during the ASE creation. For more information, see Networking considerations for an App Service Environment.
Depending on the storage you use, you need to enable service endpoints for Azure SQL Database and Azure Storage to access them without going back to the DISA CAP. You also need to enable the Event Hubs service endpoint for ASE logs. For more information, see Networking considerations for App Service Environment: Service endpoints.
How long will it take for configuration changes to take effect? Some configuration changes may take time to become effective. Allow several hours for changes to routing, NSGs, ASE Health, and so on, to propagate and take effect. Otherwise, you can optionally reboot the ASE.
Azure Resource Manager template sample
To deploy non-RFC 1918 IP addresses in the portal, you must pre-stage the VNet and subnet for the ASE. You can use an Azure Resource Manager template to deploy the ASE with non-RFC1918 IPs as well.
This template deploys an ILB ASE into the Azure Government or DoD regions.
- Sign up for Azure Government trial
- Acquiring and accessing Azure Government
- Ask questions via the azure-gov tag on StackOverflow
- Azure Government blog
- Azure Government overview
- Azure Government security
- Azure Government compliance
- Secure Azure computing architecture
- Azure Policy overview
- Azure Policy regulatory compliance built-in initiatives
- Azure Government services by audit scope
- Azure Government isolation guidelines for Impact Level 5 workloads
- Azure Government DoD overview
Submit and view feedback for