Skip to main content
Book a demo

Connect Microsoft Outlook Calendar to VS Code

Give VS Code governed access to Microsoft Outlook Calendar’s 23 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo VS Code setup guide

Set up

Add Microsoft Outlook Calendar to VS Code in four steps

Admins approve the server once. Everyone in VS Code then gets it through the same governed connection.

  1. 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. 2

    Connect VS Code to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in VS Code; users can also add it over MCP. With direct tool listing turned on for your deployment, Microsoft Outlook Calendar’s 23 tools show up in VS Code’s own tool list (VS Code 1.103 or newer).

    VS Code setup guide
  3. 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. 4

    Use Microsoft Outlook Calendar from VS Code

    Microsoft Outlook Calendar’s approved tools appear in VS Code. Every call is checked against policy and recorded.

Tools

23 Microsoft Outlook Calendar tools in VS Code

Runlayer policy decides which of these VS Code 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).

See all 23 Microsoft Outlook Calendar tools

Control

What Runlayer can see and stop in VS Code

Some controls apply to every client at the gateway. Others depend on what VS Code exposes to Runlayer.

  • Gateway policy (available)

    Every Microsoft Outlook Calendar call from VS Code passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, VS Code 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 before VS Code runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before VS Code’s model sees it.

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a tool’s output in VS Code and pass the rest through.

Frequently asked questions

Connect more

Find another combination