Lab 09b: Implement Azure Container Instances
I’m Amir Rouhanipoor, an IT Consultant specializing in Azure and cloud solutions. I help organizations streamline their IT and drive growth through secure, efficient cloud technologies.
Search for a command to run...
I’m Amir Rouhanipoor, an IT Consultant specializing in Azure and cloud solutions. I help organizations streamline their IT and drive growth through secure, efficient cloud technologies.
No comments yet. Be the first to comment.
Objective: This lab guides you through deploying a simple containerized application to Azure Container Apps (ACA). Scenario: Your organization is migrating an on-premises web application to the cloud and wants to minimize server management. You'll ev...
PowerShell Script for VM Size Comparison This script lists all session hosts with their host pool, VM name, and VM size across all host pools(loop through multiple resource groups): Connect-AzAccount # Get all host pools $hostPools = Get-AzWvdHostPo...
M03 - Unit 4: Configure an ExpressRoute Gateway Exercise Scenario To connect your Azure virtual network to your on-premises network using ExpressRoute, you must first create a virtual network gateway. A virtual network gateway serves two key purposes...
M02-Unit 3 Create and configure a virtual network gateway Scenario You will configure a VPN gateway to securely connect CoreServicesVnet (East US) and ManufacturingVnet (North Europe) using VNet-to-VNet VPN. Task 1: Create CoreServicesVnet and Manuf...
Introduction Azure ExpressRoute is a private, enterprise-grade connection that enables secure and reliable network connectivity between your on-premises infrastructure and Microsoft’s global network. It bypasses the public internet and provides high ...
You need to create three virtual networks: 1. CoreServicesVnet Region: East US Purpose: Main network (web services, databases, shared services like DC/DNS). Connectivity: Needs VPN connection to on-premises. Address Space: Large (because of expe...
Security-focused Cloud & Automation Engineer with a Master’s in Computer Science and 6+ years of experience automating and supporting enterprise IT environments across multi-site corporate and operational infrastructures. Proficient in Python scripting, Azure infrastructure, Windows Server, and identity management. Skilled in integrating third-party platforms, securing configurations, and streamlining operations. Currently pursuing the Cybersecurity Architect Expert certification with a strong focus on cloud security and automation.

Objective: This lab demonstrates how to deploy and test a containerized web application using Azure Container Instances (ACI).
Scenario: Your organization is evaluating Azure Container Instances as a solution for deploying a web application to the cloud without managing virtual machines. This is part of a broader effort to reduce infrastructure management overhead.
Key Concepts:
Azure Container Instances (ACI): A serverless compute service for running containers directly on Azure. It's ideal for simple applications, task automation, and build jobs, removing the need to manage underlying VMs.
Docker Image: A package containing an application and its dependencies, ensuring consistent execution across different environments.
Container Group: A collection of containers scheduled together on the same host in ACI. This lab uses a single-container group.
Task 1: Deploy an Azure Container Instance using a Docker image.
Task 2: Test and verify deployment of an Azure Container Instance.
Lab Tasks:
Task 1: Deploy an Azure Container Instance

Sign In: Log in to the Azure portal (https://portal.azure.com).
Create Container Instance: Search for and select "Container instances." and click "+ Create."
Basics:
Container name: az104-c1
Image source: Quickstart images
Image: mcr.microsoft.com/azuredocs/aci-helloworld:latest (Linux)
Networking: DNS name label: (Enter a globally unique name. This forms your container's public URL.) If you receive an error, try a different name.
Monitoring: Uncheck Enable container instance logs. (Simplifies the lab; you can explore logging later.)
Advanced: Accept the defaults then review + create**:** Verify the settings and click "Create.
Wait for Deployment: Allow 2-3 minutes for the deployment to complete.

Task 2: Test and Verify Deployment
Go to Resource: On the "Overview" blade, confirm the "Status" is Running.
Access the Application:
FQDN from the "Overview" blade. 
View Logs (Optional):
In your container instance, under "Settings," select "Containers."
Select "Logs."
You should see HTTP request logs from your browser. Refresh the web page a few times to generate more log entries.

Cleanup (Crucial):
az104-rg9-lod48969906 resource group to remove all lab resources. This prevents ongoing charges.