The customer's Azure environment is set up as follows: Application Gateway > VM-series > Internal Load Balancer > IaaS VNET.
(See below diagram)
Traffic flows correctly at the current moment with all traffic being NAT'd to the Application Gateway public address. I think the loadbalancers are doing the NAT, the Vm-series is simply passing traffic between them.
There is one device in the IaaS VNet that we would like to have it's own public static NAT. Ex: All addresses are automatically NAT'd to 184.108.40.206 right now via the load balancers, but we'd like this specific resource to be NAT'd to 220.127.116.11. The way to go about this is different than in a standard datacenter because of the Azure loadbalancers on either side of the VM-series.
I've included a diagram of the relevant pieces of the environment and hidden the IP addresses for privacy reasons.
Thank you for the assistance.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!