MailboxNotEnabledForRESTAPI - Microsoft Graph API 与启用 HMA 的本地服务器集成 [英] MailboxNotEnabledForRESTAPI - Microsoft Graph API integration with HMA Enabled on-premise server

查看:92
本文介绍了MailboxNotEnabledForRESTAPI - Microsoft Graph API 与启用 HMA 的本地服务器集成的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们已将我们的应用程序与 Microsoft Graph API 集成,使用户能够通过我们的应用程序访问他们的前景.集成对 office365 用户运行良好,但在本地服务器中的用户遇到间歇性问题.

最初在本地服务器中启用 HMA 后,集成开始工作,但在过去的两周里,我们遇到了集成问题并收到如下错误消息.

HTTP 错误:404错误代码:MailboxNotEnabledForRESTAPI 或 MailboxNotSupportedForRESTAPI错误消息:此邮箱尚不支持 REST API."

但我们最近没有对服务器或图形 API 访问进行任何更改.令人惊讶的是,它今天开始工作,因为这是我们在理解问题时需要帮助的零星.非常感谢任何帮助.

更新:我们今天早些时候又开始看到错误,我们捕获了以下日志信息.

<代码>{错误":{代码":ResourceNotFound",消息":无法发现资源.",内部错误":{日期":2020-10-30T08:03:20",请求 ID":c1f461d7-0757-4a54-a727-58cb0da7fe5d",客户端请求 ID":c1f461d7-0757-4a54-a727-58cb0da7fe5d"}}}

解决方案

这篇文章不是答案:-(,但应该提供更多细节,因为我们遇到了同样的问题.

为了隔离问题,我们只使用了邮递员.我们无法创建工作令牌";与邮递员.我们尝试了所有可能的 O-Auth 流程:-).当我们使用由

We had integrated our application with Microsoft Graph API enabling user to access their outlook through our application. The integration works fine with office365 users but having intermittent issues with users in on-premise server.

Initially after enabling HMA in on-premise server the integration started working, but for past two weeks we are facing issue with the integration and receiving error message as below.

HTTP error: 404
Error code: MailboxNotEnabledForRESTAPI or MailboxNotSupportedForRESTAPI
Error message: "REST API is not yet supported for this mailbox."

But we had not made any recent changes to server or Graph API access. Surprisingly, it started to working today as this was sporadic we need assistance in understanding the issue. Any help is greatly appreciated.

Update: We started seeing the error again early today and we have captured the following log information.

{
    "error": {
    "code": "ResourceNotFound",
    "message": "Resource could not be discovered.",
    "innerError": {
      "date": "2020-10-30T08:03:20",
      "request-id": "c1f461d7-0757-4a54-a727-58cb0da7fe5d",
      "client-request-id": "c1f461d7-0757-4a54-a727-58cb0da7fe5d"
    }
  }
}

解决方案

This post is not an answer :-(, but should provide more details because we are running into the same issue.

To isolate the problem, we only using postman. We are not able to create a "working token" with postman. We tried like every possible O-Auth flow :-). When we use the token generated by "Graph Playground" requests are working.

What means "working token":

Request to: https://graph.microsoft.com/v1.0/me -> GP works | PM works

Request to: https://graph.microsoft.com/v1.0/me/calendar -> GP works | PM don't work

Request to: https://graph.microsoft.com/v1.0/me/contacts > GP works | PM don't work

.....

(GP = Graph Playground // PM = Postman)

Token

On the left side we see the token created via postman. On the right side we see the token from Graph online. I can't find an important difference, you can ? :-)

这篇关于MailboxNotEnabledForRESTAPI - Microsoft Graph API 与启用 HMA 的本地服务器集成的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆