Incorp'd Deep's comments

Author: dlepow

articles/container-instances/container-instances-troubleshooting.md

@@ -7,14 +7,16 @@ manager: gwallace
 
 ms.service: container-instances
 ms.topic: article
-ms.date: 04/25/2019
+ms.date: 09/25/2019
 ms.author: danlep
 ms.custom: mvc
 ---
 
 # Troubleshoot common issues in Azure Container Instances
 
-This article shows how to troubleshoot common issues for managing or deploying containers to Azure Container Instances. See also [Frequently asked questions](container-instances-faq.md).
+This article shows how to troubleshoot common issues for managing or deploying containers to Azure Container Instances. See also [Frequently asked questions](container-instances-faq.md). 
+
+If you need additional support, see available **Help + support** options in the [Azure portal](https://portal.azure.com/?#blade/Microsoft_Azure_Support/HelpAndSupportBlade).
 
 ## Naming conventions
 
@@ -198,19 +200,19 @@ Azure Container Instances does not expose direct access to the underlying infras
 
 ## Container group IP address may not be accessible due to mismatched ports
 
-Azure Container Instances does not currently support port mapping like with regular docker configuration, however this fix is on the roadmap. If you find a container group's IP address is not accessible when you believe it should be, ensure you have configured your container image to listen to the same ports you expose in your container group with the `ports` property.
+Azure Container Instances doesn't yet support port mapping like with regular docker configuration. If you find a container group's IP address is not accessible when you believe it should be, ensure you have configured your container image to listen to the same ports you expose in your container group with the `ports` property.
 
 If you want to confirm that Azure Container Instances can listen on the port you configured in your container image, test a deployment of the `aci-helloworld` image that exposes the port. Also run the `aci-helloworld` app so that it listens on the port. `aci-helloworld` accepts an optional environment variable `PORT` to override the default port 80 it listens on. For example, to test port 9000:
 
-1. Set up the container group to expose port 9000, and pass port 9000 as the value of the environment variable. Substitute a unique value of `dns-label-name`:
+1. Set up the container group to expose port 9000, and pass the port number as the value of the environment variable:
     ```azurecli
     az container create --resource-group myResourceGroup \
     --name mycontainer --image mcr.microsoft.com/azuredocs/aci-helloworld \
-    --dns-name-label porttest001 --ports 9000 \
+    --ip-address Public --ports 9000 \
     --environment-variables 'PORT'='9000'
     ```
-1. Find the FQDN or IP address of the container group in the command output of `az container create`.
-1. After the container is provisioned successfully, browse to the FQDN and port of the container app in your browser, for example: `http://porttest001.eastus.azurecontainer.io:9000`. 
+1. Find the IP address of the container group in the command output of `az container create`. Look for the value of **ip**. 
+1. After the container is provisioned successfully, browse to the IP address and port of the container app in your browser, for example: `192.0.2.0:9000`. 
 
     You should see the "Welcome to Azure Container Instances!" message displayed by the web app.
 1. When you're done with the container, remove it using the `az container delete` command: