The Multicloud Service Model
With OCI multicloud's Oracle Database Service for Azure (ODSA), your database resources reside in an OCI account that is linked to your Azure account through Oracle Interconnect for Microsoft Azure, an Oracle-managed tunnel connection. ODSA's interconnect and account linking services are provided at no cost.
To perform basic database and infrastructure management tasks, you use the ODSA portal, which is an OCI interface.
In the Azure portal, you can view database metrics and events. Metrics appear in Azure Application Insights, while events appear in Azure Log Analytics.

The ODSA Portal
The ODSA portal is an OCI web interface with an Azure look and feel that you use for database and infrastructure provisioning and management. You always use your Azure credentials to access the ODSA portal.
The ODSA portal is distinct from the OCI Console, which is discussed below in Your OCI Account.

Oracle Interconnect for Microsoft Azure
Oracle Database Service for Azure uses Oracle Interconnect for Microsoft Azure, a high performance, low-latency, low-jitter private tunnel connection for network traffic between OCI and Azure. Oracle has partnered with Azure to offer this connection in a designated set of OCI regions located around the world. When you sign up for ODSA, the service configures the private connection to your database resources as part of the account linking process.
Oracle Database Service for Azure supports the use of the interconnect for traffic to and from OCI Oracle Databases only.
Your OCI Account
When you sign up for ODSA, if you don't have an existing OCI account, you can create one during the sign up.
To access the OCI Console for account management or to use other OCI, you choose whether to use Azure Active Directory as your identify provider, or to manage users through OCI IAM. If you choose not to create identity federation with Azure Active Directory, you only use your OCI credentials to log into the regular OCI console. As mentioned in The ODSA Portal, you always use your Azure credentials when accessing the ODSA portal.
In your OCI account, your databases and infrastructure resources are maintained in the ODSA Compartment that is automatically created for ODSA resources during the sign up process. An OCI compartment should be thought of as a logical group and not a physical container. It is similar to an Azure subscription.
ODSA creates an Oracle managed Multicloud Link configuration in your OCI account during service deployment to store details for the connected Azure and OCI accounts during the service deployment. This resource also manages ODSA linking for Azure subscriptions and regions.
Your Azure Account
During the service deployment, ODSA creates an enterprise application in Azure that does the necessary ODSA configuration in Azure and allows you to connect your Azure subscriptions to the service. ODSA automatically creates user groups and custom ODSA user roles for you in Azure Active Directory. These groups allow you to easily enable user access to ODSA databases, infrastructure, administrative resources, and Oracle Support.
Billing
Your ODSA database resources are billed by OCI. See Billing and Cost Management for information about viewing your subscription details, invoices, payment history, manage your payment method, and more. Database resources include databases, Exadata infrastructure. See Oracle Bring Your Own License (BYOL) for information on using Oracle Database licenses you currently own with databases provisioned in the Oracle Cloud (including ODSA databases). See Pricing for information on OCI pricing models and a cost estimator.
There is no charge for the following:
- Oracle Interconnect for Microsoft Azure. Oracle manages this connection, and does not charge for the use of it with ODSA, or for ODSA network traffic across the connection.
- OCI Virtual Cloud Networks used by ODSA database systems.
Azure bills for the virtual network peering required by ODSA, and for resources provisioned in Azure.