diff --git a/docs/images/integrations/bitbucket/integrations-bitbucket-env.png b/docs/images/integrations/bitbucket/integrations-bitbucket-env.png
new file mode 100644
index 000000000..8c683a100
Binary files /dev/null and b/docs/images/integrations/bitbucket/integrations-bitbucket-env.png differ
diff --git a/docs/integrations/cicd/bitbucket.mdx b/docs/integrations/cicd/bitbucket.mdx
index 8f29e43a5..757f0ac98 100644
--- a/docs/integrations/cicd/bitbucket.mdx
+++ b/docs/integrations/cicd/bitbucket.mdx
@@ -7,26 +7,74 @@ Prerequisites:
- Set up and add envars to [Infisical Cloud](https://app.infisical.com)
-
-
- Navigate to your project's integrations tab in Infisical.
+
+
+
+
+ Navigate to your project's integrations tab in Infisical.
- 
+ 
- Press on the Bitbucket tile and grant Infisical access to your Bitbucket account.
+ Press on the Bitbucket tile and grant Infisical access to your Bitbucket account.
- 
+ 
-
- 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.
-
-
-
- Select which Infisical environment secrets you want to sync to which Bitbucket repo and press start integration to start syncing secrets to the repo.
+
+ 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.
+
+
+
+ Select which Infisical environment secrets you want to sync to which Bitbucket repo and press start integration to start syncing secrets to the repo.
- 
-
-
\ No newline at end of file
+ 
+
+
+
+
+
+
+
+ Configure a [Machine Identity](https://infisical.com/docs/documentation/platform/identities/universal-auth) for your project and give it permissions to read secrets from your desired Infisical projects and environments.
+
+ 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.
+
+
+
+ Create Bitbucket variables (can be either workspace, repository, or deployment-level) to store Machine Identity Client ID and Client Secret.
+
+ 
+
+
+ Edit your Bitbucket pipeline YAML file to include the use of the Infisical CLI to fetch and inject secrets into any script or command within the pipeline.
+
+ #### Example
+
+ ```yaml
+ image: atlassian/default-image:3
+
+ pipelines:
+ default:
+ - step:
+ name: Build application with secrets from Infisical
+ 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
+ - export INFISICAL_TOKEN=$(infisical login --method=universal-auth --client-id=$INFISICAL_CLIENT_ID --client-secret=$INFISICAL_CLIENT_SECRET --silent --plain)
+ - infisical run --projectId=1d0443c1-cd43-4b3a-91a3-9d5f81254a89 --env=dev -- npm run build
+ ```
+
+
+ Set the values of `projectId` and `env` flags in the `infisical run` command to your intended source path. For more options, refer to the CLI command reference [here](https://infisical.com/docs/cli/commands/run).
+
+
+
+
+
+