Route Logic App Standard traffic through your Virtual Network through specified static public IP address(es).
This approach will not work with Logic App Consumption
1. Create Virtual Network
2. Create Logic App Standard
3. Create a workflow within the Logic App and set up an outbound HTTP action.
This external website returns the IP address of the caller. This step mimics the HTTP trigger function mentioned here:
Control Azure Functions outbound IP with an Azure virtual network NAT gateway | Microsoft Learn
4. Integrate the Virtual Network Integration on the Logic App and select the VNET/subnet that was created in Step 1.
5. (Optional) Test without the NAT Gateway Linked
Navigate to the Networking blade of the Logic App and click on the list of Outbound IP addresses to view the full set. The IP address returned is part of the list.
6. Create NAT Gateway and integrate it to the Virtual Network
These below steps can be done during or after creation:
Check to see what the IP address has been created. The Outbound IP address is this case is 20.115.24.20. This is the static IP address. You can also create more IP addresses.
7. Test with the NAT Gateway Linked
Logic Apps Standard can be integrated with a Virtual Network, which in turn can be integrated with a NAT Gateway. This helps with routing traffic on built-in connectors through the NAT Gateway, using the static IP(s) defined as the outbound IP. In this tutorial, I have created only 1 static IP, but it is possible to create more on the NAT Gateway, which will allow the Logic App's traffic to route through either one.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.