问题
I am attempting to create a call using Example 3 from the documentation. I consistently get the same HTTP 403
response.
- 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.
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"
}
}
}
回答1:
The examples in the documentation seem to be missing a required tenantId
property. Note that this property is mentioned in the documentation.
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": ""
}
Adding that tenantId
property seems to eliminate the error.
来源:https://stackoverflow.com/questions/60214894/error-7505-request-authorization-tenant-mismatch