I am creating an Azure Virtual Desktop implementation. What is the correct way to make sure that the AVD's use a static IP address for outgoing connections?
Is it by creating a NAT Gateway?
- Why not use DNS?vidarlo– vidarlo2023-07-26 13:53:03 +00:00Commented Jul 26, 2023 at 13:53
- 2No, this is for outbound purposes. For example, a user logged in to an Azure Virtual Desktop session accesses a web app. I want to whitelist the IP address the user is presenting, so I need that IP address to be static.longneck– longneck2023-07-26 13:57:13 +00:00Commented Jul 26, 2023 at 13:57
- 1I would suggest adding that to the question.vidarlo– vidarlo2023-07-26 14:01:23 +00:00Commented Jul 26, 2023 at 14:01
Add a comment |
1 Answer
If you are talking about the outbound IP then there are several different methods to ensure traffic from an Azure vNet uses a consitent IP, pick the one that works best for you:
- Assigning a Public IP to the VM, which will be used for outbound traffic. Probably not workable for AVD
- Put VMs behind an Azure load balancer and use the outbound rules to define outbound IP
- Azure vNet NAT Gateway - defines a static outbound IP for all traffic on a vnet, probably the simplest option for your scenario
- Azure Firewall (or other FW device) - all traffic is routed out the firewall, and will use this as the outbound IP.
See here for more details.
answered Jul 31, 2023 at 13:13
