Hi Ammar Siddiqui,
Microsoft Edit: This answer was created using Bing Copilot.
Thanks for reaching out to Microsoft Q&A.
The below link has detailed information about the lift & shift strategy from oracle to azure. Additionally, I have summarised them into few points for your reference. Pls check and let me know.
https://learn.microsoft.com/en-us/azure/virtual-machines/workloads/oracle/oracle-migration
Discovery:
Begin with a detailed assessment of your Oracle product portfolio. Identify the current infrastructure supporting Oracle databases and applications. For Oracle applications such PeopleSoft, discover the size of the infrastructure using Azure Migrate based discovery.
Design:
For applications, use Azure Migrate to lift and shift infrastructure and applications to Azure IaaS based on the discovery. For Oracle first-party applications, consider architecture requirements before deciding on migration. For databases, use the Azure Oracle Migration Assistance Tool (OMAT) with AWR reports as input. OMAT recommends the correct VM size and storage options for your Oracle Database on Azure IaaS. Ensure high reliability and resilience based on Recovery Point Objective (RPO) and Recovery Time Objective (RTO) parameters.
Consider the Oracle landing zone’s architecture guidance for RAC infrastructure separation into high availability (HA) and disaster recovery (DR) using Oracle Data Guard1.
Deployment:
The OMAT tool analyzes the AWR report to provide information on required infrastructure, VM size, and storage recommendations. Based on this information, select suitable HA and DR (RPO/RTO) requirements to create a resilient architecture for Business Continuity and Disaster Recovery (BCDR) using the Oracle on Azure landing zone. Optionally, use Ansible to describe the infrastructure and architecture as infrastructure as code (IaC) and launch the landing zone with either Terraform or Bicep.
Please 'Upvote'(Thumbs-up) and 'Accept' as an answer if the reply was helpful. This will benefit other community members who face the same issue.