> 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/troubleshooting.md).
# 疑難排解
常見問題及其解決方式。
### 需要管理員核准
在測試行事曆整合設定時，使用者可能會遇到 Microsoft 365 核准錯誤，指出此整合需要管理員核准。若 Azure 與 Zoom Workplace 之間的使用者同意權限不一致，或使用者在應用程式獲得核准前，曾有來自先前驗證的工作階段 Cookie，就可能發生此情況。
透過啟動新的 **私人瀏覽** **工作階段**，並重複個人行事曆與聯絡人整合流程。若成功，則失敗原因是先前的 Microsoft 365 工作階段 Cookie，且沒有設定錯誤。若失敗，請確認 Azure 與 Zoom Workplace 之間的權限設定是否一致。若權限設定一致且錯誤仍然存在，則必須重新啟動設定程序。
### 重新啟動設定程序
重新啟動 API 請求和核准程序需要從 Azure 企業應用程式中移除 Zoom 應用程式。
1. 使用 Microsoft 365 系統管理員帳戶前往 [企業應用程式](https://portal.azure.com/#blade/Microsoft_AAD_IAM/StartboardApplicationsMenuBlade/AllApps/menuId/) Azure 入口網站中的區段。
2. 根據您的 MGAPI 設定方法，找出以下應用程式 ID：
1. *f46ceaed-fb2d-4694-803b-6341837f0ed2* （應用程式權限、個人行事曆）
2. *f56e91e5-5a82-452f-b435-d4d78aeaf064* （應用程式權限、Zoom Rooms）
3. *fc108d3f-543d-4374-bbff-c7c51f651fe5* （OAuth 委派存取、個人行事曆）
4. *a651cfda-cbdd-4a39-bd03-fa829c3c1b29* （完整委派存取、Zoom Rooms）
3. 開啟應用程式並選取 **屬性**.
4. **刪除** 這些應用程式。
5. 開啟新的私人瀏覽工作階段，並從本文開頭開始重新設定整合。
如果在重新設定應用程式後錯誤仍然存在，請聯絡 Zoom 支援以取得進一步協助。
---
# 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/troubleshooting.md?ask=&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.
