Microsoft - MS-700: Managing Microsoft Teams

Sample Questions

Explanation:

If you have Microsoft Teams Rooms device or a Surface Hub in your organization, you have flexible management options. You can manage the devices yourself in the same central location where you manage all your Teams solutions, Microsoft Teams admin center or in Teams Rooms Pro Management.

With Microsoft Teams admin center, you can:

• Perform device management like restarting devices and downloading device logs
• Apply Teams-specific settings
• Check the health status of Microsoft Teams Rooms and their peripherals, including cameras, displays, microphones, and so on
• Review current and past meeting activity (such as details about call quality, network health and connectivity, and number of participants)
• See peripherals (such as cameras and projectors) connected to Microsoft Teams Rooms (only for Teams Rooms on Windows)

To manage Teams Rooms devices remotely, a Teams Rooms Pro license is required.

References:

Manage Microsoft Teams Rooms and Surface Hubs

Microsoft Teams Rooms licenses

Explanation:

To control which users can see the Use new Teams client toggle, use the Teams admin setting UseNewTeamsClient under the TeamsUpdateManagement policy. Manage this setting in the Teams Admin Center or using Teams PowerShell.

The New-CsTeamsUpdateManagementPolicy cmdlet creates a new Update policy. Configure the UseNewTeamsClient setting to one of the following possible values:

• MicrosoftChoice (default setting) This value lets Microsoft control if the Teams (preview) toggle switch is shown based on product readiness.
• User choice This value lets the new Teams toggle switch display to all users. Users can choose to opt in or out.
• AdminDisabled This value hides the new Teams toggle switch from view. Users won't be able to opt in to the new Teams.

The Grant-CsTeamsUpdateManagementPolicy cmdlet is used to assign the policy to User1.

Reference: Upgrade to the new Teams using policies

Explanation:

Microsoft Teams on Azure Virtual Desktop supports chat and collaboration. With media optimizations, it also supports calling and meeting functionality by redirecting it to the local device when using Windows App or the Remote Desktop client on a supported platform. You can still use Microsoft Teams on Azure Virtual Desktop on other platforms without optimized calling and meetings. Teams chat and collaboration features are supported on all platforms.

There are two versions of Teams, Classic Teams and New Teams, and you can use either with Azure Virtual Desktop. New Teams has with feature parity with Classic Teams, but improves performance, reliability, and security.

To redirect calling and meeting functionality to the local device, Azure Virtual Desktop uses an extra component. This component is either SlimCore or the WebRTC Redirector Service. The option you use depends on the following:

• New Teams can use either SlimCore or the WebRTC Redirector Service. If you use SlimCore, you should also install the WebRTC Redirector Service. This allows a user to fall back to WebRTC, such as if they roam between different devices that don't support the new optimization architecture.

• Classic Teams uses the WebRTC Redirector Service.

If you want to use certain optional features for Teams on Azure Virtual Desktop, you need to enable certain registry keys. 

Enable hardware encode for Teams on Azure Virtual Desktop

Hardware encode lets you increase video quality for the outgoing camera during Teams calls. In order to enable this feature, your client needs to be running version 1.2.3213 or later of the Windows Desktop client. You need to repeat the following instructions for every client device.

To enable hardware encode:

1. On your client device, from the start menu, run Registry Editor as an administrator.
2. Go to HKCU\SOFTWARE\Microsoft\Terminal Server Client\Default\AddIns\WebRTC Redirector.
3. Add the UseHardwareEncoding as a DWORD value.
4. Set the value to 1 to enable the feature.
5. Repeat these instructions for every client device.

Reference: Use Microsoft Teams on Azure Virtual Desktop

Explanation:

The Teams meeting lobby prevents certain types of participants from joining a meeting until a meeting organizer, co-organizer, or presenter admits them. When a participant goes to the lobby, organizers, co-organizers, and presenters are notified and can choose to admit them to the meeting or not.

Using the lobby settings in the Teams admin center, you can create defaults for which types of meeting participants are able to bypass the lobby and which participants must wait there until admitted to the meeting. You can control how the following types of participants interact with the lobby:

• Meeting organizer and co-organizers
• People in your organization
• Guests
• People in trusted organizations
• Anonymous participants

The Who can bypass the lobby setting controls which types of participants (except participants dialing in by phone) join a meeting directly. This policy also controls which types of participants wait in the lobby until an organizer, co-organizer, or presenter admits them. This policy sets a default that your organizers can change through their Meeting options.

Reference: IT Admins - Manage lobby options in Microsoft Teams

Explanation:

Currently, new Teams on VDI with audio/video (AV) optimization is certified with Azure Virtual Desktops, Windows 365, Citrix, and VMware.

To enable audio/video (AV) optimization, a registry key must be added to each host.

Azure Virtual Desktop requires the following key to be added for the new Teams client to be optimized:

HKLM\SOFTWARE\Microsoft\Teams:

• Name: IsWVDEnvironment
• Type: DWORD
• Value: 1

References:

Upgrade to new Teams for Virtualized Desktop Infrastructure (VDI)

Classic Teams for Virtualized Desktop Infrastructure

VMware - Configuring Media Optimization for Microsoft Teams