Tips for Orchestrating Cloud Migrations

𝐀𝐟𝐭𝐞𝐫 𝐦𝐢𝐠𝐫𝐚𝐭𝐢𝐧𝐠 𝟓𝟎+ 𝐞𝐧𝐭𝐞𝐫𝐩𝐫𝐢𝐬𝐞 𝐰𝐨𝐫𝐤𝐥𝐨𝐚𝐝𝐬 𝐭𝐨 𝐀𝐳𝐮𝐫𝐞,  Here's the Decision Framework that saved teams Millions in Cloud Spend. Most engineers jump straight to Kubernetes because it's popular.  But I've seen organizations burn 60% of their budget running AKS for workloads that needed App Service. 𝐇𝐞𝐫𝐞'𝐬 𝐦𝐲 𝐁𝐚𝐭𝐭𝐥𝐞-𝐓𝐞𝐬𝐭𝐞𝐝 𝐀𝐩𝐩𝐫𝐨𝐚𝐜𝐡: 🎯 𝐒𝐭𝐚𝐫𝐭 𝐰𝐢𝐭𝐡 𝐭𝐡𝐞𝐬𝐞 𝐪𝐮𝐞𝐬𝐭𝐢𝐨𝐧𝐬: • Already running on-prem? Consider lift-and-shift first, optimize later • Need OS-level control? VMs are still valid (don't let anyone shame you) • Containerized? Great but that doesn't automatically mean Kubernetes • Event-driven with short bursts? Functions will cut your costs dramatically 💡 𝐌𝐲 𝐫𝐞𝐜𝐨𝐦𝐦𝐞𝐧𝐝𝐚𝐭𝐢𝐨𝐧𝐬 𝐟𝐫𝐨𝐦 𝐭𝐡𝐞 𝐭𝐫𝐞𝐧𝐜𝐡𝐞𝐬: For new builds: • Default to managed services (App Service, Container Apps) unless you have a compelling reason not to • Functions for APIs under 5 min execution I've seen 80% cost reduction • AKS only when you need multi-cloud portability or complex orchestration For migrations: • Lift-and-shift to VMs first, then containerize incrementally • Azure Batch for HPC underrated and incredibly cost-effective • Service Fabric if you're deep in .NET (but evaluate carefully it's legacy) For containers: • Container Apps for 80% of microservices workloads • AKS when you need Kubernetes API access or custom controllers • Container Instances for CI/CD agents and batch jobs ⚠️ Red flags I've seen: • Running stateful databases on Functions • Using VMs when you just need to run a web app • Choosing AKS without dedicated platform team The truth?  There's no "best" service only the right fit for your workload, team skills, and operational maturity. What's your compute selection horror story?  Let's learn from each other. 👇 ♻️ Repost if you found it valuable ➕ Follow Jaswindder for more insights on Cloud Strategy, DevOps, and AI-led Engineering. #DevOps #Azure #CloudArchitecture

NEW MIGRATION GUIDANCE - Cloud migrations can be complex, but they don’t have to be uncertain, whether you're moving from on-premises environments or other clouds. To help bring more clarity, we published new Cloud Migration guidance in Microsoft’s Cloud Adoption Framework. This guidance offers a structured roadmap for migrating workloads to Azure from both on-premises and other cloud platforms. It’s the result of close collaboration with Microsoft experts and Microsoft MVPs. It reflects lessons learned from thousands of real-world migrations. The goal is to support teams at any stage of their cloud journey with clear, actionable steps.   Migration Process Overview: 1️⃣ Plan Your Migration 1. Assess readiness and team skills 2. Choose data migration paths 3. Define migration sequencing and rollback plans 4. Engage stakeholders 2️⃣ Prepare Workloads for the Cloud 1. Fix compatibility issues 2. Validate workloads' functionality 3. Build reusable infrastructure 4. Document deployment steps 3️⃣ Execute Migration to the Cloud 1. Prepare stakeholders and freeze changes 2. Finalize production environment 3. Execute cutover and validate success 4. Provide stabilization support 4️⃣Optimize Workloads After Migration 1. Fine-tune configurations in the cloud 2. Collect and act on user feedback 3. Review workloads regularly 4. Optimize hybrid and multicloud dependencies 5️⃣Decommission Source Workloads 1. Confirm decommissioning with stakeholders 2. Reclaim or reassign licenses 3. Preserve data for compliance 4. Update documentation and architecture records 🔗 Explore the new migration guidance here: https://lnkd.in/e2VgCU8m If you're navigating a cloud migration or supporting those who are, I hope this provides the guidance you need. 📣 Acknowledgments: This work reflects the contributions of many across the Microsoft community:   Microsoft MVPs: Stéphane Eyskens, Michael Stephenson, Danny McDermott, Stanislav Zhelyazkov, Joe Carlyle, Scott Corio, Simon Wåhlin, Bert Wolters, Elton Bordim, Haiko Hertes, Robert Hogg, Vladimir Stefanović, Andrew Wilson   Microsoft colleagues: Daniel Söderholm, Ivan Bondy, Rob Rinear, Brody Schulke, Philip Sills, Sandra Patricia Sánchez Martínez, Jack Tracey, Sunil Seth, Timo Salomäki, Michael Lemire, Tomas Kovarik, Larz Stridh, Konstantinos Pantos, Ryan Pfalz, Oscar Zamora, Courtney Taylor, PMP, Kevin Bell, John Lunn, Mannan Mohammed, Mark Piggott, Phani Kumar Teluguti, Yudhbir Singh, Alvaro Guadamillas Herranz CAF Engineering Lead: Jason Bouska Luke Nyswonger, Martin Ekuan, Hans Yang

I constantly hear shocking stories of cloud migration mistakes that spiral into unexpected, skyrocketing costs beyond what anyone ever imagined. Most companies underestimate the complexity. Skip dependency mapping. Pay the price. Cloud migrations go beyond moving workloads - they require knowing what to move, when, and how it affects the rest of your environment. Without a solid plan, you risk unplanned downtime, security gaps, and overspending on misconfigured cloud resources. Here’s how to migrate without chaos: 1. Start with full visibility. Map every application, service, and dependency before migration. Unknown connections lead to downtime, security risks, and hidden costs. Many organizations don’t realize how interconnected their systems are until something breaks. 2. Assess workloads before moving them. Not everything belongs in the cloud. Classify applications by criticality, complexity, and cloud readiness. Legacy systems often need refactoring or special configurations, while certain workloads may be better off staying on-premises. 3. Move in phases, not all at once. A "lift and shift" migration can break critical systems. Migrate in controlled stages, test thoroughly, and adjust before moving forward. Pilot test with non-critical workloads first, gather insights, then move mission-critical systems. 4. Optimize before the migration. Unused resources drain your budget. Right-size workloads, eliminate redundant services, and continuously monitor costs. Cloud sprawl - where forgotten instances keep running - can waste thousands per month. 5. Avoid compliance blind spots. Migrating nodes without visibility can lead to regulatory violations and security gaps. Ensure sensitive workloads follow security best practices before, during, and after migration. The hard truth? You can’t migrate what you don’t know about. Map -> Plan -> Migrate. NO SHORTCUTS.

Cloud Migration Strategy: The 7Rs Framework with Real-World Examples Cloud migration is not a technical activity alone. It is a business-driven architectural decision that impacts cost, security, scalability, and long-term agility. The 7Rs of Cloud Migration provide a structured framework to evaluate how each application should move to the cloud. In mature environments, it is common to apply multiple Rs across different workloads, rather than a single approach. 1. Rehost (Lift and Shift) What it means: Move applications to the cloud without changing the architecture. Example: A legacy Java application running on on-prem VMs is moved to Amazon EC2 or Azure VM with the same OS and configuration. When to use: • Data center exit • Tight migration timelines • Minimal refactoring budget Consideration: Quick wins, but does not fully leverage cloud-native cost or performance benefits. 2. Replatform (Lift, Tinker, and Shift) What it means: Make limited optimizations while keeping core architecture intact. Example: Migrating an on-prem MySQL database to Amazon RDS while keeping the application on EC2. When to use: • Reduce operational overhead • Improve reliability with managed services Consideration: Balanced approach between speed and optimization. 3. Repurchase (Drop and Shop) What it means: Replace the existing application with a SaaS product. Example: Replacing an on-prem CRM system with Salesforce or Microsoft Dynamics 365. When to use: • Standard business functions • Faster time-to-value Consideration: Less customization, but significantly lower maintenance effort. 4. Refactor (Re-architect) What it means: Redesign the application to be cloud-native. Example: Breaking a monolithic application into microservices using Kubernetes, API Gateway, and managed databases. When to use: • High scalability requirements • Long-term business growth Consideration: Highest effort, but maximum cloud value and resilience. 5. Relocate What it means: Move workloads between cloud platforms or managed environments without changing design. Example: Migrating VMware workloads directly into AWS or Azure using native migration tools. When to use: • Platform modernization • Vendor strategy changes 6. Retire (Decommission) What it means: Shut down applications that no longer deliver business value. Example: Decommissioning unused reporting tools or duplicate internal portals. When to use: • Cost optimization • Security risk reduction 7. Retain (Revisit Later) What it means: Keep workloads on-premises for now. Example: Latency-sensitive manufacturing systems or compliance-restricted financial platforms. When to use: • Regulatory or technical constraints Key Insight: A successful cloud migration strategy is not about choosing one R. It is about aligning each application with the right migration path based on business priority, risk tolerance, and future scalability. This framework is foundational for cloud architects,DevOps engineers

🚨 𝗡𝗘𝗪 𝗔𝗥𝗧𝗜𝗖𝗟𝗘 𝗔𝗟𝗘𝗥𝗧: 𝗛𝗼𝘄 𝗪𝗲 𝗠𝗮𝗻𝗮𝗴𝗲𝗱 𝟰𝟬+ 𝗜𝗻𝗳𝗿𝗮𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲 𝗥𝗶𝘀𝗸𝘀 𝗗𝘂𝗿𝗶𝗻𝗴 𝗮 𝗖𝗹𝗼𝘂𝗱 𝗠𝗶𝗴𝗿𝗮𝘁𝗶𝗼𝗻 (And why planning for failure saved the entire project.) Have you ever led a project where a single outage could bring everything to a halt? Where shipping, invoicing, and customer portals were all riding on fragile legacy systems? This edition of 𝗧𝗵𝗲 𝗣𝗠 𝗣𝗹𝗮𝘆𝗯𝗼𝗼𝗸 breaks down how we migrated core systems to the cloud without causing chaos. With 600 employees and a live production environment, we didn’t have the luxury of “figuring it out later.” 𝗛𝗲𝗿𝗲’𝘀 𝘄𝗵𝗮𝘁 𝘄𝗲 𝘄𝗲𝗿𝗲 𝘂𝗽 𝗮𝗴𝗮𝗶𝗻𝘀𝘁: ➝ A 90-day timeline with zero margin for error ➝ Legacy systems with undocumented dependencies ➝ Vendors, data risks, and real-time operations under pressure 𝗛𝗲𝗿𝗲’𝘀 𝗵𝗼𝘄 𝘄𝗲 𝗺𝗮𝗻𝗮𝗴𝗲𝗱 𝘁𝗵𝗲 𝗿𝗶𝘀𝗸: ✅ Created a living risk register with 40+ tracked scenarios ✅ Simulated outages with a Red Team before go-live ✅ Designed rollback paths for every migration step 𝗪𝗵𝗮𝘁 𝘆𝗼𝘂’𝗹𝗹 𝗹𝗲𝗮𝗿𝗻: → How to make risk planning the core of your migration strategy → Why real-time simulations beat assumptions every time → How to coordinate vendors around failure planning → How to deliver under pressure without losing control 𝗪𝗲’𝗿𝗲 𝗮𝗹𝘀𝗼 𝗶𝗻𝗰𝗹𝘂𝗱𝗶𝗻𝗴: 🧠 The risk categories you need to track during cloud migrations 📊 How we resolved live issues in under 2 hours 🚀 Lessons you can apply to any system transition under pressure If you’ve ever lost sleep over infrastructure risks, this one’s for you. 👉 READ THE FULL ARTICLE NOW and drop a comment: What’s the smartest move you’ve made to manage infrastructure risk? 2 Disgruntled PMs Podcast

On prem to Cloud migration Step-by-Step AWS Cloud Migration Process 1. Plan the Migration Assessment: Identify the current environment (servers, databases, dependencies, and configurations). Inventory: Document application components and dependencies. Sizing: Determine AWS resources (EC2 instance types, RDS configurations, etc.) based on current usage. Network Design: Plan VPC setup, subnets, security groups, and connectivity. Backup Plan: Create a fallback plan for any issues during migration. 2. Prepare the AWS Environment VPC Setup: Create a VPC with subnets across multiple Availability Zones (AZs). Security: Configure security groups, IAM roles, and policies. Database Configuration: Set up an Amazon RDS instance or EC2-based database for the migration. AD Server: Use AWS Managed Microsoft AD or deploy your AD on EC2. Application Server: Launch EC2 instances and configure the operating system and required dependencies. 3. Migrate Database Backup: Create a backup of the current database. Export/Import: Use database migration tools (e.g., AWS DMS or native database tools) to migrate data to the AWS database. Replication: Set up database replication for real-time sync with the on-prem database. Validation: Verify data consistency and integrity post-migration. 4. Migrate Application Server Packaging: Package the application (e.g., as Docker containers, AMIs, or simple binaries). Deployment: Deploy the application on AWS EC2 instances or use AWS Elastic Beanstalk. DNS Configuration: Update DNS records to point to the AWS environment. 5. Migrate Active Directory (AD) Replication: Create a replica of the on-prem AD in AWS using the AD Trust setup. DNS Sync: Sync DNS entries between on-prem and AWS environments. Validation: Test authentication and resource access. 6. Test and Validate End-to-End Testing: Validate the complete environment (application, database, and AD). Performance Check: Monitor performance using CloudWatch and address any issues. Failover Testing: Simulate failure scenarios to ensure HA/DR readiness. 7. Cutover and Go Live Schedule Downtime: Coordinate with stakeholders and users for a minimal downtime window. Final Sync: Perform a final sync of the database and switch traffic to AWS. DNS Propagation: Update DNS settings to route traffic to the AWS environment (may take up to 24 hours). Monitoring: Continuously monitor AWS resources and performance post-migration. 8. Post-Migration Optimization Scaling: Implement auto-scaling policies for the application. Security: Regularly review and improve security configurations. Cost Optimization: Use AWS Cost Explorer to analyze and optimize resource usage. Downtime Considerations Database Migration: Plan a maintenance window of 2–4 hours for the final database sync and cutover. DNS Propagation: Approx. 15 minutes to 24 hours, depending on TTL settings. Use short TTLs during migration to minimize delays. #AWSMigration #CloudMigration #MinimalDowntime #DatabaseToAWS #ApplicationToAWS #ADToAWS

𝗔𝗿𝗲 𝘆𝗼𝘂 𝘁𝗵𝗶𝗻𝗸𝗶𝗻𝗴 𝗼𝗳 𝗺𝗶𝗴𝗿𝗮𝘁𝗶𝗻𝗴 𝘆𝗼𝘂𝗿 𝗮𝗽𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻 𝘁𝗼 𝘁𝗵𝗲 𝗰𝗹𝗼𝘂𝗱? 𝗠𝗼𝘀𝘁 𝘁𝗲𝗮𝗺𝘀 𝘀𝘁𝗮𝗿𝘁 𝗯𝘆 𝗹𝗶𝗳𝘁𝗶𝗻𝗴 𝗮𝗻𝗱 𝘀𝗵𝗶𝗳𝘁𝗶𝗻𝗴, 𝗯𝘂𝘁 𝘀𝗺𝗮𝗿𝘁 𝘁𝗲𝗮𝗺𝘀 𝗿𝗲𝘁𝗵𝗶𝗻𝗸 𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲. You do not modernize by just moving monoliths. You modernize by rebuilding for flexibility, scalability, and performance. Just like Telia did. Telia, a major European telecom provider, reimagined its Customer Information Management (CIM) system by migrating from a monolithic application to a microservices architecture on AWS, with the help of Tech Mahindra. Here is how they approached it: 1. Telia’s CIM platform, once plagued by performance issues and deployment delays, was re-architected using AWS Fargate and ECS from Monolith to Microservices. Each component became an independent microservice, scalable, deployable, and resilient. 2. Database Modernization: They replaced costly on-prem Oracle with Amazon Aurora PostgreSQL. Using AWS DMS, they migrated over 70 million records in 90 minutes. All with minimal downtime. 3. CI/CD That Works Manual deployments? Gone. Jenkins, Maven, and JFrog Artifactory now automate everything from builds to Dockerized deployments on Fargate. 4. Cloud-Native Architecture: Each microservice is containerized. Routing is via Route 53. Load balancing is via ALB. Security is via VPCs, IAM, and private subnets. Logging and monitoring? That’s CloudWatch. 5. Security and Compliance Site-to-site VPN, network ACLs, security groups, and CloudTrail. A compliance-first approach is embedded at every layer. The result? * Improved performance. * Zero-downtime deployments. * Cost savings by eliminating third-party dependencies. * Resilience and elasticity using native AWS scaling mechanisms. Cloud is not just about hosting. It is about re-architecting for the future. What’s your migration strategy? Are you still running monoliths? Let us share insights. For more case studies like this, follow Sunil Sharma. If you want to dive deeper into this transformation, check out the full blog here: https://lnkd.in/guEeUSzA Credits: AWS, Tech Mahindra #cloudmigration #awscloud #microservices #serverless #awspartner #applicationmodernization #monolithtomicroservices #cloudarchitecture #scalablesystems #techtransformation #topvoiceintech #buildwithaws