> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cloudgeni.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Azure Pipelines

> Use Azure Pipelines as a thin automation layer over the Cloudgeni API rather than expecting a separate managed pipeline integration.

# Azure Pipelines

Azure Pipelines can trigger Cloudgeni scans with a normal script step.

## Static Analysis Example

```yaml theme={null}
steps:
  - bash: |
      curl --fail --silent --show-error \
        -X POST \
        -H "Content-Type: application/json" \
        -H "X-CLOUDGENI-API-KEY: $(CLOUDGENI_API_KEY)" \
        "$(CLOUDGENI_API_URL)/api/v1/organizations/$(CLOUDGENI_ORG_ID)/workspaces/$(CLOUDGENI_WORKSPACE_ID)/repositories/$(CLOUDGENI_REPO_ID)/static-analysis" \
        -d '{"analysisEngine":"checkov","excludedPaths":[]}'
    displayName: Trigger Cloudgeni static analysis
```

## For Cloud Scans

Use the cloud endpoint shape instead:

`/api/v1/organizations/:orgId/workspaces/:workspaceId/cloud/:integrationId/:analysisEngine/infra-scans`

## Next

See [Scanning API](/api-reference/scanning-api) for the routes these pipeline calls map to.