Oracle Database service for Azure – linking subscriptions

As part of my multi-cloud research, I wanted to test Oracle Database Service for Azure. In this article, you will see how to sign up for the new service and how to link Oracle and Azure accounts. I used Frankfurt datacenters, Azure MSDN, and OCI paid account (Free Tier does not work) using my private Azure Active Directory.

First and foremost my biggest learning from testing Oracle Database Service for Azure is this: you need to have a paid OCI account, it will not work with the Free Tier offering.

Upgrade Free Tier to a paid account will cost you temporary (?) 100 EUR…

If you do not upgrade your OCI subscription to a paid account you will get this error message: “There was a problem validating your account!” – you have to be quite smart to figure out what’s the real problem here. I wish someone told me this when I was wasting time – but finally got the idea of what could be the issue here 🙂

The next thing is to think and design a little before you start clicking on the cloud portals. Azure and Oracle Cloud-link is a networking-heavy exercise, you have to be keen on what you enter into the networking dialogue to deploy this right. Automation will help you to connect clouds behind the scenes, but only if you provide the proper networking details.

My plan was to connect regions that are close to each other and to my location (in case I add an on-premises link to the comparison).

I picked Frankfurt for both Azure resource group and networking and for Oracle DB Services.
I used the fully automated configuration. Hopefully, this full-screen-related error message will not show up for you (I tried various browsers and I am not in full-screen mode) – anyways, hit the “Proceed anyway” button, that works. Do not get me wrong, I respect the developer team who put together this, it is amazing!
You need to pick a Microsoft Azure subscription to link.
Ensure you have all required permissions granted to the user (on the Azure Subscription) doing the link.
Remember, you need to have permission on Azure Active Directory to register a new service. The user is a global admin in my own Azure Active Directory.
The cloud-link wizard registers an Enterprise Application to Azure Active Directory called “Oracle Database Service”

A fantastic “please wait” picture… After waiting a few minutes, it will do the magic and map Azure resources in Oracle Cloud and create the CloudLink in the background.
*** update 2 months later since I tried first – they improved the picture 🙂

That’s it. Oracle-hosted Azure-Like portal is ready to provision resources in both OCI and Azure.
If you check Take a look at the Status column, it says Linked.
The cheapest option is the Base Database. It is actually a managed VM with an Oracle DB on it.
I think it is a smart idea to check prices using Oracle Cloud Cost Estimator. Autonomous Database obviously costs more than Standard Edition Oracle Database on a cheap VM shape.
I used VM.Standard series VMs with 1-2 OCPU and 15-30GB RAM. That’s more than enough for testing this service.

In my next article, I will share my ideas of how to connect Azure services to the newly provisioned OCI database utilizing automatically provisioned and free-to-use OCI-Azure cloud-link.

Above is my first design idea of connecting Azure App Service and Power App via the premium connector. Over time I noticed, that this design needs some change and improvement.

By the time I am writing this article, everything worked for me what I wanted to test, stay tuned, I will continue to share my learnings on Azure Oracle Services / Oracle Database Service for Azure.

Related posts

Fixing Proxmox Boot Hangs When Passing Through 2× RTX 3090 GPUs: Step-by-Step Troubleshooting Guide

Running multiple NVIDIA GPUs for AI workloads in Proxmox VE can cause early boot hangs if the host OS tries to load conflicting drivers. In this guide I document how my Proxmox host with 2× RTX 3090 was stuck at systemd-modules-load, how I debugged it, which files to inspect (/etc/default/grub, /etc/modprobe.d/, /etc/modules-load.d/), and the final stable configuration for rock-solid GPU passthrough to an Ubuntu VM.

Building the Perfect Edge AI Supercomputer – Adding an Edge Virtualization Layer with Proxmox and GPU Passthrough

I built on my edge AI hardware by adding Proxmox VE as the virtualization layer. After prepping BIOS, using Rufus with the nomodeset trick, and installing Proxmox, I enabled IOMMU, configured VFIO, and passed through 2× RTX 3090 GPUs to a single Ubuntu VM. This setup lets me run private AI workloads at near bare-metal speed, while keeping Windows and native Ubuntu for special use cases.

Budget AI Supercomputers: Dell Server vs. Threadripper Build vs. Next-Gen AI Desktop

Exploring three budget AI supercomputer paths: a Dell R740xd for enterprise labs with big storage but limited GPU flexibility, a TRX50 + Threadripper 7970X workstation offering fast DDR5, Gen5 NVMe, and dual RTX GPU power, and the futuristic GB10 AI desktop with unified CPU/GPU memory. Dell is lab-friendly, GB10 is AI-only, but the TRX50 build strikes the best balance today.

Building the Perfect Edge AI Supercomputer – Cost Effective Hardware

Keeping up with today’s technology is both exciting and demanding. My passion for home labs started many years ago, and while my family often jokes about the time and money I spend on self-education, they understand the value of staying ahead in such a fast-moving field. What started as curiosity has grown into a journey of building cost-effective supercomputers for edge AI and virtualization.

Fix VMware Workstation Performance Issues on Windows 11: Disable Hyper-V and VBS

This blog explains why VMware Workstation runs slower on Windows 11 compared to Windows 10, focusing on changes like Hyper-V, VBS, and HVCI being enabled by default on modern CPUs. It explores why sharing hypervisors with native hardware causes performance issues, and why disabling Hyper-V restores full VMware performance. Step-by-step PowerShell scripts are provided to toggle Hyper-V on or off safely.

Terraform deployment for FortiGate Next-Generation Firewall in Microsoft Azure

This blog explores deploying FortiGate VM in Azure, tackling challenges like license restrictions, Terraform API changes, and Marketplace agreements. It offers insights, troubleshooting tips, and lessons learned for successful single VM deployment in Azure. Using an evaluation license combined with B-series Azure VMs running FortiGate is primarily intended for experimentation and is not recommended for production environments.

Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.