Azure DevOps Integration

Connect GovernanceAI with Azure DevOps for automated repository scanning and compliance governance.

Setup

Step 1: Create Personal Access Token

• Azure DevOps → User Settings → Personal access tokens
• New Token with scopes:
  • Code: Read - Read repositories
  • Build: Read - Access pipelines
  • Pull Request Threads: Read - Read PR comments
• Copy token

Step 2: Connect in GovernanceAI

• Integrations → Azure DevOps
• Enter organization URL
• Paste PAT token
• Select projects to scan

Step 3: Configure Scanning

• Repositories: Select which to scan
• Trigger: Push, Pull Request, Scheduled
• Frequency: Hourly, Daily, Weekly

Azure Pipelines Integration

1
# azure-pipelines.yml
2
trigger:
3
  - main
4
5
pool:
6
  vmImage: 'ubuntu-latest'
7
8
steps:
9
- script: |
10
    curl -X POST https://api.governanceai.com/v1/scans \
11
      -H "Authorization: Bearer $(GOVERNANCEAI_API_KEY)" \
12
      -d '{
13
        "repository": "$(Build.Repository.Name)",
14
        "ref": "$(Build.SourceVersion)"
15
      }'
16
  displayName: 'GovernanceAI Scan'
17
18
- script: |
19
    # Check for critical findings
20
    curl -H "Authorization: Bearer $(GOVERNANCEAI_API_KEY)" \
21
      https://api.governanceai.com/v1/scans/results/latest \
22
      | jq -e '.critical_count == 0'
23
  displayName: 'Verify Compliance'

Pull Request Checks

Automatically adds checks to PRs:

• AI Model findings
• Dependency analysis
• Compliance status
• Risk assessment

Permissions

• Code: Read - Required for scanning
• Build: Read - For pipeline integration
• Pull Request Threads: Read - For PR comments

Troubleshooting

• Auth failures - Verify PAT token is valid
• Projects not showing - Check permissions
• Webhooks not firing - Check Service Connection
• Pipeline failing - Verify API key in pipeline variables

Next Steps

• GitHub or GitLab - Other Git providers
• Jira Integration - Track issues
• API Reference - Integration APIs