You are migrating an on-premises web app that uses a custom public hostname to Azure and will keep that hostname. To enable HTTPS on the Azure web app, what should you do first with the certificate from the on-premises server?

To enable HTTPS on an Azure web app using a custom domain, you need to upload a certificate that includes both the public and private keys. A PFX (Personal Information Exchange) file is the standard format for storing a certificate and its corresponding private key. Exporting the private key is crucial because it allows the Azure web app to decrypt the SSL/TLS traffic. TripleDES is a commonly supported encryption algorithm for PFX files, ensuring compatibility with Azure App Service. Exporting only the public key (as a P7b or CER file) is insufficient because it lacks the private key necessary for SSL/TLS handshake completion. While AES256 is a stronger encryption algorithm than TripleDES, not all Azure services or older systems might fully support it for PFX imports, making TripleDES a more universally compatible choice for this scenario.