How do I configure continuous deployment for Azure App Service with GitHub?

Question

I’m working on setting up continuous deployment for an Azure App Service web app using GitHub. I’d like to understand the steps for connecting my GitHub repository to Azure App Service so that it automatically deploys when there’s a new commit. Are there specific permissions I need to grant or any pitfalls I should avoid in the setup? Also, would this process differ if I’m using a private repository?

Answer 1

@Shivani Reddy Sureddy Thanks for posting your question in Microsoft Q&A. apologize for any inconvenience caused on this.

You can follow the below documented steps to enable continuous deployment using deployment center with any of the supported source control in App service.

1. Continuous deployment in App service.
2. Deploy to App Service using GitHub Actions.

Are there specific permissions I need to grant or any pitfalls I should avoid in the setup? Also, would this process differ if I’m using a private repository? Deployment Center also lets you easily configure the more secure OpenID Connect authentication with the user-assigned identity option.

If your Azure account has the needed permissions, you can select to create a user-assigned identity. Otherwise, you can select an existing user-assigned managed identity in the Identity dropdown. You can work with your Azure administrator to create a user-assigned managed identity with the Website Contributor role.

The process of configuring deployment center for private GitHub repositories are same as for public as well.

Hope this helps, let me know if you have any further questions on this.

Please accept as "Yes" if the answer is helpful so that it can help others in the community.