Announcing the public preview of Oracle Database built-in connector for Azure Logic Apps Standard

Run Oracle Database operations natively in your Logic Apps Standard workflows.

Today we’re excited to announce the public preview of Oracle Database built-in connector for Azure Logic Apps (Standard). This connector brings first-class Oracle Database connectivity to single-tenant workflows by running in-process with the Logic Apps runtime, helping you build reliable, high-throughput integrations with Oracle-backed systems while keeping network traffic within your chosen network boundary.

Why this matters?

• In-process execution: Operations execute within the Logic Apps Standard runtime for streamlined connectivity and lower latency.
• No on-premises data gateway (when your Logic App has network connectivity to Oracle): Simplify architecture and reduce operational overhead.
• Better fit for enterprise network topologies: Use VNET integration, private endpoints, and network controls consistent with your environment.
• Purpose-built Oracle capabilities: Get Oracle-focused actions including Execute stored procedure, a common gap for generic JDBC-based approaches.
• Designed for scale: Built-in connectors align with the direction of Logic Apps Standard for performance and operational consistency across workloads.
• On-premises integrations: With Hybrid Logic Apps, you can connect on-premises Oracle databases from on-premises-hosted Logic Apps.

What can you do with the connector?

The Oracle Database built-in connector currently supports the following actions:

1. Get tables: Discover tables (and views, depending on permissions) available to your connection.
2. Get rows: Read rows from a selected table with pagination support.
3. Insert row: Insert a row into a selected table.
4. Execute query: Run SQL statements (for example, select, update, delete) and return results when applicable.
5. Execute stored procedure: Call stored procedures to encapsulate business logic and advanced operations.

Connector details at a glance

• Logic Apps SKU: Standard (single-tenant).
• Execution model: Built-in (in-process) connector.
• Connectivity: No gateway required when your Logic App runtime can reach the Oracle endpoint (for example, via VNET integration).
• Oracle versions: Supports Oracle Database 11 and later (compatible with the managed driver).
• Authentication: Username and password.
• Triggers: The connector is actions-only in the current release.

Getting started

1. Ensure network connectivity from your Logic App Standard runtime to your Oracle Database endpoint (host and port), including any required DNS and firewall rules.
2. Create a new Oracle Database connection in the Logic Apps designer.

3. Provide connection parameters

o   Server address

o   Username

o   Password

4. Choose a server address format that matches your environment:

o   Easy Connect (host/port/service name) for quick setup.

o   TNS descriptor for advanced connection configuration.

5. Add an action (for example, Get rows or Execute stored procedure) and start building your workflow.

Known limitations (current release)

• No triggers: The connector currently supports actions only.
• Update/Delete actions: Use Execute query or Execute stored procedure for update/delete scenarios.
• Connection validation: Some connection issues may surface at workflow runtime rather than during connection creation.
• Timeouts: Default query timeout is 30 seconds (configurable via app settings). The function host may impose an upper limit (commonly up to 10 minutes depending on configuration).
• Case sensitivity: Oracle identifiers can be case sensitive; ensure table/column names match your schema as defined.

Troubleshooting and observability

When issues occur, you’ll typically see failures surfaced through workflow run history and diagnostics. Oracle error details are returned as standard connector failures, and many common Oracle error conditions map to familiar HTTP status codes (for example, authentication failures, connectivity issues, and timeouts).

• 401 (authentication): Verify username/password, account lock status, and password expiry policies.
• 502 (connectivity): Verify host/port reachability, DNS resolution, firewall rules, and Oracle listener availability.
• 504 (timeout): Verify query complexity, indexes, and configured timeouts (query timeout and host timeout).
• 404 (object not found): Verify schema/table/view names and permissions; ensure correct casing.
• 429 (resource/session limits): Review Oracle session limits and workflow concurrency patterns.

Get started today

If you’re building new integrations with Oracle, or modernizing legacy workloads, try the Oracle Database built-in connector in your Logic Apps Standard workflows and let us know what you build. We’re especially interested in feedback on triggers, advanced authentication options, and additional Oracle operations you’d like to see next.

Thank you for your continued feedback and partnership as we expand built-in connectivity across Azure Logic Apps.

References: Connect to Oracle Database from Workflows - Azure Logic Apps | Microsoft Learn