After your certificate request is approved, you can download your certificate from the SSL manager and install it on your Microsoft IIS Server. Once the certificate is installed on your IIS server, follow this guide to convert the certificate to a
.pfx file and upload it to your Microsoft Azure Portal.
- Click on your Start Menu, then click Run.
- In the prompt, type inetmgr and click OK to launch the Internet Information Services (IIS) Manager.
- Under the Connections panel on the left, click on your Server Name.
- In the main panel under the IIS section, double click on Server Certificates.
- Select your recently installed certificate.
- Under the Actions panel on the right, click Export….
- In the new window, click … under the Export to: section.
- Find the directory on your server where certificate and key files are stored, then type out your desired File name. Click Open.
- For the Password and Confirm password fields, type in a password to secure the file. This will be used when uploading the file to Azure.
- Click OK to create the
- Sign in to your Azure portal at https://portal.azure.com.
- On the left sidebar, click App Services and select your app in the new listing column that appears.
- On the left sidebar within your application area, find the SETTINGS grouping and click SSL certificates.
- In the new SSL area, click Upload Certificate.
- On the Add certificate sidebar to the right, click the folder icon to browse and select your
.pfxfile and click Open.
- Type out your password for the
.pfxfile in the Certificate password field and click Submit.
- In the main SSL area, click Add binding below your new certificate.
- On the Add SSL Binding sidebar to the right, select your Hostname and Certificate.
- Choose SNI SSL for SSL Type and click Add Binding to finalize the SSL install.
- Use our Certificate Checker to confirm the SSL is installed.
- Redirect your web app to HTTPS with a web.config file.
Note: As a courtesy, we provide information about how to use certain third-party products, but we do not endorse or directly support third-party products and we are not responsible for the functions or reliability of such products. Third-party marks and logos are registered trademarks of their respective owners. All rights reserved.