Microsoft 365 integration overview (change request)

Overview

This article is a high-level overview of how Opensense integrates with Microsoft 365 for consistent, branded email signatures across your organization. The setup follows Microsoft’s best practices for email signature infrastructure and configuration, using connectors, rules, and DNS updates. For how signatures flow through Opensense, see How does Opensense work with Microsoft 365?

Not a step-by-step guide

Work with your dedicated Implementation Engineer, or contact help@opensense.com, to complete the integration.

Integration components

The integration of Opensense with your Microsoft 365 (O365) message environment requires six elements:

1. Connector: Opensense Outbound Connector
2. Connector: Opensense Inbound Connector
3. Rule: Exclude Calendar
4. Rule: Enable Opensense
5. Rule: Opensense Stamping
6. DNS entries update

Connectors

Setting	Opensense Outbound Connector	Opensense Inbound Connector
From	Office 365	Your organization's email server
To	Your organization's email server	Office 365
Used only when	A transport rule redirects messages to the connector	—Not listed
Routing	To the Opensense API endpoint office365-api.sendergen.com	—Not listed
Certificate	Connects through TLS, with a certificate from a trusted certificate authority (CA)	Identified by a certificate signed from the *.sendergen.com domain

Transport rules

A dash means that no exception is listed for that rule.

Rule	Exclude Calendar	Enable Opensense	Opensense Stamping
Rule name	Opensense Exclude Calendar	Enable Opensense	Opensense Stamping
Sent from inside the organizationApplies when	Yes	Yes	Yes
From your domainsApplies when	Yes	Yes	Yes
Also requiresApplies when	The message type is Calendaring	The subject or body contains the Opensense token [[#]]	The sender is a member of a group (at first, a distribution list or a mail-enabled security group)
Effect	Sets a message header, so that no signature is placed on calendar messages	Uses the Opensense Outbound Connector	Applies the Opensense plain-text signature through the disclaimer feature, and adds an Opensense message header to show that the stamping rule applied a signature
Confirms the sender address matches the envelope sender	Yes	Yes	Yes
Automatic repliesException	—Not listed	Yes	Yes
Emails with a header value that Opensense appliesException	—Not listed	Yes, to avoid duplicate signatures	Yes
Non-customer or non-routable domainsException	—Not listed	Yes	Yes

Disabling Rich Text Format (RTF)

Emails sent in Rich Text Format (RTF) do not support HTML rendering, which interferes with how Opensense signatures display. RTF strips or breaks HTML signatures. To keep signatures formatted and on brand on all devices and mail clients, disable RTF in the Exchange mail flow settings. See Why do we set use RTF to never in Exchange Online?

Updating DNS entries

Opensense customers must update the required DNS entries in both external and internal DNS, if applicable. This keeps your brand consistent and improves deliverability. See Required DNS settings for Opensense.

What’s next

• How does Opensense work with Microsoft 365?: how email flows through Opensense.
• Required DNS settings for Opensense: the DNS entries to add.
• Choosing a deployment method: Stamping, Plain Text Block, and the other methods.