From 5ba15defe5eb63cc0bdeb8d8d794a4c6b06351cc Mon Sep 17 00:00:00 2001 From: Max Coulombe <109547106+maxcoulombe@users.noreply.github.com> Date: Thu, 21 Sep 2023 14:05:44 -0400 Subject: [PATCH] Azure secret doc enhancement (#23079) * * azure secret doc enhancement Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com> --------- Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com> --- website/content/docs/secrets/azure.mdx | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/website/content/docs/secrets/azure.mdx b/website/content/docs/secrets/azure.mdx index f7ab3b55f774..0e3eedb05895 100644 --- a/website/content/docs/secrets/azure.mdx +++ b/website/content/docs/secrets/azure.mdx @@ -23,6 +23,15 @@ The password will be deleted when the lease is revoked. ## Setup + + + You can configure the Azure secrets engine with the Vault API or + established environment variables such as `AZURE_CLIENT_ID` or + `AZURE_CLIENT_SECRET`. If you use both methods, note that + environment variables always take precedence over API values. + + + Most secrets engines must be configured in advance before they can perform their functions. These steps are usually completed by an operator or configuration management tool.