This guide covers how to integrate Opensense with Microsoft 365 for consistent, branded email signatures across your organization. The setup follows Microsoft’s recommended architecture using connectors, rules, and DNS updates.
Learn how Opensense works with Microsoft 365
We follow Microsoft’s best practices for email signature infrastructure and configuration
Integration Components
The integration of Opensense to your O365 message environment requires six (6) elements:
O365 Connector: Opensense Outbound Connector
O365 Connector: Opensense Inbound Connector
O365 Rule: Exclude Calendar
O365 Rule: Enable Opensense
O365 Rule: Opensense Stamping
Update DNS Entries
O365 Connector – Outbound
The Opensense Outbound Connector is configured as:
From: Office 365
To: Your organization’s email server
Used only when: A transport rule redirects messages to the connector
Routing: To Opensense API endpoint
office365-api.sendergen.comConnection: Via TLS with a certificate from a trusted CA
O365 Connector – Inbound
The Opensense Inbound Connector is configured as:
From: Your organization’s email server
To: Office 365
Identification: By a certificate signed from the
sendergen.comdomain
O365 Rule – Exclude Calendar
Name: Opensense Exclude Calendar
This rule applies when:
Emails are sent from inside the organization
Emails are from your domain(s)
The message type is “Calendaring”
Effect:
Sets a message header so no signature is placed on calendar messages.
Confirms that the sender address matches the one in the envelope.
O365 Rule – Enable Opensense
Name: Enable Opensense
This rule applies when:
Emails are sent from inside the organization
Emails are from your domain(s)
The subject or body contains the Opensense token:
[[#]]
Effect:
Uses the Opensense Outbound Connector
Exceptions:
If the message is an Automatic Reply
If the email has a header value that Opensense applies (avoids duplicate signatures)
If the email is from a non-customer or non-routable domain
Also confirms the sender address matches the envelope sender.
O365 Rule – Opensense Stamping
Name: Opensense Stamping
This rule applies when:
Emails are sent from inside the organization
Emails are from your domain(s)
The sender is part of a group (initially via DL or mail-enabled security group)
Effect:
Applies Opensense plain-text signature via disclaimer functionality
Adds an Opensense message header to indicate a signature is applied via stamping rule
Exceptions:
If the message is an Automatic Reply
If the email has a header value that Opensense applies
If the email is from a non-customer or non-routable domain
Also confirms the sender address matches the envelope sender.
Disable Rich Text Format (RTF)
Emails sent in Rich Text Format (RTF) do not support HTML rendering, which interferes with the display of Opensense signatures. To ensure proper formatting and branding, RTF should be disabled.
Issue: RTF strips or breaks HTML-based signatures
Resolution: Disable RTF within the Exchange mail flow settings.
This ensures signatures appear consistently across all devices and mail clients.
DNS Entries Update
Opensense customers are required to update the following DNS entries to both external and internal DNS (if applicable). This ensures brand continuity and improves deliverability.
Required DNS Settings for Opensense
Opensense Support
For further assistance, contact Opensense Support:
Email: help@opensense.com
Knowledge Base: help.opensense.com