Skip to content

Commit 10d0d68

Browse files
Merge pull request #54038 from staleycyn/patch-1
Content-drift container instances
2 parents 538e1c4 + d269530 commit 10d0d68

5 files changed

Lines changed: 15 additions & 11 deletions

File tree

learn-pr/wwl-azure/configure-azure-container-instances/includes/3-review.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,12 +26,12 @@ Let's review some of the [benefits of using Azure Container Instances](/azure/co
2626

2727
- **Public IP connectivity and DNS names**. Containers can be directly exposed to the internet with an IP address and FQDN (fully qualified domain name).
2828

29-
- **Custom sizes**. Container nodes can be scaled dynamically to match actual resource demands for an application.
29+
- **Custom sizes**. You specify CPU cores (from 0.1 to 4 vCPU) and memory (from 0.1 to 16 GB) for each container at deployment time. Resource allocation is fixed for the lifetime of the container group.
3030

3131
- **Persistent storage**. Containers support direct mounting of Azure Files file shares.
3232

3333
- **Linux and Windows containers**. Container Instances can schedule both Windows and Linux containers. Specify the operating system type when you create your container groups.
3434

3535
- **Coscheduled groups**. Container Instances supports scheduling of multi-container groups that share host machine resources.
3636

37-
- **Virtual network deployment**. Container Instances can be deployed into an Azure virtual network.
37+
- **Virtual network deployment**. Linux container groups can be deployed into an Azure virtual network for private communication with other Azure resources. Virtual network deployed containers receive no public IP address and communicate only within the virtual network or peered networks.

learn-pr/wwl-azure/configure-azure-container-instances/includes/4-implement-container-groups.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -10,11 +10,13 @@ Let's review some of details about container groups for Azure Container Instance
1010

1111
- Azure Container Instances allocates resources to a multi-container group by adding together the resource requests of all containers in the group. Resources can include items such as CPUs, memory, and GPUs.
1212

13-
- There are two common ways to deploy a multi-container group: Azure Resource Manager (ARM) templates and YAML files.
13+
- There are three common ways to deploy a multi-container group.
1414

15-
- **ARM template**. An ARM template is recommended for deploying other Azure service resources when you deploy your container instances, such as an Azure Files file share.
15+
- **Azure Resource Manager template**. JSON-based infrastructure as code, ideal when deploying alongside other Azure resources.
16+
17+
- **Bicep**. Microsoft's recommended infrastructure as code language, more concise than Azure Resource Manager templates. Bicep includes full IntelliSense support.
1618

17-
- **YAML file**. Due to the concise nature of the YAML format, a YAML file is recommended when your deployment includes only container instances.
19+
- **YAML files**. Container-focused format, ideal for deployments that include only container instances.
1820

1921
- Container groups can share an external-facing IP address, one or more ports on the IP address, and a DNS label with an FQDN.
2022

@@ -49,4 +51,4 @@ Consider the following scenarios for working with multi-container groups. Think
4951

5052
- **Consider app monitoring**. Enable monitoring for your app with a multi-container group. A monitoring container periodically makes a request to your application container to ensure your app is running and responding correctly. The monitoring container raises an alert if it identifies possible issues with your app.
5153

52-
- **Consider front-end and back-end support**. Create a multi-container group to hold your front-end container and back-end container. The front-end container can serve a web app. The back-end container can run a service to retrieve data.
54+
- **Consider front-end and back-end support**. Create a multi-container group to hold your front-end container and back-end container. The front-end container can serve a web app. The back-end container can run a service to retrieve data.

learn-pr/wwl-azure/configure-azure-container-instances/includes/5-review-docker-platform.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ Azure Container Apps doesn't provide direct access to the underlying Kubernetes
3434

3535
#### Compare container management solutions
3636

37-
Azure Container Instances (ACI) can be managed in several ways. Azure Container Apps (ACA) is one way, and Azure Kubernetes Service (AKS) is another. Here’s a comparison table for when to use ACA and AKS.
37+
Azure offers several container platforms for different scenarios. Azure Container Instances (ACI) is best for isolated, short-lived tasks. Azure Container Apps (ACA) serves serverless microservices. Azure Kubernetes Service (AKS) provides full Kubernetes control for complex orchestration needs.
3838

3939
| Feature | Azure Container Apps (ACA) | Azure Kubernetes Service (AKS) |
4040
| --- | --- | --- |
@@ -43,4 +43,3 @@ Azure Container Instances (ACI) can be managed in several ways. Azure Container
4343
| Management | ACA builds upon AKS and offers a simplified PaaS experience for running containers. | AKS provides a more granular control over the Kubernetes environment, suitable for teams with Kubernetes expertise. |
4444
| Scalability | ACA supports both HTTP-based autoscaling and event-driven scaling, making it ideal for applications that need to respond quickly to changes in demand. | AKS offers horizontal pod autoscaling and cluster autoscaling, providing robust scalability options for containerized applications. |
4545
| Use Cases | ACA is designed for microservices and serverless applications that benefit from rapid scaling and simplified management. | AKS is best for complex, long-running applications. These applications require full Kubernetes features and tight integration with other Azure services. |
46-
| Integration | ACA integrates with Azure Logic Apps, Functions, and Event Grid for event-driven architectures. | AKS provides features like Azure Policy for Kubernetes, Azure Monitor for containers, and Azure Defender for Kubernetes for comprehensive security and governance. |

learn-pr/wwl-azure/configure-azure-container-instances/includes/8-summary-resources.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,10 @@ Copilot can assist you in configuring Azure infrastructure solutions. Copilot ca
1313

1414
- Compare benefits and usage cases for containers and virtual machines.
1515

16-
- Compare benefits and usage cases for Azure Container Apps and Azure Kubernetes Service.
16+
- What are the best practices for configuring Azure Container Instances for task-based workloads? Explain the restart policies.
17+
18+
- How do I deploy a multi-container group in Azure Container Instances using Bicep? Show an example with environment variables.
19+
1720

1821
## Learn more with documentation
1922

@@ -29,4 +32,4 @@ Copilot can assist you in configuring Azure infrastructure solutions. Copilot ca
2932

3033
- [Implement Azure Container Apps](/training/modules/implement-azure-container-apps/). Learn how Azure Container Apps can help you deploy and manage microservices and containerized apps on a serverless platform that runs on top of Azure Kubernetes Service.
3134

32-
- [Introduction to Docker containers](/training/modules/intro-to-docker-containers/). Learn the benefits of using Docker containers as a containerization platform. Discuss the infrastructure provided by the Docker platform.
35+
- [Introduction to Docker containers](/training/modules/intro-to-docker-containers/). Learn the benefits of using Docker containers as a containerization platform. Discuss the infrastructure provided by the Docker platform.

learn-pr/wwl-azure/configure-azure-container-instances/index.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ metadata:
55
prefetch-feature-rollout: true
66
title: Configure Azure Container Instances
77
description: "Learn how to configure Azure Container Instances including container groups."
8-
ms.date: 02/21/2026
8+
ms.date: 03/23/2026
99
author: wwlpublish
1010
ms.author: cynthist
1111
ms.topic: module

0 commit comments

Comments
 (0)