How to deliver Microsoft Teams voicemails to a shared mailbox

One of the more frustrating gaps in Microsoft Teams Phone service is that voicemail can’t be delivered to a shared mailbox natively. Instead, Microsoft pushes organizations toward using Microsoft 365 Groups for shared voicemail scenarios, which isn’t always practical in real-world environments.

This is a very common request, especially because many call queues and departmental phone numbers already map to long-standing shared mailboxes. Think about inboxes like:

• billing@company.com
• helpdesk@company.com
• reception@company.com
• hr@company.com

Most organizations already have established workflows built around these shared mailboxes, and it’s annoying to be forced into redesigning that just because Teams doesn’t offer a simple “send voicemail to shared mailbox” option.

Unfortunately, Teams voicemail is still tied to an individual user mailbox or a M365 group. There’s no native toggle to deliver voicemail directly into an existing shared mailbox.

The good news is that there is a workaround: Exchange Online transport rules.

Why this works

When someone leaves a voicemail in Teams Phone, Microsoft delivers that voicemail as an email message. These voicemail emails typically include:

• Caller information
• The voicemail audio file attachment
• A transcription (if enabled)
• Delivery to the mailbox

Since voicemail arrives through Exchange mail flow, we can use transport rules to automatically copy or redirect these messages into a shared mailbox.

The workaround: exchange transport rules

With a mail flow rule, you can detect voicemail messages and send them to a shared mailbox. This provides a “shared voicemail inbox” experience, even though Teams itself doesn’t support it natively.

Step-by-Step: Routing voicemail to a shared mailbox

Step 1: Identify the voicemail recipient mailbox

First, determine which mailbox currently receives the voicemail. This might be:

• A user mailbox
• A M365 Group

Example:

• Reception_voicemail@company.com

This mailbox will continue receiving voicemail, but we’ll also deliver copies to a shared mailbox.

I typically have it go to an M365 group with one user and ensure the “Send copies of team emails and events to team members’ inboxes” is enabled in the settings of the M365 group.

Step 2: Confirm the shared mailbox

Make sure the shared mailbox already exists, such as:

• reception@company.com
• hr@company.com

Assign access permissions to the appropriate staff members so they can monitor and manage voicemails.

Step 3: Open the Exchange Admin Center

Go to:

Exchange Admin Center → Mail Flow → Rules

Then click:

+ Add a rule → Create a new rule

Step 4: Create the rule conditions

Give the rule a clear name, such as:

Teams Voicemail → Shared Mailbox

Under Apply this rule if…, choose conditions that match voicemail traffic. Common options include:

• The recipient is this person – then select the user in the M365 group
• The subject or body includes any of these words “Shared Voicemail (Name of call queue or auto attendant”

This prevents the rule from capturing unrelated Teams notifications.

Step 5: Choose the best action

Under Do the following…, select:

Recommended option: copy via BCC

Choose:

Add recipients → to the Bcc box…

Then select the shared mailbox:

• reception@company.com

This is usually best because:

• The original M365 group still receives voicemail
• The shared mailbox also gets a copy
• Nothing breaks Teams voicemail history

Step 6: Save and test

Save the rule, then leave a test voicemail for the Teams number.

Confirm that:

• The voicemail arrives in the M365 group
• The shared mailbox also receives it
• The audio attachment plays correctly
• Transcription appears if enabled

Important considerations

Before rolling this out broadly, keep these caveats in mind:

• This is not an official “shared voicemail” feature in Teams
• Microsoft may change voicemail email formatting over time
• Voicemail transcription may contain sensitive information
• Only authorized users should have shared mailbox access
• Transport rules should be tested carefully before production rollout
• This relies on the user’s account in the M365 group remaining active

Final thoughts

Microsoft Teams Phone continues to improve, but voicemail delivery remains a limitation for organizations that already rely on shared mailboxes.

Until Microsoft provides native support for shared mailbox voicemail, Exchange Online transport rules are one effective way to bridge the gap and support real-world call queue workflows.

If your organization is using Teams Phone and needs voicemail emails delivered to a shared mailbox, this workaround is worth considering.