awatertrevi/infisical
1
0
Fork 0
mirror of https://github.com/awatertrevi/infisical.git synced 2026-10-07 12:27:28 +00:00
Code Issues Packages Projects Releases Wiki Activity

Minor fix on docs titles

Browse Source
This commit is contained in:
Carlos Monastyrski
2025-07-30 15:35:47 -03:00
parent 5fcae35fae
commit b20ff0f029
4 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/integrations/app-connections/azure-app-configuration.mdx
+1 -1
View File
@@ -3,7 +3,7 @@ title: "Azure App Configuration Connection"
description: "Learn how to configure a Azure App Configuration Connection for Infisical." description: "Learn how to configure a Azure App Configuration Connection for Infisical."
--- ---
Infisical currently only supports one method for connecting to Azure, which is OAuth. Infisical currently only supports two methods for connecting to Azure, which are OAuth and Client Secrets.
<Accordion title="Self-Hosted Instance"> <Accordion title="Self-Hosted Instance">
Using the Azure App Configuration connection on a self-hosted instance of Infisical requires configuring an application in Azure Using the Azure App Configuration connection on a self-hosted instance of Infisical requires configuring an application in Azure
docs/integrations/app-connections/azure-client-secrets.mdx
+1 -1
View File
@@ -3,7 +3,7 @@ title: "Azure Client Secrets Connection"
description: "Learn how to configure an Azure Client Secrets Connection for Infisical." description: "Learn how to configure an Azure Client Secrets Connection for Infisical."
--- ---
Infisical currently only supports one method for connecting to Azure, which is OAuth. Infisical currently only supports two methods for connecting to Azure, which are OAuth and Client Secrets.
<Accordion title="Self-Hosted Instance"> <Accordion title="Self-Hosted Instance">
Using the Azure Client Secrets connection on a self-hosted instance of Infisical requires configuring an application in Azure Using the Azure Client Secrets connection on a self-hosted instance of Infisical requires configuring an application in Azure
docs/integrations/app-connections/azure-devops.mdx
+1 -1
View File
@@ -3,7 +3,7 @@ title: "Azure DevOps Connection"
description: "Learn how to configure an Azure DevOps Connection for Infisical." description: "Learn how to configure an Azure DevOps Connection for Infisical."
--- ---
Infisical currently supports two methods for connecting to Azure DevOps, which are OAuth and Azure DevOps Personal Access Token. 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"> <Accordion title="Azure OAuth on a Self-Hosted Instance">
Using the Azure DevOps <b>OAuth connection</b> on a self-hosted instance of Infisical requires configuring an application in Azure Using the Azure DevOps <b>OAuth connection</b> on a self-hosted instance of Infisical requires configuring an application in Azure
docs/integrations/app-connections/azure-key-vault.mdx
+1 -1
View File
@@ -3,7 +3,7 @@ title: "Azure Key Vault Connection"
description: "Learn how to configure a Azure Key Vault Connection for Infisical." description: "Learn how to configure a Azure Key Vault Connection for Infisical."
--- ---
Infisical currently only supports one method for connecting to Azure, which is OAuth. Infisical currently only supports two methods for connecting to Azure, which are OAuth and Client Secrets.
<Accordion title="Self-Hosted Instance"> <Accordion title="Self-Hosted Instance">
Using the Azure Key Vault connection on a self-hosted instance of Infisical requires configuring an application in Azure Using the Azure Key Vault connection on a self-hosted instance of Infisical requires configuring an application in Azure