Use the same exposed public ip for outbound traffic start from the containergroup
I have some question related to the Public IP used by container group create from Azure Container Instance. Actually the container group can expose public ip (set ipAddress.type = “Public”) which is used to access from external, but for the traffic start from the container group I found it does use the assigned exposed public ip. I’d like to check if possible to using the same exposed public ip for the outbound traffic starting from the container group ? if not, how the outbound traffic public ip is assigned to the container group ? Thanks previously for your kindly response.
We recently published guidance on using Azure Firewall to achieve this for ACI deployments in a Vnet. Would appreciate your feedback on this experience:
Todor Popov commented
This is a bad work around.
Michael Prado commented
It's been two years, this seems like a very desired feature.
Stephane Lapointe commented
Would like to have a single ip address for both inbound and outbound. It would greatly facilitate ip whitelisting for outbound traffic out of container instances.