Static private IP for Azure Container Instance

Hello Alexander Lapin, If an answer has been helpful, please consider accepting the answer to help increase visibility of this question for other members of the Microsoft Q&A community. If not, please let us know what is still needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!

Thanks for your reply. Apparently I didn't describe the problem very clearly. I have an instance of a container (ACI), I include it in a virtual network, which automatically assigns it an internal dynamic IP address; when the container is rebooted or turned off and on, this address may change to another. How can I make sure it doesn't change?

Hello Alexander Lapin, Thankyou for replying back. Create a subnet with a delegated prefix of /29 or larger. You can do this using the Azure portal, Azure CLI, or Azure PowerShell. Deploy your container group to the subnet you created in step 1. You can do this using the Azure portal, Azure CLI, or Azure PowerShell. Assign a static private IP address to your container group. You can do this using the Azure portal, Azure CLI, or Azure PowerShell. Here's an example command using the Azure CLI:

az container update \
    --resource-group <resource-group-name> \
    --name <container-name> \
    --image <container-image> \
    --vnet <vnet-name> \
    --subnet <subnet-name> \
    --subnet-ip-address <reserved-ip-address> \
    --restart-policy Always

az container --update command doesn't exist...

Hello Alexander Lapin, We noticed that you rated an answer as not helpful. I have provided an answer with the relevant details to make this a positive experience for you. i. Azure Container Instances do not natively support assigning static IP addresses directly to individual containers. ii.Instead, one can mitigate this limitation by reserving a block of IP addresses within the subnet where ACI instances operate. iii. This reservation ensures a stable pool of IP addresses, thereby minimizing significant variations in dynamic allocations. iv. By reserving IP addresses within the subnet, organizations can establish a consistent and predictable range for their ACI instances. v. This predictability proves invaluable for implementing robust access control measures, such as IP-based whitelisting and access restriction policies. vi. The establishment of a predictable IP range through reserved addresses contributes to a more resilient and controlled environment by ensuring reliable enforcement of security measures. We value your feedback. If my answer is helpful, would you be so kind to re-evaluate your feedback, accept my answer and upvote the same please.