Custom domains and SSL in Azure - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a custom domain in Azure App Service?

A custom domain is a personalized web address (like www.yourwebsite.com) that you can use instead of the default Azure domain. It helps make your site look professional and easier to remember.

beginner

Why do you need SSL for your custom domain?

SSL (Secure Sockets Layer) encrypts data between users and your website. It protects sensitive information and shows visitors your site is safe with a padlock icon in the browser.

intermediate

How do you verify domain ownership in Azure when adding a custom domain?

You verify ownership by creating a DNS record (like a TXT or CNAME) at your domain registrar. Azure checks this record to confirm you control the domain before linking it.

intermediate

What is Azure App Service Managed Certificate?

It is a free SSL certificate provided by Azure for your custom domains. It automatically renews and helps secure your site without extra cost or manual steps.

intermediate

What is the difference between a CNAME and an A record when configuring custom domains?

A CNAME points your domain to another domain name (like your Azure app URL), while an A record points directly to an IP address. CNAMEs are easier to manage for cloud services.

What is the first step to use a custom domain in Azure App Service?

A Buy an SSL certificate

B Verify domain ownership by adding DNS records

C Create a virtual machine

D Deploy your app

You must first prove you own the domain by adding DNS records before linking it to Azure.

Which Azure feature provides free SSL certificates for custom domains?

A Azure CDN

B Azure Key Vault

C Azure Firewall

D Azure App Service Managed Certificate

Azure App Service Managed Certificate offers free SSL certificates that renew automatically.

What does SSL protect when used with a custom domain?

A Website design

B Domain registration

C Data between user and website

D Azure subscription

SSL encrypts data sent between the user and the website to keep it secure.

Which DNS record type is commonly used to verify domain ownership in Azure?

A TXT record

B SRV record

C PTR record

D MX record

TXT records are often used to prove domain ownership by adding specific values.

What is the main advantage of using a CNAME record for custom domains?

A Easier to manage cloud service URLs

B Points directly to IP address

C Faster DNS resolution

D Required for SSL

CNAME records point to domain names, making it easier to manage dynamic cloud service addresses.

Explain the process of adding a custom domain and securing it with SSL in Azure App Service.

Think about steps from owning a domain to making it secure with HTTPS.

Describe the difference between CNAME and A records when configuring custom domains in Azure.

Consider how DNS records link your domain to Azure resources.

Practice

1. What is the main purpose of adding a custom domain to an Azure web app?

easy

A. To increase the storage capacity of the web app

B. To use your own website name instead of Azure's default URL

C. To enable automatic backups of the web app

D. To improve the speed of the web app

Solution

1. Step 1: Understand what a custom domain is

   A custom domain lets you replace the default Azure URL with your own website name, making it easier for visitors to remember.

2. Step 2: Identify the purpose of using a custom domain

   Using your own domain improves branding and trust, not storage or speed.

3. Final Answer:

   To use your own website name instead of Azure's default URL -> Option B

4. Quick Check:

   Custom domain = Your own website name [OK]

Hint: Custom domain means your own website name, not Azure's URL [OK]

Common Mistakes:

• Confusing custom domain with storage or speed features
• Thinking custom domain automatically improves backups
• Assuming custom domain changes app performance

2. Which Azure CLI command is used to bind an SSL certificate to a web app's custom domain?

easy

A. az webapp domain bind

B. az webapp create ssl

C. az ssl certificate add

D. az webapp config ssl bind

Solution

1. Step 1: Recall Azure CLI commands for SSL binding

   The correct command to bind an SSL certificate to a web app is az webapp config ssl bind.

2. Step 2: Eliminate incorrect commands

   az webapp create ssl and az ssl certificate add are not valid commands. az webapp domain bind binds domains but not SSL certificates.

3. Final Answer:

   az webapp config ssl bind -> Option D

4. Quick Check:

   SSL bind command = az webapp config ssl bind [OK]

Hint: SSL bind uses 'az webapp config ssl bind' command [OK]

Common Mistakes:

• Using 'az webapp domain bind' for SSL binding
• Confusing create and bind commands
• Trying non-existent commands like 'az ssl certificate add'

3. Given this Azure CLI command:
az webapp config ssl bind --certificate-thumbprint abc123 --name myapp --resource-group mygroup --ssl-type SNI
What will this command do?

medium

A. Bind the SSL certificate with thumbprint abc123 to the web app myapp using SNI SSL

B. Create a new SSL certificate with thumbprint abc123 for the web app myapp

C. Remove the SSL certificate from the web app myapp

D. List all SSL certificates for the web app myapp

Solution

1. Step 1: Analyze the command parameters

   The command uses az webapp config ssl bind with a certificate thumbprint, web app name, resource group, and SSL type SNI.

2. Step 2: Understand the command effect

   This command binds the existing SSL certificate identified by thumbprint abc123 to the web app myapp using Server Name Indication (SNI) SSL.

3. Final Answer:

   Bind the SSL certificate with thumbprint abc123 to the web app myapp using SNI SSL -> Option A

4. Quick Check:

   SSL bind command with thumbprint = Bind SSL cert [OK]

Hint: Binding SSL uses thumbprint and 'az webapp config ssl bind' [OK]

Common Mistakes:

• Thinking the command creates or removes certificates
• Confusing listing certificates with binding
• Misunderstanding SNI SSL as removal

4. You tried to bind an SSL certificate to your Azure web app but got an error saying the certificate thumbprint was not found. What is the most likely cause?

medium

A. The SSL type SNI is not supported

B. The web app name is incorrect

C. The SSL certificate was not uploaded to the Azure resource group

D. The custom domain is not verified

Solution

1. Step 1: Understand the error about missing certificate thumbprint

   The error means Azure cannot find the SSL certificate with the given thumbprint in the resource group.

2. Step 2: Identify the cause

   This usually happens if the certificate was not uploaded or imported into the Azure resource group before binding.

3. Final Answer:

   The SSL certificate was not uploaded to the Azure resource group -> Option C

4. Quick Check:

   Missing thumbprint error = Certificate not uploaded [OK]

Hint: Upload SSL cert before binding to avoid thumbprint errors [OK]

Common Mistakes:

• Assuming web app name causes thumbprint errors
• Thinking SNI SSL is unsupported
• Ignoring domain verification as cause

5. You want to secure your Azure web app with a custom domain and SSL. Which sequence of steps is correct?

hard

A. Add custom domain to web app, upload SSL certificate, then bind SSL certificate to domain

B. Bind SSL certificate to web app, then add custom domain, then upload SSL certificate

C. Upload SSL certificate, add custom domain, then bind SSL certificate to domain

D. Add custom domain, bind SSL certificate, then upload SSL certificate

Solution

1. Step 1: Add the custom domain to the Azure web app

   You must first add your custom domain to the web app so Azure knows which domain to secure.

2. Step 2: Upload the SSL certificate to Azure

   Next, upload the SSL certificate to the Azure resource group to make it available for binding.

3. Step 3: Bind the SSL certificate to the custom domain

   Finally, bind the uploaded SSL certificate to the custom domain on the web app to enable HTTPS.

4. Final Answer:

   Add custom domain to web app, upload SSL certificate, then bind SSL certificate to domain -> Option A

5. Quick Check:

   Domain add -> cert upload -> cert bind [OK]

Hint: Add domain first, upload cert second, bind cert last [OK]

Common Mistakes:

• Trying to bind SSL before uploading certificate
• Binding SSL before adding custom domain
• Uploading certificate after binding