GitHub Actions CI Pipeline: Build and Push Docker Image to Azure Container Registry (ACR)

Learn how to create a GitHub Actions CI Pipeline that builds an ASP.NET Core Web API Docker image and securely pushes it to Azure Container Registry (ACR). In this step-by-step tutorial, we will configure a complete Continuous Integration workflow using GitHub Actions, Docker, Microsoft Azure, OpenID Connect, a user-assigned managed identity, and Azure Container Registry. You will learn how GitHub Actions authenticates with Microsoft Azure without storing a permanent client secret, obtains a temporary ACR access token, signs Docker into the registry, builds the Docker image using Buildx, and pushes the image with both the latest tag and the Git commit SHA. Topics covered in this video: Understanding the end-to-end CI pipeline Preparing an ASP.NET Core Web API for Docker Creating a multi-stage Dockerfile Building and testing the Docker image locally Creating an Azure Container Registry Creating a user-assigned managed identity Configuring RBAC and ABAC permissions Creating a GitHub federated credential Authenticating GitHub Actions with Azure using OIDC Obtaining a temporary Azure Container Registry access token Authenticating Docker with ACR Creating a GitHub Actions workflow Building the Docker image with Docker Buildx Tagging the image with the latest and the Git commit SHA Pushing both image tags to Azure Container Registry Verifying the Docker image and tags in the Azure Portal Matching an ACR image tag with the GitHub commit Understanding RBAC, ABAC, managed identity, and OIDC End-to-end CI flow: Developer pushes code to the GitHub main branch → GitHub Actions starts the workflow → The source code is checked out → GitHub Actions authenticates with Azure using OIDC → The workflow obtains a temporary ACR access token → Docker authenticates with Azure Container Registry → Docker builds the ASP.NET Core Web API image → The image is tagged with latest, and the Git commit SHA → Both tags are pushed to Azure Container Registry → The image becomes available for deployment This workflow performs Continuous Integration only. It builds and publishes the Docker image to Azure Container Registry. Deployment to Azure Kubernetes Service, Azure App Service, or Azure Container Apps can be handled by a separate Continuous Deployment pipeline. Connect with Us for Live Training: 📞 Contact Number/WhatsApp: +91 7021801173 💬 WhatsApp Group: https://chat.whatsapp.com/BtH53Zmuopb... 📧 Email: [email protected] 📢 Telegram Group: https://telegram.me/dotnettutorials 🌍 Website: https://dotnettutorials.net/ Follow & Subscribe for More .NET Tutorials: 📺 Subscribe to our YouTube Channel:    / @dotnettutorials   👥 Join Our Facebook Group:   / 501905403704561   📘 Like & Follow Our Facebook Page:   / tutorialsdotnet   💼 Join Our LinkedIn Group:   / 14539101   🏢 Follow Our LinkedIn Company Page:   / dot-net-tutorials   Please subscribe to the channel and share this video with students, developers, and professionals interested in .NET, Docker, GitHub Actions, Microsoft Azure, and DevOps. #GitHubActions #Docker #AzureContainerRegistry #ACR #CICD #DevOps #AspNetCore #DotNet #MicrosoftAzure #OIDC