Azure Architect for DevOps Migration
Budget: $25 – $50 USD
I’m refreshing our entire technology footprint on Microsoft Azure and need a seasoned cloud architect who is equally at home drawing high-level designs and rolling up their sleeves in DevOps tooling.
Scope
• Infrastructure setup is the first priority. I already have high-level diagrams; you will refine them, build the landing zone, and provision resources through code.
• End-to-end DevOps is crucial. I want automated CI/CD pipelines (GitHub Actions or Azure DevOps), IaC with Bicep or Terraform, and policy-as-code baked in from day one.
• Migration comes next. Every workload—web apps, databases, and a handful of legacy services—will move across. I expect clear runbooks and cut-over plans.
What I’ll hand over
– Existing architecture sketches and current on-prem inventories
– Access to an empty Azure subscription
– A shortlist of preferred Azure services
What I need back
– Reusable IaC templates committed to our repo
– Pipelines that build, test, scan, and deploy automatically
– A validated migration strategy with phased schedules and rollback steps
– Knowledge-transfer sessions so my internal team can run the platform confidently
Acceptance criteria
1. All core resources deploy via a single pipeline and pass Azure Policy compliance checks.
2. Application migration executes with zero data loss and under the agreed outage windows.
3. Documentation covers architecture, pipeline steps, and operational runbooks.
If you’ve architected similar Azure transformations and can demonstrate successful web, database, and legacy migrations, let’s talk.
Scope
• Infrastructure setup is the first priority. I already have high-level diagrams; you will refine them, build the landing zone, and provision resources through code.
• End-to-end DevOps is crucial. I want automated CI/CD pipelines (GitHub Actions or Azure DevOps), IaC with Bicep or Terraform, and policy-as-code baked in from day one.
• Migration comes next. Every workload—web apps, databases, and a handful of legacy services—will move across. I expect clear runbooks and cut-over plans.
What I’ll hand over
– Existing architecture sketches and current on-prem inventories
– Access to an empty Azure subscription
– A shortlist of preferred Azure services
What I need back
– Reusable IaC templates committed to our repo
– Pipelines that build, test, scan, and deploy automatically
– A validated migration strategy with phased schedules and rollback steps
– Knowledge-transfer sessions so my internal team can run the platform confidently
Acceptance criteria
1. All core resources deploy via a single pipeline and pass Azure Policy compliance checks.
2. Application migration executes with zero data loss and under the agreed outage windows.
3. Documentation covers architecture, pipeline steps, and operational runbooks.
If you’ve architected similar Azure transformations and can demonstrate successful web, database, and legacy migrations, let’s talk.
Related categories:
Cloud Computing
Azure
Amazon Web Services
Database Administration
Continuous Integration
DevOps
Terraform
CI/CD