Skip to content

← All integrations

Cloud service

Uploads the certificate to a web app and binds it to its custom host names.

The appliance runs the integration and connects to Azure App Service through Azure Resource Manager over HTTPS on port 443. No service agent is installed on Azure App Service.

What happens

  1. The appliance connects to Azure App Service through Azure Resource Manager on port 443.
  2. The integration uploads or reuses a certificate in the web app’s resource group and region. Covered custom hostnames are bound to it, preserving existing SNI or IP mode.
  3. Bindings are read back and each concrete hostname is checked over TLS for up to 90 seconds. Unreachable or still propagating frontends are reported separately.

Technical details

Connection
The integration runs on the appliance, which connects over HTTPS to Azure Resource Manager, port 443. No service agent is installed.
What you need
Azure portal > Microsoft Entra ID > App registrations > New registration. Certificates & secrets > New client secret; copy the value (shown only once). Then on the web app's resource group: Access control (IAM) > Add role assignment > Website Contributor > the app registration. Enter the directory (tenant) ID, the application (client) ID, the secret and the subscription ID here.
Actions
Discovery, Installation, Verification, Rollback, Removal
Integrations
azure-appservice-api 2.0.0
Note
  • Rollback uses previous_state to restore prior SSL mode and thumbprint on bindings still belonging to the deployment. Undeploy also removes the integration’s upload once no web app uses it. Reused certificates are retained; no local journal is required.

Next steps