Yealink Forums

Full Version: Office 365 Calendar Issues - On-Premise S4B
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
We have on premise Skype for Business servers and Office 365 for calendaring and email. Everything is working great on the T48G except calendar (getting Disconnect exchange server) when I touch calendar on the phone.

I'm trying to figure out how the phone determines the calendar location (I don't see an EWS URL in the configuration from the website on the phone - i.e. I can't force the outlook.office365.com URL for calendar). I assumed it would have pulled it from the Skype client, or via autodiscover rules, but perhaps I'm wrong there.

I need to figure out how to tell the phone to look at Office 365 for Calendar, but on premise for the Skype configuration.

Thanks in advance
(10-04-2016 05:51 AM)cbartlow Wrote: [ -> ]We have on premise Skype for Business servers and Office 365 for calendaring and email. Everything is working great on the T48G except calendar (getting Disconnect exchange server) when I touch calendar on the phone.

I'm trying to figure out how the phone determines the calendar location (I don't see an EWS URL in the configuration from the website on the phone - i.e. I can't force the outlook.office365.com URL for calendar). I assumed it would have pulled it from the Skype client, or via autodiscover rules, but perhaps I'm wrong there.

I need to figure out how to tell the phone to look at Office 365 for Calendar, but on premise for the Skype configuration.

Thanks in advance

Hi , we have the same problem.
SfB on premise and exchange online. the calòendar is disconnected.
Do you have found any solutions?
Best Regards
I realize this thread is several years old, but I'm having the same issue today and wondering if it was ever overcome and what the fix was?

Thanks.
(02-26-2018 06:46 PM)Chuck2 Wrote: [ -> ]I realize this thread is several years old, but I'm having the same issue today and wondering if it was ever overcome and what the fix was?

Thanks.

We had this issue after a problem with auto-provisioning settings. validate your autoprovisioning is correct.
Reference URL's