Questions about OAuth authentication between local Exchange 2013 and exchange Online organizations

Recently done a project about the local exchange2013 and the century connected Office 365 Exchange Online Hybrid deployment, we will now share the problems encountered in this project and hope to help you

Environment Description:

Locally built 4 Exchange CU14 messaging Systems (2 CAs, 2 mbx)

Office 365 is using the century-connected version of Office 365 E3

Problem Description:

No errors were reported after the configuration of the Hybrid wizard, and when tested with the command, it was successful to test the OAuth validation from the local exchange2013, such as:

Test-oauthconnectivity-service Ews-targeturi Https://partner.outlook.cn/ews/exchange.asmx-Mailbox < On-premises Mailbox>-verbose | Fl

650) this.width=650; "height=" "title=" image "style=" border:0px;padding-top:0px;padding-right:0px;padding-left:0 Px;background-image:none; "alt=" image "src=" http://s3.51cto.com/wyfs02/M00/8B/AE/wKiom1hU2wWD1PCMAAA__ F-bzyi330.png "border=" 0 "/>

However, when testing from Exchange online, an error occurred (500 internal server errors), such as:

Test-oauthconnectivity-service Ews-targeturi <external hostname authority of your Exchange on-premises deploymen T>/metadata/json/1-mailbox <Exchange Online Mailbox>-verbose | Fl

650) this.width=650; "height=" 182 "title=" image "style=" Border:0px;padding-top:0px;padding-right:0px;padding-left : 0px;background-image:none; "alt=" image "src=" http://s3.51cto.com/wyfs02/M00/8B/AB/ Wkiol1hu2wbccggvaadxo8celdm493.png "border=" 0 "/>

The result of this issue is that users of Exchange online cannot view the free and busy information for local Exchange2013 mailbox users, but local is able to view the free and busy information of Exchange online users normally.

Workaround:

I tried to configure OAuth authentication manually, but the results were the same for this issue.

Microsoft's technology was later known to Microsoft products that this issue was caused by 1 Exchange2013 CU14 bugs, and Microsoft currently has no instructions for this bug.

There are 2 ways to solve this problem:

1. Re-build 1 Exchange2013 CU11 full roles and Exchange online for hybrid deployments

2. Wait for Exchange CU15 Update (released on 12.12th)

I resolved the issue by using the 2nd method of updating the local Exchange CU14 to CU15.

This article is from "Jianbin Liu's Blog" blog, please be sure to keep this source http://liujb.blog.51cto.com/269257/1883579

Questions about OAuth authentication between local Exchange 2013 and exchange Online organizations