Seeking advise on Exadata migration

[VinodNN]

Hello Erman,
Our 12.2.10 EBS is on Azure at present. With two standby databases (HA & DR). SSO is implemented using Azure AD, OAM, OIG and OUD. SSO is enabled for the database with Microsoft Entra ID. There are some custom applications on top of the EBS DB, which are Java based mostly. This is our production environment.
Non prod is 12 instances on 12 VMs. They don't have SSO, HA, DR etc. And they are on-prem.
We are thinking of moving prod as well as non prod to Oracle@Azure on Exadata. Are there any potential risks in this migration? Particularly around customizations?

[ErmanArslansOracleBlog]

Yes. You are migrating to Exadata. A platform change is there. Normally, it gives you performance (through Smart Scan and Cell Offloading,) but still you need to be ensure about the connectivity and RAC Awareness.

Smart Scan vs. Indexing --> this is important.. In Exa, you want to go parallel and enable smart scan during the execution -- generally for instance
The Interconnect Bottleneck
Customization Hardcoding and File Systems

+

You currently have a sophisticated identity stack (OAM/OIG/OUD) and DB-level Entra ID integration.

When the database moves to the Oracle@Azure delegated subnet, the way the database communicates with the Entra ID endpoints must be validated. You will need to ensure that the OCI-side networking (which manages the Exadata resource) has the necessary egress rules to reach Azure’s identity services.

Check the latency in the link between Azure and OCI - and potential (if so) effect to your case , as well.