错误7505-请求授权租户不匹配 [英] Error 7505 - Request Authorization Tenant Mismatch

问题描述

我正在尝试使用E 文档.我始终得到相同的HTTP 403响应.

I am attempting to create a call using Example 3 from the documentation. I consistently get the same HTTP 403 response.

• 我的数据通过Azure Portal Office Developer帐户托管.
• 发送通过
• 该漫游器是使用Office 365开发人员帐户在Azure AD中定义的.
• 收件人是免费AD部署中的两个用户，并且安装了16个用户包以进行测试.

• My data is hosted via an Azure Portal Office Developer account.
• Sending a bearer token obtained through the process described as "Get access without a user."
• The bot is defined in Azure AD using an Office 365 developer account.
• The recipients are two of the users from that free AD deployment and the 16-user pack installed for testing.

在HTTP 403响应的正文中，我得到:

In the body of the HTTP 403 response, I get:

{
  "error": {
    "code": "7505",
    "message": "Request authorization tenant mismatch.",
    "innerError": {
      "request-id": "foo",
      "date": "2020-02-13T17:30:24"
    }
  }
}

推荐答案

文档中的示例似乎缺少必需的tenantId属性.请注意，在文档中提到了此属性.

The examples in the documentation seem to be missing a required tenantId property. Note that this property is mentioned in the documentation.

必须使用实际值替换授权令牌，回调URL，应用程序ID，应用程序名称，用户ID，用户名和租户ID 的值，才能使示例工作.

The values of authorization token, callback URL, application ID, application name, user ID, user name, and tenant ID must be replaced with actual values to make the example work.

The Example 3 from the Beta documentation, however, does seem to include this property in the request:

{
  "@odata.type": "#microsoft.graph.call",
  "direction": "",
  "subject": "",
  "callbackUri": ",
  "source": {...},
  "targets": [...],
  "requestedModalities": [...],
  "mediaConfig": {...},
  "tenantId": ""
}

添加tenantId属性似乎可以消除该错误.

Adding that tenantId property seems to eliminate the error.

这篇关于错误7505-请求授权租户不匹配的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！