Implementing Multi-cloud Strategy with OCI and Azure

All answers to this question.

We implemented the Interconnect in the US-East region and the latency consistently hovers around 1.5ms. It’s essentially like having both clouds in the same data center. The biggest pitfall is the identity management; make sure you set up federated SSO correctly between Azure AD and OCI IAM early on. Also, remember that while there are no egress fees between the two via the Interconnect, you still need to manage your routing tables in both portals to ensure traffic stays on the private link.

   Answered 2024-02-07 by Barbara Clark

Did you run into any issues with CIDR block overlaps when connecting your Azure VNet to the Oracle VCN, or was the IP planning straightforward for your team?

   Answered 2024-02-09 by Richard Lewis

• Richard, IP planning is definitely the most critical step. We had to re-map some of our Azure subnets because we hadn't accounted for the internal OCI service CIDRs. It's best to use a completely unique private IP range for OCI to avoid any routing conflicts. Once we cleared that up, the FastConnect setup through the portal was actually very intuitive and took less than an hour to go live.

     Commented 2024-02-11 by Barbara Clark

The performance is solid, but keep an eye on your support model. You'll need to coordinate between two vendors if a weird networking bug pops up across the link.

   Answered 2024-02-13 by Patricia Moore

• Good point, Patricia. Having a unified monitoring strategy using something like OCI Observability and Management alongside Azure Monitor is vital for visibility across both environments.

     Commented 2024-02-15 by Jennifer Adams