Linking Oracle Database@Azure to Multiple Azure Subscriptions

Learn about using two or more Azure subscriptions to manage your Oracle Database@Azure service.

For private offer Oracle Database@Azure deployments, you can use the service with up to 25 total Azure subscriptions within a single Azure account. This gives you the ability to isolate projects, environments, and application domains for security and cost allocation, while maintaining a single Azure account for simplified billing and account management. When using two or more Azure subscriptions with Oracle Database@Azure, all Azure subscriptions are linked to the OCI tenancy used for service onboarding.

How Multiple Azure Subscriptions Work in Oracle Database@Azure

During Oracle Database@Azure onboarding, you select an Azure subscription to use initially with the service. In this documentation, the subscription selected during onboarding is referred to as the primary subscription for Oracle Database@Azure. After onboarding is complete and your Azure account is linked to your OCI tenancy, the OCI tenancy has a new, automatically created compartment for the management of the service.

When you add more Azure subscriptions to your Oracle Database@Azure service, the service automatically creates a child compartment within the main Oracle Database@Azure compartment created during onboarding. You don't have to do any manual configuration of your OCI tenancy to add more Azure subscriptions to the service.

Important

When adding Azure subscriptions to your Oracle Database@Azure service, the new subscriptions must use the same billing account as the primary Azure subscription selected during service onboarding.

After you add a new Azure subscription to the Oracle Database@Azure service, you can begin provisioning database resources in that subscription. For database systems with more than one component (for example, Exadata systems with an infrastructure resource and a VM cluster resource), all components must be provisioned within the subscriptions added to the Oracle Database@Azure service.

When users are working within an Azure subscription, they only see the Oracle Database@Azure resources provisioned within subscriptions added to Oracle Database@Azure service. For example you can provision an Exadata Infrastructure resource in one Azure subscription, and use it to create an Exadata VM cluster in another Azure subscription, if both subscriptions have been added to the Oracle Database@Azure service.

Prerequisites

  • You must onboard with Oracle Database@Azure before you can link Azure subscriptions to the service as described in this topic. See Onboarding with Oracle Database@Azure and Task 1: Prerequisites for Oracle Database@Azure for more information.
  • The following resource providers must be registered with the subscriptions you're adding to the service:

    • Oracle.Database
    • Microsoft.BareMetal
    • Microsoft.Network
    • Microsoft.Compute

    To register a resource provider, navigate to the Azure subscription details page, then click Resource providers under Settings. Select the resource provider you want to register from the list of providers, then click Register.

    Note that you can't provision Oracle Database@Azure resources in a subscription until the "Microsoft.BareMetal", "Microsoft.Network", and "Microsoft.Compute" resource providers are registered for the subscription.

OCI IAM Policy to Manage Resources in a Compartment

When you use more than one Azure subscription with Oracle Database@Azure, OCI creates a subcompartment for each Azure subscription within the primary compartment for the service. To control user access to resources in a specified OCI subcompartment linked to an Azure subscription, you can use a policy such as the following:

Allow group <new-odbaa-exa-infra-administrators> to manage <resource> in compartment id <compartment-id>:<sub-compartment-id>

See Groups in Oracle Cloud Infrastructure for information on OCI IAM for Oracle Database@Azure. See the following IAM topics for information in managing users and groups in OCI:

Adding an Azure Subscription to the Oracle Database@Azure Service

  1. Sign in to the Azure Portal and navigate to the Oracle Database@Azure Overview page. You can find this page by searching for "Oracle Database@Azure" in the Azure portal search.

  2. Click View Oracle Subscription to go to the list of OracleSubscription resources. This list represents Oracle Database@Azure offers that have been accepted. For most customers, the list has only one OracleSubscription resource, named default.
  3. Click default to view the details page for the Oracle Database@Azure offer that you subscribed to during service onboarding.

    Note

    On the details page for the default offer, the name of the primary Azure subscription for the Oracle Database@Azure service is shown in the Subscription field. The Subscription ID of the primary subscription is also shown.
  4. Click Add Azure subscriptions.
  5. In the Add Azure Subscriptions panel, select one or more subscriptions to add to your service using the Azure Subscriptions selector, then click Add.
  6. Optional. View the list of Azure subscriptions registered with the Oracle Database@Azure service. On the details page of the default offer, you can see active Azure subscriptions for the service under Oracle Cloud account. Click the View link beside Added Azure subscriptions to see the list of added subscriptions.

Viewing Billing by Subscription

Your Azure bill displays the total cost for Oracle Database@Azure usage under the primary subscription. You can view usage costs by subscription in the OCI Console using the Cost Analysis tool. See Required IAM Policy in the Cost Analysis documentation for permissions information for this tool. To view costs by subscription:

  1. Open the navigation menu and click Billing & Cost Management. Under Cost Management, click Cost Analysis.
  2. From Reports, select Cost by Service.
  3. From Filters, select the Tag filter.
  4. In the Tag dialog box, select the following:

    • Tag Namespace: orcl-OracleDatabase@Azure
    • Tag Key: AzureSubscriptionId
  5. Click Select.
  6. From Grouping Dimensions, select Service or subscription ID.
  7. Click Apply.

For more information, see the Cost Analysis documentation.