title: Assign Static Public Address to Azure Container Instance deployment
body: <h1>Context</h1>
  <p>Working on a project to deploy a restful API application and seperate TCP service to an Azure Container Instance. The TCP service requires a static Ipv4 address due to legacy reasons.</p>
  <p><a href="https://i.stack.imgur.com/T5BxS.png" rel="noreferrer"><img src="https://i.stack.imgur.com/T5BxS.png" alt="ContextDiagram" /></a></p>
  <h1>Question</h1>
  <p>I am attempting to isolate my options to assign as static public IP address to the TCP service hosted on an Azure Container Instance. What are the options ?</p>
  <h1>Tested</h1>
  <ol>
  <li><p>Deployed Azure Application Gateway with a static public IP address. The App Gateway allows backend pool to be directed to an IP or FQDN endpoint. This appears to be operational (see diagram). Altough the options from the backend pool appear to allow HTTP and HTTPS only , not custom ports. Maybe this can be manipulated if the TCP service can listen on 80 and web API on 443. App gateway is Layer 7 resource for HTTP and HTTPS traffic only.</p>
  </li>
  <li><p>Azure Load Balancer. Could only be directed at the VM, Availablity Set or VM Scale Set.</p>
  </li>
  <li><p>Assign static address to the Resource. Not allowed for Container Instances.</p>
  </li>
  <li><p>Traffic Manager. Doesn't appear to be the correct type of resource for this deployment.</p>
  </li>
  </ol>
  <p>See diagram. The Container Instances for API and TCP SERVICE have the same private IP address when I query via a BASH session. Suggested they are hosted on the same host (labled as Container Group) in the attached diagram. Not sure if that is the correct label sorry, I am new to Container tech.</p>
  <p>Thank you for any advice.
  Scott</p>