Oracle Integration Cloud: How to set up custom sender emails

Oracle Integration Cloud (OIC) streamlines workflows but sends notifications from an Oracle-controlled address by default. Replacing this with your company’s domain strengthens brand recognition and keeps messages out of spam folders. Here’s how to configure a custom “From” email address in OIC without compromising deliverability or security.

Why switch to a custom sender email?

Enterprise users often need emails to appear as trusted communications. While Oracle’s default address like no-reply@mail.integration.eu-frankfurt-1.ocp.oraclecloud.com meets basic needs, it lacks the branding and authentication required for professional correspondence. Switching to a verified corporate domain—such as alerts@yourcompany.com—improves recognition, trust, and email filtering outcomes.

Common concerns addressed by custom sender setup include:

• Brand consistency in customer-facing notifications
• Reduced risk of messages being flagged as spam
• Compliance with corporate email policies
• Clear sender identification for recipients

Step-by-step: configuring a custom sender in OIC

Before changing settings, ensure you have administrative access to OIC and your domain’s DNS records.

Step 1: Add the email address in OIC

Log in to your Oracle Integration Cloud dashboard and navigate to:

Settings → Notifications → Senders

Click Add Email Address and enter your desired sender (for example, notifications@yourcompany.com). Save the entry. Oracle will immediately initiate verification.

Step 2: Verify ownership via email confirmation

OIC sends a verification code to the entered address. Retrieve the code from the inbox and paste it back into the OIC interface. Once confirmed, the address becomes an approved sender in your OIC environment.

Step 3: Request DNS records from Oracle Support

Even after verification, messages may still be rejected by email filters. Submit a Service Request (SR) to Oracle Support with the exact wording: “Request CNAME details to configure a custom sender email address in Oracle Integration Cloud.” Oracle will respond with two key values:

• A unique CNAME key (e.g., oci-sender._domainkey.yourcompany.com)
• A corresponding CNAME value (a long alphanumeric string)

This step is mandatory for authentication and spam prevention.

Step 4: Update your domain’s DNS records

Forward the CNAME details to your DNS administrator. They will add the key-value pair to your domain’s DNS zone file. This record allows receiving mail servers to verify that Oracle is authorized to send emails on your behalf.

Step 5: (Recommended) Add an SPF record for extra protection

To further strengthen deliverability, configure Sender Policy Framework (SPF) in DNS. Ask your administrator to add an SPF record like:

v=spf1 include:spf.oracle.com ~all

This specifies that Oracle’s servers are permitted senders, reducing spoofing risks and improving email trust scores.

Step 6: Apply the custom sender in your integrations

Once all DNS and verification steps are complete, update your OIC integrations to use the new From address. This applies to:

• Integration Insight notifications
• Process automation alerts
• Workflow completion messages

Every notification sent from OIC will now originate from your domain, maintaining professional consistency.

Final checklist before going live

• [x] Custom email address added and verified in OIC
• [x] CNAME record added to DNS
• [x] SPF record updated (optional but recommended)
• [x] Integration processes tested with sample notifications
• [x] Spam folder checks performed for recent test emails

Configuring a custom sender in Oracle Integration Cloud is a one-time setup that pays ongoing dividends in branding, trust, and deliverability. With your domain now authenticated, future notifications will arrive reliably—supporting seamless business communication.

Future updates to OIC may introduce new authentication methods. Stay informed through Oracle’s release notes to maintain optimal email settings.