Just finished setup of a new Teams Room using the Logitech Large Room system for teams (kit with Rally camera, TAP touch display and prebuilt PC). I followed exclusively the Microsoft deployment directions for office365 online only (no on premise or hybrid exchange).
Meetings, calls, sharing ect all is working....with one exception. On the TAP display (connected to the teams room computer) it displays a cannot fetch calendar error after it logs into the team room account. However I do know the calendar works because if I sign into desktop teams on my own computer using the meeting room credentials it all work, I can see the room calendar entries ect. In addition it is auto accepting invites sent to it from organization users and I can see the room calendar in my outlook along with busy times ect. It simply cannot fetch calendar when logged in on the meeting room PC.
@cbotI have the same 'Cannot Fetch Calendar' error. First some history....I was part of the SrSv2 TAP and early on with Skype and Exchange on-prem...I also had the same calendar fetch issue. It turned out back then that MSFT assumed that the SIP and UPN was the same but in our environment it isnt. Now fast fwd to the most recent calendar fetch issue. This issue reappeared after migrating the resource mbx to O365.
So Im curious...does your SIP and UPN for the user account match?
So as it turns out our problem was autodiscovery wasn't working. We had recently migrated our DNS management to s new service and actually all of the required DNS records for Office365 were missing other than the MX records. After we setup the DNS records (which include autodiscovery service) the calendar started working working as expected.
I just set up our first Logitech Smart Dock Teams console and I followed the account creation instructions and everything is working except I too am getting the Cannot fetch calendar error. I have nothing on premises. Everything is in the cloud. How did you know it was a auto discover issue? If I do a nslookup on the console for the auto discover record for my domain it seems to resolve it just fine. I have noticed that it seems to return the ipv6 address first before the ipv4 is address, do you think this is a problem? Really frustrating.