Merge pull request #206067 from craigcaseyMSFT/vcraigcasey072222

Content refresh of container instances quickstart

Author: Stacyrch140

articles/container-instances/container-instances-quickstart-portal.md

@@ -6,7 +6,7 @@ ms.author: tomcassidy
 author: tomvcassidy
 ms.service: container-instances
 services: container-instances
-ms.date: 06/17/2022
+ms.date: 07/26/2022
 ms.custom: mvc, devx-track-js, mode-ui
 ---
 
@@ -26,34 +26,51 @@ If you don't have an Azure subscription, create a [free account][azure-free-acco
 
 ## Create a container instance
 
-Select the **Create a resource** > **Containers** > **Container Instances**.
+On the Azure portal homepage, select **Create a resource**.
 
-:::image type="content" source="media/container-instances-quickstart-portal/qs-portal-01.png" alt-text="Begin creating a new container instance in the Azure portal":::
+:::image type="content" source="media/container-instances-quickstart-portal/quickstart-portal-create-resource.png" alt-text="Screenshot showing how to begin creating a new container instance in the Azure portal.":::
 
-On the **Basics** page, enter the following values in the **Resource group**, **Container name**, and **Container image** text boxes. Leave the other values at their defaults, then select **OK**.
+Select **Containers** > **Container Instances**.
+
+:::image type="content" source="media/container-instances-quickstart-portal/qs-portal-01.png" alt-text="Screenshot showing how to select a new container instance that you want to create in the Azure portal.":::
+
+On the **Basics** page, choose a subscription and enter the following values for **Resource group**, **Container name**, **Image source**, and **Container image**.
 
 * Resource group: **Create new** > `myresourcegroup`
 * Container name: `mycontainer`
 * Image source: **Quickstart images**
-* Container image: `mcr.microsoft.com/azuredocs/aci-helloworld` (Linux)
+* Container image: `mcr.microsoft.com/azuredocs/aci-helloworld:latest` (Linux)
 
 :::image type="content" source="media/container-instances-quickstart-portal/qs-portal-03.png" alt-text="Configuring basic settings for a new container instance in the Azure portal":::
 
-For this quickstart, you use default settings to deploy the public Microsoft `aci-helloworld` image. This sample Linux image packages a small web app written in Node.js that serves a static HTML page. You can also bring your own container images stored in Azure Container Registry, Docker Hub, or other registries.
+> [!NOTE]
+> For this quickstart, you use default settings to deploy the public Microsoft `aci-helloworld:latest` image. This sample Linux image packages a small web app written in Node.js that serves a static HTML page. You can also bring your own container images stored in Azure Container Registry, Docker Hub, or other registries.
+
+Leave the other values as their defaults, then select **Next: Networking**.
 
 On the **Networking** page, specify a **DNS name label** for your container. The name must be unique within the Azure region where you create the container instance. Your container will be publicly reachable at `<dns-name-label>.<region>.azurecontainer.io`. If you receive a "DNS name label not available" error message, try a different DNS name label.
 
+An auto-generated hash is added as a DNS name label to your container instance's fully qualified domain name (FQDN), which prevents malicious subdomain takeover. Specify the **DNS name label scope reuse** for the FQDN. You can choose one of these options:
+
+* Tenant
+* Subscription
+* Resource Group
+* No reuse
+* Any reuse (This option is the least secure.)
+
+For this example, select **Tenant**.
+
 :::image type="content" source="media/container-instances-quickstart-portal/qs-portal-04.png" alt-text="Configuring network settings for a new container instance in the Azure portal":::
 
-Leave the other settings at their defaults, then select **Review + create**.
+Leave all other settings as their defaults, then select **Review + create**.
 
 When the validation completes, you're shown a summary of the container's settings. Select **Create** to submit your container deployment request.
 
 :::image type="content" source="media/container-instances-quickstart-portal/qs-portal-05.png" alt-text="Settings summary for a new container instance in the Azure portal":::
 
-When deployment starts, a notification appears to indicate the deployment is in progress. Another notification is displayed when the container group has been deployed.
+When deployment starts, a notification appears that indicates the deployment is in progress. Another notification is displayed when the container group has been deployed.
 
-Open the overview for the container group by navigating to **Resource Groups** > **myresourcegroup** > **mycontainer**. Take note of the **FQDN** (the fully qualified domain name) of the container instance, as well its **Status**.
+Open the overview for the container group by navigating to **Resource Groups** > **myresourcegroup** > **mycontainer**. Make a note of the **FQDN** of the container instance and its **Status**.
 
 :::image type="content" source="media/container-instances-quickstart-portal/qs-portal-06.png" alt-text="Container group overview in the Azure portal":::
 
@@ -67,7 +84,7 @@ Congratulations! By configuring just a few settings, you've deployed a publicly
 
 Viewing the logs for a container instance is helpful when troubleshooting issues with your container or the application it runs.
 
-To view the container's logs, under **Settings**, select **Containers**, then **Logs**. You should see the HTTP GET request generated when you viewed the application in your browser.
+To view the container's logs, under **Settings**, select **Containers** > **Logs**. You should see the HTTP GET request generated when you viewed the application in your browser.
 
 :::image type="content" source="media/container-instances-quickstart-portal/qs-portal-11.png" alt-text="Container logs in the Azure portal":::