Study guide
6.4 App Service Plan, Apps, and Runtime Configuration
AZ-104 Microsoft Azure Administrator Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Orientation and Microsoft Learn Source Control
1.1 Current AZ-104 Exam Facts 1.2 Administrator Role and Candidate Profile 1.3 Skills Outline and Weighted Study Map 1.4 Exam Duration, Question Types, Labs, and Learn Access 1.5 Scoring, Retakes, Renewal, and Account Choice 1.6 Using the Practice Bank, Labs, and Error Log
2 Chapter 2: Identity, RBAC, and Governance Foundations
2.1 Microsoft Entra Users, Groups, and Properties 2.2 Licenses, External Users, and SSPR 2.3 Azure RBAC Built-In Roles and Scopes 2.4 Role Assignment Interpretation and Deny Effects 2.5 Management Groups, Subscriptions, and Resource Groups 2.6 Azure Policy, Locks, Tags, and Governance Controls 2.7 Identity and Governance Case Lab
3 Chapter 3: Subscriptions, Policy, Costs, and Resource Organization
3.1 Subscription Design and Management Groups 3.2 Resource Groups, Lifecycle, and Move Operations 3.3 Tagging Strategy and Cost Allocation 3.4 Budgets, Alerts, and Azure Advisor Cost Recommendations 3.5 Policy, Initiative, Assignment, and Remediation 3.6 Resource Locks, RBAC, Policy, and Tags Combined 3.7 Governance and Cost Case Lab
4 Chapter 4: Storage Accounts, Access, and Data Protection
4.1 Storage Account Design, Redundancy, and Encryption 4.2 Storage Firewalls, Private Access, and Network Rules 4.3 SAS Tokens, Stored Access Policies, and Access Keys 4.4 Identity-Based Access for Azure Files 4.5 Blob Tiers, Lifecycle, Soft Delete, and Versioning 4.6 Azure Files, Snapshots, File Sync, and AzCopy 4.7 Storage Case Lab
5 Chapter 5: Compute, Virtual Machines, Scale Sets, and Bicep
5.1 ARM Templates, Bicep, and Deployment Workflow 5.2 Create, Configure, and Manage Virtual Machines 5.3 VM Disks, Sizes, Encryption, and Host Settings 5.4 Availability Zones, Sets, and VM Scale Sets 5.5 Move VMs Across Resource Groups, Subscriptions, and Regions 5.6 Backup, Restore, and Operational Maintenance for VMs 5.7 VM Compute Case Lab
6 Chapter 6: Containers, App Service, and Platform Compute
6.1 Azure Container Registry and Image Workflow 6.2 Azure Container Instances and Container Apps 6.3 Container Sizing, Scaling, and Environment Choices 6.4 App Service Plan, Apps, and Runtime Configuration 6.5 App Service Certificates, TLS, Custom Domains, and Networking 6.6 App Service Backups, Deployment Slots, and Scaling 6.7 Platform Compute Case Lab
7 Chapter 7: Virtual Networking, Routing, and Secure Access
7.1 VNet, Subnet, and Address Space Design 7.2 VNet Peering and Cross-Network Connectivity 7.3 Public IP Addresses and NAT Patterns 7.4 User-Defined Routes and Effective Routes 7.5 NSGs, ASGs, and Effective Security Rules 7.6 Azure Bastion, Service Endpoints, and Private Endpoints 7.7 Secure Networking Case Lab
8 Chapter 8: Name Resolution, Load Balancing, and Connectivity Troubleshooting
8.1 Azure DNS, Private DNS, and Name Resolution 8.2 Public and Internal Load Balancer Design 8.3 Backend Pools, Health Probes, and Load Balancing Rules 8.4 Load Balancing Troubleshooting Workflow 8.5 Network Watcher: IP Flow, Next Hop, and Connection Troubleshoot 8.6 Hybrid Connectivity, VPN, ExpressRoute, and DNS Considerations 8.7 Connectivity Troubleshooting Case Lab
9 Chapter 9: Monitoring, Alerting, Backup, and Site Recovery
9.1 Azure Monitor Metrics, Logs, and Diagnostic Settings 9.2 Log Analytics, KQL, and Operational Queries 9.3 Alert Rules, Action Groups, and Alert Processing Rules 9.4 VM, Storage, and Network Insights 9.5 Recovery Services Vault, Backup Vault, and Backup Policies 9.6 Azure Site Recovery, Failover, and Replication 9.7 Monitoring and Recovery Case Lab
10 Chapter 10: AZ-104 Integration and Troubleshooting Case Labs
10.1 Domain Weight Triage and Study Prioritization 10.2 Identity, Storage, and Compute Integrated Cases 10.3 Networking, Monitoring, and Security Integrated Cases 10.4 Migration, Move, Backup, and Recovery Cases 10.5 Permissions, Network, and Storage Troubleshooting Chain 10.6 Microsoft Learn Lookup Strategy Under Time Pressure 10.7 Full-Domain Case Lab
11 Chapter 11: Final Review, Exam Experience, Renewal, and Career Path
11.1 Final Two-Week Study Plan 11.2 Hands-On Lab Checklist and Command Review 11.3 Exam Day, Pearson VUE, Breaks, and Learn Access 11.4 Retake Plan, Score Report, and Weak-Domain Repair 11.5 Renewal Assessment and Annual Certification Maintenance 11.6 After AZ-104: AZ-305, AZ-400, SC-500, and Job Paths
6.4 App Service Plan, Apps, and Runtime Configuration
Key Takeaways Explain This Topic AI
An App Service plan defines the compute resources, region, operating system family, tier, and scale boundary for App Service apps.
Web apps, API apps, and custom container apps run inside a plan and share its worker capacity.
Runtime stack, app settings, connection strings, managed identity, and deployment settings are configured on the app.
Scaling and feature availability depend heavily on the App Service plan tier.
Exam scenarios often test whether a setting belongs on the plan, the app, the slot, or the deployment source.
Last updated: May 2026
App Service plan versus app
Azure App Service is a platform service for hosting web apps, APIs, and custom container workloads. The App Service plan is the compute container for one or more apps. It defines the region, OS type, pricing tier, worker size, and scale capacity. The app defines the hostname, runtime stack, code or container settings, app settings, authentication options, identity, custom domains, TLS bindings, deployment source, and logs.
A useful exam rule: if the question asks how much compute exists or which paid features are available, look at the plan. If it asks what code runs, what environment variable is set, what container image is used, or what identity the app uses, look at the app.
Setting or feature Configure on plan or app? Notes
Pricing tier and worker size App Service plan Controls capacity and feature availability.
Number of instances for scale out App Service plan Apps in the same plan share workers.
Runtime stack such as .NET, Node, Java, Python App Selected when creating or configuring the web app.
Custom container image and registry App App points to image and registry authentication.
App settings and connection strings App or slot Can be marked as deployment slot settings.
Managed identity App Used for Azure resource access such as Key Vault or ACR pull.
Custom domain and TLS binding App Requires DNS validation and certificate binding.
Deployment slots App, dependent on tier Slots are available in supported tiers and swap app content/configuration.
Portal creation path: Azure portal > App Services > Create > Web App . During creation, the portal asks for resource group, name, publish model, runtime stack or container, OS, region, and App Service plan. For custom containers, choose container publishing and provide the image source, registry, image, and tag.
- CLI example for code-based app: az appservice plan create \
- -resource-group rg-web \
- -name asp-prod-linux \
- -location eastus \
- -is-linux \
- -sku P1v3
- az webapp create \
- -resource-group rg-web \
- -plan asp-prod-linux \
- -name exam-web-prod \
- -runtime "NODE:20-lts"
- CLI example for container-based app: az webapp create \
- -resource-group rg-web \
- -plan asp-prod-linux \
- -name exam-container-web \
- -deployment-container-image-name examacr104.azurecr.io/apps/web:v1
- Plan tier decisions
Plan tier is one of the most tested App Service topics because many features depend on it. Free and Shared are useful for low-cost testing but are limited. Basic supports dedicated compute for simple production apps. Standard adds features commonly associated with production such as autoscale and deployment slots. Premium tiers provide stronger scale and advanced networking-related capabilities. Isolated tiers are associated with App Service Environment requirements.
Do not memorize only price names. Read the requirement. If the scenario asks for deployment slots, custom domain with TLS, scale out, or VNet integration, a very low tier is usually wrong. If the scenario says several apps are in one plan and one app consumes all CPU, the fix may be scaling the plan, moving the noisy app to a separate plan, or configuring autoscale depending on constraints.
Plan sharing is important. Multiple apps in the same App Service plan share the same worker resources. This can reduce cost for related apps, but it also means heavy apps can affect others. The exam may ask why two apps show degraded performance at the same time; if they share a plan, check plan CPU, memory, and instance count.
Runtime configuration
App settings are environment variables exposed to the application. Connection strings are stored separately in the App Service configuration surface. Both can be changed without rebuilding the application package. For slot-based deployments, some settings can be marked as slot settings so they remain with the slot during swaps. This is critical for values like database connection strings, feature flags, and external service endpoints.
Portal path: App Service > Configuration > Application settings for app settings and connection strings. App Service > Identity enables system-assigned or user-assigned managed identity. App Service > Deployment Center configures deployment source. App Service > Log stream and App Service logs help troubleshoot startup and runtime failures.
- CLI examples: az webapp config appsettings set \
- -resource-group rg-web \
- -name exam-web-prod \
- -settings ENVIRONMENT=prod API_BASE_URL=https://api.contoso.com
- az webapp identity assign \
- -resource-group rg-web \
- -name exam-web-prod
For custom containers, the container must listen on the expected port. If the app starts but App Service cannot reach it, configure the port setting expected by the platform, commonly through app settings such as WEBSITES_PORT for Linux custom containers when needed. Always inspect container logs before changing DNS or certificates.
Portal and CLI choice
Use the portal for one-off setup, certificate binding, identity confirmation, log streaming, and visual scale configuration. Use CLI, ARM, or Bicep for repeatable plan creation, app settings, and deployment automation. AZ-104 includes interpretation tasks, so you should understand what commands change.
Example interpretation: az webapp config appsettings set does not scale the app. It updates environment variables. az appservice plan update --sku P1v3 changes the plan tier. az webapp deployment slot swap swaps slots. az webapp config container set changes container settings.
Troubleshooting runtime failures
Use this sequence:
Confirm the App Service plan is running and not exhausted.
Confirm the app runtime stack or container image matches the application.
Confirm app settings and connection strings are present.
Confirm managed identity has required permissions to dependencies.
Confirm the app listens on the expected port.
Use logs before making infrastructure changes.
If a web app cannot access Key Vault, changing the App Service plan size is rarely the first fix. Check managed identity, Key Vault access model, RBAC or access policy, firewall, and private endpoint/DNS if used. If a web app returns 502 after a custom container deployment, check startup logs, image pull success, exposed port, and health behavior.
Exam traps
Do not confuse App Service plan region with app code location. Apps in a plan run where the plan is located. Do not create a Windows plan for a Linux container app or assume you can mix Windows and Linux apps freely in the same plan. OS type is a plan-level decision.
Do not assume every App Service feature exists in Free or Shared tiers. Do not place unrelated high-traffic production apps into the same plan without considering resource contention. Do not store secrets in source code because App Service offers configuration, managed identities, and integration with secret stores.
The most reliable mental model is: plan equals workers and tier; app equals runtime and behavior; slot equals alternate deployment surface for the same app; deployment source equals how code or images arrive.