> ## Documentation Index
> Fetch the complete documentation index at: https://onecli.sh/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Outlook Calendar Integration: Scheduling for Agents

> Let agents view, create, and manage calendar events in Microsoft 365. Works with shared calendars and room resources.

<Note>Outlook Calendar is available on the Cloud plan only.</Note>

## Overview

OneCLI connects AI agents to Outlook Calendar through Microsoft's OAuth flow. Agents can list events, create meetings, check availability, and manage RSVPs. The gateway injects OAuth credentials into requests to the Microsoft Graph API automatically.

This is useful for scheduling agents in Microsoft 365 environments that need to coordinate meetings, check availability, or manage calendars.

## Setup

<Steps>
  <Step title="Go to Connections">
    Open the OneCLI dashboard and navigate to **Connections** > **Outlook Calendar**.
  </Step>

  <Step title="Authorize">
    Click **Connect Outlook Calendar**. You'll be redirected to Microsoft to sign in and authorize OneCLI. Review the permissions and click **Accept**.
  </Step>
</Steps>

## What agents can do

* List events on your calendar within a date range
* Get details for a specific event (attendees, location, Teams link, body)
* Create new events with attendees, location, and online meeting settings
* Update existing events (reschedule, modify attendees, change details)
* Delete or cancel events
* Check free/busy availability for one or more users
* Respond to event invitations (accept, decline, tentative)
* List all calendars on the account
* Create and manage calendar groups
* Find meeting times that work for all attendees

## Controlling access

Access is per agent: [grant](/docs/guides/agent-access) the connection to each agent that needs it, choosing per tool what runs freely, what needs human approval, and what stays blocked — a read-only agent is a single grant. Organization [rules](/docs/guides/rules) add guardrails on top, like rate limits and blanket blocks. Everything is checked before credential injection, so a blocked request never reaches Microsoft Graph.