Microsoft ends Oracle cloud AI partnership, pushing developers to migrate workloads to Azure

What happened

Microsoft has abruptly ended its cloud-AI partnership with Oracle, and the integration points that let teams run hybrid AI workloads across Azure and Oracle Cloud Infrastructure (OCI) are being switched off. According to developer guides published on dev.to, in three near-identical versions in English, Spanish and Portuguese, the fallout spread fast: the story reportedly trended on Google Trends within hours and ignited debate on Stack Overflow, Reddit's r/MachineLearning and Azure–Oracle user groups. The Portuguese version of the guide says that within roughly 48 hours the hybrid Azure–OCI AI integration had vanished from marketplace listings. Notably, the guides cite no statements from either company; the detail below is the guides' own analysis.

Per those guides, what was cancelled includes Oracle's AI platform and OCI Data Science listings in the Azure Marketplace, automatic provisioning of OCI resources from the Azure portal, and cross-cloud billing and traffic routing between the two platforms. Anyone still using OCI for training or inference now has to move artifacts, reconfigure pipelines and revisit their cost model.

What is affected on the Oracle side

The Spanish-language guide enumerates the Oracle services tied to the partnership: OCI Data Science (notebooks, experiment tracking, distributed training), OCI Generative AI Studio, Oracle Digital Assistant and OCI Foundation Models. These depended on Azure AD single sign-on and joint billing, and in some cases on Azure services such as Container Registry, Azure Bot Service and Azure OpenAI. The guides also warn that hybrid Azure DevOps pipelines calling OCI APIs will hit authentication failures and need rework against the Azure Machine Learning SDK or Azure OpenAI APIs.

For teams that only consume pre-trained models, the same guide claims a switch to Azure OpenAI can be completed in minutes by importing weights into Azure Machine Learning.

The cost picture, with caveats

All three guides attempt cost comparisons, but their numbers disagree because they quote pricing snapshots from different periods and purchase models. The English version puts an 8-hour single-GPU fine-tuning run at $7.45 per hour on OCI's BM.GPU4.8 versus $6.12 per hour on Azure's ND-A100 v4 with a one-year reservation, roughly 18 percent cheaper, plus $0.08 per GB of egress to move data out of OCI. The Portuguese version quotes $3.20 per hour for an Azure A100 spot instance against $3.60 per hour on demand at OCI, and an egress rate of $0.09 per GB, slightly different from the English guide's figure. The Spanish version cites much lower per-GPU-hour rates from an April 2024 comparison. The consistent direction across all three: Azure lands somewhat cheaper once reservations and Savings Plans apply, and data egress is the main cost to watch during the move.

Migrating without downtime

The recommended pattern in the guides is blue-green deployment: stand up a parallel environment in Azure, validate inference there, then shift traffic before decommissioning the OCI side. Concretely, the guides describe exporting an OCI resource inventory and importing it into Terraform state; provisioning Azure equivalents (ND-series GPU VMs, Blob Storage, AKS) through Azure CLI or Terraform; copying checkpoints to Azure Blob; re-registering container images in Azure Container Registry; and using Azure Front Door to flip traffic weights to the Azure backend. For bulk data, the Portuguese guide estimates that copying 10 TB via Azure Data Factory at around 5 GB/s would take about six hours, and suggests scheduling low-demand windows. A shared security checklist covers moving identities to Azure AD and revoking OCI IAM tokens, encrypting data in transit and at rest, enabling auditing, and applying RBAC across AKS and Azure ML workspaces.

If you want to stay partly on Oracle

A full exit is not mandatory. The Portuguese guide notes you can keep some workloads on OCI by linking an Azure virtual network to an OCI VCN over a site-to-site VPN, but warns of egress costs and added latency on inference calls. It also says Microsoft is offering help: filing an Azure Migration & Modernization ticket reportedly gets you compatibility-validation scripts and cost estimates.

Why it matters

The partnership's end turns what was an architecture choice into an operational deadline. Teams that leaned on Azure–OCI interop for GPU capacity, marketplace billing or hybrid pipelines now own a migration project, and the conflicting pricing figures between the guides show how much the final cost depends on region, commitment level and data volume. The wider lesson is vendor risk: cross-cloud integrations are convenient until one party walks away. Teams that kept infrastructure as code, portable model artifacts and a traffic-switching layer in place are the ones positioned to execute a cutover like this with no visible downtime.