.png?fit=max&auto=format&n=tsMQJyneJ1xquFUo&q=85&s=4d401cc03b547d99b6f75a6bd170c334){kind=spacer}
Documentation Index
Fetch the complete documentation index at: https://help.dsalta.com/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Azure DevOps is Microsoft’s suite of developer tools including Azure Repos, Pipelines, Boards, and Artifacts. DSALTA monitors repository security configuration, code review policies, and access management.Read-only access. DSALTA never modifies, creates, or deletes resources in your Azure DevOps environment. All API access is strictly read-only.
Integration Details
| Property | Value |
|---|---|
| Category | Code Repository |
| Data Library Modules | Access, Code Changes |
| Authentication | Personal Access Token with Code (Read) scope |
| Sync Frequency | Every 24 hours (manual sync available) |
| Permissions | Read-only |
What Data DSALTA Collects
When you connect Azure DevOps, DSALTA automatically collects the following data on every sync cycle:- Repository configurations
- Branch protection rules
- Pull request review requirements
- CI/CD status check enforcement
- User access and permissions
Key Use Cases
- Enforce branch protection on all repositories
- Require peer review before code merges
- Ensure CI status checks pass before merging
- Track offboarded user access revocation
- Classify code repositories by criticality
How to Connect
Navigate to Integrations
Go to Settings → Integrations in your DSALTA dashboard and find Azure DevOps in the catalog.
Authenticate
Follow the on-screen instructions to authenticate with your Azure DevOps account. Admin-level access is required for the initial setup.
Configure Scope
Select which accounts, projects, or resources DSALTA should monitor. You can adjust this later from the integration settings.
Automated Compliance Tests
When you connect Azure DevOps, DSALTA automatically generates the following compliance tests. Each test runs every 24 hours and produces pass/fail evidence for your auditor.| Test | Description |
|---|---|
| Code repositories should be classified | Checks that all Azure DevOps code repositories are classified by criticality. |
| Peer review should be enforced for code changes | Checks that peer review is required before code changes can be merged in Azure DevOps. |
| Merging code changes should require passing status checks | Checks that passing status checks are required before merging in Azure DevOps. |
| Branch protection rules should be enforced for admins | Checks that branch protection rules apply to admin users in Azure DevOps. |
| Code changes should be reviewed by peers before merging | Checks that all code changes are reviewed by at least one peer before merging in Azure DevOps. |
| Azure DevOps access should be removed for offboarded users | Checks that Azure DevOps access is revoked for offboarded users. |
Tests run automatically every 24 hours. Failed tests generate alerts and appear in your compliance dashboard with remediation guidance. All test results are stored as audit evidence with timestamps.
Compliance Frameworks
This integration provides evidence for the following compliance frameworks:SOC 2
Access controls, monitoring, and change management evidence.
ISO 27001
Asset management, access control, and operations security evidence.
GDPR
Access records and data processing evidence.
Troubleshooting
Integration shows Disconnected
Integration shows Disconnected
Re-authenticate by going to Settings → Integrations → Azure DevOps and clicking Reconnect. This usually happens when API tokens expire or permissions change.
Data is not syncing
Data is not syncing
Verify that the connected account still has the required admin permissions. Try a manual sync from the integration settings page. If the issue persists, check your Azure DevOps API rate limits.
Tests are not generating
Tests are not generating
Tests generate after the first successful data sync. If sync completed but tests are missing, ensure the relevant features are configured in Azure DevOps (e.g., GuardDuty must be enabled in AWS for GuardDuty tests to appear).
Some users are missing from the sync
Some users are missing from the sync
DSALTA syncs all users visible to the connected admin account. If users are missing, verify they are within the scope you configured during setup. Suspended or deleted accounts may not appear.