Need help connecting Copilot Studio agent to a shared mailbox

(1) Share

Report

Posted on by MU-26031012-0

Hi everyone,

I’m currently trying to build a Copilot Studio agent that manages emails.

I successfully configured all the necessary connections, and the agent works very well with my personal mailbox:

when I receive an email, it automatically suggests a draft reply,
I can choose to send the draft,
I can ask for my latest emails,
and perform several other actions on my mailbox.

However, I’m also part of a shared mailbox, and this is where I’m blocked.

At the moment, my agent:

cannot read incoming messages from the shared mailbox,
cannot perform actions on it,
and the only thing I seem able to do is send emails as the shared mailbox.

My actual goal is for the agent to manage ONLY the shared mailbox, not my personal mailbox.

I’ve been searching for an existing Copilot Studio → shared mailbox connection, but I can’t find any solution.

Does anyone know of a workaround or an approach that could help?
Maybe something involving Power Automate?

Any advice or feedback would be greatly appreciated.

Thanks!

Categories:

Calling actions from Copilot Studio

I have the same question (0)

All responses (4)

Answers (1)

Sort by

Verified answer

11manish 2,286 on at

Like (1)

Report
Copy link

Link copied!
Yes — using Power Automate is currently the best and most practical workaround.

Copilot Studio native mailbox capabilities primarily operate in the authenticated user’s mailbox context and do not fully support shared mailbox management scenarios.

The recommended enterprise approach is:

Copilot Studio

→ Power Automate flows

→ Shared mailbox actions / Microsoft Graph

This allows your agent to:

read shared mailbox emails

generate drafts

send replies as the shared mailbox

move/manage emails

avoid interacting with the personal mailbox entirely

For long-term scalability and flexibility, Microsoft Graph-based APIs are even better than standard Outlook connector actions.

Was this reply helpful? Yes No
Suggested answer

Valantis 5,130 on at

Like (1)

Report
Copy link

Link copied!

Hi @MU-26031012-0,

Microsoft is expanding Copilot Chat in Outlook to support shared and delegated mailboxes across new Outlook versions starting early April 2026.

Users with Microsoft 365 Copilot licenses can use Copilot features directly in these mailboxes, improving team collaboration without extra setup or mailbox-specific prompts.

GA is expected for early june 2026

more info in to the graphic in the post: https://www.linkedin.com/posts/valantis-avramopoulos-046972172_microsoft-is-expanding-copilot-chat-in-outlook-share-7457026437766705152-GTfv?utm_source=share&utm_medium=member_desktop&rcm=ACoAACkT0LYBS2nTGaSoi4pSPowswHlg4C3iS4A

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No
Suggested answer

AP-26031104-0 Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!
just adding one practical point that addresses your specific goal of managing only the shared mailbox (not your personal one):

In your Copilot Studio agent, make sure all topic flows go through your Power Automate flows exclusively, and never use the built-in "Send a message" or native email actions in the agent designer — those will always default to your personal mailbox.

A clean setup looks like this:

All email intents (read / reply / manage) → Call a Power Automate flow → flow targets shared mailbox via "Mailbox Address" field or Graph API

This way your personal mailbox is never touched at all.

Quick recap of the full solution:

Short-term: Power Automate flows with Office 365 Outlook connector ("Mailbox Address" field)

Long-term: Microsoft Graph API for more flexibility

Future: Native shared mailbox support in Copilot Chat in Outlook expected GA June 2026

Hope that completes the picture!

Was this reply helpful? Yes No
Suggested answer

Haque 2,952 on at

Like (2)

Report
Copy link

Link copied!

Here are the key points need to address:

(1) Shared Mailbox Access via Power Automate / Connectors:
The standard "Get Emails (V3)" connector and many Outlook connectors by default operate on the signed-in user's primary mailbox. To access a shared mailbox, you typically need to specify the shared mailbox address explicitly in the connector's parameters (e.g., the "MailFolder" or "User" field).

(2) Delegated Permissions: Your user account must have Full Access permission to the shared mailbox in Exchange Online. This permission is granted by your Exchange or Microsoft 365 admin.

(3) Using the Shared Mailbox in Power Automate: When configuring the "Get Emails (V3)" or similar actions, you can specify the shared mailbox email address in the "Original Mailbox Address" or "User" field to target that mailbox instead of your personal mailbox.

(4) In Copilot Studio: Currently, there is no out-of-the-box "shared mailbox" connector separate from the personal mailbox connectors. You must configure your Power Automate flows or custom connectors to explicitly target the shared mailbox by passing its address.

(5) Sending Emails as Shared Mailbox: You mentioned you can send emails as the shared mailbox—this is because "Send As" permission is often easier to grant and use than full mailbox access.

(6) Custom Connector or API Approach: If the built-in connectors don’t fully support your scenario, consider building a custom connector or using Microsoft Graph API calls with delegated permissions to access and manage the shared mailbox.

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No