Skip to content

Ulysses Neves

Microsoft Entra ID, authentication, and hybrid identity troubleshooting.

Menu
  • Home
  • Microsoft Azure
  • Microsoft AD FS
  • Microsoft 365
  • Contact
  • Troubleshooting Index
Menu

Azure App Services – Publishing an application with a custom domain and SSL on Azure

Posted on July 4, 2020

Hello everyone. In today’s article I’ll explain step by step how to create an app service on Azure, configure the application on a custom domain, and enable SSL for secure access using HTTPS.

What is an Azure App Service?

Azure App Service allows you to publish and scale applications on Azure using containers on Windows or Linux. You can work with .NET, .NET Core, Node.js, Java, Python, or PHP applications.

In this article, we will perform the following activities:

  • Create an app service on Azure.
  • Configure the application page.
  • Configure the custom domain on the app service.
  • Apply the SSL certificate for secure access using HTTPS.
  • Validate access to the published application.

Creating an App Service on Azure

Let’s start by creating the app service on Azure. Access the Azure App Service menu.

Click Add.

Follow the steps below to start creating the application:
1 – Select the resource group you want to use for the application.
2 – Create a name for the application on Azure.

Follow the steps below to configure the platform and region where the application will be hosted:
1 – Select the platform to be used for the application.
2 – Select the region where the application will be hosted. Keep in mind that some regions won’t have all platforms available.

Follow the steps below to configure the service plan:
1 – Let’s select the default plan offered by the North Europe region.
2 – Let’s change the application capacity to support custom domains.

To support custom domains, we need to select at least the S1 plan from the Production menu as shown below:

Click Apply.

Let’s keep the remaining settings and click Review + Create.

Click Create once the configuration validations are OK.

Configuring the application page

Once the application creation is complete, let’s view the settings by clicking the name of the created application.

We can see that the application already supports HTTPS using the default Azure domain: azurewebsites.net.

For this example, I created a simple HTML page. Let’s publish the page by following the steps below:
1 – Select Deployment Center in the Deployment menu.
2 – Select FTP to publish the page to Azure.
3 – Let’s click Dashboard to get the FTP access information.

Copy the FTPS URL by clicking Copy.

Paste the copied URL into Windows Explorer, enter the password provided on the previous screen, and click Log On.

Now let’s copy the created page to the wwwroot folder.

Now let’s validate access to the published page using the URL: https://portal-ulysses.azurewebsites.net available in the application settings.

Configuring the custom domain on the application

In a production environment, it’s important for the company’s domain to be used to access the application. To achieve this, we have the Custom domains option.

Let’s change the domain in the application access URL by selecting the Custom domains menu.

Select the Add custom domain option.

Enter the custom domain in the Custom domain menu and click Validate.

We can see that it’s necessary to confirm ownership of the domain to proceed with the configuration.

Let’s create, at the service where the domain was registered, the records that allow us to confirm ownership of the domain ulyneves.com as instructed above. In our case, we’ll publish this on GoDaddy’s DNS.

As shown below, we’ll create a TXT-type record with the code generated by the application on Azure.

With the correct settings, let’s click Adicionar.

Let’s also add an A-type record pointing to the IP of the server where the application is hosted on Azure.

Let’s click Salvar.

Once the DNS record propagation is complete, let’s follow the steps below to publish the custom domain:
1 – Click Validate again.
2 – Click Add custom domain.

We can see, when accessing the created application’s settings again, that the custom domain is now being used, but still on http.

When accessing the new (URL) we see the “not secure” site message.

Adding the SSL certificate to the application

To ensure security when accessing the configured application, we’ll apply the certificate generated by Certisign for the domain ulyneves.com to the application, in order to enable access using https.

With the certificate in hand, select the TLS/SSL settings menu.

In the Private Key Certificates (pfx) menu, click Upload Certificate.

Perform the activities below to add the custom domain’s SSL certificate:
1 – Select the .pfx type certificate
2 – Enter the certificate password.

Let’s enable the http to https redirection option and activate the PFX certificate added in the previous step:
1 – In the HTTPS Only option, select On.
2 – In the TLS/SSL bindings option, click Add TLS/SSL Binding.

Follow the steps below:
1 – Select the custom domain configured on the application.
2 – Select the SSL certificate for the selected domain.
3 – Let’s use the SNI SSL type, which allows multiple TLS/SSL certificates for multiple domains using the same IP address.

Accessing the application after configuring SSL

With the configuration complete, we can see the URL with HTTPS and the custom domain in the created application’s settings.

Let’s validate the settings made in this article by accessing the URL https://ulyneves.com.

Summary

In today’s article, we demonstrated how to create an application on Azure App Service, configure a custom domain for use with this application, and an SSL certificate for HTTPS access.

I hope this content has contributed to enriching your knowledge of Azure App Services.

Did you like the post? Like and share it. 🙂

If you have any suggestions or comments, let us know.

[ ]’s

Ulysses Neves

Related guides: Browse the Microsoft Identity Troubleshooting Index or the Microsoft Azure topic archive.

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Recent Posts

  • Microsoft Defender for Identity domain investigation: six questions to ask first September 10, 2026
  • Microsoft Entra Kerberos key rotation: what changes—and what administrators should check September 6, 2026
  • Microsoft Authenticator Will Block Jailbroken Devices in 2026 — What You Need to Know March 17, 2026
  • Enhancing Azure role activation security with FIDO2/Passkeys September 23, 2024
  • Microsoft Entra ID CAP | Enforcing WHfB using Authentication Strength April 21, 2024

Archives

  • September 2026
  • March 2026
  • September 2024
  • April 2024
  • February 2024
  • December 2023
  • September 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • December 2019
  • November 2019
  • October 2019
  • September 2019
  • August 2019
  • July 2019

Tags

#aaddownleveldevice #adfs #adfscertificate #adfscertificates #adfsmfaadapter #azureauth #azureCA #azuredevice #capolicy #cloudsummit2021 #conditionalaccess #conditionalaccesspolicy #deviceregistration #farmbehavior #gopasswordless #mfaserver #msidentity #namedlocation #securingazure #securingazuread #sslprivatekey #troubleshootingadfs #troubleshootingwaptrust #tshootadfs #waptrust #webapplicationproxy #WHFBcerttrust #whfbdeployment #WHfBhybridsetup #WHfBprovisioning #widdatabase adconnect AD FS authenticationstrength az500 azurepim Azure security cloudsecurity microsoft365 Microsoft Azure Microsoft Entra hybrid join Microsoft Entra ID Microsoft Entra MFA PowerShell WHfB
©2026 Ulysses Neves | Design: Newspaperly WordPress Theme
Ulysses Neves
Gerenciar Consentimento de Cookies
Para fornecer as melhores experiências, usamos tecnologias como cookies para armazenar e/ou acessar informações do dispositivo. O consentimento para essas tecnologias nos permitirá processar dados como comportamento de navegação ou IDs exclusivos neste site. Não consentir ou retirar o consentimento pode afetar negativamente certos recursos e funções.
Funcional Always active
O armazenamento ou acesso técnico é estritamente necessário para a finalidade legítima de permitir a utilização de um serviço específico explicitamente solicitado pelo assinante ou utilizador, ou com a finalidade exclusiva de efetuar a transmissão de uma comunicação através de uma rede de comunicações eletrónicas.
Preferências
O armazenamento ou acesso técnico é necessário para o propósito legítimo de armazenar preferências que não são solicitadas pelo assinante ou usuário.
Estatísticas
O armazenamento ou acesso técnico que é usado exclusivamente para fins estatísticos. O armazenamento técnico ou acesso que é usado exclusivamente para fins estatísticos anônimos. Sem uma intimação, conformidade voluntária por parte de seu provedor de serviços de Internet ou registros adicionais de terceiros, as informações armazenadas ou recuperadas apenas para esse fim geralmente não podem ser usadas para identificá-lo.
Marketing
O armazenamento ou acesso técnico é necessário para criar perfis de usuário para enviar publicidade ou para rastrear o usuário em um site ou em vários sites para fins de marketing semelhantes.
  • Manage options
  • Manage services
  • Manage {vendor_count} vendors
  • Read more about these purposes
Ver preferências
  • {title}
  • {title}
  • {title}