> For the complete documentation index, see [llms.txt](https://library.zoom.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://library.zoom.com/admin-corner/third-party-integrations/zoom-calendaring-integration-explainer.md).

# Zoom Calendaring Integration Explainer

How Zoom's calendaring integration works, including supported providers and the authentication flow between Zoom and connected clients.

## Overview

The Zoom Calendaring Integration connects Zoom to third-party calendar providers, enabling users to view and manage calendar events directly in Zoom clients and room systems without switching between applications.

Zoom supports calendar integration with Microsoft 365, Microsoft Exchange Server, and Google Workspace. When calendar integration is active, Zoom's Web Calendaring Service handles authentication, token management, and event synchronization across all connected endpoints — including desktop and mobile apps, Zoom Rooms, and standards-based H.323/SIP room systems. Bi-Directional Calendar Sync, which is enabled by default, ensures that changes made in either Zoom or the connected calendar provider are reflected automatically across both.

This document explains how the calendaring integration works, describes the data flow and security model for each endpoint type, and provides configuration guidance for Microsoft and Google environments.

{% content-ref url="/pages/qdKhOsM8wxtiOuxTcXvH" %}
[Zoom Calendaring Overview](/admin-corner/third-party-integrations/zoom-calendaring-integration-explainer/zoom-calendaring-overview.md)
{% endcontent-ref %}

{% content-ref url="/pages/oi53FjTUwwGLv7WjCZhP" %}
[Zoom Calendaring Endpoints](/admin-corner/third-party-integrations/zoom-calendaring-integration-explainer/zoom-calendaring-endpoints.md)
{% endcontent-ref %}

{% content-ref url="/pages/BeyxuGQ2KKyK1BA9qKDB" %}
[Provider-Specific Details](/admin-corner/third-party-integrations/zoom-calendaring-integration-explainer/provider-specific-details.md)
{% endcontent-ref %}

{% content-ref url="/pages/rxLkT1OAWZYmMg25j6dw" %}
[Appendix](/admin-corner/third-party-integrations/zoom-calendaring-integration-explainer/appendix.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://library.zoom.com/admin-corner/third-party-integrations/zoom-calendaring-integration-explainer.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.