Skip to content

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

move text into a shared snippet

adilson615333fe81ed
diff --git a/docs/integrations/app-connections/azure-app-configuration.mdx b/docs/integrations/app-connections/azure-app-configuration.mdx
index a721e5a8ed..877210902f 100644
--- a/docs/integrations/app-connections/azure-app-configuration.mdx
+++ b/docs/integrations/app-connections/azure-app-configuration.mdx
@@ -4,6 +4,8 @@ sidebarTitle: "Azure App Configuration"
description: "Learn how to configure a Azure App Configuration Connection for Infisical."
---
+import AzureOAuthAppConfigurationServicePrincipal from "/snippets/app-connections/azure/oauth-app-configuration-service-principal.mdx";
+
Infisical currently only supports two methods for connecting to Azure, which are OAuth and Client Secrets.
<Accordion title="Self-Hosted Instance">
@@ -114,15 +116,7 @@ Infisical currently only supports two methods for connecting to Azure, which are
![Connect via Azure OAuth](/images/app-connections/azure/app-configuration/create-oauth-method.png)
- <Info>
- If you use Infisical Cloud, the OAuth flow requests every permission on Infisical's shared Azure app registration (the `.default` scope), including the permissions for Azure App Configuration. If your Azure tenant doesn't have the Azure App Configuration service principal, the OAuth flow fails. To create the service principal, run the following [Azure CLI](https://learn.microsoft.com/en-us/cli/azure/install-azure-cli) command, then try to connect again:
-
- ```bash
- az ad sp create --id 35ffadb3-7fc1-497e-b61b-381d28e744cc
- ```
-
- `35ffadb3-7fc1-497e-b61b-381d28e744cc` is the application ID that Microsoft assigns to Azure App Configuration, and it's the same in every Azure tenant.
- </Info>
+ <AzureOAuthAppConfigurationServicePrincipal />
</Step>
<Step title="Grant Access">
You will then be redirected to Azure to grant Infisical access to your Azure account. Once granted,
diff --git a/docs/integrations/app-connections/azure-client-secrets.mdx b/docs/integrations/app-connections/azure-client-secrets.mdx
index 8bf16a814b..b5719a0080 100644
--- a/docs/integrations/app-connections/azure-client-secrets.mdx
+++ b/docs/integrations/app-connections/azure-client-secrets.mdx
@@ -4,6 +4,8 @@ sidebarTitle: "Azure client secrets"
description: "Learn how to configure an Azure Client Secrets Connection for Infisical."
---
+import AzureOAuthAppConfigurationServicePrincipal from "/snippets/app-connections/azure/oauth-app-configuration-service-principal.mdx";
+
Infisical currently only supports two methods for connecting to Azure, which are OAuth and Client Secrets.
<Accordion title="Self-Hosted Instance">
@@ -155,15 +157,7 @@ Infisical currently only supports two methods for connecting to Azure, which are
![Connect via Azure OAuth](/images/app-connections/azure/client-secrets/create-oauth-method.png)
- <Info>
- If you use Infisical Cloud, the OAuth flow requests every permission on Infisical's shared Azure app registration (the `.default` scope), including the permissions for Azure App Configuration. If your Azure tenant doesn't have the Azure App Configuration service principal, the OAuth flow fails. To create the service principal, run the following [Azure CLI](https://learn.microsoft.com/en-us/cli/azure/install-azure-cli) command, then try to connect again:
-
- ```bash
- az ad sp create --id 35ffadb3-7fc1-497e-b61b-381d28e744cc
- ```
-
- `35ffadb3-7fc1-497e-b61b-381d28e744cc` is the application ID that Microsoft assigns to Azure App Configuration, and it's the same in every Azure tenant.
- </Info>
+ <AzureOAuthAppConfigurationServicePrincipal />
</Step>
<Step title="Grant Access">
You will then be redirected to Azure to grant Infisical access to your Azure account. Once granted,
diff --git a/docs/integrations/app-connections/azure-devops.mdx b/docs/integrations/app-connections/azure-devops.mdx
index 9e1b8468e0..6c9d4363cb 100644
--- a/docs/integrations/app-connections/azure-devops.mdx
+++ b/docs/integrations/app-connections/azure-devops.mdx
@@ -4,6 +4,8 @@ sidebarTitle: "Azure DevOps"
description: "Learn how to configure an Azure DevOps Connection for Infisical."
---
+import AzureOAuthAppConfigurationServicePrincipal from "/snippets/app-connections/azure/oauth-app-configuration-service-principal.mdx";
+
Infisical currently supports three methods for connecting to Azure DevOps, which are OAuth, Azure DevOps Personal Access Token and Client Secrets.
<Accordion title="Azure OAuth on a Self-Hosted Instance">
@@ -138,15 +140,7 @@ Infisical currently supports three methods for connecting to Azure DevOps, which
You can find the **Organization Name** on https://dev.azure.com/
</Tip>
- <Info>
- If you use Infisical Cloud, the OAuth flow requests every permission on Infisical's shared Azure app registration (the `.default` scope), including the permissions for Azure App Configuration. If your Azure tenant doesn't have the Azure App Configuration service principal, the OAuth flow fails. To create the service principal, run the following [Azure CLI](https://learn.microsoft.com/en-us/cli/azure/install-azure-cli) command, then try to connect again:
-
- ```bash
- az ad sp create --id 35ffadb3-7fc1-497e-b61b-381d28e744cc
- ```
-
- `35ffadb3-7fc1-497e-b61b-381d28e744cc` is the application ID that Microsoft assigns to Azure App Configuration, and it's the same in every Azure tenant.
- </Info>
+ <AzureOAuthAppConfigurationServicePrincipal />
</Step>
<Step title="Grant Access">
You will then be redirected to Azure to grant Infisical access to your Azure account. Once granted,
diff --git a/docs/integrations/app-connections/azure-key-vault.mdx b/docs/integrations/app-connections/azure-key-vault.mdx
index f2f1b5b381..4ddc60eef5 100644
--- a/docs/integrations/app-connections/azure-key-vault.mdx
+++ b/docs/integrations/app-connections/azure-key-vault.mdx
@@ -4,6 +4,8 @@ sidebarTitle: "Azure Key Vault"
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).
<Accordion title="Self-Hosted Instance">
@@ -121,15 +123,7 @@ Infisical supports three methods for connecting to Azure Key Vault: OAuth, Clien
![Connect via Azure OAuth](/images/app-connections/azure/key-vault/create-oauth-method.png)
- <Info>
- If you use Infisical Cloud, the OAuth flow requests every permission on Infisical's shared Azure app registration (the `.default` scope), including the permissions for Azure App Configuration. If your Azure tenant doesn't have the Azure App Configuration service principal, the OAuth flow fails. To create the service principal, run the following [Azure CLI](https://learn.microsoft.com/en-us/cli/azure/install-azure-cli) command, then try to connect again:
-
- ```bash
- az ad sp create --id 35ffadb3-7fc1-497e-b61b-381d28e744cc
- ```
-
- `35ffadb3-7fc1-497e-b61b-381d28e744cc` is the application ID that Microsoft assigns to Azure App Configuration, and it's the same in every Azure tenant.
- </Info>
+ <AzureOAuthAppConfigurationServicePrincipal />
</Step>
<Step title="Grant Access">
You will then be redirected to Azure to grant Infisical access to your Azure account. Once granted,
diff --git a/docs/snippets/app-connections/azure/oauth-app-configuration-service-principal.mdx b/docs/snippets/app-connections/azure/oauth-app-configuration-service-principal.mdx
new file mode 100644
index 0000000000..5f9df73c65
--- /dev/null
+++ b/docs/snippets/app-connections/azure/oauth-app-configuration-service-principal.mdx
@@ -0,0 +1,9 @@
+<Info>
+ If you use Infisical Cloud, the OAuth flow requests every permission on Infisical's shared Azure app registration (the `.default` scope), including the permissions for Azure App Configuration. If your Azure tenant doesn't have the Azure App Configuration service principal, the OAuth flow fails. To create the service principal, run the following [Azure CLI](https://learn.microsoft.com/en-us/cli/azure/install-azure-cli) command, then try to connect again:
+
+ ```bash
+ az ad sp create --id 35ffadb3-7fc1-497e-b61b-381d28e744cc
+ ```
+
+ `35ffadb3-7fc1-497e-b61b-381d28e744cc` is the application ID that Microsoft assigns to Azure App Configuration, and it's the same in every Azure tenant.
+</Info>