From 73a8a9ee37a75459f7e065e61da06f2cc936f483 Mon Sep 17 00:00:00 2001
From: hc-github-team-secure-vault-core
 <82990506+hc-github-team-secure-vault-core@users.noreply.github.com>
Date: Wed, 30 Aug 2023 12:49:33 -0400
Subject: [PATCH] backport of commit 92734f109d385f85f877fc1040c87658778e5e5b
 (#22643)

Co-authored-by: ram-parameswaran <109940849+ram-parameswaran@users.noreply.github.com>
---
 website/content/docs/secrets/azure.mdx | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/website/content/docs/secrets/azure.mdx b/website/content/docs/secrets/azure.mdx
index 8fa65a91b..9682fd5d0 100644
--- a/website/content/docs/secrets/azure.mdx
+++ b/website/content/docs/secrets/azure.mdx
@@ -300,6 +300,18 @@ Azure service principal configured with the same permissions.
   `ffffff`. These may be used to search for Vault-created credentials using the `az` tool
   or Portal.
 
+## Azure debug logs
+
+The Azure secret engine plugin supports debug logging which includes additional information
+about requests and responses from the Azure API.
+
+To enable the Azure debug logs, set the `AZURE_GO_SDK_LOG_LEVEL`  environment variable to `DEBUG` on your Vault
+server:
+
+```shell
+AZURE_GO_SDK_LOG_LEVEL=DEBUG
+```
+
 ## Help &amp; support
 
 The Azure secrets engine is written as an external Vault plugin and