This is one of those “why didn’t I think about that” types of things. As someone who works with many different companies (both as a partner or customer relationship), I get invited to lots of tenants to participate as a guest. One of the challenges of this, is that if someone from that organization tries to message me directly, many times it ends up going to the Guest account in their tenant instead of to my External account that I am in 99.999% of the time. This means I don’t see the message until I switch to that tenant or, if I’m lucky, I get the “Your colleague is trying to reach you in Teams” email. Here’s a great example of this:

This is a very quick, easy post. Recently, I received a Crestron Teams Panel (model TSS-1070-T-B-S-LB Kit). This device is for the outside of a room so your co-workers can see what the schedule is for the room. One of the very cool parts of the device is the light bar that goes with it. It allows you to see at a glimpse as you are walking down the hall whether the room is available or not.

Microsoft Teams Rooms - Cannot Fetch Calendar

Recently found myself having to troubleshoot an issue with a couple of Microsoft Teams Rooms (MTR’s) at a customer that said “Cannot Fetch Calendar”. I started to go through the basics and thought I should document them for others and then reveal what we found.

The basics:

1. Ensure that you created the Exchange account correctly - I always start with this page when creating new MTR accounts: [https://docs.microsoft.com/en-us/MicrosoftTeams/rooms/with-office-365] (https://docs.microsoft.com/en-us/MicrosoftTeams/rooms/with-office-365)
2. Verify your Autodiscover record - I tend to do something like this: Resolve-DnsName autodiscover.domain.com (Note: this needs to point to either Exchange Online or if on-prem, Exchange 2013 or higher)
3. If you only just created the account, wait a bit longer.
4. Use the Remote Connectivity Analyzer (RCA) - https://testconnectivity.microsoft.com/tests/exchange

In our case, we got to step 4. After running the RCA, we got the following message: