I don't know if the issue is one of time (i.e. it'll get added eventually) or that the Windows network stack just simply isn't able to support giving a container/task its own ip address - does anyone have any insight on this?
From my perspective, having the dedicated ip means each task can have a dedicated security group thereby providing a network level security layer between tasks (very useful in multitenant environments).
Thanks