In order to still expose the container, but control the IP's that are allowed access you will need to redeploy using the Virtual Network deployment feature : https://learn.microsoft.com/en-us/azure/container-instances/container-instances-vnet
Once the container instance is running in a Virtual Network, you can create a Network Security Group which will allow you to specify your IP rules.
Now that you have a privately running container, you just need to access it.
- This could be done privately through peering the Virtual Network to another Network which has connectivity to your client app/workstation.
- It could be to the internet, exposed via another Azure service.
For some example scenarios, see;
App GW : https://learn.microsoft.com/en-us/azure/container-instances/container-instances-application-gateway
Azure Firewall : https://learn.microsoft.com/en-us/azure/container-instances/container-instances-egress-ip-address