You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/container-instances/container-instances-standby-pools-monitor-pool-events.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: mimckitt
5
5
ms.author: mimckitt
6
6
ms.service: azure-container-instances
7
7
ms.topic: how-to
8
-
ms.date: 5/19/2025
8
+
ms.date: 11/17/2025
9
9
ms.reviewer: tomvcassidy
10
10
# Customer intent: As a cloud administrator, I want to monitor and analyze standby pool events in Azure Container Instances using Log Analytics, so that I can proactively manage resources and ensure system reliability.
Copy file name to clipboardExpand all lines: articles/container-instances/container-instances-start-command.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ author: tomvcassidy
7
7
ms.service: azure-container-instances
8
8
ms.custom: devx-track-azurecli
9
9
services: container-instances
10
-
ms.date: 08/29/2024
10
+
ms.date: 11/17/2025
11
11
# Customer intent: As a container administrator, I want to override the default entrypoint in a container instance, so that I can customize command execution for specific tasks or batch jobs.
Copy file name to clipboardExpand all lines: articles/container-instances/container-instances-stop-start.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.author: tomcassidy
6
6
author: tomvcassidy
7
7
ms.service: azure-container-instances
8
8
services: container-instances
9
-
ms.date: 08/29/2024
9
+
ms.date: 11/17/2025
10
10
# Customer intent: "As a cloud engineer, I want to manually stop and start container groups in Azure Container Instances, so that I can control resource allocation and manage costs efficiently while maintaining container configurations."
11
11
---
12
12
# Manually stop or start containers in Azure Container Instances
Copy file name to clipboardExpand all lines: articles/container-instances/container-instances-support-help.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.author: tomcassidy
6
6
ms.service: azure-container-instances
7
7
services: container-instances
8
8
ms.topic: troubleshooting
9
-
ms.date: 08/29/2024
9
+
ms.date: 11/17/2025
10
10
ms.custom: support-help-page
11
11
# Customer intent: As a developer using Azure Container Instances, I want to access various support and troubleshooting resources, so that I can resolve issues effectively and enhance my application development experience.
# Customer intent: As a cloud developer, I want to troubleshoot deployment and runtime issues with Azure Container Instances, so that I can efficiently manage and resolve problems affecting my containerized applications.
Copy file name to clipboardExpand all lines: articles/container-instances/container-instances-tutorial-azure-function-trigger.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.author: tomcassidy
6
6
author: tomvcassidy
7
7
ms.service: azure-container-instances
8
8
services: container-instances
9
-
ms.date: 08/29/2024
9
+
ms.date: 11/17/2025
10
10
ms.custom: devx-track-azurepowershell
11
11
# Customer intent: "As a cloud developer, I want to create an HTTP-triggered serverless function that deploys container groups, so that I can automate resource provisioning in Azure Container Instances."
Copy file name to clipboardExpand all lines: articles/container-instances/container-instances-tutorial-deploy-app.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.author: tomcassidy
6
6
author: tomvcassidy
7
7
ms.service: azure-container-instances
8
8
services: container-instances
9
-
ms.date: 08/29/2024
9
+
ms.date: 11/17/2025
10
10
ms.custom: mvc, devx-track-azurecli
11
11
# Customer intent: "As a developer, I want to deploy a container application using the Azure CLI, so that I can run my application in Azure Container Instances and verify its functionality through the browser and logs."
Copy file name to clipboardExpand all lines: articles/container-instances/container-instances-tutorial-deploy-confidential-container-default-portal.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.author: tomcassidy
6
6
author: tomvcassidy
7
7
ms.service: azure-container-instances
8
8
services: container-instances
9
-
ms.date: 08/29/2024
9
+
ms.date: 11/17/2025
10
10
ms.custom: mvc
11
11
# Customer intent: "As a developer, I want to deploy a confidential container with a development policy to Azure Container Instances, so that I can test and develop applications in a secure environment."
12
12
---
@@ -16,7 +16,7 @@ ms.custom: mvc
16
16
In this tutorial, you use Azure portal to deploy a confidential container to Azure Container Instances with a development confidential computing enforcement policy. After deploying the container, you can browse to the running application.
17
17
18
18
> [!NOTE]
19
-
> When deploying confidential containers on Azure Container Instances via Portal you will only be able to deploy with a development confidential computing enforcement policy. This policy is only recommended for development and test workloads. Logging, and exec functionality are still available in the container group when using this policiy and software components are not validated. To full attest your container group while running production workloads, it is recommended that you deploy with a custom confidential computing enforcement policy via an Azure Resource Manager template. For more information, see the [tutorial](./container-instances-tutorial-deploy-confidential-containers-cce-arm.md).
19
+
> When deploying confidential containers on Azure Container Instances via Portal, you'll only be able to deploy with a development confidential computing enforcement policy. This policy is only recommended for development and test workloads. Logging, and exec functionality are still available in the container group when using this policy and software components aren't validated. To full attest your container group while running production workloads, it's recommended that you deploy with a custom confidential computing enforcement policy via an Azure Resource Manager template. For more information, see the [tutorial](./container-instances-tutorial-deploy-confidential-containers-cce-arm.md).
20
20
21
21
:::image type="content" source="media/container-instances-confidential-containers-tutorials/confidential-containers-aci-hello-world.png" alt-text="Screenshot of a hello-world application deployed via Azure portal, PNG.":::
22
22
@@ -48,7 +48,7 @@ On the **Basics** page, choose a subscription and enter the following values for
48
48
:::image type="content" source="media/container-instances-confidential-containers-tutorials/confidential-containers-aci-portal-sku.png" alt-text="Screenshot of the SKU selection of a container group, PNG.":::
49
49
50
50
> [!NOTE]
51
-
> When deploying confidential containers on Azure Container Instances via Portal you will only be able to deploy with a development confidential computing enforcement policy. This policy is only recommended for development and test workloads. Logging, and exec functionality are still available in the container group when using this policiy and software components are not validated. To full attest your container group while running production workloads, it is recommended that you deploy with a custom confidential computing enforcement policy via an Azure Resource Manager template. For more information, see the [tutorial](./container-instances-tutorial-deploy-confidential-containers-cce-arm.md).
51
+
> When deploying confidential containers on Azure Container Instances via Portal you'll only be able to deploy with a development confidential computing enforcement policy. This policy is only recommended for development and test workloads. Logging, and exec functionality are still available in the container group when using this policy and software components aren't validated. To full attest your container group while running production workloads, it's recommended that you deploy with a custom confidential computing enforcement policy via an Azure Resource Manager template. For more information, see the [tutorial](./container-instances-tutorial-deploy-confidential-containers-cce-arm.md).
52
52
53
53
Leave all other settings as their defaults, then select **Review + create**.
Copy file name to clipboardExpand all lines: articles/container-instances/container-instances-tutorial-deploy-confidential-containers-cce-arm.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.author: tomcassidy
6
6
author: tomvcassidy
7
7
ms.service: azure-container-instances
8
8
services: container-instances
9
-
ms.date: 08/29/2024
9
+
ms.date: 11/17/2025
10
10
ms.custom: mvc, devx-track-arm-template
11
11
# Customer intent: "As a developer deploying container applications, I want to create an ARM template for confidential container instances, so that I can ensure data protection and compliance through hardware-based attestation and in-memory encryption."
Copy file name to clipboardExpand all lines: articles/container-instances/container-instances-tutorial-deploy-spot-containers-cli.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ author: athinanthny
7
7
ms.service: azure-container-instances
8
8
ms.custom: devx-track-azurecli
9
9
services: container-instances
10
-
ms.date: 08/29/2024
10
+
ms.date: 11/17/2025
11
11
# Customer intent: As a developer, I want to deploy Spot containers using the Azure CLI, so that I can efficiently run cost-effective, interruptible workloads without needing a full orchestration platform.
0 commit comments