Blog Post

Running SAP Applications on the Microsoft Platform
4 MIN READ

Simplifying Vertex Tax Software Deployment with Oracle Database@Azure

anbugovi's avatar
anbugovi
Icon for Microsoft rankMicrosoft
Mar 17, 2025
                                                  Co-Authors

Scott Gamble, Frank Kassanits, Suresh Devarajan, Momin Qureshi, Venkat Ramakrishnan,                                                  Ross Sponholtz & Anbu Govindasamy

In this blog, we will explore how to leverage Oracle Database@Azure for Vertex Tax Software, which is part of the SAP solution. Oracle Database@Azure is an Oracle database service that runs Oracle databases on Oracle Cloud Infrastructure (OCI) within Microsoft datacenters, ensuring the fastest possible access to Azure resources and applications.

Oracle database can be deployed on Azure VM as an IaaS solution or as an Oracle Database@Azure service just like other Azure services. Each approach has its own merits. In this blog, we will discuss the Oracle Database@Azure solution and how it simplifies and accelerates the deployment and maintenance of Oracle Databases on Azure. While Oracle Database@Azure is not currently supported solution for running SAP systems, at the same time, Oracle Database@Azure can be leveraged with non-SAP products.

Oracle Database@Azure - Architecture of the implemented Vertex Tax solution

Please find below the implementation architecture corresponding to the Vertex Tax solution implementation on Oracle Database@Azure – Oracle Exadata database service, followed by focus on Networking, Architectural considerations for coming up with a similar architecture for your needs.

Oracle Database@Azure - Networking Considerations
  • When you design your network topology for the Oracle Exadata Database service on Oracle Database@Azure, please refer to the Microsoft Cloud Adoption Framework – Landing Zone Accelerator.
  • It is critical to understand the core networking design considerations and recommendations applicable for your environment along with the best practices for configuring and managing the Azure network as required for connecting your applications to the database.
  • In the above architecture, each application virtual network is directly peered to the database virtual network. Application and database virtual networks connect to a hub network for shared services like firewalls or Domain Name System (DNS).
  • This design helps ensure low-latency direct communication while enabling centralized traffic inspection and management. Reference diagram provided below as well.
Oracle Database@Azure - Architectural Considerations
  • Deployment Approach: The Vertex Oracle Database is deployed on Oracle Database@Azure Exadata database service, while the Vertex Application Servers are hosted on Azure as an Infrastructure as a Service (IaaS) solution.
  • Landing Zone: The Azure Landing Zone architecture implements a hub-and-spoke network pattern. Both SAP and Vertex share a single landing zone and subscription, while Oracle Database@Azure is deployed to its own separate landing zone and subscription.
  • Network: The database VNET is peered with the application VNET hosting Vertex, allowing communication between the Oracle database and Vertex application. The database VNET is also peered with Hub VNET for migrating data from on-prem and setting up DR with DR region.
  • Migration: Oracle Data Guard is used for one time database migration, ensuring minimal downtime and seamless transition.
  • HA/DR: High Availability setup between zones by leveraging Oracle Data Guard (ODG) with FSFO. ODG is also part of DR solution.
  • Existing Oracle Database software customers can use the Bring Your Own License (BYOL) option or Unlimited License Agreements (ULAs).
Oracle Database@Azure Benefits

Given that you can now deploy and use Oracle database services running on OCI within the native Azure portal and APIs, you benefit from an OCI-in-Azure-like experience. Here are some of the key benefits of Oracle Database@Azure.

  • Optimized performance and sub millisecond latency between app and data by running Oracle Databases on Oracle Cloud Infrastructure (OCI) hosted in Azure datacenters.
  • SLA, Feature and Price parity with Oracle Cloud Infrastructure, along with a collaborative support model with Oracle.
  • Native integration with Azure services like Microsoft Entra ID for identity and access management, Azure Kubernetes Service (AKS), and Azure AI/ML services. Azure vnet provides secure connectivity.
  • Seamless integration with existing applications and infrastructure, maintaining operational consistency.
  • Exadata provides extensive automation for installation, upgrades, and patching, reducing manual efforts.
  • The Exadata database service allows for co-management and scale-out of infrastructure with ultra-low lead times while the customer continues to benefit from database-optimized compute, networking, storage associated with Exadata.
  • On-premises operational procedures, automation, and best practices can be ported to Azure without losing any knowledge base, ensuring quicker adoption.
QuickStart - Oracle Database@Azure – Exadata service

To begin your Oracle Database@Azure journey, reach out to the Oracle sales team or your Oracle sales representative. They will assist you in creating a private offer for the Oracle Exadata database service on the Azure Marketplace. Once the offer is ready, you can accept it and complete the purchase directly through the Azure Marketplace in the Azure Portal.

After completing the purchase, you can provision the Oracle Exadata Database service for Oracle Database@Azure using the Azure portal, Azure APIs, SDKs, and Terraform.

For more detailed information on additional Azure region availability, design consideration and onboarding details please refer to Getting Started.  

Conclusion

The deployment of the Exadata Database service on Oracle Database@Azure for Vertex Tax Software simplifies Oracle database deployment, management and operation. In our experience, On-premises operational procedures, automation, and best practices can be ported to Azure without losing any knowledge base, ensuring quicker adoption.

Updated Mar 14, 2025
Version 1.0
No CommentsBe the first to comment