Learn cloud DevOps and infrastructure engineering on Microsoft Azure. Covers setting up and deploying AKS (Azure Kubernetes Service), network layout with Azure Virtual Network (VNet), role security with Microsoft Entra ID (formerly Azure AD), and scripting with the Azure CLI.
Intermediate
Updated Oct 1, 2026
~3 min read
8 sections
5 code examples
☁️
Deploying containers on AKSVNet virtual network designEntra ID permission managementAzure CLI scripts
Learn cloud DevOps and infrastructure engineering on Microsoft Azure. Covers setting up and deploying AKS (Azure Kubernetes Service), network layout with Azure Virtual Network (VNet), role security with Microsoft Entra ID (formerly Azure AD), and scripting with the Azure CLI. Rather than listing concepts, this guide is organized so you can follow the content in the order you have to make decisions on a real project.
Key perspective
Infrastructure / operations
Rather than memorizing install commands, understand the order in which traffic, runtime, observability, and incident response connect.
Deploying containers on AKSVNet virtual network designEntra ID permission managementAzure CLI scripts
Architecture diagrams
To make what you read stick, it helps to capture the flow as a picture first. The two diagrams below are reference maps you can keep coming back to while learning Azure.
Learning flow
Rendering diagram…
Architecture view
Rendering diagram…
Deploying containers on AKS
When you first open Azure, the big picture matters more than individual commands. This section starts with the problems the concepts ahead were created to solve.
AKS (Azure Kubernetes Service) simplifies the deployment and orchestration of microservices. Combined with the Azure CNI network plugin, pods get real IPs of the virtual network assigned directly, which makes on-premises integration and routing smooth.
BASH
# Create a resource group for the AKS cluster deploymentaz group create --name rg-dev-k8s --location eastus# Create the AKS cluster (with an autoscaling node pool)az aks create --resource-group rg-dev-k8s --name aks-dev-cluster \\ --node-count 3 --enable-cluster-autoscaler --min-count 1 --max-count 5 \\ --generate-ssh-keys# Fetch the kubectl configurationaz aks get-credentials --resource-group rg-dev-k8s --name aks-dev-cluster
Azure VNet design
Here you look at Azure VNet design alongside real code. Rather than copying the example as-is, read it with an eye on the inputs, the outputs, and the parts most likely to change.
Azure Virtual Network (VNet) is the foundation for designing a dedicated private cloud network. Set Network Security Group (NSG) policies to block access on specific ports and from external IP ranges.
Here you look at Microsoft Entra ID (Azure AD) security alongside real code. Rather than copying the example as-is, read it with an eye on the inputs, the outputs, and the parts most likely to change.
Entra ID handles cloud user permissions and app role authentication (RBAC). Create a Service Principal to give the CI/CD pipeline (GitHub Actions) a login role, and restrict its permissions.
BASH
# Create a service principal and assign it a role scoped to the resource groupaz ad sp create-for-rbac --name "github-actions-deployer" --role contributor \\ --scopes /subscriptions/your-subscription-id/resourceGroups/rg-dev-k8s --sdk-auth
Azure Monitor & Log Analytics
Here you look at Azure Monitor & Log Analytics alongside real code. Rather than copying the example as-is, read it with an eye on the inputs, the outputs, and the parts most likely to change.
For AKS and App Service, Diagnostic Settings must be turned on for logs and metrics to collect in a Log Analytics Workspace. If this setting lives outside the infrastructure code, it is easy to forget log collection every time a new resource is created, so it is safer to declare the diagnostic settings in the same Terraform/Bicep code that creates the resource.
BASH
# Create a Log Analytics Workspaceaz monitor log-analytics workspace create \ --resource-group rg-dev-k8s --workspace-name law-dev# Wire AKS diagnostic logs to be sent to Log Analyticsaz aks enable-addons --resource-group rg-dev-k8s --name aks-dev-cluster \ --addons monitoring --workspace-resource-id <LOG_ANALYTICS_RESOURCE_ID># Query recent error logs with KQLaz monitor log-analytics query \ --workspace <WORKSPACE_ID> \ --analytics-query "ContainerLogV2 | where LogLevel == 'error' | take 20"# Create a metric alert rule (when CPU exceeds 80%)az monitor metrics alert create --name high-cpu-alert \ --resource-group rg-dev-k8s \ --scopes <AKS_RESOURCE_ID> \ --condition "avg Percentage CPU > 80" \ --window-size 5m --evaluation-frequency 1m
Metric/query
Meaning
Why it matters
Percentage CPU (VM/AKS nodes)
Node CPU utilization
The basis for autoscaling thresholds and capacity planning
requests | where success == false
Failed requests in App Insights
The fastest way to catch an error rate surge right after a deployment
ContainerLogV2 severityLevel=="error"
Error logs from AKS pods
Can be wired all the way to alerts with a Log Analytics query
Using the Azure CLI
Here you look at Using the Azure CLI alongside real code. Rather than copying the example as-is, read it with an eye on the inputs, the outputs, and the parts most likely to change.
The az CLI is the official command-line tool for viewing, creating, and deleting almost every Azure resource from the shell: resource groups, VMs, AKS, networks, and more. After authenticating with az login, you can handle infrastructure as code from deployment scripts and CI/CD pipelines without opening the console.
BASH
# Log in & set the subscriptionaz loginaz account set --subscription "my-subscription-id"# List resource groups & resourcesaz group list --output tableaz resource list --resource-group rg-dev-k8s --output table# Check the AKS cluster stateaz aks show --resource-group rg-dev-k8s --name aks-dev-cluster --query provisioningState# Check costs (per subscription)az consumption usage list --output table
Azure practical design
Azure practical design is a point where the options diverge. Using the table to compare what each approach is for and how it differs in operation makes later decisions much easier.
Azure design is founded on the VNet subnet architecture and NSG security rule design, CNI integration for AKS clusters, and the RBAC role assignment scheme based on Microsoft Entra ID.
Decision point
Question to ask
Practical guideline
Boundaries
Which parts of the Azure code are most likely to change?
Separate input/output, configuration, external integrations, and the core rules.
State
Where is state created and where does it go away?
Make the owner and lifecycle of state visible in the code.
Failure
What does the caller receive on failure?
Decide the timeout, fallback, and error contract first.
Azure operating standards
This section covers Azure operating standards from a practical perspective. Instead of memorizing the concept, focus on the situations in which you would reach for it.
Continuously check Azure Monitor and Log Analytics metrics, the AKS node upgrade history, and compliance with Entra ID sign-in security policies.
Azure verification strategy
Azure verification strategy is a point where the options diverge. Using the table to compare what each approach is for and how it differs in operation makes later decisions much easier.
Include Azure Policy compliance checks, ARM template/Terraform validation, and network reachability tests for Private Endpoints.
Quality axis
How to verify
Definition of done
Correctness
Automate the normal/failure cases.
The core scenarios pass reproducibly.
Regression prevention
When fixing a bug, leave the same case behind as a test.
The same failure is not deployed again.
Operability
Check the logs, metrics, and alerts.
There is a path for tracing the cause when a problem occurs.
Azure: frequently asked questions
How do subscriptions, resource groups, and resources relate in Azure?
A subscription is the unit that gets billed, a resource group is a logical container for resources managed together, and a resource is an individual service such as a virtual machine or a database. Putting resources with the same lifecycle in one resource group makes it easy to grant permissions or delete them together.
What are the ways to run containers on Azure?
There is AKS, the managed Kubernetes service; Container Apps, which runs container-based apps serverlessly; and App Service for hosting web applications. With no Kubernetes operations experience and an ordinary web service, starting with Container Apps or App Service is simpler.
What is a managed identity?
It is an identity assigned to an Azure resource that lets it authenticate to other Azure services without putting passwords or keys in code. Azure issues and rotates the credentials, so it is the default choice when an application accesses a database or storage.