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

# 故障排除

常见问题及其解决方法。

### 需要管理员批准 <a href="#oq9dbnq2cjs" id="oq9dbnq2cjs"></a>

测试日历集成配置时，用户可能会遇到 Microsoft 365 批准错误，提示该集成需要管理员批准。如果 Azure 与 Zoom Workplace 之间的用户许可权限不匹配，或者用户持有应用程序获批之前进行身份验证时留下的会话 Cookie，就可能出现此问题。

<figure><img src="https://2325962437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FctBXUMeBy4rtLMmMkKRG%2Fuploads%2Fgit-blob-a67a5ad465ee7215642a45fe2bb35585b68c5054%2F15.png?alt=media" alt=""><figcaption></figcaption></figure>

通过启动新的 **无痕浏览** **会议**来测试集成，然后重复个人日历和联系人的集成流程。如果成功，则故障是由先前的 Microsoft 365 会话 Cookie 导致的，并非配置错误。如果失败，请确认 Azure 与 Zoom Workplace 之间的权限设置是否一致。如果权限设置一致但错误仍然存在，则必须重新启动配置流程。

### 重新启动配置流程 <a href="#ju89iwsylwaz" id="ju89iwsylwaz"></a>

要重新启动 API 请求和批准流程，必须从 Azure 企业应用程序中移除 Zoom 应用。

1. 使用 Microsoft 365 管理员账户导航到 Azure 门户中的 [企业应用程序](https://portal.azure.com/#blade/Microsoft_AAD_IAM/StartboardApplicationsMenuBlade/AllApps/menuId/) 部分。
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/guan-li-yuan-zhuan-qu/third-party-integrations/microsoft-365-calendaring-field-guide/troubleshooting.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.
