Skip to content

NLB-7335: Add guidance for using the Azure Key Vault Secret Identifiers #1576

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rishabh-f5 merged 5 commits into from
Dec 15, 2025
Merged

NLB-7335: Add guidance for using the Azure Key Vault Secret Identifiers #1576

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
651c214
NLB-7335: Add guidance for using the Azure Key Vault Secret Identifiers
rishabh-f5 Dec 15, 2025
442b68c
NLB-7335: remove anchor from heading
rishabh-f5 Dec 15, 2025
84989f2
Merge branch 'main' into NLB-7335-emphasize-akv-secret-identifier-for…
rishabh-f5 Dec 15, 2025
b5366ce
NLB-7335: remove azure key vault objects
rishabh-f5 Dec 15, 2025
f2ec738
Merge branch 'main' into NLB-7335-emphasize-akv-secret-identifier-for…
rishabh-f5 Dec 15, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions ...as-azure/getting-started/ssl-tls-certificates/ssl-tls-certificates-azure-cli.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,6 +43,11 @@ az nginx deployment certificate create --certificate-name
--key-vault-secret-id keyVaultSecretId
```

{{< call-out "important" >}}
The `--key-vault-secret-id` must be the **Secret Identifier**, not the Certificate Identifier.
To find the Secret Identifier, see [Finding the Azure Key Vault Secret Identifier]({{< ref "/nginxaas-azure/getting-started/ssl-tls-certificates/ssl-tls-certificates-portal/#finding-the-azure-key-vault-secret-identifier" >}}).
{{< /call-out >}}

See [Azure CLI Certificate Create Documentation](https://learn.microsoft.com/en-us/cli/azure/nginx/deployment/certificate#az-nginx-deployment-certificate-create) for more details on the available parameters.

## Update a certificate
Expand Down
24 changes: 24 additions & 0 deletions ...nxaas-azure/getting-started/ssl-tls-certificates/ssl-tls-certificates-portal.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,30 @@ You can manage SSL/TSL certificates for F5 NGINXaaS for Azure (NGINXaaS) using t

{{< include "/nginxaas-azure/ssl-tls-prerequisites.md" >}}

## Finding the Azure Key Vault Secret Identifier

When adding a certificate using the Azure CLI, Terraform, or ARM/Bicep templates, you need to provide the **Secret Identifier** from Azure Key Vault.

{{< call-out "important" >}}
**Use the Secret Identifier, not the Certificate Identifier.**

NGINXaaS requires the **Secret Identifier** to access the certificate and its private key.
{{< /call-out >}}

To find the Secret Identifier:

1. Go to your Azure Key Vault in the Azure portal.
1. Select **Certificates** from the left menu.
1. Select the certificate you want to use.
1. Select the current version of the certificate.
1. Copy the **Secret Identifier** value (not the Certificate Identifier).

The Secret Identifier format is:

```text
https://{vault-name}.vault.azure.net/secrets/{certificate-name}
```

### Adding an SSL/TLS certificate

Before you begin, refer Azure documentation to [Import a certificate to your Key Vault](https://learn.microsoft.com/en-us/azure/key-vault/certificates/tutorial-import-certificate?tabs=azure-portal#import-a-certificate-to-your-key-vault).
Expand Down