Merge pull request #273534 from tomvcassidy/aciPowerShellUpdates

updates to powershell and aci quickstarts

Author: v-shils

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

@@ -6,15 +6,15 @@ ms.author: tomcassidy
 author: tomvcassidy
 ms.service: container-instances
 services: container-instances
-ms.date: 06/17/2022
+ms.date: 04/26/2024
 ms.custom: devx-track-azurepowershell, mvc, mode-api
 ---
 
 # Quickstart: Deploy a container instance in Azure using Azure PowerShell
 
 Use Azure Container Instances to run serverless Docker containers in Azure with simplicity and speed. Deploy an application to a container instance on-demand when you don't need a full container orchestration platform like Azure Kubernetes Service.
 
-In this quickstart, you use Azure PowerShell to deploy an isolated Windows container and make its application available with a fully qualified domain name (FQDN). A few seconds after you execute a single deployment command, you can browse to the application running in the container:
+In this quickstart, you use Azure PowerShell to deploy an isolated Windows container and make its application available with a fully qualified domain name (FQDN) and port. A few seconds after you execute a single deployment command, you can browse to the application running in the container:
 
 ![App deployed to Azure Container Instances viewed in browser][qs-powershell-01]
 
@@ -36,22 +36,28 @@ First, create a resource group named *myResourceGroup* in the *eastus* location
 New-AzResourceGroup -Name myResourceGroup -Location EastUS
 ```
 
+## Create a port for your container instance
+
+You can expose your containers to the internet by specifying one or more ports to open, a DNS name label, or both. In this quickstart, you deploy a container with a DNS name label so it's publicly reachable. In this guide, we'll do both, but first, you need to create a port object in PowerShell for your container instance to use.
+
+```azurepowershell-interactive
+$port = New-AzContainerInstancePortOject -Port 80 -Protocol TCP
+```
+
 ## Create a container group
 
-Now that you have a resource group, you can run a container in Azure. To create a container instance with Azure PowerShell, you'll first need to create a `ContainerInstanceObject` by providing a name and image for the container. In this quickstart, you use the public `mcr.microsoft.com/windows/servercore/iis:nanoserver` image. This image packages Microsoft Internet Information Services (IIS) to run in Nano Server.
+Now that you have a resource group and port, you can run a container that's exposed to the internet in Azure. To create a container instance with Azure PowerShell, you'll first need to create a `ContainerInstanceObject` by providing a name, image, and port for the container. In this quickstart, you use the public `mcr.microsoft.com/azuredocs/aci-helloworld` image.
 
 ```azurepowershell-interactive
-New-AzContainerInstanceObject -Name myContainer -Image mcr.microsoft.com/windows/servercore/iis:nanoserver
+New-AzContainerInstanceObject -Name myContainer -Image mcr.microsoft.com/azuredocs/aci-helloworld -Port @($port)
 ```
 
 Next, use the [New-AzContainerGroup][New-AzContainerGroup] cmdlet. You need to provide a name for the container group, your resource group's name, a location for the container group, the container instance you just created, the operating system type, and a unique IP address DNS name label.
 
-You can expose your containers to the internet by specifying one or more ports to open, a DNS name label, or both. In this quickstart, you deploy a container with a DNS name label so that IIS is publicly reachable.
-
 Execute a command similar to the following to start a container instance. Set a `-IPAddressDnsNameLabel` value that's unique within the Azure region where you create the instance. If you receive a "DNS name label not available" error message, try a different DNS name label.
 
 ```azurepowershell-interactive
-New-AzContainerInstanceObject -ResourceGroupName myResourceGroup -Name myContainerGroup -Location EastUS -Container myContainer -OsType Windows -IPAddressDnsNameLabel aci-demo-win
+$containerGroup = New-AzContainerInstanceObject -ResourceGroupName myResourceGroup -Name myContainerGroup -Location EastUS -Container myContainer -OsType Windows -IPAddressDnsNameLabel aci-quickstart-win -IpAddressType Public -IPAddressPort @($port)
 ```
 
 Within a few seconds, you should receive a response from Azure. The container's `ProvisioningState` is initially **Creating**, but should move to **Succeeded** within a minute or two. Check the deployment state with the [Get-AzContainerGroup][Get-AzContainerGroup] cmdlet:
@@ -60,12 +66,17 @@ Within a few seconds, you should receive a response from Azure. The container's
 Get-AzContainerGroup -ResourceGroupName myResourceGroup -Name myContainerGroup
 ```
 
-The container's provisioning state, fully qualified domain name (FQDN), and IP address appear in the cmdlet's output:
+You can also print out the $containerGroup object and filter the table for the container's provisioning state, fully qualified domain name (FQDN), and IP address.
+
+```azurepowershell-interactive
+$containerGroup | Format-Table InstanceViewState, IPAddressFqdn, IPAddressIP
+```
+
+The container's provisioning state, FQDN, and IP address appear in the cmdlet's output:
 
 ```console
 PS Azure:\> Get-AzContainerGroup -ResourceGroupName myResourceGroup -Name myContainerGroup
 
-
 ResourceGroupName        : myResourceGroup
 Id                       : /subscriptions/<Subscription ID>/resourceGroups/myResourceGroup/providers/Microsoft.ContainerInstance/containerGroups/myContainerGroup
 Name                     : myContainerGroup
@@ -86,9 +97,9 @@ State                    : Pending
 Events                   : {}
 ```
 
-Once the container's `ProvisioningState` is **Succeeded**, navigate to its `Fqdn` in your browser. If you see a web page similar to the following, congratulations! You've successfully deployed an application running in a Docker container to Azure.
+If the container's `ProvisioningState` is **Succeeded**, go to its FQDN in your browser. If you see a web page similar to the following, congratulations! You've successfully deployed an application running in a Docker container to Azure.
 
-![IIS deployed using Azure Container Instances viewed in browser][qs-powershell-01]
+![View an app deployed to Azure Container Instances in browser][./media/container-instances-quickstart/view-an-application-running-in-an-azure-container-instance.png]
 
 ## Clean up resources
 
@@ -105,9 +116,6 @@ In this quickstart, you created an Azure container instance from an image in the
 > [!div class="nextstepaction"]
 > [Azure Container Instances tutorial](./container-instances-tutorial-prepare-app.md)
 
-<!-- IMAGES -->
-[qs-powershell-01]: ./media/container-instances-quickstart-powershell/qs-powershell-01.png
-
 <!-- LINKS -->
 [New-AzResourceGroup]: /powershell/module/az.resources/new-Azresourcegroup
 [New-AzContainerGroup]: /powershell/module/az.containerinstance/new-Azcontainergroup

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

@@ -6,7 +6,7 @@ ms.author: tomcassidy
 author: tomvcassidy
 ms.service: container-instances
 services: container-instances
-ms.date: 06/17/2022
+ms.date: 04/26/2024
 ms.custom: mvc, devx-track-azurecli, mode-api
 ---