Day 2/90 — Deploying a React Portfolio to Azure App Service with GitHub Actions CI/CD
As part of my 90-day Cloud Engineering journey, I worked on deploying my React portfolio to Microsoft Azure.
The goal was to get hands-on experience with Azure App Service and understand how CI/CD automation works using GitHub Actions.
☁️ Project Overview
I deployed my existing React portfolio to Microsoft Azure App Service and configured a GitHub Actions workflow to automate the deployment process.
🛠️ Technologies Used
- React.js
- Microsoft Azure App Service
- GitHub Actions
- GitHub
- OpenID Connect (OIDC)
- YAML
⚙️ What I Did
- Created and configured an Azure App Service.
- Connected my GitHub repository to the deployment workflow.
- Configured OIDC authentication between GitHub and Azure.
- Set up the GitHub Actions deployment workflow.
- Executed the workflow and verified the deployment.
- Confirmed that the portfolio was accessible through its Azure URL.
🔐 A Key Learning: OIDC Authentication
One important part of this project was configuring OpenID Connect authentication.
Instead of relying on a long-lived Azure client secret, OIDC allows GitHub Actions to authenticate with Azure using a federated identity.
This helped me understand a more secure approach to connecting CI/CD pipelines with cloud platforms.
🚀 Project Links
- Live Portfolio: https://saad-portfolio-azure.azurewebsites.net/
- GitHub Project: https://github.com/saadshah2033-cyber/react-portfolio-azure-appservice-cicd
📚 What I Learned
- Hosting React applications on Azure App Service.
- Configuring GitHub Actions workflows.
- Understanding CI/CD deployment automation.
- Setting up OIDC authentication.
- Troubleshooting Azure deployment and authentication issues.
What's Next?
This is only Day 2 of my 90-day Cloud Engineering journey.
I'll continue building practical projects, exploring cloud services, and sharing what I learn along the way.







Top comments (0)