Connect Microsoft Outlook to GitHub Copilot CLI
Give GitHub Copilot CLI governed access to Microsoft Outlook’s 37 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Microsoft Outlook to GitHub Copilot CLI in four steps
Admins approve the server once. Everyone in GitHub Copilot CLI then gets it through the same governed connection.
- 1
Approve Microsoft Outlook in Runlayer
Add Microsoft Outlook from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect GitHub Copilot CLI to Runlayer
Users add the Runlayer Plugin to GitHub Copilot CLI by following Runlayer’s setup guide. GitHub Copilot CLI reaches Microsoft Outlook’s 37 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
GitHub Copilot CLI setup guide - 3
Sign in to Microsoft Outlook
Sign in the way Microsoft Outlook requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Microsoft Outlook from GitHub Copilot CLI
Microsoft Outlook’s approved tools appear in GitHub Copilot CLI. Every call is checked against policy and recorded.
Tools
37 Microsoft Outlook tools in GitHub Copilot CLI
Runlayer policy decides which of these GitHub Copilot CLI users can call. 6 read data only and 2 can change or delete data.
Create draft
Create a new Outlook draft message in the Drafts folder without sending it.
Create reply draft
Create an editable Reply or Reply-All draft attached to an existing Outlook thread.
Delete attachment
Delete an attachment from an Outlook message or draft.
Delete message
Delete a message from an Outlook mailbox.
Download attachment
Download the content of a specific attachment from an Outlook message.
Forward message
Forward an existing Outlook message to one or more recipients.
Get attachments
List all attachments on an Outlook message, returning metadata but not file content.
Get message
Fetch the full content of a single Outlook message by id, headers and body included.
Control
What Runlayer can see and stop in GitHub Copilot CLI
Some controls apply to every client at the gateway. Others depend on what GitHub Copilot CLI exposes to Runlayer.
Gateway policy (available)
Every Microsoft Outlook call from GitHub Copilot CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, GitHub Copilot CLI as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Stop a call before it runs (available)
Runlayer can deny a tool call or permission request before GitHub Copilot CLI runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before GitHub Copilot CLI’s model sees it.
Redact output in place (available)
Runlayer can mask sensitive parts of a successful tool’s output in GitHub Copilot CLI and pass the rest through.
In GitHub Copilot CLI
- When a tool fails, Runlayer records the error but cannot replace it.
Frequently asked questions
Connect more
