---
title: "Microsoft 365 integration overview (change request)"
slug: "change-request-office-365-integration-with-opensense"
description: "The six Microsoft 365 elements an Opensense integration needs: outbound and inbound connectors, three transport rules, and DNS entries. Plus disabling RTF."
updated: 2025-10-02T18:45:28.000Z
canonical: "https://help.opensense.com/docs/change-request-office-365-integration-with-opensense"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.opensense.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 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](https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/use-connectors-to-configure-mail-flow/integrate-office-365-with-an-email-add-on-service), using connectors, rules, and DNS updates. For how signatures flow through Opensense, see [How does Opensense work with Microsoft 365?](https://help.opensense.com/docs/how-does-opensense-work-with-office-365)

:::caution[Not a step-by-step guide]
Work with your dedicated Implementation Engineer, or contact [help@opensense.com](mailto: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

<div class="kb-deployment-compare kb-deployment-compare--plain">
  <div class="kb-deployment-compare__viewport" role="region" aria-label="Opensense connectors" tabindex="0">
    <table>
      <colgroup><col class="kb-deployment-compare__feature-col"></colgroup>
      <thead>
        <tr>
          <th scope="col">Setting</th>
          <th scope="col"><span class="kb-deployment-compare__method">Opensense Outbound Connector</span></th>
          <th scope="col"><span class="kb-deployment-compare__method">Opensense Inbound Connector</span></th>
        </tr>
      </thead>
      <tbody>
        <tr>
          <th scope="row">From</th>
          <td>Office 365</td>
          <td>Your organization's email server</td>
        </tr>
        <tr>
          <th scope="row">To</th>
          <td>Your organization's email server</td>
          <td>Office 365</td>
        </tr>
        <tr>
          <th scope="row">Used only when</th>
          <td>A transport rule redirects messages to the connector</td>
          <td><span aria-hidden="true">—</span><span class="sr-only">Not listed</span></td>
        </tr>
        <tr>
          <th scope="row">Routing</th>
          <td>To the Opensense API endpoint <code>office365-api.sendergen.com</code></td>
          <td><span aria-hidden="true">—</span><span class="sr-only">Not listed</span></td>
        </tr>
        <tr>
          <th scope="row">Certificate</th>
          <td>Connects through TLS, with a certificate from a trusted certificate authority (CA)</td>
          <td>Identified by a certificate signed from the <code>*.sendergen.com</code> domain</td>
        </tr>
      </tbody>
    </table>
  </div>
</div>


### Transport rules

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

<div class="kb-deployment-compare kb-deployment-compare--plain">
  <div class="kb-deployment-compare__viewport" role="region" aria-label="Opensense transport rules" tabindex="0">
    <table>
      <colgroup><col class="kb-deployment-compare__feature-col"></colgroup>
      <thead>
        <tr>
          <th scope="col">Rule</th>
          <th scope="col"><span class="kb-deployment-compare__method">Exclude Calendar</span></th>
          <th scope="col"><span class="kb-deployment-compare__method">Enable Opensense</span></th>
          <th scope="col"><span class="kb-deployment-compare__method">Opensense Stamping</span></th>
        </tr>
      </thead>
      <tbody>
        <tr>
          <th scope="row">Rule name</th>
          <td><code>Opensense Exclude Calendar</code></td>
          <td><code>Enable Opensense</code></td>
          <td><code>Opensense Stamping</code></td>
        </tr>
        <tr>
          <th scope="row">Sent from inside the organization<span class="kb-deployment-compare__row-note">Applies when</span></th>
          <td><span class="kb-deployment-compare__mark is-yes" title="Yes"><span class="sr-only">Yes</span></span></td>
          <td><span class="kb-deployment-compare__mark is-yes" title="Yes"><span class="sr-only">Yes</span></span></td>
          <td><span class="kb-deployment-compare__mark is-yes" title="Yes"><span class="sr-only">Yes</span></span></td>
        </tr>
        <tr>
          <th scope="row">From your domains<span class="kb-deployment-compare__row-note">Applies when</span></th>
          <td><span class="kb-deployment-compare__mark is-yes" title="Yes"><span class="sr-only">Yes</span></span></td>
          <td><span class="kb-deployment-compare__mark is-yes" title="Yes"><span class="sr-only">Yes</span></span></td>
          <td><span class="kb-deployment-compare__mark is-yes" title="Yes"><span class="sr-only">Yes</span></span></td>
        </tr>
        <tr>
          <th scope="row">Also requires<span class="kb-deployment-compare__row-note">Applies when</span></th>
          <td>The message type is <strong>Calendaring</strong></td>
          <td>The subject or body contains the Opensense token <code>[[#]]</code></td>
          <td>The sender is a member of a group (at first, a distribution list or a mail-enabled security group)</td>
        </tr>
        <tr>
          <th scope="row">Effect</th>
          <td>Sets a message header, so that no signature is placed on calendar messages</td>
          <td>Uses the Opensense Outbound Connector</td>
          <td>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</td>
        </tr>
        <tr>
          <th scope="row">Confirms the sender address matches the envelope sender</th>
          <td><span class="kb-deployment-compare__mark is-yes" title="Yes"><span class="sr-only">Yes</span></span></td>
          <td><span class="kb-deployment-compare__mark is-yes" title="Yes"><span class="sr-only">Yes</span></span></td>
          <td><span class="kb-deployment-compare__mark is-yes" title="Yes"><span class="sr-only">Yes</span></span></td>
        </tr>
        <tr>
          <th scope="row">Automatic replies<span class="kb-deployment-compare__row-note">Exception</span></th>
          <td><span aria-hidden="true">—</span><span class="sr-only">Not listed</span></td>
          <td><span class="kb-deployment-compare__mark is-yes" title="Yes"><span class="sr-only">Yes</span></span></td>
          <td><span class="kb-deployment-compare__mark is-yes" title="Yes"><span class="sr-only">Yes</span></span></td>
        </tr>
        <tr>
          <th scope="row">Emails with a header value that Opensense applies<span class="kb-deployment-compare__row-note">Exception</span></th>
          <td><span aria-hidden="true">—</span><span class="sr-only">Not listed</span></td>
          <td>Yes, to avoid duplicate signatures</td>
          <td><span class="kb-deployment-compare__mark is-yes" title="Yes"><span class="sr-only">Yes</span></span></td>
        </tr>
        <tr>
          <th scope="row">Non-customer or non-routable domains<span class="kb-deployment-compare__row-note">Exception</span></th>
          <td><span aria-hidden="true">—</span><span class="sr-only">Not listed</span></td>
          <td><span class="kb-deployment-compare__mark is-yes" title="Yes"><span class="sr-only">Yes</span></span></td>
          <td><span class="kb-deployment-compare__mark is-yes" title="Yes"><span class="sr-only">Yes</span></span></td>
        </tr>
      </tbody>
    </table>
  </div>
</div>


## 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?](https://help.opensense.com/docs/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](https://help.opensense.com/docs/dns-entries-must-have).

## What's next

- [How does Opensense work with Microsoft 365?](https://help.opensense.com/docs/how-does-opensense-work-with-office-365): how email flows through Opensense.
- [Required DNS settings for Opensense](https://help.opensense.com/docs/dns-entries-must-have): the DNS entries to add.
- [Choosing a deployment method](https://help.opensense.com/docs/choose-a-deployment-method): Stamping, Plain Text Block, and the other methods.
