Our environment: SfB On Prem, Exchange Hybrid with Okta for MFA
Our issue: Our Trio 8800 systems are encountering an error where they are getting EWS deployed and can connect to SfB for calls and meetings but the calendaring service is showing up as "Not Available" and thus preventing them from being able to one touch into meetings from the device.
Phone Software Version: 5.9.1.10906
Phone Model: Trio 8800
Serial: 64167F4EC022
On rooms currently logged in there is no issue but if a room goes offline for maintenance or the Polycom is disconnected for some reason it can't reconnect to the calendaring service.
Hello @JGibbs19
Welcome to the Poly community.
Our records show that the unit 64167F4EC022 was sold by SCANSOURCE INC via CDW Logistics, Inc. back in 01/08/2018
Our Skype for Business FAQ has this post here:
Jan 17, 2017 Question: How can I troubleshoot simple Skype for Business, Office365 or Teams issues?
Resolution: Have a look => here <=
The above can be used to try and self diagnose the issue or post logs for other members to try and troubleshoot this for you.
If this fails please go ahead and open a support ticket.
In order to raise a support ticket, you need to work with your Poly reseller as they may need to do this for you.
End Customers are usually unable to open a ticket directly with Poly support. Available End User Poly services offerings are detailed here
If this is some sort of an Internet discounter providing your MAC address or your Poly devices serial will enable us to look up who would be able to support you. This may not be who you purchased the Poly device from.
If the unit is no longer within the warranty please be prepared to Pay Per Incident / PPI. This is all outlined in detail here
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Best Regards
Steffen Baier
If official support is required please check how to phone or open a case here
----------------Is MFA enabled in SfB as well? If not, you will need to disable MFA on the resource accounts the devices are using to sign in. The sign-in method used for SfB and Exchange must match.
Same issue here, did you ever get this fixed?