Microsoft - MS-700: Managing Microsoft Teams

Sample Questions

• Users in Branch1 must use only audio and video for meetings.
• Users in Branch2 must be able to enable Together Mode for meetings.
• Network bandwidth costs must be minimized.

Explanation:

Teams is designed to give the best audio, video, and content sharing experience regardless of your network conditions. That said, when bandwidth is insufficient, Teams prioritizes audio quality over video quality.

Where bandwidth isn't limited, Teams optimizes media quality, including high-fidelity audio, up to 1080p video resolution, and up to 30 fps (frames per second) for video and content.

This table describes how Teams uses bandwidth. Teams is always conservative on bandwidth utilization and can deliver HD video quality in under 1.5 Mbps. The actual bandwidth consumption in each audio/video call or meeting will vary based on several factors, such as video layout, video resolution, and video frames per second. When more bandwidth is available, quality and usage will increase to deliver the best experience.

Minimum, Recommended, and Best performance bandwidth requirements are based on per-endpoint usage. Typically, there's one endpoint per user, such as a computer or mobile device. However, if a user joins a Teams meeting on both a computer and a mobile device, two endpoints are associated with that user.

Reference: Prepare your organization's network for Microsoft Teams

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.

Enable media optimization for Teams

To enable media optimization for Teams, set the following registry key on each session host:

From the start menu, run Registry Editor as an administrator. Go to 

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Teams.

Create the Teams key if it doesn't already exist.

Create the following value for the Teams key:

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

Alternatively, you can create the registry entry by running the following commands from an elevated PowerShell session:

New-Item -Path "HKLM:\SOFTWARE\Microsoft\Teams" -Force
New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Teams" -Name IsWVDEnvironment -PropertyType DWORD -Value 1 -Force

Reference: Use Microsoft Teams on Azure Virtual Desktop

Explanation:

To provision a device remotely, the admin needs to upload the MAC IDs of the devices being provisioned and create a verification code. The entire process can be completed remotely from the Teams admin center. The verification code is generated in bulk or at the device level and is valid for 24 hours.

The technician must enter the device-specific verification code in the provided input field when provisioning the device.

Reference: Remote provisioning and sign in for Teams Android devices

Explanation:

A common area phone is typically placed in an area like a lobby, reception area, or a conference room and is available to many people to make a call. Common area phones are signed in with resource accounts tied to a Microsoft Teams Shared Devices license.

First, we need to create a new resource account. 

Second, we set up the common area phone as a hotline phone also known as PLAR (Private Line Auto Ringdown) phone. This step will  program the phone to autodial a preconfigured PSTN number or a directory contact when the phone handset is picked up.

Lastly, we create a Teams IP Phone policy to control which features are available to users on common area phones. Here, we use the policy to restrict searching the organization's Global Address Book.

Reference: Set up common area phones for Microsoft Teams

Explanation:

If your organization has Microsoft Purview Data Loss Prevention (DLP), you can define policies that help prevent people from sharing sensitive information in a Microsoft Teams channel or chat session. Here are some examples of how this protection works:

• Protecting sensitive information in messages. Suppose that someone attempts to share sensitive information in a Teams chat or channel with guests (external users). If you have a DLP policy defined to prevent this, messages with sensitive information that are sent to external users are deleted. This happens automatically, and within seconds, according to how your DLP policy is configured.  

• Protecting sensitive information in documents. Suppose that someone attempts to share a document with guests in a Microsoft Teams channel or chat, and the document contains sensitive information. If you have a DLP policy defined to prevent this, the document won't open for those users. Your DLP policy must include SharePoint and OneDrive in order for protection to be enforced. This is an example of DLP for SharePoint that shows up in Microsoft Teams, and therefore requires that users are licensed for Office 365 DLP (included in Office 365 E3), but doesn't require that users be licensed for Office 365 Advanced Compliance.

• Protecting communications in Teams Shared Channels. For shared channels, the host Teams team DLP policy is applied. For example, let's say there's a shared channel owned by Team A of Contoso. Team A has a DLP policy P1. There are three ways to share a channel:

• Share with member: You invite User1 from Contoso to join the shared channel without making them a member of Team A. Everyone in this shared channel, including User1, is covered by P1.
• Share with team (internally): You share the channel with another team within Contoso, Team B. That other team might have a different DLP policy, but that doesn’t matter. P1 applies to everyone in this shared channel, including both Team A and Team B users.
• Share with team (cross tenant): You share the channel with a team, Team F, in Fabrikam. Fabrikam might have its own DLP policy, but that doesn't matter. P1 applies to everyone in this shared channel, including both Team A (Contoso) and Team F (Fabrikam) users.

• Protecting communications when chatting with external users in Microsoft Teams. People from different Microsoft 365 organizations who are all using the external access feature can all join the same chat session. Each user is subject to the DLP policies of their own organization. For instance, say that UserA, UserB and UserC, all from Contoso, and UserX, UserY, and UserZ, all from Fabrikam, are in the same Teams chat. Contoso's DLP policies for sharing information in Teams apply to UserA, UserB and UserC, while Fabrikam's DLP policies apply to UserX, UserY, and UserZ.

Reference: Data loss prevention and Microsoft Teams