Skip to content

Commit 3210513

Browse files
Merge pull request #2620 from tomvcassidy/aciFP7
final aci freshness pass
2 parents 5a2c4de + 6fee7bf commit 3210513

31 files changed

+38
-38
lines changed

articles/container-instances/container-instances-standby-pools-monitor-pool-events.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: mimckitt
55
ms.author: mimckitt
66
ms.service: azure-container-instances
77
ms.topic: how-to
8-
ms.date: 5/19/2025
8+
ms.date: 11/17/2025
99
ms.reviewer: tomvcassidy
1010
# 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.
1111
---

articles/container-instances/container-instances-start-command.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: tomvcassidy
77
ms.service: azure-container-instances
88
ms.custom: devx-track-azurecli
99
services: container-instances
10-
ms.date: 08/29/2024
10+
ms.date: 11/17/2025
1111
# 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.
1212
---
1313

articles/container-instances/container-instances-stop-start.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: tomcassidy
66
author: tomvcassidy
77
ms.service: azure-container-instances
88
services: container-instances
9-
ms.date: 08/29/2024
9+
ms.date: 11/17/2025
1010
# 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."
1111
---
1212
# Manually stop or start containers in Azure Container Instances

articles/container-instances/container-instances-support-help.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: tomcassidy
66
ms.service: azure-container-instances
77
services: container-instances
88
ms.topic: troubleshooting
9-
ms.date: 08/29/2024
9+
ms.date: 11/17/2025
1010
ms.custom: support-help-page
1111
# 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.
1212
---

articles/container-instances/container-instances-troubleshooting.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: tomcassidy
66
author: tomvcassidy
77
ms.service: azure-container-instances
88
services: container-instances
9-
ms.date: 08/29/2024
9+
ms.date: 11/17/2025
1010
ms.custom: mvc, devx-track-azurecli, linux-related-content
1111
# 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.
1212
---

articles/container-instances/container-instances-tutorial-azure-function-trigger.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: tomcassidy
66
author: tomvcassidy
77
ms.service: azure-container-instances
88
services: container-instances
9-
ms.date: 08/29/2024
9+
ms.date: 11/17/2025
1010
ms.custom: devx-track-azurepowershell
1111
# 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."
1212
---

articles/container-instances/container-instances-tutorial-deploy-app.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: tomcassidy
66
author: tomvcassidy
77
ms.service: azure-container-instances
88
services: container-instances
9-
ms.date: 08/29/2024
9+
ms.date: 11/17/2025
1010
ms.custom: mvc, devx-track-azurecli
1111
# 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."
1212
---

articles/container-instances/container-instances-tutorial-deploy-confidential-container-default-portal.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: tomcassidy
66
author: tomvcassidy
77
ms.service: azure-container-instances
88
services: container-instances
9-
ms.date: 08/29/2024
9+
ms.date: 11/17/2025
1010
ms.custom: mvc
1111
# 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."
1212
---
@@ -16,7 +16,7 @@ ms.custom: mvc
1616
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.
1717

1818
> [!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).
2020
2121
:::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.":::
2222

@@ -48,7 +48,7 @@ On the **Basics** page, choose a subscription and enter the following values for
4848
:::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.":::
4949

5050
> [!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).
5252
5353
Leave all other settings as their defaults, then select **Review + create**.
5454

articles/container-instances/container-instances-tutorial-deploy-confidential-containers-cce-arm.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: tomcassidy
66
author: tomvcassidy
77
ms.service: azure-container-instances
88
services: container-instances
9-
ms.date: 08/29/2024
9+
ms.date: 11/17/2025
1010
ms.custom: mvc, devx-track-arm-template
1111
# 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."
1212
---

articles/container-instances/container-instances-tutorial-deploy-spot-containers-cli.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: athinanthny
77
ms.service: azure-container-instances
88
ms.custom: devx-track-azurecli
99
services: container-instances
10-
ms.date: 08/29/2024
10+
ms.date: 11/17/2025
1111
# 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.
1212
---
1313

0 commit comments

Comments
 (0)