Forum Discussion
Scheduled meetings on Surface Hub (1703 Creators Update)
MicrosoftHello rohgin,
The video issue definitely needs to be investigated, I suggest opening a ticket with the Teams team (you can do it from the Office 365 portal).
The join button issue for forwarded meetings might be due to Windows Defender Safe Links. The Surface Hub will scan meeting invites for the Teams URL so if that is hidden, it won't show the meeting join button. Can you check how these look on the device account calendar? You can use OWA to check it.
I strongly encourage you to open a support ticket so we can resolve the issues and be happy with your Surface Hub 
Thank you,
Cezar
I just tested the forwarding, it actually works when I send a meeting request from my on-premise user to one of our 365 accounts, next I forwarded the meeting request to the Surface Hub from the 365 user, and now it's actually showing the "Join" button.
But a friend of mine from a different organisation did send me an invite, and the original invite didn't have a join button, neither on the surface hub or my personal account where he did send the invitation to, so it's already missing on the original invitation. I was able to use the "Join Meeting" link in the body of the calendar item, but since the surface hub isn't able to open the actual item, It's depending on the join button. Most external invitations we receive do have the Join button, but it seems that sometimes from some companies it doesn't. So normally it doesn't matter when I'm able to use the link, but since the Surface Hub is depending on the button, I can't trust to tell my users to use this method while sometimes the button is not visible on the invitation. That's just not a workable solution.
So currently I'm testing it, the guy from Microsoft did send me an invite and the join button was visible, it seems it has something to do with the time settings. so probably when the join button isn't available, it's because the person who made the invitation, didn't have the correct time settings.
Update, that wasn't the problem, I'm thinking it has something to do with OAUTH not implemented, they have a hybrid environment, I think they haven't configured OAUTH, since he told me they didn't have the calendar button on Teams yet.
- cezarcretu
Hello rohgin,
Ok, I understand. The solution to invite the external companies is a good workaround for now.
This is currently being investigated and I hope to have a definitive solution soon
Thank you,
Cezar
Hi Cezar,
It has nothing to do with the Hub on itself.
So company X did send me an invitation
The result:
The join button wasn't available in Teams web or desktop client, or Outlook desktop or webclient in the first place on my computer without forwarding it whatsoever.
So I've tested it with Microsoft sending me an invitation, and when they did it, the Join button was
available.
So, they came to the conclusion that the problem is happening on the side of the company which is inviting me.
It's only been a handful of external companies where the join button wasn't included in the invitation.
And the problem here is that the Hub needs the join button to enter the meeting. So this makes it impossible to guarantee that forwarding will always work.
And logging in on the Surface hub and showing the meetings I've got is only available for mailboxes in the cloud. Since this is currently not an option, I want to use methods like forwarding, or directly inviting the hub. So right now we instruct our users to always invite the external companies from our side, this way we'll be a 100% sure that the hub will work.
- cezarcretu
Hello rohgin,
The meeting URL shouldn't change based on the OAUTH settings of the inviter. As I said, the Surface Hub will scan all incoming meetings and if it finds a Teams URL it will show the Join button.
Current investigations show that the issue might be with the Outlook client when forwarding external meetings to the Surface Hub. Can you try to forward the same meeting using OWA instead?
Or better yet, login with your credential in "My meetings and files" and try to join the call from there instead (no forward to the Hub)
Thank you,
Cezar