Azure DevOps
Git, CI/CD, Boards, pipelines
Overview
We set up Azure DevOps for the data platform: repos, branch policies, YAML pipelines, and boards only where the team will actually move work items. Service connections use workload identity federation or a tightly scoped service principal, not a personal access token.
Pipelines build and deploy infrastructure and application code into separate environments, with approvals on production. Variable groups point at Key Vault, and we document how a developer requests a change.
What we deliver
- Project, repos, and branch policies for the data platform
- YAML pipelines for infrastructure and application deployment
- Service connections without long-lived personal tokens
- Environment approvals and variable groups backed by Key Vault
Business benefits
- Production changes go through a pipeline and an approval
- A branch policy stops a direct push to the main branch
- Secrets for the pipeline come from Key Vault, not from a variable pasted in the UI
Typical use
Git, CI/CD, Boards, pipelines
Related services
Contact
Let's talk about your Azure project
We're a real team, not bots. Send a few details and we'll reply within one working day.
