Skip to main content

​
Sending Integrations

TenantCore can connect TenantCore-created mailboxes to supported sending platforms and keep the connection state attached to the mailbox. This removes much of the repetitive work involved in moving mailbox credentials, Microsoft authentication, and connection status between separate tools.

​
Integration account

A sending integration represents the operator’s connected sending-platform account or workspace. TenantCore can store the provider connection securely and use it only for the authenticated TenantCore account that owns it. Provider credentials are not returned through the public API after they are configured.

​
Mailbox connection

A mailbox connection links:
TenantCore tracks states such as:
  • connected
  • pending
  • failed
  • disconnected

​
One active sending platform per mailbox

TenantCore prevents a mailbox from being actively connected to multiple sending integrations at the same time where that would create conflicting connection state. If a mailbox is pending or connected to a different integration, TenantCore can block a second conflicting connection attempt.

​
Retrying interrupted connections

A persisted pending or connecting state does not mean the mailbox should remain locked forever. If the operator closes a popup, refreshes the browser, or an OAuth attempt is interrupted, TenantCore allows the connection to be retried. Only an active connection attempt in the current browser session should temporarily prevent duplicate clicks.

​
Credentials and MFA during connection

Where useful, TenantCore can show the mailbox email and password before the provider connection begins so the operator can copy them into the provider flow. If TenantCore-managed MFA is not configured, the operator may:
  • set up MFA
  • continue without TenantCore MFA
TenantCore-managed MFA is not a mandatory prerequisite for sending-tool connection.

​
Supported and manual providers

TenantCore automates the connection workflow only where the provider exposes the level of access required. Some providers may require a manual connection workflow until a supported API or partner integration is available. TenantCore can add additional direct provider integrations over time without changing how your tenants, domains, or mailboxes are organized.

​
Public API model

The Complete API exposes TenantCore-defined integration operations such as:
  • create a TenantCore integration
  • test it
  • connect a TenantCore mailbox
  • check connection state
  • retry or disconnect
It does not expose raw provider APIs as a generic passthrough. Every integration and mailbox must belong to the authenticated TenantCore account before the provider action is attempted.