Azure Key Vault
Copy link to the page “Azure Key Vault”Imports the certificate as a new version into Azure Key Vault.
What happens
- The appliance connects to Azure Key Vault through Azure API on port 443.
- Certificate, key and chain are imported as a new current version of the selected Key Vault certificate name. Existing PEM or PFX format is preserved.
- The integration compares the stored leaf. Consumers with versionless references pick up the new version on their own schedule; no frontend TLS probe is performed.
Technical details
- Connection
- The integration runs on the appliance, which connects over HTTPS to Azure API, port 443. No service agent is installed.
- What you need
- Microsoft Entra admin center > App registrations > New registration. In the app: Certificates & secrets > New client secret, and copy its value. Azure portal > the key vault > Access control (IAM) > Add role assignment: give the app the roles Key Vault Certificates Officer and Key Vault Secrets User. A vault that uses access policies instead: Access policies > Create, certificate permissions Get, List, Import and Delete, secret permission Get. Enter the directory (tenant) ID, the application (client) ID and the secret value here.
- Actions
- Discovery, Installation, Verification, Rollback
- Integrations
-
azure-keyvault-api2.0.0 - Note
-
- Rollback uses previous_state and the vault’s previous exportable material to reimport the previous identity; an older version cannot be made current directly. No Azure CLI or local key backup is required. The certificate chain consists of the intermediate certificates that link the server certificate to a root certificate the browser trusts.