This article will assist you in setting up a VPN connection between your Azure network to your MuleSoft VPC
• Make sure to select a VpnGw1 SKU or higher. I will use the default in this example
• Tunnels with a basic SKU are not supported.
• Once deployed write down the public IP address for future reference
Fill in the VPN creation form with the following information:
Name: Choose a name for your VPN. Example: mulesoft-azure-nonprod-vpn
VPC: Select the Cloudhub VPC that you would like to connect to Azure
Remote IP address: The Public IP address of the Azure VPN that you wrote down earlier
Static Routes: Add one route per each IP address space of the Azure Virtual Network
Tunnel Configuration: Leave it as automatic
- Go to Runtime Manager - Private Space - <name of your PS> - Create Connection - VPN - Enter Name of your VPN - Next
- Remote IP: The Public IP address of the Azure VPN that you wrote down earlier
- Leave ASN default
- Advanced Options - uncheck "Automatic Tunnel Initiation"
IMPORTANT!!!: For Cloudhub 2.0 Private Spaces please make sure to go into Advanced Options and UNCHECK "Automatic Tunnel Initiation"
Name: Add a new for each env tunnel
IP address: Enter the IP of the first tunnel
Address Spaces: CIDR of the Cloudhub VPC
Virtual Network Gateway: The VPN gateway on your Azure Virtual Network
Local Network Gateway: The LNG Created for the first tunnel
Shared Key (PSK): The PSK you wrote down from Cloudhub page
IPsec/IKE Policy: Custom (use any approved by your networking team but the screenshot parameters should work)
IMPORTANT: Make sure a value is selected for PFS Group
IPsec SA lifetime in seconds: 3000 (IMPORTANT: keep this value as 3000)
DPD timeout in seconds: 30
Connection Mode: InitiatorOnly (IMPORTANT)
https://help.salesforce.com/s/articleView?id=001115029&type=
Deploy net-tools app and use socket connection to a host in Azure.
NOTE: ping is not supported in Cloudhub 2.0
005103361

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.