diff --git a/docs/images/app-connections/azure/client-secrets/create-certificate-method.png b/docs/images/app-connections/azure/client-secrets/create-certificate-method.png
new file mode 100644
index 000000000..37f642310
Binary files /dev/null and b/docs/images/app-connections/azure/client-secrets/create-certificate-method.png differ
diff --git a/docs/images/app-connections/azure/client-secrets/upload-certificate.png b/docs/images/app-connections/azure/client-secrets/upload-certificate.png
new file mode 100644
index 000000000..518c70b2d
Binary files /dev/null and b/docs/images/app-connections/azure/client-secrets/upload-certificate.png differ
diff --git a/docs/integrations/app-connections/azure-client-secrets.mdx b/docs/integrations/app-connections/azure-client-secrets.mdx
index cb25fb596..6c3b48ef6 100644
--- a/docs/integrations/app-connections/azure-client-secrets.mdx
+++ b/docs/integrations/app-connections/azure-client-secrets.mdx
@@ -66,29 +66,72 @@ Infisical currently only supports two methods for connecting to Azure, which are
-
- Ensure your Azure application has the required permissions that Infisical needs for the Azure Client Secrets connection to work.
- **Prerequisites:**
- - An active Azure setup.
+
-
-
- For the Azure Client Secrets connection to work, assign the following permissions to your Azure application:
+
+ Ensure your Azure application has the required permissions that Infisical needs for the Azure Client Secrets connection to work.
+
+ **Prerequisites:**
+ - An active Azure setup.
+
+
+
+ For the Azure Client Secrets connection to work, assign the following permissions to your Azure application:
+
+ #### Required API Permissions
+
+ **Microsoft Graph**
+ - `Application.ReadWrite.All`
+ - `Application.ReadWrite.OwnedBy`
+ - `Application.ReadWrite.All` (Delegated)
+ - `Directory.ReadWrite.All` (Delegated)
+ - `User.Read` (Delegated)
+
+ 
+
+
+
+
+ Ensure your Azure application has the required permissions that Infisical needs for the Azure Client Secrets connection to work.
+
+ **Prerequisites:**
+ - An active Azure setup.
+
+
+
+ For the Azure Client Secrets connection to work, assign the following permissions to your Azure application:
+
+ #### Required API Permissions
+
+ **Microsoft Graph**
+ - `Application.ReadWrite.All`
+ - `Application.ReadWrite.OwnedBy`
+ - `Application.ReadWrite.All` (Delegated)
+ - `Directory.ReadWrite.All` (Delegated)
+ - `User.Read` (Delegated)
+
+ 
+
+
+
+ Navigate to the **Certificates & secrets** section of your Azure App Registration, and press the **Upload certificate** button.
+
+ Select the **Upload** button and upload your certificate.
+
+ 
+
+
+ Keep in mind that you'll need the both the certificate & private key in order to configure the Azure Client Secrets connection within Infisical.
+
+
+
+
+
+
+
- #### Required API Permissions
-
- **Microsoft Graph**
- - `Application.ReadWrite.All`
- - `Application.ReadWrite.OwnedBy`
- - `Application.ReadWrite.All` (Delegated)
- - `Directory.ReadWrite.All` (Delegated)
- - `User.Read` (Delegated)
- 
-
-
-
## Setup Azure Connection in Infisical
@@ -123,6 +166,17 @@ Infisical currently only supports two methods for connecting to Azure, which are

+
+
+ Fill in the **Tenant ID**, **Client ID**, **Certificate**, and **Private Key** fields with the Directory (Tenant) ID, Application (Client) ID, Certificate and Private Key you obtained in the [previous step](#certificate-authentication).
+
+
+ The private key is never transmitted to Azure, and it is only used to sign the client assertion used to authenticate with Azure.
+
+
+ 
+
+