We were asked to investigate an issue for a client today where the Whiteboard app wasn’t available to Teams users in a Teams meeting.
Here are the key requirements for enabling Whiteboard:
- Enable Whiteboard for tenant
- License the users
- Enable the Teams Policy
- Apply the Teams Policy to users
Enabled Whitebard for the tenant. Head on over to the Office 365 Admin Centre. Click on Settings\Org settings\Services
Turn on Whiteboard for everyone in your org
License your users. It is bundled in with the licenses like E3 and E5 so you may or may not have to enable it. Probably not by now.
Head over to the Teams admin portal and go to: Meetings\Meeting Policies\Global and Allow whiteboard
Now, you think you would be good to go? Maybe… As you have enabled it in the “Global (Org-wide default)” you need to check that is the policy that is actually applied to your users. Probably like us you have never changed those, neither had our client. They were all in fact assigned the “RestrictedAnonymousAccess” policy.
This policy does NOT have Whiteboard enabled.
I haven’t looked too much into this, but i suspect this is to do with the cross-over from Skype for Business to Teams and perhaps was to do with the Coexistence policy at some point. In fact that Policy shouldn’t really be used. When you run this command in PowerShell you see this:
Get-CsTeamsMeetingPolicy -Identity “Tag:RestrictedAnonymousAccess” | FL Identity, Description
Identity : Tag:RestrictedAnonymousAccess
Description : Do not assign. This policy is same as global defaults and would be deprecated
If you look at your users:
Get-CsOnlineUser [UPN] | FL TeamsMeetingPolicy
You can see what policy they have assigned. Blank (or $NULL) means “Global (Org-wide default)”. If you see “RestrictedAnonymousAccess” then you should update it.
This is easy with: Get-CsOnlineUser [UPN] | Grant-CsTeamsMeetingPolicy -PolicyName $Null or via the GUI. You can in fact do it via bulk select:
Now what was interesting is that this question came to us pretty much the same that Microsoft sent out a “Message Center Major Change Update Notification” regarding csTeamsMeetingPolicy
csTeamsMeetingPolicy update to manage access to past meetings (MC211972)
We’re making some changes to settings within csTeamsMeetingPolicy.
Starting mid-June 2020, we’re changing the behavior of meeting policies which allows users to create and schedule meetings:
This change will impact all the users who are assigned any of the above policies with the value set to “False”.
After this change, the past meetings created/organized by the users impacted will be expired. That means, no one will be able to join the meetings.
Correcting the policy applied to users resolves this as well.
Connect to Skype for Business Online PowerShell
$sfbSession = New-CsOnlineSession