Azure DevOps Pipeline & Cloud
Budget: $15 – $25 USD
I’m looking for hands-on help to establish a robust CI/CD workflow and to streamline the way our Microsoft Azure environment is provisioned and maintained.
Right now all code is hosted in Azure Repos. What I need is a set of Azure DevOps pipelines that automatically build, test, and deploy to separate staging and production resource groups, with approvals and roll-back logic baked in. At the same time, I want the underlying Azure infrastructure—VMs, Web Apps, storage, networking, and supporting services—defined as code so it can be version-controlled and reproduced on demand.
You will:
• Design and implement the full Azure DevOps pipeline, including build, unit/integration test, artifact packaging, and release stages.
• Create or refactor infrastructure-as-code templates (ARM or Terraform—your call) that spin up everything the pipeline targets, following best practices for security, scalability, and cost control.
• Integrate monitoring hooks so future alerts can be wired into our existing dashboard.
• Document the setup clearly so another engineer can run a single command and have the same environment up and running.
Acceptance is simple: a green pipeline that deploys a sample commit all the way to Azure, plus a repo folder containing the IaC templates and a README explaining how to replicate the flow.
If you have deep experience with Azure DevOps and cloud architecture on Microsoft Azure, I’d love to hear how you would tackle this.
Right now all code is hosted in Azure Repos. What I need is a set of Azure DevOps pipelines that automatically build, test, and deploy to separate staging and production resource groups, with approvals and roll-back logic baked in. At the same time, I want the underlying Azure infrastructure—VMs, Web Apps, storage, networking, and supporting services—defined as code so it can be version-controlled and reproduced on demand.
You will:
• Design and implement the full Azure DevOps pipeline, including build, unit/integration test, artifact packaging, and release stages.
• Create or refactor infrastructure-as-code templates (ARM or Terraform—your call) that spin up everything the pipeline targets, following best practices for security, scalability, and cost control.
• Integrate monitoring hooks so future alerts can be wired into our existing dashboard.
• Document the setup clearly so another engineer can run a single command and have the same environment up and running.
Acceptance is simple: a green pipeline that deploys a sample commit all the way to Azure, plus a repo folder containing the IaC templates and a README explaining how to replicate the flow.
If you have deep experience with Azure DevOps and cloud architecture on Microsoft Azure, I’d love to hear how you would tackle this.