Updated the CI/CD pipeline configuration to support deployment to a second Azure region. By adjusting the environment variables in the workflow, the infrastructure and application can now target the Indonesia Central region consistently. This change streamlines our multi-region deployment strategy.

Updated the CI/CD pipeline configuration to use southeastasia as the deployment region. This change ensures compliance with Azure policy restrictions on allowed resource deployment locations. Infrastructure deployments will now target this permitted region.

This change updates the SUBSCRIPTION-ID in .github/workflows/eshoponweb-cicd.yml, so the GitHub Actions pipeline will now authenticate and deploy against a new Azure subscription. There’s no application code change here, but it does materially affect where infrastructure changes and app deployments land. The practical effect is that future pipeline runs will target a different Azure environment.

Updated the CI/CD workflow configuration to target the 'westeurope' Azure region and updated the subscription ID. This change aims to resolve deployment issues by leveraging a different Azure account policy. Testing is underway to verify if this environment stabilizes the deployment process.

The CI/CD pipeline configuration has been updated to standardize the deployment region to southeastasia. This change ensures that both the infrastructure resource group and the web application naming conventions align with the Southeast Asia Azure region, maintaining consistency across our deployment targets.

This change updates the GitHub Actions deployment configuration to point at a new Azure region by renaming the resource group, location, and web app target from westeurope to westus. It looks like an environment migration or infrastructure realignment rather than an application code change, but it directly affects where automated deployments land. The practical effect is that future pipeline runs on this workflow will provision and deploy against the West US Azure footprint.

This change wires the eshoponweb-cicd.yml workflow to use real Azure environment values for the resource group, subscription, and web app instead of placeholder defaults. It also switches the trigger to workflow_dispatch, which makes sense for manually validating the IaC and deployment flow during the lab rather than running on every push. The practical effect is that the pipeline is now ready for controlled test executions against an actual target environment.

This change updates the default vmSize parameter in infra/simple-windows-vm.bicep from Standard_B1s to Standard_B1ms to keep the template aligned with Azure SKU availability. It prevents new deployments from depending on a retiring VM size and avoids unnecessary provisioning failures or follow-up manual edits. In practice, anyone using the default template settings should get a smoother, future-proof VM deployment.

This push consolidates a batch of dependency and CI updates, including Azure SDK packages, Ardalis libraries, and newer GitHub Actions versions. The only substantive code change was in src/Web/Program.cs, where deprecated Azure App Configuration caching APIs were replaced with the current refresh interval calls so the app continues to compile and behave correctly after the upgrade. With all 10 projects validating cleanly, the practical effect is a more secure and up-to-date codebase without breaking the build.

This change turns the GitHub Actions workflow into a more generic template by replacing hard-coded Azure resource names, subscription details, and region-specific values with placeholders. It also leaves the push trigger commented out, which suggests the workflow is still being prepared before being enabled for regular runs. The practical effect is safer reuse of the pipeline without leaking environment-specific configuration, but it is not yet an active automation change.

This change corrects the Azure DevOps release pipeline to reference artifacts under the actual downloaded artifact root, $(Pipeline.Workspace)/eshoponweb-ci, instead of paths that would not exist at deploy time. Both the infrastructure template path and the Linux web app package path were updated in .ado/eshoponweb-cd-webapp-code.yml, which should prevent deployment failures caused by missing files. Practical effect: the CD pipeline should now successfully locate its build outputs and deploy the web app reliably.

This change reconfigures the CI/CD workflow’s deployment variables by switching the resource group, Azure region, and web app name to an East US target. It looks like the pipeline is being aligned with a new or corrected Azure environment, likely to match current infrastructure provisioning. The practical effect is that future workflow runs will deploy the app to the East US app service instead of the old West Europe setup.

This change updates infra/webapp.bicep to provision the App Service Plan with the S1 tier rather than B1. That likely reflects a need for stronger baseline performance and platform capabilities in the deployed web app environment, rather than leaving it on a lower-cost basic tier. The practical effect is that new deployments will come up on a more capable hosting plan with fewer resource constraints.

This change turns the placeholder workflow configuration into something runnable by replacing template Azure values with concrete resource group, subscription, and web app settings. It also switches the workflow trigger to workflow_dispatch, which suggests deployments are being controlled manually while the pipeline is being validated. The practical effect is that the CI/CD workflow is now closer to an actual deployable setup, with safer manual execution during setup or testing.