Merge pull request #48721 from ShawnKupfer/WB1619

JamesJBarnett · web-flow · commit 966640c1c190 · 2025-01-22T11:40:46.000-07:00
Technical Review 1016216: Run Docker containers with Azure Container …
diff --git a/learn-pr/azure/run-docker-with-azure-container-instances/1-introduction.yml b/learn-pr/azure/run-docker-with-azure-container-instances/1-introduction.yml
@@ -5,7 +5,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Introduction
   description: Introduction to Azure Container Instances.
-  ms.date: 04/03/2024
+  ms.date: 01/15/2025
   author: v-tcassi
   ms.author: tomcassidy
   ms.topic: unit
diff --git a/learn-pr/azure/run-docker-with-azure-container-instances/2-run-aci.yml b/learn-pr/azure/run-docker-with-azure-container-instances/2-run-aci.yml
@@ -5,7 +5,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Exercise - Run Azure Container Instances
   description: Run Azure Container Instances.
-  ms.date: 04/03/2024
+  ms.date: 01/15/2025
   author: v-tcassi
   ms.author: tomcassidy
   ms.topic: unit
diff --git a/learn-pr/azure/run-docker-with-azure-container-instances/3-restart-policies.yml b/learn-pr/azure/run-docker-with-azure-container-instances/3-restart-policies.yml
@@ -5,7 +5,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Exercise - Control Azure Container Instances restart behavior
   description: Control Container Instances restart behavior.
-  ms.date: 04/03/2024
+  ms.date: 01/15/2025
   author: v-tcassi
   ms.author: tomcassidy
   ms.topic: unit
diff --git a/learn-pr/azure/run-docker-with-azure-container-instances/4-use-environment-variables.yml b/learn-pr/azure/run-docker-with-azure-container-instances/4-use-environment-variables.yml
@@ -5,7 +5,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Exercise - Set environment variables
   description: Set environment variables in Azure Container Instances.
-  ms.date: 04/03/2024
+  ms.date: 01/15/2025
   author: v-tcassi
   ms.author: tomcassidy
   ms.topic: unit
diff --git a/learn-pr/azure/run-docker-with-azure-container-instances/5-use-data-volumes.yml b/learn-pr/azure/run-docker-with-azure-container-instances/5-use-data-volumes.yml
@@ -5,7 +5,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Exercise - Use data volumes
   description: Use data volumes with Azure Container Instances (ACI).
-  ms.date: 04/03/2024
+  ms.date: 01/15/2025
   author: v-tcassi
   ms.author: tomcassidy
   ms.topic: unit
diff --git a/learn-pr/azure/run-docker-with-azure-container-instances/6-troubleshoot-aci.yml b/learn-pr/azure/run-docker-with-azure-container-instances/6-troubleshoot-aci.yml
@@ -5,7 +5,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Exercise - Troubleshoot Azure Container Instances
   description: Troubleshoot Azure Container Instances.
-  ms.date: 04/03/2024
+  ms.date: 01/15/2025
   author: v-tcassi
   ms.author: tomcassidy
   ms.topic: unit
diff --git a/learn-pr/azure/run-docker-with-azure-container-instances/7-knowledge-check.yml b/learn-pr/azure/run-docker-with-azure-container-instances/7-knowledge-check.yml
@@ -6,7 +6,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Knowledge check
   description: Knowledge check
-  ms.date: 04/03/2024
+  ms.date: 01/15/2025
   author: v-tcassi
   ms.author: tomcassidy
   ms.topic: unit
@@ -19,35 +19,35 @@ quiz:
     choices:
     - content: Always
       isCorrect: true
-      explanation: "The restart policy **Always** will ensure needed processes continue to be available even if a restart is required."
+      explanation: "The restart policy **Always** ensures needed processes continue to be available even if a restart is required."
     - content: Never
       isCorrect: false
-      explanation: "The restart policy **Always** will ensure needed processes continue to be available even if a restart is required."
+      explanation: "The restart policy **Always** ensures needed processes continue to be available even if a restart is required."
     - content: OnFailure
       isCorrect: false
-      explanation: "The restart policy **Always** will ensure needed processes continue to be available even if a restart is required."
+      explanation: "The restart policy **Always** ensures needed processes continue to be available even if a restart is required."
 
   - content: "By default, you can see the values of an environment variable in:"
     choices:
     - content: "Only the Azure portal."
       isCorrect: false
-      explanation: "Environment variables are not secured by default and their values can be seen in the Azure portal and the Azure CLI output."
+      explanation: "Environment variables are not secured by default, and you can see their values in the Azure portal and the Azure CLI output."
     - content: "Only the Azure CLI output."
       isCorrect: false
-      explanation: "Environment variables are not secured by default and their values can be seen in the Azure portal and the Azure CLI output."
+      explanation: "Environment variables are not secured by default, and you can see their values in the Azure portal and the Azure CLI output."
     - content: "Both the Azure portal and the Azure CLI output."
       isCorrect: true
-      explanation: "Environment variables are not secured by default and their values can be seen in the Azure portal and the Azure CLI output."
+      explanation: "Environment variables are not secured by default, and you can see their values in the Azure portal and the Azure CLI output."
 
-  - content: "Which troubleshooting command can be used to view container startup events?"
+  - content: "Which troubleshooting command can you use to view container startup events?"
     choices:
-    - content: az container logs
+    - content: "`az container logs`"
       isCorrect: false
       explanation: "The `az container logs` command examines the logs for a container in a container group."
-    - content: az container attach
+    - content: "`az container attach`"
       isCorrect: true
       explanation: "The `az container attach` command shows container events and logs. By contrast, the `az container logs` only shows the logs and not the startup events."
-    - content: az container exec
+    - content: "`az container exec`"
       isCorrect: false
       explanation: "The `az container exec` command executes a command from within a running container of a container group."
 
diff --git a/learn-pr/azure/run-docker-with-azure-container-instances/8-summary.yml b/learn-pr/azure/run-docker-with-azure-container-instances/8-summary.yml
@@ -6,7 +6,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Summary
   description: "Summary"
-  ms.date: 04/03/2024
+  ms.date: 01/15/2025
   author: v-tcassi
   ms.author: tomcassidy
   ms.topic: unit
diff --git a/learn-pr/azure/run-docker-with-azure-container-instances/includes/1-introduction.md b/learn-pr/azure/run-docker-with-azure-container-instances/includes/1-introduction.md
@@ -9,3 +9,7 @@ In this module, you'll:
 - Use environment variables to configure your container when it starts.
 - Attach a data volume to persist data when your container exits.
 - Learn some basic ways to troubleshoot issues on your Azure containers.
+
+## Prerequisites
+
+You need your own Azure subscription to run this exercise, and you might incur charges. If you don't already have an Azure subscription, [create a free account](https://azure.microsoft.com/free/) before you begin.
diff --git a/learn-pr/azure/run-docker-with-azure-container-instances/includes/2-run-aci.md b/learn-pr/azure/run-docker-with-azure-container-instances/includes/2-run-aci.md
@@ -1,4 +1,4 @@
-Create a container in Azure and expose it to the Internet with a fully qualified domain name (FQDN).
+In this unit, you create a container in Azure and expose it to the Internet with a fully qualified domain name (FQDN).
 
 [!include[](../../../includes/azure-exercise-subscription-prerequisite.md)]
 
@@ -37,7 +37,9 @@ For scenarios where you need full container orchestration, including service dis
     DNS_NAME_LABEL=aci-demo-$RANDOM
     ```
 
-1. Run the following `az container create` command to start a container instance:
+1. Create a container by providing a name, a Docker image, and an Azure resource group to the `az container create` command. You can optionally expose the container to the Internet by specifying a DNS name label. In this example, deploy a container that hosts a small web app. You can also select the location to place the image; we use the **East US** region, but you can change it to a location close to you.
+
+    Run the following `az container create` command to start a container instance:
 
     ```azurecli
     az container create \
@@ -69,12 +71,12 @@ For scenarios where you need full container orchestration, including service dis
     aci-demo-0000.eastus.azurecontainer.io  Succeeded
     ````
 
-    If your container is in the **Creating** state, wait a few moments, and run the command again until you see the **Succeeded** state.
+    If your container is in the **Creating** state, wait a few moments and run the command again until you see the **Succeeded** state.
 
 1. From a browser, go to your container's FQDN to see it running. Ensure you enter the *http://* prefix in front of the *aci-demo...* string. You should get this welcome page:
 
     :::image type="content" source="../media/2-browser.png" alt-text="Screenshot of the sample Node.js container app running in a browser." loc-scope="other"::: <!-- no-loc -->
 
 ## Summary
 
-Here, you created an Azure container instance to run a web server and application. You also accessed this application using the FQDN of the container instance.
+Here, you created an Azure container instance to run a web server and application. You also accessed this application using the container instance's FQDN.
diff --git a/learn-pr/azure/run-docker-with-azure-container-instances/includes/3-restart-policy.md b/learn-pr/azure/run-docker-with-azure-container-instances/includes/3-restart-policy.md
@@ -8,7 +8,7 @@ Azure Container Instances has three restart-policy options:
 
 | Restart policy   | Description |
 | ---------------- | :---------- |
-| **Always** | Containers in the container group are always restarted. This policy makes sense for long-running tasks like a web server. This setting is the **default** applied when no restart policy is specified at container creation. |
+| **Always** | Containers in the container group are always restarted. This policy makes sense for long-running tasks like a web server. This setting is the *default* applied when no restart policy is specified at container creation. |
 | **Never** | Containers in the container group are never restarted. The containers run one time only. |
 | **OnFailure** | Containers in the container group are restarted only when the process executed in the container fails (when it terminates with a nonzero exit code). The containers are run at least once. This policy works well for containers that run short-lived tasks. |
 
diff --git a/learn-pr/azure/run-docker-with-azure-container-instances/includes/4-use-environment-variables.md b/learn-pr/azure/run-docker-with-azure-container-instances/includes/4-use-environment-variables.md
@@ -1,6 +1,6 @@
 Environment variables allow you to dynamically configure the application or script the container runs. You can use the Azure CLI, PowerShell, or the Azure portal to set variables when you create the container. Secured environment variables prevent sensitive information from displaying in the container's output.
 
-Create an Azure Cosmos DB instance and use environment variables to pass the connection information to an Azure container instance. An application in the container uses the variables to write and read data from Azure Cosmos DB. Create both an environment variable and a secured environment variable so that you can see the difference between them.
+Here, you create an Azure Cosmos DB instance and use environment variables to pass the connection information to an Azure container instance. An application in the container uses the variables to write and read data from Azure Cosmos DB. You create both an environment variable and a secured environment variable so that you can see the difference between them.
 
 ## Deploy Azure Cosmos DB
 
@@ -36,7 +36,7 @@ Create an Azure Cosmos DB instance and use environment variables to pass the con
 
 ## Deploy a container that works with your database
 
-Create an Azure container instance that can read from and write records to your Azure Cosmos DB instance.
+Next, you create an Azure container instance that can read from and write records to your Azure Cosmos DB instance.
 
 The two environment variables you created in the last part, `COSMOS_DB_ENDPOINT` and `COSMOS_DB_MASTERKEY`, hold the values you need to connect to the Azure Cosmos DB instance.
 
@@ -83,7 +83,7 @@ The two environment variables you created in the last part, `COSMOS_DB_ENDPOINT`
 
 In the previous section, you used two environment variables to create your container. By default, these environment variables are accessible through the Azure portal and command-line tools in plain text.
 
-In this section, learn how to prevent sensitive information, such as connection keys, from being displayed in plain text.
+In this section, you learn how to prevent sensitive information such as connection keys from being displayed in plain text.
 
 1. Let's start by seeing the current behavior in action. Run the following `az container show` command to display your container's environment variables:
 
diff --git a/learn-pr/azure/run-docker-with-azure-container-instances/includes/5-use-data-volumes.md b/learn-pr/azure/run-docker-with-azure-container-instances/includes/5-use-data-volumes.md
@@ -1,10 +1,10 @@
 By default, Azure Container Instances are stateless. If the container crashes or stops, all of its state is lost. To persist state beyond the lifetime of the container, you must mount a volume from an external store.
 
-Mount an Azure file share to an Azure container instance so that you can store data and access it later.
+In this exercise, you mount an Azure file share to an Azure container instance so that you can store data and access it later.
 
 ## Create an Azure file share
 
-Create a storage account and a file share. Later, you can make the file share accessible to an Azure container instance.
+First, you create a storage account and a file share. Later, you can make the file share accessible to an Azure container instance.
 
 1. Your storage account requires a unique name. For learning purposes, run the following command to store a unique name in a Bash variable:
 
@@ -101,7 +101,7 @@ To mount an Azure file share as a volume in a container, you specify the share a
 
     :::image type="content" source="../media/5-files-ui.png" alt-text="Screenshot of the Azure Container Instances file share demo running in a browser." loc-scope="other"::: <!-- no-loc -->
 
-1. Enter some text into the form, and select **Submit**. This action creates a file that contains the text you entered in the Azure file share.
+1. Enter some text into the form and select **Submit**. This action creates a file that contains the text you entered in the Azure file share.
 
 1. Run this `az storage file list` command to display the files that are contained in your file share:
 
diff --git a/learn-pr/azure/run-docker-with-azure-container-instances/includes/6-troubleshoot-aci.md b/learn-pr/azure/run-docker-with-azure-container-instances/includes/6-troubleshoot-aci.md
@@ -1,4 +1,4 @@
-To help you understand basic ways to troubleshoot container instances, perform some basic operations like:
+To help you understand basic ways to troubleshoot container instances, you can perform some basic operations like:
 
 * Pulling container logs
 * Viewing container events
@@ -176,4 +176,6 @@ In this module, you created resources using your Azure subscription. You should
 
 1. In the **Overview** tab of the resource group, select **Delete resource group**.
 
-1. A new dialog box opens. Enter the name of the resource group again, and select **Delete**. All of the resources we created in this module are deleted.
+1. A new dialog box opens. Enter the name of the resource group and select **Delete**.
+
+1. Select **Delete** again to confirm deletion. All of the resources we created in this module are deleted.
diff --git a/learn-pr/azure/run-docker-with-azure-container-instances/includes/8-summary.md b/learn-pr/azure/run-docker-with-azure-container-instances/includes/8-summary.md
@@ -14,5 +14,5 @@ You should now be able to:
 
 The following additional resources are intended to provide more information on topics in this module or on additional topics related to this module.
 
- -  [Run container images in Azure Container Instances](/learn/modules/create-run-container-images-azure-container-instances/) is a Microsoft Learn module that provides additional information about running container images using Azure Container Instances.
- -  [Configure Azure Container Instances](/learn/modules/configure-azure-container-instances/) is a Microsoft Learn module that helps you configure Azure Container Instances and container groups.
+- [Run container images in Azure Container Instances](/learn/modules/create-run-container-images-azure-container-instances/) is a Microsoft Learn module that provides additional information about running container images using Azure Container Instances.
+- [Configure Azure Container Instances](/learn/modules/configure-azure-container-instances/) is a Microsoft Learn module that helps you configure Azure Container Instances and container groups.
diff --git a/learn-pr/azure/run-docker-with-azure-container-instances/index.yml b/learn-pr/azure/run-docker-with-azure-container-instances/index.yml
@@ -6,7 +6,7 @@ metadata:
   title: Run Docker containers with Azure Container Instances
   description: Learn how to run and troubleshoot containerized apps using Docker containers with Azure Container Instances.
   manager: akashdubey
-  ms.date: 04/03/2024
+  ms.date: 01/15/2025
   author: v-tcassi
   ms.author: tomcassidy
   ms.topic: module
@@ -15,13 +15,14 @@ title: Run Docker containers with Azure Container Instances
 summary: Learn how to run containerized apps using Docker containers with Azure Container Instances (ACI).
 abstract:  | 
   In this module, you will:
-  - Run containers in Azure Container Instances
-  - Control what happens when your container exits
-  - Use environment variables to configure your container when it starts
-  - Attach a data volume to persist data when your container exits
-  - Learn some basic ways to troubleshoot issues on your Azure containers
+  - Run containers in Azure Container Instances.
+  - Control what happens when your container exits.
+  - Use environment variables to configure your container when it starts.
+  - Attach a data volume to persist data when your container exits.
+  - Learn some basic ways to troubleshoot issues on your Azure containers.
 
-prerequisites: None
+prerequisites: | 
+  You need your own Azure subscription to run this exercise, and you might incur charges. If you don't already have an Azure subscription, [create a free account](https://azure.microsoft.com/free/) before you begin.
 iconUrl: /training/achievements/run-docker-with-azure-container-instances.svg
 levels:
 - intermediate
diff --git a/learn-pr/azure/run-docker-with-azure-container-instances/media/2-portal-cloudshell-access.png b/learn-pr/azure/run-docker-with-azure-container-instances/media/2-portal-cloudshell-access.png
