Forum Discussion
Skype for Business Server Side conversation history for Exchange Online users not working
Hello,
I am looking for help with not working Skype for Business Server Side conversation history for Exchange Online users.
Our environment:
- On-premises Skype for Business Server 2015 CU: June 2016
- Hybrid Exchange Server 2016/2010 CU3
Recently I’ve successfully configured OAuth, SSCH and OWA integration for on-prem Exchange and S4B.
OAuth and OWA integration between S4B on-prem and Exchange Online were also configured successfully. Unfortunately, SSCH does not work for some reason, and “Test-CsExStorageConnectivity” fails for Exchange Online users.
Analyzing autodiscover traces of “Test-CsExStorageConnectivity” shows:
- S4B is connecting to on-prem Exchange and is redirected to Exchange Online autodiscover:
2016/12/13 06:18:06.120 Autodiscover.EWSMA trace, type=AutodiscoverResponse, message=<Trace Tag="AutodiscoverResponse" Tid="133" Time="2016-12-13 06:18:06Z">Autodiscover service returned redirection email address 'onlineuser@company.mail.onmicrosoft.com'.</Trace>
- Then, it is redirected to another autodiscover address:
2016/12/13 06:18:06.498 Autodiscover.EWSMA trace, type=AutodiscoverConfiguration, message=<Trace Tag="AutodiscoverConfiguration" Tid="133" Time="2016-12-13 06:18:06Z">Trying to get Autodiscover redirection URL from http://autodiscover.company.mail.onmicrosoft.com/autodiscover/autodiscover.xml.</Trace>
2016/12/13 06:18:06.598 Autodiscover.EWSMA trace, type=AutodiscoverConfiguration, message=<Trace Tag="AutodiscoverConfiguration" Tid="133" Time="2016-12-13 06:18:06Z">Redirection URL found: 'https://autodiscover-s.outlook.com/autodiscover/autodiscover.xml'</Trace>
- And it fails some redirection Url validation:
2016/12/13 06:18:06.598 Autodiscover.Validate Redirection Url, redirectionUrl=https://autodiscover-s.outlook.com/autodiscover/autodiscover.xml, redirectAllowed=False, reason=no match
- After that, it starts autodiscover process two more times and finishes the same way.
Error in the “Test-CsExStorageConnectivity” is:
Test-CsExStorageConnectivity : ExCreateItem exchange operation failed, code=50043, reason=#CTX#{ctx:{traceId:18446744073545522150, activityId:"82a65a8b-629f-413c-be6b-16737f719a51"}}#CTX#Could not get the required ExchangeServiceBinding client, exception=System.ServiceModel.FaultException: #CTX#{ctx:{traceId:18446744073545522150, activityId:"82a65a8b-629f-413c-be6b-16737f719a51"}}#CTX#Could not get the required ExchangeServiceBinding clientAlso, in the Event Logs on the FrontEnd server events with ID 32054 are raised:
ExchangeAutodiscoverException: code=ErrorEwsAutodiscover, reason=GetUserSettings failed, smtpAddress=onlineuser@company.com, AutodiscoverUri=https://autodiscover.company.com/autodiscover/autodiscover.svc, Autodiscover WebProxy=<NULL> ---> Microsoft.Exchange.WebServices.Data.AutodiscoverLocalException: The Autodiscover service couldn't be located.
Any help in fixing this issue or additional investigation ideas are appreciated.
Thank you in advance.
Can you please post get-csoauthconfiguration and check if the autodiscoveruri for the cloud is used?
3 Replies
- EarlZirkleIron Contributor
Hi, I'm facing this same issue with mobile devices. On mobile devices that connect to on-premises Skype for Business and Exchange online they receive "conversation history can't be updated right now and might be out of sync". It looks like we need the Exchange autodiscover URL.
- ivanja
Microsoft
Can you please post get-csoauthconfiguration and check if the autodiscoveruri for the cloud is used?
- Святослав ТерлецькийCopper Contributor
Hello Ivan,
Thank you for your reply.
Changing "ExchangeAutodiscoverUrl" to "https://autodiscover-s.outlook.com/autodiscover/autodiscover.svc" solved the problem. But, as far as I remember from some documentation, "ExchangeAutodiscoverUrl" in the hybrid Exchange configuration should point to the on-prem exchange autodiscover.
As I understand, now every request for saving the conversation in the history is traveling over the Internet and for on-prem users is redirected back to the on-prem Exchange. Currently, most of our users are located on-prem, so I also want to try to set "ExchangeAutodiscoverUrl" to on-prem Exchange, and specify the "*.company.com","*.outlook.com","*.company.mail.onmicrosoft.com" in the "ExchangeAutodiscoverAllowedDomains" parameter.
Thank you for pointing me to the right direction.