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

# Connect ReachKit Manually

> Use the current manual ReachKit Microsoft mailbox connection flow until a supported automated TenantCore integration is available.

# Connect ReachKit Manually

ReachKit is not currently part of TenantCore's fully automated sending-provider connection flow.

The limitation is vendor access, not the TenantCore mailbox model.

Until a supported programmatic OAuth-init flow is available from ReachKit, connect the mailbox through ReachKit's own Microsoft connection experience.

## Before you begin

You need:

* a TenantCore-created mailbox
* the mailbox password
* the required Microsoft MFA method, if enabled
* access to your ReachKit workspace

## In TenantCore

1. Open the mailbox.
2. Copy the mailbox email address.
3. Reveal/copy the current password if ReachKit requires it.
4. If you use TenantCore-managed MFA, be ready to request the current code during Microsoft authentication.

## In ReachKit

1. Open the ReachKit inbox connection area.
2. Choose the Microsoft connection option.
3. Start **Connect with Microsoft**.
4. Complete the Microsoft sign-in flow for the mailbox.
5. Finish any ReachKit setup steps.

ReachKit currently starts its Microsoft authorization through ReachKit's own authenticated application flow.

TenantCore should not construct or reuse ReachKit OAuth `state` values.

## SMTP/IMAP prerequisites

If ReachKit's current setup instructions require Microsoft mailbox apps such as Authenticated SMTP or IMAP to be enabled, follow the provider's current instructions for the mailbox.

Provider requirements can change independently of TenantCore.

## Automation status

TenantCore can add a direct ReachKit workflow later if ReachKit exposes a supported API/partner operation for generating the Microsoft OAuth authorization flow.

Until then, treat this as a manual provider connection.