Compatible with
account required
Azure Key Vault private issuer
Azure Key Vault certificate issuer policies, create/import, version listing and secret retrieval for deployment are implemented via ARM and the vault data plane.
Verification: test_verified. Connection: unknown. Credentials: none. Live E2E: no.
Azure service principal with Key Vault certificate permissions is not configured.
What sslcertificates.io can do
Azure Key Vault certificate issuer policies, create/import, version listing and secret retrieval for deployment are implemented via ARM and the vault data plane. Capabilities: issuer_policies, create_certificate, import, versions. Authentication uses service_principal.
Required permissions
Key Vault Certificates Officer on selected vaults. Discover subscriptions and vaults first.
Setup
Open Dashboard → Integrations → Azure Key Vault private issuer. Enter the credentials described on this page. Values are encrypted at rest and never shown again. Run Test connection. Discovery runs only after authentication succeeds. Select a discovered resource. Do not paste opaque IDs unless the provider cannot enumerate them. Perform the certificate or notification action, then confirm the external system matches. Disconnect removes stored credentials and owned test resources created by sslcertificates.io.
Known limitations
Merged with Azure Key Vault Certificates for customer-managed issuers. Does not claim Microsoft public CA partnership.
Official sources
Fact checked 2026-09-20. https://learn.microsoft.com/azure/key-vault/certificates/overview-from-customer-managed-ca Azure Key Vault private issuer is a trademark of its owner. sslcertificates.io is not a partner or certified reseller unless a written agreement exists.
Capabilities
Connect
Azure Key Vault private issuer is a trademark of its owner. sslcertificates.io is not a partner or certified reseller unless a written agreement exists.