Azure Tips and Tricks - How to use GitHub Actions from Azure App Service
How to use GitHub Actions from Azure App Service
Automated deployments create better software
When you need to manually build and deploy your app, each time that you make a change, you will make mistakes, which result in bugs and downtime for users. Automating your build and deployment processes makes them less error-prone and allows you to deploy as often as you want. GitHub Actions can help to automate your builds and deployments and integrates with Azure App Service.
In this post, we'll automatically build and deploy code to an Azure App Service using GitHub Actions.
Prerequisites
If you want to follow along, you'll need the following:
- An Azure subscription (If you don't have an Azure subscription, create a free account before you begin)
- An Azure App Service Web App. You can create one using this tutorial.
- A GitHub account with a repository in it that contains code that can run on Azure App Service (like an ASP.NET Core website)
Create a GitHub Action from an Azure App Service
We already have an Azure App Service Web App, and a GitHub repository that contains an ASP.NET Core application. Let's use GitHub Actions to deploy the code from the repository to the Web App.
- Go to the Azure portal.
- Navigate to the Azure App Service Web App
- Select the Deployment Center menu
- In the deployment center, select GitHub as the source control location
- If you haven't used your GitHub account with your Azure account before, you need to click the Authorize button to authorize Azure to access GitHub
- Select Continue to go to the next step
- In the Build providers step, select GitHub Actions
(Select GitHub Actions in the Deployment Center)
- Select Continue
- In the Configure step:
- Select the Repository that you want to use
- Select the code Branch to build and deploy from
- Select the Runtime stack. In our case, this is .NET Core with the latest version
(Configure GitHub access in the Deployment Center)
- Select Continue to proceed
- You'll now see the GitHub Action workflow configuration file that describes the GitHub action. Select Finish to finalize the workflow
We have now successfully created a GitHub Action for the Azure Web App. After a few minutes, the workflow will be finished and the code from the repository should be deployed to the Web App. You should be able to see the deployed code run in the Web App when you click on the Browse button from the Deployment Center.
(Application running in Azure App Service Web App)
And from the Deployment Center, you can click on the GitHub Action link to go to the action in GitHub. Here, you can see all the GitHub Action workflows that are configured and their builds and deployments and drill down into the logs of already executed, or in-progress workflows.
(Details of a GitHub Action workflow)
Conclusion
Automating your build and deployment processes improves the quality of your software. GitHub Actions allow you to easily automate your builds and deployments and integrate with Azure App Service.
Create a trial account today and go and check it out!
Published on:
Learn moreRelated posts
Azure Tops $100 Billion As Microsoft Reports FY26 Q4 Results
On July 29, Microsoft released their FY26 Q4 results. We learned that Microsoft 365 Copilot has 30 million paid seats, but that's still less t...
Azure SDK Release (July 2026)
Azure SDK releases every month. In this post, you'll find this month's highlights and release notes. The post Azure SDK Release (July 2026) ap...
How AMD and Azure push the boundaries of compute
Azure OpenAI Service: Complete Guide for Beginners
Introduction Artificial Intelligence is transforming how businesses build software, automate workflows and deliver personalised customer exper...
Find any commit in seconds: Commit Search comes to Azure DevOps
Great code has a long memory. The fix you shipped last quarter, the refactor that touched a dozen files, the one-line change that explained wh...
Using Azure OpenAI to Auto-Summarize Dataverse Case Notes – AI Integration + Dataverse CE
Why I Built This If you work in Dynamics 365 Customer Service or any Dataverse CE environment, you already know the pain: a single case can ac...