Atlas Liaison GroupConnecting you with what's next.
Colleagues keeping a copy of a sent-message card in shared team history while the original remains in a personal Sent tray.
A missing shared Sent Items copy does not establish that a message failed to reach its recipient. This staged scene illustrates saving team history rather than resending a reply.

Business software

A shared-mailbox reply was sent. Why can't the team find it in Sent Items?

The recipient may have the reply while the team's shared Sent Items folder does not. Before resending it, identify the sender, sending identity, client and folder where the copy was stored.

By Atlas Liaison Group · Sources checked November 2, 2026 · Documentation research

Check the two likely places

Look in the individual's Sent Items and the shared mailbox's Sent Items. Microsoft documents a delegated-mailbox scenario where messages are stored in the sending user's folder instead of the shared mailbox's folder. A missing shared copy therefore does not, by itself, establish a delivery failure.

Use a harmless test message to reproduce the behavior. Record the time, recipient and subject so you can follow one message without confusing it with earlier attempts.

Identify how the reply was sent

DetailWhy it matters
Send As or Send on BehalfMicrosoft provides separate server-side copy controls for these modes.
Outlook version or web clientClient-specific workarounds may not apply everywhere.
Actual From addressA reply sent from the individual's identity is a different event from the intended shared response.
Mailbox access permissionsReading the mailbox and sending from it remain separate permissions.

Have the administrator review the copy setting

Microsoft's troubleshooting guidance describes mailbox settings named MessageCopyForSentAsEnabled and MessageCopyForSendOnBehalfEnabled. These govern keeping shared-mailbox copies for the corresponding sending modes. Have the administrator review the current state and required behavior before changing it.

The same documentation includes older client-specific approaches. Avoid applying a registry workaround copied from an unrelated Outlook version. Microsoft specifically distinguishes which method applies to new Outlook, so a server and client combination should be assessed together.

Test the team history after the change

  1. Send a new test using the intended shared address.
  2. Confirm the recipient sees the correct identity.
  3. Check the shared Sent Items from another authorized team member's view.
  4. Check whether the user's own Sent Items behaves as intended.
  5. Make sure the final arrangement does not create confusing duplicate copies.

The practical goal is a shared history that supports the next handoff. Agree on where staff should look before sending a second response. Finding a saved copy is useful evidence of the sending workflow; troubleshoot actual receipt or delivery errors separately when those are the problem.

Troubleshoot a mailbox that will not appear · Compare a shared mailbox and an alias · Explore business software.

Sources