Deploying to Cloud Infrastructure
MS Learn path: Design and implement a release strategy — deepen module 8.
Overview
Where deployment automation lands: shipping to PaaS / container / Kubernetes targets on Azure, and using staging to make those deploys safe. The deploy pattern follows the target’s model — App Service slot swap, Container Instances / Container Apps image release, or Azure Kubernetes Service cluster rollout.
Units
- Deploying to PaaS (app-service slots, deployment slots + swap)
- Containers (push image, provision via arm-template/Bicep)
- Kubernetes (aks) — image + promote between stages
Concepts introduced
- app-service · deployment-slots · aks · aci · arm-template · staging
Key terms
- PaaS deploy — slot swap; instant, atomic, rollback-able.
- Container/image deploy — publish an image, promote between stages.
- Staging — a pre-prod environment mirroring prod; the last gate before production.
Hands-on
⚠ verify — add: deploy an App Service with a staging slot, swap, then roll back.
Exam focus
- Target choice drives the deploy pattern — slot swap (PaaS) vs image release + promote (container/AKS).
- Staging parity — automatically deploy to a prod-identical staging before go-live.
- Kubernetes (aks) deploys are made of image/application releases promoted across clusters, not a front-door swap.
Related
app-service · deployment-slots · aks · aci · arm-template · Path MOC