Connect Microsoft Outlook Calendar to Codex
Give Codex 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 Codex in four steps
Admins approve the server once. Everyone in Codex 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 Codex to Runlayer
Runlayer’s CLI adds the Runlayer Plugin to Codex’s local plugin marketplace, and users then enable it in Codex. With direct tool listing turned on for your deployment, Microsoft Outlook Calendar’s 23 tools show up in Codex’s own tool list (Codex 0.122 or newer, installed through the Runlayer CLI).
Codex 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 Codex
Microsoft Outlook Calendar’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
23 Microsoft Outlook Calendar tools in Codex
Runlayer policy decides which of these Codex 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 Codex
Some controls apply to every client at the gateway. Others depend on what Codex exposes to Runlayer.
Gateway policy (available)
Every Microsoft Outlook Calendar call from Codex passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Codex 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 Codex runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before Codex’s model sees it.
Redact output in place (not available)
Codex cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.
Frequently asked questions
Connect more