VPN connections

This topic addresses frequently asked questions about the Episerver Customer-Centric Digital Experience Platform (DXP) and VPN connections. 

How it works

The Azure App Service connects through point-to-site VPN to the Azure Virtual Network Gateway (vnet). This has a Site-to-site VPN connection to your local network gateway which your on-premise resources such as web and database servers are connected to.

Frequently asked questions

• Is the VPN connection one-way from DXP to on-premises resources?

  Yes. The limitation is due to Azure App Services IP assignments. Accessing an Azure App Service on the internal IP that gets assigned to the app service when connected to a VPN is not possible.

• Is my VPN Gateway a compatible device for route-based VPN?

  See About VPN devices and IPsec/IKE parameters for Site-to-Site VPN Gateway connections.

• Can I use my own DNS server that is an on-premises single VPN-established connection?

  Yes. Once the VPN connection has been successfully configured on both sides, Episerver can help you configure your app services running in DXP to use DNS servers hosted in your on-premise solution. This should be tested on Integration and/or Preproduction before applied in Production. Note that this requires a restart of your app service.

• Can I set up multiple VPN connections within the same DXP package?

  Yes, at an additional cost. However, each environment (Integration, Preproduction & Production) can be connected to the same VPN connection (virtual network gateway).

Related topics

• VPN Gateway documentation
• About VPN Gateway configuration settings
• About VPN devices and IPsec/IKE parameters for Site-to-Site VPN Gateway connections.
• About cryptographic requirements and Azure VPN gateways

Last updated: Apr 02, 2020