Skip to content

Infisical is the open-source platform for securing secrets, certificates, access, and AI Agents.

document the managed identity method for azure key vault connections

DimitrisStaratzis400d74cd48d9
diff --git a/docs/integrations/app-connections/azure-key-vault.mdx b/docs/integrations/app-connections/azure-key-vault.mdx
index 4ddc60eef5..40c913f319 100644
--- a/docs/integrations/app-connections/azure-key-vault.mdx
+++ b/docs/integrations/app-connections/azure-key-vault.mdx
@@ -6,7 +6,7 @@ description: "Learn how to configure a Azure Key Vault Connection for Infisical.
import AzureOAuthAppConfigurationServicePrincipal from "/snippets/app-connections/azure/oauth-app-configuration-service-principal.mdx";
-Infisical supports three methods for connecting to Azure Key Vault: OAuth, Client Secret, and Certificate (SPN with certificate).
+Infisical supports four methods for connecting to Azure Key Vault: OAuth, Client Secret, Certificate (SPN with certificate), and Managed Identity.
<Accordion title="Self-Hosted Instance">
Using the Azure Key Vault connection on a self-hosted instance of Infisical requires configuring an application in Azure
@@ -102,6 +102,15 @@ Infisical supports three methods for connecting to Azure Key Vault: OAuth, Clien
</Steps>
</Accordion>
+<Accordion title="Managed Identity Authentication">
+ To use managed identity authentication, you need a user-assigned managed identity that can access the Azure Key Vault instances you want to use. Infisical doesn't store a secret for this method.
+
+ **Prerequisites:**
+ - An existing Azure Key Vault instance
+ - A [user-assigned managed identity](https://learn.microsoft.com/en-us/entra/identity/managed-identities-azure-resources/how-manage-user-assigned-managed-identities) with access to your target Azure Key Vault instance(s) via Access Policies or RBAC (such as the **Key Vault Secrets Officer** role)
+ - If you self-host Infisical, a `SITE_URL` that Azure can reach from the internet, because Azure fetches Infisical's signing keys from it
+</Accordion>
+
## Setup Azure connection in Infisical
<Steps>
@@ -167,6 +176,23 @@ Infisical supports three methods for connecting to Azure Key Vault: OAuth, Clien
</Step>
</Steps>
</Tab>
+ <Tab title="Managed Identity">
+ <Steps>
+ <Step>
+ Select the **Managed Identity** method, fill in the **Tenant ID** and **Client ID** of your managed identity, then select **Configure Federated Credential**. Infisical creates the connection and shows its **Issuer**, **Subject Identifier**, and **Audience**.
+ </Step>
+ <Step>
+ In the Azure portal, open your managed identity and go to **Settings** > **Federated credentials** > **Add Credential**. Choose the **Other issuer** scenario and enter the values from Infisical.
+ </Step>
+ <Step>
+ Back in Infisical, select **Verify Connection**.
+ </Step>
+ </Steps>
+
+ <Tip>
+ If you create the connection through [the create endpoint](/api-reference/endpoints/app-connections/azure-key-vault/create), the response includes these values in `credentials.federatedCredential`.
+ </Tip>
+ </Tab>
</Tabs>
</Step>
<Step title="Connection Created">