Administrative Control Through New Setting in Teams Meeting Policy
Background blur for Teams meetings has been available since September 2018. Background effects, better known as the ability for users to choose blurring or background images to use during Teams meetings (Figure 1) appeared in early April. The availability of background effects created some issues for Office 365 tenants, such as making sure that people select appropriate images. Microsoft didn’t have an answer at the time, so they went with the solution of providing a set of curated images for people to choose from. However, it’s easy to upload custom images and use those images instead.
Policy Controls First Followed by Client Updates
In Office 365 notification MC212361, Microsoft explains how tenant administrators can control background effects on a per-user basis. Two changes are needed. First, a new setting (VideoFiltersMode) can be updated in Teams meeting policies to control which (if any) video effects are available to users. Policies can be updated now in preparation for a future update for the Teams client that will respect the setting. The client update is rolling out from mid-May to end-May using the standard client refresh mechanism. I tested using version 1.3.00.13515.
Updating the VideoFiltersMode Setting
The available values for the VideoFiltersMode setting are:
- NoFilters: No filters are available.
- BlurOnly: Background blur is available (but only if certain hardware conditions are met).
- BlurAndDefaultBackgrounds: Background blur and the set of curated background images selected by Microsoft can be used (essentially, what happens today).
- AllFilters: All filters are available, and the user can upload custom images. This is the default value for meeting policies.
Some will doubt the need to control how people use background effects and say that they trust people to do the right thing. The default value of AllFilters means that people can continue to use background images without any restriction. Others will welcome the opportunity to exert control. For example, these organizations can set VideoFiltersMode to BlurAndDefaultBackgrounds to allow users to use blur and effects but not be able to upload new images through the GUI. We don’t know yet if this option will stop custom images being picked up if they are distributed to client workstations via group policy or other mechanisms. Figure 2 shows what happens when the meeting policy applied to an account only allows background blur to be chosen.
Teams meeting policies are usually updated through the Teams admin center. In this case, the GUI to manipulate the VideoFiltersMode control is not yet available in the Teams admin center, so you must set the value with PowerShell. Like all Teams policies, the PowerShell cmdlets to manipulate meeting policies are available in the Skype for Business Online module.
Updating Teams Meeting Policies with PowerShell
After connecting to the Skype for Business Online endpoint, to list the existing policies and the assigned value for VideoFiltersMode, run the Get-CsTeamsMeetingPolicy cmdlet:
Get-CsTeamsMeetingPolicy | Format-Table Identity, VideoFiltersMode Identity VideoFiltersMode -------- ---------------- Global AllFilters Tag:RestrictedFunctionality NoFilters Tag:Allow Meeting Recording AllFilters
To update a policy, run the Set-CsTeamsMeetingPolicy cmdlet:
Set-CsTeamsMeetingPolicy -Identity RestrictedFunctionality -VideoFiltersMode NoFilters
Once the meeting policy is updated, it can be assigned to users as normal through the Teams Admin Center (Figure 3). It can take up to 24 hours before a change made to a policy is picked up and applied by clients.
Things keep on changing. Stay on top of change by subscribing to the Office 365 for IT Pros eBook and receive monthly updates with new information integrated and outdated content removed.