Study guide
6.5 App Service Certificates, TLS, Custom Domains, and Networking
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.5 App Service Certificates, TLS, Custom Domains, and Networking
Key Takeaways Explain This Topic AI
Custom domains require DNS ownership validation before they can be bound to an App Service app.
TLS requires a certificate binding after the custom hostname is added.
App Service supports inbound controls and outbound VNet integration, but these solve different network problems.
Private endpoints provide private inbound access to an app, while VNet integration is mainly for outbound access from the app.
Exam traps often mix DNS, TLS, access restrictions, service endpoints, private endpoints, and VNet integration.
Last updated: May 2026
Custom domains and DNS validation
Every App Service app receives a default hostname such as <app-name>.azurewebsites.net . Production apps usually need a custom hostname such as www.contoso.com or api.contoso.com . Before App Service accepts the hostname, Azure must verify that you control the domain. This is done through DNS records at the domain's DNS host.
Common record patterns are CNAME for subdomains and A records for apex domains. A www hostname often uses a CNAME that points to the Azure default hostname. An apex domain such as contoso.com usually needs an A record to the app's inbound IP address, plus validation records as required by the portal. TXT records are often used to prove ownership and prevent takeover risk.
Portal path: App Service > Custom domains > Add custom domain . The portal shows required DNS records and validation status. If validation fails, do not change the App Service plan first. Check public DNS propagation, record name, record type, target value, and whether the domain is managed in Azure DNS or an external registrar.
Goal Likely DNS or App Service action Common mistake
Add www.contoso.com Create CNAME to the app default hostname, then add hostname Creating only a certificate without hostname binding.
Add apex contoso.com Create A record and validation TXT as shown by portal Using CNAME at apex when DNS provider does not support it.
Prove domain ownership Add TXT validation record Putting TXT value under the wrong record name.
Secure the hostname Bind certificate after hostname is added Expecting DNS alone to enable HTTPS.
TLS and certificates
TLS for App Service requires a certificate and a binding to the custom hostname. App Service managed certificates are convenient for many simple custom domains, but they have limitations. Imported certificates are used when the organization already owns a certificate or needs a specific certificate authority, wildcard, or policy. App Service certificates can also be purchased and managed through Azure in supported scenarios.
Portal path: App Service > Certificates for certificate inventory and App Service > Custom domains for binding certificates to hostnames. You can enforce HTTPS-only and configure the minimum TLS version in TLS/SSL settings. If the requirement says users must not access the site over HTTP, enable HTTPS-only after a valid certificate binding exists.
- CLI examples: az webapp config hostname add \
- -resource-group rg-web \
- -webapp-name exam-web-prod \
- -hostname www.contoso.com
- az webapp update \
- -resource-group rg-web \
- -name exam-web-prod \
- -https-only true
Exam questions may present a site that works at azurewebsites.net but fails on the custom domain. Separate the layers. DNS maps the name. App Service hostname binding authorizes the name on the app. The certificate secures HTTPS for the name. Access restrictions or private endpoints determine whether clients can reach it.
Inbound and outbound networking
App Service has several network features that are easy to confuse. Access restrictions control inbound access to the public endpoint by allowing or denying client IP ranges, service tags, or virtual network sources in supported configurations. Private endpoint provides private inbound access to the web app from a virtual network. VNet integration is primarily for outbound traffic from the app to resources in a virtual network.
- Requirement Feature to recognize Direction
- Allow only corporate public IPs to reach the app Access restrictions Inbound
- Reach an Azure SQL private endpoint from the app VNet integration plus DNS/routing Outbound
- Let private clients access the app through a private IP Private endpoint for App Service Inbound
Resolve private endpoint names from the app Private DNS configuration with VNet integration Outbound dependency
Block general internet access to the app Private endpoint plus public access controls, or access restrictions depending on design Inbound
VNet integration does not make the app privately reachable. This is one of the most important traps. It lets the app send outbound traffic into a VNet. If users need to access the app privately, use a private endpoint for inbound access. Conversely, a private endpoint for the app does not automatically grant the app outbound access to a private database; configure outbound integration and DNS as needed.
Private DNS and name resolution
Private endpoint scenarios often fail because the network path exists but DNS still resolves to a public endpoint. For App Service connecting to a private endpoint dependency, the app must be integrated with a VNet that can resolve the dependency's private DNS name. If a SQL server, storage account, or Key Vault has public network access disabled, the app must resolve and route to the private endpoint.
The same DNS concept applies to inbound private endpoint access to the web app. Private clients should resolve the web app hostname to the private endpoint IP where appropriate. In Azure, this is usually handled with private DNS zones linked to the VNet. In hybrid environments, DNS forwarding may be required.
Troubleshooting path for private access:
Confirm the correct feature: private endpoint for inbound, VNet integration for outbound.
Confirm subnet and region requirements for the chosen feature.
Confirm private DNS zone records and VNet links.
Confirm public network access or access restrictions are set intentionally.
Test name resolution from the client or workload network.
Check logs on the app and dependency.
Portal versus CLI
The portal is often the fastest way to add and validate custom domains because it shows exact DNS records. Use the portal for certificate binding when learning or troubleshooting. Use CLI, ARM, or Bicep when deploying repeatable environments, especially for access restrictions, VNet integration, and hostname configuration.
Portal paths to memorize: Custom domains , Certificates , TLS/SSL settings , Networking , Access restrictions , and Identity . Many exam tasks use those names directly. If a lab-style task asks where to make a change, those labels matter.
Exam traps
Do not choose a certificate as the first step when the domain has not been validated or bound. Do not choose VNet integration when the requirement is private inbound access to the web app. Do not choose private endpoint when the only requirement is that the app call a database over a VNet; that requirement points first to outbound VNet integration for the app and private endpoint or service endpoint behavior for the dependency.
Do not assume that TLS fixes DNS. A valid certificate cannot help clients reach the wrong IP. Do not assume DNS validation fixes HTTPS. A custom domain can be validated but still lack a TLS binding. Work layer by layer: DNS ownership, hostname binding, certificate binding, HTTPS policy, inbound controls, outbound connectivity, and DNS resolution for private dependencies.