"状态代码:未找到；原因:未找到".在创建本地邮箱的订阅时 [英] "Status Code: NotFound; Reason: Not Found" when creating subscription to on-premise mailbox
问题描述
我们有混合Exchange部署.尝试创建订阅以获取更新，创建，删除日历和联系人.
We have a hybrid Exchange deployment. Trying to create a subscription to get updates, creates, deletes on Calendar and Contacts.
在Graph Explorer中，我以Office 365用户身份登录，该用户具有对我尝试访问的本地邮箱(user@domain.com)的完全访问权限.我输入:
In Graph Explorer I'm logged in as an Office 365 user that has full access to the On-Premise mailbox I'm trying to access (user@domain.com). I'm entering:
POST | v1.0 | https://graph.microsoft.com/v1.0/subscriptions
请求正文:
{
"changeType": "updated",
"notificationUrl": "https://our.URL/WebHooks/Graph/GraphMessagesHook.php",
"resource": "users/user@domain.com/contacts",
"expirationDateTime": "2018-10-23T04:00:00Z",
"clientState": "secret"
}
响应为:
{
"error": {
"code": "ExtensionError",
"message": "Operation: Create; Exception: [Status Code: NotFound; Reason: Not Found]",
"innerError": {
"request-id": "981c0892-e6d8-490b-838d-880d8268037f",
"date": "2018-10-20T20:32:07"
}
}
}
作为测试，我在Office 365中创建了另一个用户，并执行了相同的请求正文:
As a test, I created another user in Office 365 and did the same request body:
{
"changeType": "updated",
"notificationUrl": "https://our.URL/WebHooks/Graph/GraphMessagesHook.php",
"resource": "users/userOn365@domain.com/contacts",
"expirationDateTime": "2018-10-23T04:00:00Z",
"clientState": "secret"
}
这一次，我得到的是403:
{
"error": {
"code": "ExtensionError",
"message": "Operation: Create; Exception: [Status Code: Forbidden; Reason: Forbidden]",
"innerError": {
"request-id": "1f378cf0-b1ec-4b87-ba03-8dee120b748b",
"date": "2018-10-21T20:42:46"
}
}
}
我想念什么?
推荐答案
用于内部邮箱的Microsoft Graph API只是云功能的一部分.
The Microsoft Graph API for on premise mailboxes is only a subset of the cloud functionality.
不要以为他们实现了本地邮箱的订阅.双方都将耗费大量资源.
Don’t think they implemented subscriptions for on-premise mailboxes. That would be pretty resource intensive on both sides.
据我所知，他们只是将请求代理到本地Exchange(已配置为接受Azure令牌).对于轻松的通话，对于订阅，路由将很困难.
To my knowledge they just proxy the request to your local Exchange (which is configured to accept the Azure tokens). For rest calls that is easy, for subscriptions the routing would be difficult.
这篇关于"状态代码:未找到；原因:未找到".在创建本地邮箱的订阅时的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
