Connect Microsoft Outlook Calendar to GitHub Copilot CLI
Give GitHub Copilot CLI governed access to Microsoft Outlook Calendar’s 23 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Microsoft Outlook Calendar 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 Calendar in Runlayer
Add Microsoft Outlook Calendar 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 Calendar’s 23 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 Calendar
Sign in the way Microsoft Outlook Calendar requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Microsoft Outlook Calendar from GitHub Copilot CLI
Microsoft Outlook Calendar’s approved tools appear in GitHub Copilot CLI. Every call is checked against policy and recorded.
Tools
23 Microsoft Outlook Calendar tools in GitHub Copilot CLI
Runlayer policy decides which of these GitHub Copilot CLI users can call. 5 read data only and 2 can change or delete data.
Calendar accept event
Accept an event invitation on the signed-in user's calendar.
Calendar cancel event
Cancel an event the signed-in user organized and notify the attendees.
Calendar create event
Create a new event on the signed-in user's primary calendar.
Calendar decline event
Decline an event invitation on the signed-in user's calendar.
Calendar delete event
Delete an event from the signed-in user's calendar.
Calendar find meeting times
Suggest meeting times based on attendee availability.
Calendar get event
Fetch a single calendar event by id.
Calendar get schedule
Fetch free/busy information for one or more users, distribution lists, or resources (rooms/equipment).
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 Calendar 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