Azure Cloud Migration Specialist

• Azure Architecture: Proven experience designing and implementing centralized, secure Azure Landing Zones, including management group hierarchies and resource organization.

• Cloud Governance & Security: Deep knowledge of cloud security frameworks, Azure Policy framework deployment, and Role-Based Access Control (RBAC) configuration.

• Advanced Networking: Solid experience in network topology design, including firewalls, gateways, routing, and private access configuration.

• Observability: Hands-on experience setting up centralized logging and monitoring using Log Analytics and Azure Monitor.

• Migration Execution: Background in executing data synchronization, infrastructure reconfiguration, and traffic/service cutovers using industry-standard migration tools.

• Financial Assessment: Ability to analyze infrastructure utilization and generate detailed, realistic estimates for monthly Azure costs.

• Change Management: Familiarity with formal Change Management processes, including drafting, submitting, and tracking Change Management Requests (CMRs) to a CAB (Change Advisory Board).

• Testing & Support: Experience executing system verification testing (smoke tests, performance checks) and providing dedicated technical support during UAT (User Acceptance Testing) and Hypercare periods.

Key Responsibilities

Phase 1: Application Assessment & Planning

• Current-State Review: Analyze infrastructure utilization, access patterns, known issues, user experiences, connectivity, and application dependencies.

• Architecture & Documentation: Create detailed infrastructure design documents tailored to specific application requirements.

• Cost Management: Generate comprehensive monthly Azure cost estimations.

• Migration Strategy: Build detailed migration plans specifying proposed migration tools, data replication methodologies, timelines, risk management strategies, testing frameworks, and post-migration support plans.

• Plan Governance: Review, update, and secure formal approval for the final migration plan.

Phase 2: Core Azure Landing Zone Implementation

• Architecture & Frameworks: Design and deploy a centralized, secure Azure landing zone architecture. Establish governance, security, and compliance frameworks according to cloud security requirements.

• Networking & Security: Create standardized networking pathways and build/deploy network security topologies, including firewalls, gateways, routing, and private access paths.

• Resource Optimization: Enable scalable resource deployment, establish naming conventions, and implement resource tagging standards.

• Identity & Access Management (IAM): Design and execute the IAM plan, including management group hierarchy, Azure Policy framework deployment, and Role-Based Access Control (RBAC) configuration.

• Infrastructure Deployment: Build and deploy application compute, storage, and network infrastructure topology.

• Observability: Implement centralized logging, monitoring, and alerting capabilities using Log Analytics and Azure Monitor.

Phase 3: Application Migration, Testing & Go-Live

• Change Management: Collaborate with stakeholders to finalize cutover schedules, identifying blackout windows and required downtime. Draft, submit, and track Change Management Requests (CMRs) through the CAB/governance body to secure timely approvals.

• Migration Execution: Execute data synchronization, infrastructure reconfiguration, and traffic/service cutovers strictly within approved change windows while maintaining real-time status updates with all parties.

• Verification Testing: Conduct rigorous post-cutover system testing (smoke tests, core functionality, and performance checks) to validate application health. Document results and resolve critical issues prior to UAT.

• UAT Support: Provide dedicated technical support to end-users and stakeholders during the User Acceptance Testing period, diagnosing and troubleshooting application defects in coordination with development teams.

• Go-Live & Decommissioning: Secure formal Go-Live approval post-UAT, enable Azure application access for all users, and systematically remove access to legacy applications.

• Hypercare: Establish a dedicated post-go-live technical support and incident management window to address production bottlenecks and ensure stability during the initial weeks.