Hi dough_boat,
I understood you are looking for a way to whitelist your Azure VM on this 3rd party service. I think there are some services that you can test, but It will also depend on how this external service is dealing with the traffic :
- You can use Azure NAT Gateway to let all instances in a private subnet connect outbound to the internet while remaining fully private. (https://learn.microsoft.com/en-us/azure/nat-gateway/), I think this could be the best option for you (https://learn.microsoft.com/en-us/azure/nat-gateway/quickstart-create-nat-gateway-portal)
- This could be a second good option Azure Labs provides a way to find the specific public IP address used by a lab in Azure Lab Services. You can use these IP addresses to configure your firewall settings and specify inbound and outbound rules to enable lab users to connect to their lab virtual machines. (https://learn.microsoft.com/en-us/azure/lab-services/how-to-configure-firewall-settings)
- Last option from my side is Azure Firewall that can help with outbound connectivity with specific public IPs. However, it’s not possible to NAT certain subnets through a specific public IP on the firewall. Azure Firewall randomly selects the source public IP address to use for a connection. (https://learn.microsoft.com/en-us/answers/questions/850707/azure-firewall-outbound-through-specific-public-ip)
These options will depend on how this 3rd party service whitelist the communication for TCP traffic. Besides that consideration and because It is a development environment I recommend you start with Nat Gateway for a quick win.
Cheers,
Luis
If the information helped address your question, please Accept the answer.