← All insightsCI/CD

Integrating Microsoft Azure into your CI/CD pipeline

Nir Geier, CodeWizard · 24 December 2025 · 3 min read · Intermediate

Getting Microsoft Azure into your pipeline is where it starts paying off - automated, repeatable and reviewed. Here is a working integration and the habits that keep it reliable.

A working pipeline snippet

OIDC login from GitHub Actions to Azure.

yaml
- uses: azure/login@v2
  with:
    client-id: ${{ secrets.AZURE_CLIENT_ID }}
    tenant-id: ${{ secrets.AZURE_TENANT_ID }}
    subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }}

Do this

  • Use OIDC federated credentials for CI
  • Apply least-privilege RBAC and Azure Policy
  • Prefer Bicep/Terraform over portal click-ops

Avoid this

  • Client-secret credentials instead of OIDC federation
  • Owner role assignments sprayed across subscriptions
  • Public storage/network without Private Endpoints

Want senior help putting Microsoft Azure to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.

Like where this is going?

Get hands-on help from the engineers who write these posts.

Book a free consult