Add GitLab and Azure Key Vault docs

docs/integrations/cicd/gitlab.mdx

@@ -1,34 +1,70 @@
 ---
-title: "Gitlab Pipeline"
+title: "GitLab"
+description: "How to automatically sync secrets from Infisical into GitLab."
 ---
 
-To integrate Infisical secrets into your Gitlab CI/CD setup, three steps are required.
+Prerequisites:
 
-## Generate service token 
-To expose Infisical secrets in Gitlab CI/CD, you must generate a service token for the specific project and environment in Infisical. For instructions on how to generate a service token, refer to [this page](../../getting-started/dashboard/token)
+- Set up and add envars to [Infisical Cloud](https://app.infisical.com)
 
-## Set Infisical service token in Gitlab 
-To provide Infisical CLI with the service token generated in the previous step, go to **Settings > CI/CD > Variables** in Gitlab and create a new **INFISICAL_TOKEN** variable. Enter the generated service token as its value.
+<Tabs>
+  <Tab title="Standard">
+  ## Navigate to your project's integrations tab
 
-## Configure Infisical in your pipeline 
-Edit your .gitlab-ci.yml to include the installation of the Infisical CLI. This will allow you to use the CLI for fetching and injecting secrets into any script or command within your Gitlab CI/CD process.
+![integrations](../../images/integrations.png)
+
+## Authorize Infisical for GitLab
+
+Press on the GitLab tile and grant Infisical access to your GitLab account.
+
+![integrations gitlab authorization](../../images/integrations-gitlab-auth.png)
+
+<Info>
+  If this is your project's first cloud integration, then you'll have to grant
+  Infisical access to your project's environment variables. Although this step
+  breaks E2EE, it's necessary for Infisical to sync the environment variables to
+  the cloud platform.
+</Info>
+## Start integration
+
+Select which Infisical environment secrets you want to sync to which GitLab repository and press create integration to start syncing secrets to GitLab.
+
+![integrations gitlab](../../images/integrations-gitlab-create.png)
+![integrations gitlab](../../images/integrations-gitlab.png)
+
+  </Tab>
+  <Tab title="Pipeline">
+
+## Generate service token
+
+Generate an [Infisical Token](../../getting-started/dashboard/token) for the specific project and environment in Infisical.
+
+## Set the Infisical Token in Gitlab
+
+Create a new variable called `INFISICAL_TOKEN` with the value set to the token from the previous step in Settings > CI/CD > Variables of your GitLab repository.
+
+## Configure Infisical in your pipeline
+
+Edit your `.gitlab-ci.yml` to include the Infisical CLI installation. This will allow you to use the CLI for fetching and injecting secrets into any script or command within your Gitlab CI/CD process.
 
 #### Example
-```yaml 
+
+```yaml
 image: ubuntu
 
-stages:       
+stages:
   - build
   - test
   - deploy
 
-build-job:     
+build-job:
   stage: build
   script:
     - apt update && apt install -y curl
     - curl -1sLf 'https://dl.cloudsmith.io/public/infisical/infisical-cli/setup.deb.sh' | bash
     - apt-get update && apt-get install -y infisical
     - infisical run -- npm run build
+```
 
-...
-```
+  </Tab>
+</Tabs>

docs/integrations/cloud/azure-key-vault.mdx

@@ -0,0 +1,36 @@
+---
+title: "Azure Key Vault"
+description: "How to automatically sync secrets from Infisical into your Azure Key Vault."
+---
+
+Prerequisites:
+
+- Set up and add envars to [Infisical Cloud](https://app.infisical.com)
+- Set up Azure and have an existing key vault
+
+## Navigate to your project's integrations tab
+
+![integrations](../../images/integrations.png)
+
+## Authorize Infisical for Azure Key Vault
+
+Press on the Azure Key Vault tile and grant Infisical access to Azure Key Vault.
+
+## Start Integration
+
+Obtain the Vault URI of your key vault in the Overview tab.
+
+![integrations](../../images/integrations-azure-key-vault-vault-uri.png)
+
+Select which Infisical environment secrets you want to sync to your key vault. Then, input your Vault URI from the previous step. Finally, press create integration to start syncing secrets to Azure Key Vault.
+
+![integrations](../../images/integrations-azure-key-vault-create.png)
+
+![integrations](../../images/integrations-azure-key-vault.png)
+
+<Info>
+  If this is your project's first cloud integration, then you'll have to grant
+  Infisical access to your project's environment variables. Although this step
+  breaks E2EE, it's necessary for Infisical to sync the environment variables to
+  the cloud platform.
+</Info>

docs/integrations/overview.mdx

@@ -20,8 +20,9 @@ Missing an integration? Throw in a [request](https://github.com/Infisical/infisi
 | [Fly.io](/integrations/cloud/flyio)                            | Cloud     | Available   |
 | [AWS Parameter Store](/integrations/cloud/aws-parameter-store) | Cloud     | Available   |
 | [AWS Secret Manager](/integrations/cloud/aws-secret-manager)   | Cloud     | Available   |
+| [Azure Key Vault](/integrations/cloud/azure-key-vault)         | Cloud     | Available   |
 | [GitHub Actions](/integrations/cicd/githubactions)             | CI/CD     | Available   |
-| [GitLab Pipeline](/integrations/cicd/gitlab)                   | CI/CD     | Available   |
+| [GitLab](/integrations/cicd/gitlab)                            | CI/CD     | Available   |
 | [CircleCI](/integrations/cicd/circleci)                        | CI/CD     | Available   |
 | [Travis CI](/integrations/cicd/travisci)                       | CI/CD     | Available   |
 | [React](/integrations/frameworks/react)                        | Framework | Available   |

docs/mint.json

@@ -225,7 +225,8 @@
         "integrations/cloud/render",
         "integrations/cloud/flyio",
         "integrations/cloud/aws-parameter-store",
-        "integrations/cloud/aws-secret-manager"
+        "integrations/cloud/aws-secret-manager",
+        "integrations/cloud/azure-key-vault"
       ]
     },
     {