Multiple updates

Author: ryanberg-aquent

support/azure/azure-container-instances/configuration-setup/container-group-deployment-waiting-state.md

@@ -4,15 +4,15 @@ description: Learn how to resolve an issue in which a container group deployment
 ms.date: 04/17/2025
 author: kennethgp
 ms.author: kegonzal
-editor: v-ryanberg
-ms.reviewer: v-ryanberg
+editor: v-jsitser
+ms.reviewer: edneto, v-leedennis
 ms.service: azure-container-instances
 ms.custom: sap:Configuration and Setup
 #Customer intent: As an Azure administrator, I want to learn how to resolve a container group deployment that's stuck in the "Waiting" state so that I can successfully deploy an image onto a container instance.
 ---
 # Container group deployment remains in Waiting state
 
-This article discusses possible causes and how to resolve an unresponsive deployment, which doesn't exit the Waiting state.
+This article discusses possible causes and how to resolve an unresponsive deployment which doesn't exit the Waiting state.
 
 ## Symptoms
 
@@ -32,7 +32,7 @@ The Waiting state indicates there's a condition preventing deployment setup or c
 
 Possible solutions include:
 
-- Check that the container runs fine locally. A local machine with Docker can be used to do validate the container runs correctly.
+- Check that the container runs fine locally. A local machine with Docker can be used to validate the container runs correctly.
 - Inspect possible errors on the **Container Events** tab starting with the main container process.
 - Make sure no reserved ports are being used in the container definition. For more information, see [Does the ACI service reserve ports for service functionality?](/azure/container-instances/container-instances-faq#does-the-aci-service-reserve-ports-for-service-functionality-).
 - Check that there's connectivity to the Azure file share and that the key is correct or valid. If deployment is on BYOVNET, check that domain name system (DNS) resolution is working for the Azure file share fully qualified domain name (FQDN).
@@ -46,9 +46,6 @@ Possible solutions include:
 ## Resources
 
 - [Tutorial: Deploy a multi-container group using a Resource Manager template](/azure/container-instances/container-instances-multi-container-group)
-
 - [Azure Container Instances states](/azure/container-instances/container-state)
 
-[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
-
 [!INCLUDE [Third-party contact disclaimer](~/includes/third-party-contact-disclaimer.md)]

support/azure/azure-container-instances/configuration-setup/container-group-transitioning-state.md

@@ -5,7 +5,6 @@ ms.date: 01/15/2025
 author: kennethgp
 ms.author: kegonzal
 editor: v-jsitser
-ms.reviewer: kegonzal
 ms.service: azure-container-instances
 ms.topic: troubleshooting-problem-resolution
 ms.custom: sap:Configuration and Setup
@@ -17,43 +16,38 @@ This article discusses how to resolve an operational failure that occurs when a
 
 ## Symptoms
 
-When you issue start/stop operation on a container group, this error is thrown:
+When you issue a start/stop operation on a container group, you receive the following error message:
 
-> **InternalErrorCode**: "ContainerGroupTransitioning"  
-> **StatusCode**: "409"  
-> **Message**: "The container group '\<container-group-name>' is still transitioning, please retry later."
+**InternalErrorCode**: "ContainerGroupTransitioning"  
+**StatusCode**: "409"  
+**Message**: "The container group '\<container-group-name>' is still transitioning, please retry later."
 
 ## Cause
 
 ### Cause 1: After stop operation
 
-During a continuous stop operation of the container group, system sidecar containers the container group aren't terminated in time.
+During a continuous stop operation of the container group, system sidecar containers in the container group aren't terminated in time.
 
 ### Cause 2: After start operation
 
 The stopped state for previous operation wasn't propagated yet or didn't propagate correctly (known platform issue).
 
-## Solution
+## Solution 1
 
 - Wait until the container group is fully stopped to allow the system sidecars to fully terminate (allow at least 10 seconds between operations).
-- If the [container is deployed by using an Azure Logic App](/azure/connectors/connectors-create-api-container-instances?toc=%2Fazure%2Fcontainer-instances%2Ftoc.json&bc=%2Fazure%2Fcontainer-instances%2Fbreadcrumb%2Ftoc.json), check the state of the container, make sure the status is **Stopped** before issuing start operation.
-- For Job container groups (process runs once and exits, restart policy is **Never**) in **Terminated** state, issue a stop operation before start operation to make sure the correct status is propagated first. Another alternative is to issue a restart operation instead. A restart operation avoids a new container group deployment and instead restarts the application process inside the container.
+- If the [container is deployed by using an Azure Logic App](/azure/connectors/connectors-create-api-container-instances?toc=%2Fazure%2Fcontainer-instances%2Ftoc.json&bc=%2Fazure%2Fcontainer-instances%2Fbreadcrumb%2Ftoc.json), check the state of the container and then make sure the status is **Stopped** before issuing a start operation.
+- For job container groups (process runs once and exits, restart policy is **Never**) in **Terminated** state, issue a stop operation before a start operation to make sure the correct status is propagated first. You can also issue a restart operation. A restart operation avoids a new container group deployment and instead restarts the application process inside the container.
 
 > [!NOTE]
 > As a best practice, we recommend that you always issue a stop operation before a start operation to ensure the correct status is propagated. If you start a container group that already has a running container, you might cause the transitioning state problem.
 
-## Solution 3: Open a support ticket
+## Solution 2: Open a support ticket
 
-If the previous solutions don't fix the problem, and you still encounter the error message, open a support ticket.
+If the previous solutions don't fix the problem and you still encounter the error message, open a support ticket.
 
-## More information
+## Resources
 
 - [Tutorial: Deploy a multi-container group using a Resource Manager template](/azure/container-instances/container-instances-multi-container-group)
-
 - [Azure Container Instances states](/azure/container-instances/container-state)
-
 - [Manually stop or start containers in Azure Container Instances](/azure/container-instances/container-instances-stop-start)
-
 - [Update containers in Azure Container Instances](/azure/container-instances/container-instances-update)
-
-[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/azure/azure-container-instances/configuration-setup/docker-hub-rate-limit-registryerrorresponse.md

@@ -32,7 +32,7 @@ You might also see the following error messages:
 
 ## Cause
 
-This issue might occur due to the rate limits on image pulls from Docker Hub. An agreement between Microsoft and Docker to allow Azure IP addresses to make unlimited anonymous image pulls from Docker Hub ended on June 30, 2024. If you're deploying to a Virtual Network (BYOVNET), note the image pull occurs via random platform public IP.
+This issue might occur due to the rate limits on image pulls from Docker Hub. An agreement between Microsoft and Docker to allow Azure IP addresses to make unlimited anonymous image pulls from Docker Hub ended on June 30, 2024. If you're deploying to a Virtual Network (BYOVNET), the image pull occurs through a random platform public IP.
 
 ## Solution
 
@@ -41,12 +41,10 @@ Create a Docker account and use the Docker account credentials to authenticate t
 > [!NOTE]
 > Docker offers a free subscription that allows customers to get 200 pulls every six hours. If 200 pulls aren't enough for you, we recommend purchasing a paid Docker subscription. A paid Docker subscription gives you 5,000 pulls every 24 hours, which can be increased by contacting Docker directly.
 
-## References
+## Resources
 
 - [Docker Hub usage and rate limits](https://docs.docker.com/docker-hub/download-rate-limit/)
 - [Configure Artifact Cache to consume public content](/azure/container-registry/buffer-gate-public-content#configure-artifact-cache-to-consume-public-content)
 - [Artifact cache in Azure Container Registry](/azure/container-registry/container-registry-artifact-cache)
 
 [!INCLUDE [Third-party disclaimer](../../../includes/third-party-disclaimer.md)]
-
-[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/azure/azure-container-instances/configuration-setup/error-codes-spot-container-creation.md

@@ -21,10 +21,7 @@ This article provides solutions to common errors that occur when you try to crea
 | `SpotPriorityContainerGroupWithGPUResourcesNotSupported` | `Spot Priority Container Groups that include containers requesting GPU resources are not supported.` | GPUs aren't supported for Spot containers. Remove the GPU from the request, and try again. |
 | `PriorityNotSpecified` | `The 'Priority' must be one of 'Regular,Spot' for container group '{xyz}'.` | If the priority is mentioned in the request body, specify a value of `Regular` or `Spot`. |
 
-## More information
+## Resources
 
 - [Azure Container Instances Spot containers (preview)](/azure/container-instances/container-instances-spot-containers-overview)
-
 - [FAQ - Spot containers on Azure Container Instances (Preview)](/azure/container-instances/container-instances-faq#spot-containers-on-azure-container-instances--preview)
-
-[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/azure/azure-container-instances/configuration-setup/inaccessible-image.md

@@ -46,14 +46,10 @@ When you try to deploy a container instance, the deployment fails, and you recei
 You must use a managed identity to allow the Container Instances trusted service to access the container registry. For more information, see [Allow trusted services to securely access a network-restricted container registry](/azure/container-registry/allow-access-trusted-services#about-trusted-services). You can also learn more at [Deploy to Azure Container Instances from Azure Container Registry using a managed identity](/azure/container-instances/using-azure-container-registry-mi).
 
 > [!NOTE]
-> Image pull phase happens before container is created. If you're deploying to a Virtual Network (BYOVNET), image pull occurs via random platform public IP. Because of this reason, private registries other than Azure Container Registry aren't supported even if there's private connectivity from target subnet.
+> Image pull phase happens before container is created. If you're deploying to a Virtual Network (BYOVNET), image pull occurs through a random platform public IP. Because of this, private registries other than Azure Container Registry aren't supported even if there's private connectivity from the target subnet.
 
-## References
+## Resources
 
 - [Managed identities in Azure Container Apps](/azure/container-apps/managed-identity)
-
 - [Azure Container Apps image pull with managed identity](/azure/container-apps/managed-identity-image-pull)
-
 - [Tutorial: Deploy a multi-container group using a Resource Manager template](/azure/container-instances/container-instances-multi-container-group)
-
-[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/azure/azure-container-instances/configuration-setup/long-image-pulls.md

@@ -5,8 +5,8 @@ ms.date: 04/14/2025
 ms.service: azure-container-instances
 author: tysonfms
 ms.author: tysonfreeman
-editor: kennethgp
-ms.reviewer: edneto, v-leedennis
+editor: v-jsitser
+ms.reviewer: edneto, v-leedennis, kennethgp
 ms.custom: sap:Configuration and Setup
 #Customer intent: As a user of Azure Container Instances, I want to learn why an image pull takes a long time to complete so that I can create and use container groups successfully.
 ---
@@ -20,7 +20,7 @@ This article discusses possible causes for an image pull taking long time to com
 
 ## Symptoms
 
-- Container groups are stuck in a "Creating" status for a significant amount of time.
+- Container groups are stuck in a **Creating** status for a significant amount of time.
 - The image size is large.
 
 ## Cause
@@ -37,7 +37,7 @@ To view the timeline of the container events, run the following [az container sh
 az container show --resource-group <resource-group-name> --name <container-group-name>
 ```
 
-The time span between the **Pulling** and **Pulled** events allows you to determine whether the image pull time is expected or abnormal. Sample command output:
+The time span between the `Pulling` and `Pulled` events allows you to determine whether the image pull time is expected or abnormal. The following is a sample command output:
 
 ```json
 {
@@ -149,8 +149,6 @@ The time span between the **Pulling** and **Pulled** events allows you to determ
 }
 ```
 
-## More information
+## Resources
 
 - [Azure Container Apps image pull with managed identity](/azure/container-apps/managed-identity-image-pull)
-
-[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/azure/azure-container-instances/configuration-setup/service-unavailable-container-group-quota-exceeded.md

@@ -4,8 +4,8 @@ description: Learn how to resolve a (ServiceUnavailable - container group quota
 ms.date: 02/23/2024
 author: tysonfms
 ms.author: tysonfreeman
-editor: kennethgp
-ms.reviewer: v-leedennis
+editor: v-jsitser
+ms.reviewer: v-leedennis, kennethgp
 ms.service: azure-container-instances
 ms.custom: sap:Configuration and Setup
 #Customer intent: As an Azure administrator, I want to learn how to resolve a "ServiceUnavailable" error ("Resource type 'Microsoft.ContainerInstance/containerGroups' container group quota 'ContainerGroups' exceeded in region") so that I can successfully deploy container groups onto Azure Container Instances.
@@ -29,10 +29,8 @@ However, you confirm there's enough quota settings for this deployment.
 
 ## Cause
 
-You try to simultaneously deploy multiple container groups in different regions that use the same name. This action triggers the fraud detection logic in Container Instances. Automation scripts that are run in the cloud might be trying to do this multi-deployment operation. You can identify this scenario by the '0' limit and usage fields in error message.
+You try to simultaneously deploy multiple container groups in different regions that use the same name. This action triggers the fraud detection logic in Container Instances. Automation scripts that are run in the cloud might be trying to do this multi-deployment operation. You can identify this scenario by the `0` limit and usage fields in the error message.
 
 ## Solution
 
-To avoid this error, issue requests for container group deployments one at a time.
-
-[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
+To avoid this error, issue requests for container group deployments one at a time.

support/azure/azure-container-instances/configuration-setup/service-unavailable-gpu-enabled-aci-deployment-failures.md

@@ -2,10 +2,9 @@
 title: Azure Container Instances fails to run GPU-enabled containers
 description: Provides solutions to GPU-enabled Azure container instance deployment failures.
 ms.date: 05/27/2024
-ms.reviewer: v-rekhanain, momajed, v-weizhu
+ms.reviewer: v-rekhanain, momajed, v-weizhu, kennethgp
 ms.service: azure-container-instances
 ms.custom: sap:Configuration and Setup
-editor: kennethgp
 ---
 # GPU-enabled container deployment fails with "service unavailable" error
 
@@ -68,5 +67,3 @@ Your container image doesn't have NVIDIA drivers or libraries installed. GPU-ena
 ### Solution 4: Use the NVIDIA GPU Cloud (NGC) repository
 
 Check your container image and make sure that it has the NVIDIA drivers and libraries installed. You can use the NVIDIA GPU Cloud (NGC) repository to find and pull prebuilt GPU-accelerated images for various frameworks and applications.
-
-[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/azure/azure-container-instances/configuration-setup/service-unavailable-requested-resource-is-not-available.md

@@ -4,8 +4,8 @@ description: Provides a solution to the service unavailable error
 ms.date: 02/23/2024
 author: tysonfms
 ms.author: tysonfreeman
-editor: kennethgp
-ms.reviewer: tomcassidy, v-leedennis
+editor: v-jsitser
+ms.reviewer: tomcassidy, v-leedennis, kennethgp
 ms.topic: troubleshooting-problem-resolution
 ms.service: azure-container-instances
 ms.custom: sap:Configuration and Setup
@@ -25,16 +25,11 @@ You receive an error message that resembles the following text:
 
 This issue might occur if a feature isn't available in certain regions or if there's a lack of capacity. This issue is typically intermittent.
 
-If container group deployment requests more than 4 CPU or 16 GB memory the deployment is marked as Big Container Group. Big Container Group region capacity is enabled on demand, if there's no infrastructure available for the deployment the error is thrown.
+If container group deployment requests are larger than four (4) CPU or 16 GB memory the deployment is marked as **Big Container Group**. Big Container Group region capacity is enabled on demand and if there's no infrastructure available for the deployment the error is encountered.
 
 ## Solution
 
-1. To determine whether you can deploy to an available region, see [Resource availability & quota limits for Azure Container Instances](/azure/container-instances/container-instances-resource-and-quota-limits).
-
-1. To determine which features are available in your region, use the [Location - List Capabilities](/rest/api/container-instances/location/list-capabilities) REST API. You can also verify available features per region by selecting the "Try it" button in that article.
-
-1. If you're deploying in an available region, and there's no feature limitation, retry the deployment.
-
-1. If you're deploying a Big Container Group, open a support ticket to validate region capacity.
-
-[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
+- To determine whether you can deploy to an available region, see [Resource availability & quota limits for Azure Container Instances](/azure/container-instances/container-instances-resource-and-quota-limits).
+- To determine which features are available in your region, use the [Location - List Capabilities](/rest/api/container-instances/location/list-capabilities) REST API. You can also verify available features per region by selecting the "Try it" button in that article.
+- If you're deploying in an available region, and there's no feature limitation, retry the deployment.
+- If you're deploying a Big Container Group, open a support ticket to validate region capacity.

support/azure/azure-container-instances/configuration-setup/spot-container-group-quota-reached-error.md

@@ -2,8 +2,7 @@
 title: ContainerGroupQuotaReached error when deploying Spot containers
 description: Provides solutions to the ContainerGroupQuotaReached error that occurs when you deploy a Spot container to Azure Container Instances.
 ms.date: 10/28/2024
-ms.reviewer: chiragpa, v-weizhu
-editor: kennethgp
+ms.reviewer: chiragpa, v-weizhu, kennethgp
 ms.service: azure-container-instances
 ms.custom: sap:Configuration and Setup
 ---
@@ -45,6 +44,4 @@ To resolve this issue, increase the StandardSpotCores limit. To do so, use one o
 - File support request to increase capacity for Spot containers. For more information, see [How do I file quota requests for ACI Spot containers?](/azure/container-instances/container-instances-faq#spot-containers-on-azure-container-instances--preview)
 
 > [!NOTE]
-> Spot containers with Azure Container Instances is in preview and is not recommended for production scenarios.
-
-[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
+> Spot containers with Azure Container Instances is currently in preview and not recommended for production scenarios.