> 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/technical-library/zh-tw/guan-li-yuan-zhuan-qu/third-party-integrations/microsoft-365-calendaring-field-guide/introduction.md).

# 簡介

開始使用 Microsoft 365 行事曆與 Zoom

當將 Microsoft 365 行事曆與 Zoom 平台整合時，您的組織可透過 Zoom Workplace 應用程式、Zoom Rooms 或第三方會議室，提升會議與行事曆管理。請注意，Microsoft 365（前稱 Office 365）在 Zoom 平台內及部分其他支援文章中，仍稱為 Office 365。

對於 Zoom Rooms 與第三方會議室，使用者可以將會議排程到 Microsoft 365 會議室資源，從而在整個工作日內實現一鍵加入以及在會議室內自動同步的排程。

對於個人行事曆，使用者可透過 Zoom Workplace 應用程式中的「行事曆」分頁或側邊欄，以原生方式查看其 Microsoft 365 行事曆事件；而雙向行事曆同步等功能則可直接從 Zoom 網頁入口網站自動同步並排程會議到其 Outlook 行事曆，或反之亦然。

若要執行以下一項或多項設定流程，本指南的使用者將會使用下列權限、設定與系統，以啟用行事曆服務：

* Microsoft Entra ID（前稱 Azure Active Directory）使用者同意設定
* Microsoft Exchange Online
* Microsoft Graph API（MGAPI）
* Microsoft PowerShell
* Zoom 行事曆與聯絡人使用者同意設定
* Zoom 增強型 API 連接器


---

# 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/technical-library/zh-tw/guan-li-yuan-zhuan-qu/third-party-integrations/microsoft-365-calendaring-field-guide/introduction.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.