Copilot Studio Outlook Connector: Read, Draft, and Review

The Outlook connector in Microsoft Copilot Studio gives an agent access to a mailbox for reading messages, drafting replies, and sending within the permissions you configure. It is one of the most commonly used connectors in business agent workflows because email remains central to how organizations communicate. Tools like fenbs can keep the agreed follow-up tasks and approved procedures from a Copilot Studio workflow available to other assistants, without copying private message content.

Before using the connector in production, understand exactly what mailbox access the agent will have and build a review step into every workflow that involves sending.

What the Outlook connector can do

Through the Copilot Studio Outlook connector, an agent can: read emails from a specified mailbox or folder, search for messages by sender, subject, or date, draft a new message or a reply, move messages to folders, and send messages on behalf of an authorized account.

The connector uses the Microsoft Graph API under the hood, which means the permissions it requests are standard Microsoft 365 permissions. The user or service account that authorizes the connector determines what the agent can see and do.

Configuring mailbox permissions

Copilot Studio agents authenticate with Microsoft 365 using either end-user authentication (the agent acts as the signed-in user) or service principal authentication (the agent uses an app registration with delegated or application permissions). The right choice depends on whether the agent should access each user's own mailbox or a shared mailbox.

For a shared inbox workflow, a service principal with Mail.Read and Mail.Send on the shared mailbox is a clean setup. For a personal assistant that reads a user's inbox, end-user authentication with delegated permissions keeps the agent scoped to that user's data.

Microsoft's Microsoft Graph permissions reference documents the exact scopes available. Review them before choosing delegated versus application permissions, as application permissions give broader access and require more careful scoping.

Building a review step before sending

A Copilot Studio agent that drafts and sends email without a human review step can send the wrong message, to the wrong recipient, at the wrong time. This is a genuinely serious risk for business communications.

Build an approval or review step into every workflow that sends email. In Copilot Studio, this typically means the agent drafts the message and surfaces it for human approval before calling the Send action. An adaptive card in Teams or a Power Automate approval flow are common ways to implement this.

Do not skip the review step to speed up the workflow. The cost of a sent mistake is higher than the cost of an extra approval click.

Common connector errors and how to fix them

Authorization failures are the most common issue. If the connector returns a 401 or 403 error, the service account or delegated permission is not set up correctly. Check the app registration in Azure Active Directory and verify that the required Graph permissions have been granted and, for application permissions, that an administrator has consented to them.

Shared mailbox access often requires an additional step: the service account must be granted "Full Access" to the shared mailbox in Exchange Admin Center in addition to the Graph API permissions. Missing this step is a frequent cause of failures on shared mailbox workflows.

For broader Copilot Studio setup, see the Copilot Studio overview. For comparison with other connectors on the same platform, see Copilot Studio SQL Server connector.

Privacy and data handling

Email inboxes contain sensitive personal and business information. When you grant an agent access to a mailbox, review exactly which folders it can see, whether it logs message content, and whether the Copilot Studio environment stores conversation history that includes email data.

Check your organization's data handling policies before deploying an Outlook connector to production. In regulated industries, email data may be subject to retention and access requirements that affect how an AI agent can use it.

Scoping the agent to a specific mailbox or folder

Rather than giving a Copilot Studio agent access to an entire inbox, scope it to the folder or label where the relevant messages arrive. If the agent handles customer support requests, connect it to the support inbox or the folder where those messages are filtered. That scope limits what the agent can read and reduces the risk of it processing unrelated messages.

Folder-based scoping is also easier to audit. When you review what the agent has processed, a single folder is faster to check than a full inbox with years of unrelated messages.

How to do this with fenbs

1. Create a free account at fenbs. Add a project for the email workflow the Copilot Studio agent handles.
2. Write the rules for the workflow as Decisions and rules: which mailbox the agent accesses, what it may send without review, and who approves edge cases.
3. Add action items that the agent surfaces from email processing as fenbs tasks, with the recipient, the deadline, and the agreed next step.
4. Connect another assistant over MCP from Integrations to read the project context and action items. That assistant sees the same agreed rules and next steps without needing Outlook access.
5. Save Where we left off after each processing batch so the next run starts from the correct state.

fenbs does not connect to Outlook or Microsoft 365. It holds the process rules and follow-up tasks that result from email workflows so they are available to your whole team and any connected assistant.