Module 4 — Configure Azure App Service
Grounded in MS Learn: az-104-manage-compute-resources → Configure Azure App Service (
learn.wwl.configure-azure-app-services)
Overview
Fourth module of the AZ-104 compute path. Provision and operate Azure App Service web apps hosted on an App Service plan: create an app, use deployment slots for safe releases, secure the app, configure custom domains, back up/restore, and enable Application Insights monitoring.
Learning objectives (authoritative)
- Identify features and usage cases for Azure App Service.
- Create an app with Azure App Service.
- Configure deployment settings, specifically deployment slots.
- Secure your Azure App Service app.
- Configure custom domain names.
- Back up and restore your Azure App Service app.
- Configure Azure Application Insights.
Concepts introduced
- Azure App Service — PaaS web/API/mobile backend hosting.
- App Service plans — the plan/instance the app runs under.
- Deployment slots — warm staging environments + zero-downtime swap.
- App Service authentication (Entra/social), managed TLS/SSL, IP restrictions, managed identities.
- Custom domains + TLS/Binding; backup & restore; Azure Application Insights telemetry.
Key terms & commands
- Create app:
az webapp create --resource-group <rg> --plan <plan> --name <app> --runtime "NODE|18-lts" - Deploy:
az webapp deploy --src-path <zip> --type zip; slots:az webapp deployment slot create --slot staging,az webapp deployment slot swap --slot staging - Custom domain:
az webapp config hostname add --hostname app.example.com+ validate (CNAME/alias) + TLS bind cert. - Backup:
az webapp config backup create; Monitoring:az monitor app-insights component+ enable on app.
Hands-on
- Create an app, deploy via ZIP, open a staging slot, deploy there, swap to production (observe zero downtime), and swap back to roll back.
- Add a slot (sticky) app setting so a production key does not move to staging during swap.
- Attach a custom domain with a cert and enable Application Insights to see requests/errors.
Exam focus
- Deployment slots workflow (deploy → validate → swap → rollback) and the slot-settings vs app-settings difference (sticky settings stay with their slot).
- App Service authentication = built-in identities module; custom domains need validation + TLS binding.
- Autoscale/scale actually lives on the plan (see module 3), not the app.
- Backup/restore of the app content + settings; Application Insights for runtime telemetry (not just VM diagnostics).
Related
Path MOC · app-service · app-service-plan · deployment-slots · Prev: plans