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

# Connect Microsoft 365

> Receive and answer email in your Support inbox.

<Note>
  This guide includes features awaiting release. If an option is not available in your workspace, contact StackShift Support.
</Note>

## What you can do

Receive and answer email in your Support inbox. Where to find it: Settings → Channels.

## Before you start

* A Microsoft account with access to the intended mailbox; shared mailboxes also need Exchange delegation and sending rights.
* Permission to manage integrations, plus an existing brand and inbox.

## Steps

<Steps>
  <Step>
    Choose the workspace and environment, create a channel, and select Microsoft 365. Give it a recognizable name and choose its inbox.
  </Step>

  <Step>
    Select Continue with Microsoft. Sign in with the account authorized to approve access. Complete any organization consent required by Microsoft.
  </Step>

  <Step>
    Select the exact mailbox. For a shared mailbox, the signing-in user and mailbox address can be different; check both before continuing.
  </Step>

  <Step>
    Open Readiness and resolve the listed missing permissions or account checks. Complete Qualify, then Activate. Qualify means confirming the connection checks; it does not mean changing your subscription.
  </Step>

  <Step>
    Send a new message from a separate customer account. Confirm it reaches the selected inbox, then reply from Support and check the original channel.
  </Step>

  <Step>
    If authorization later expires, reconnect this channel, repeat the checks and activate it again. Do not create duplicate channels to work around an expired login.
  </Step>
</Steps>

## Example

Use a test enquiry such as “What are your opening hours?” and confirm your staff reply reaches the sending account.

## Things to know

* Reading a shared mailbox does not by itself grant Send As permission. Verify an actual reply. Synchronization is for new messages, not a full historical import.
* Connecting one environment does not automatically connect another. Keep live customer traffic separate from test work.

## What happens next

<Check>
  A new customer message and your reply appear in the same intended channel.
</Check>

## If something goes wrong

<Warning>
  * Receiving works but replies fail: ask the Microsoft administrator to check sending rights for the selected shared mailbox. Reconnect if the account grant expired.
  * Messages delayed: check channel health, activation, inbox selection and remaining conversation allowance.
  * Send uncertain: inspect the provider thread before retrying; the message may already have been accepted.
</Warning>

## Related guides

<CardGroup cols={2}>
  <Card title="Support channels and message recovery" href="/stackshift-support/channel-reliability">
    Connect supported inboxes, preserve message history, and recover interrupted delivery safely.
  </Card>

  <Card title="Reply, add private notes and work together" href="/stackshift-support/reply-and-collaborate">
    Keep customer replies separate from internal discussion.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.