Microsoft - MS-700: Managing Microsoft Teams

Sample Questions

Explanation:

The EnableRoomMailboxAccount parameter of the New-Mailbox cmdlet specifies whether to enable the disabled user account that's associated with this room mailbox. Valid values are:

• $true: The disabled account that's associated with the room mailbox is enabled. You also need to use the RoomMailboxPassword with this value. The account is able to log in and access the room mailbox or other resources.

• $false: The account that's associated with the room mailbox is disabled. The account is not able to log in and access the room mailbox or other resources. In on-premises Exchange, this is the default value.

You need to enable the account for features like the Skype for Business Room System or Microsoft Teams Rooms.

The Set-CalendarProcessing cmdlet is used to modify calendar processing options for resource mailboxes, which include the Calendar Attendant, resource booking assistant, and calendar configuration. Note that this cmdlet is effective only on resource mailboxes.

• None: Calendar processing is disabled on the mailbox. Both the resource booking attendant and the Calendar Attendant are disabled on the mailbox.

• AutoUpdate: Only the Calendar Attendant processes meeting requests and responses. Meeting requests are tentative in the calendar until they're approved by a delegate. Meeting organizers receive only decisions from delegates.

• AutoAccept: Both the Calendar Attendant and resource booking attendant are enabled on the mailbox. This means that the Calendar Attendant updates the calendar, and then the resource booking assistant accepts the meeting based upon the policies. Eligible meeting organizers receive the decision directly without human intervention (free = accept; busy = decline).

• $true: Conflicts are allowed.

• $false: Conflicts aren't allowed. This is the default value.

References:

New-Mailbox

Set-CalendarProcessing

Explanation:

Microsoft Teams Rooms 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 traffic in the following order: audio, content sharing, lastly participant video.

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.

The following table provides bandwidth requirements for the various streams in kbps (up/down):

Best performance video streaming in meetings requires 4Mbps/4Mbps. We have 25 Rooms devices that can share a bandwith of 500 Mbps up and 500 Mbps down. This is 25 Mbps up/down per device, which is by far enough to support video during Teams meetings.

Recommended bandwith for screen sharing during meetings is 2.5Mbps/2.5Mbps. We have 100 users connected to the wired network that require a total of 250 Mbps/250Mbps.

Recommended performance video streaming in meetings requires 2.5Mbps/4Mbps. We have 75 users connected to the wireless network that require a total of 187.5Mbps/300Mbps which exceeds the available bandwith of the wireless network.

Reference: Prepare your organization's network for Microsoft Teams

Explanation:

After completing planning for Teams Rooms, the next phase is deployment. Deploying Teams Rooms is broken down into a few phases:

1. Ordering equipment and confirming that your deployment locations (spaces) meet the deployment dependencies
2. Preparing your network environment and configuration steps to ensure your devices work on your corporate network
3. Creating resource accounts for your Microsoft Teams devices
4. Enabling the Teams Rooms Pro Management Portal and assigning administrative roles
5. Configuring Intune for your Teams Rooms
6. Physically deploying your Teams Rooms devices and completing the initial setup steps

Teams Rooms devices need resource accounts to be able to successfully sign into Teams and allow end users to book and ensure join buttons appear on the rooms calendar. 

A one-time password (OTP) is used to provide authentication when someone is setting up and deploying Teams Rooms consoles that run on Windows without the need for a specific username and password used on the device. The one-time password is created in the Microsoft Teams Rooms Pro Management portal and only used for a single sign in session.

References:

Deployment overview

Create a one-time password

Set up Microsoft Teams Rooms consoles using one-time passwords

• Meet the device compliance requirements specified in Microsoft Intune.
• Support Intelligent Speaker.
• Support Operator Connect.
• Minimize costs.

Explanation:

Microsoft offers two licenses for Teams Rooms systems that participate in Teams meetings and calls:

• Microsoft Teams Rooms Pro delivers enhanced in-room meeting experiences like intelligent audio and video, front row and large galleries, and dual screen support. The Teams Rooms Pro license also provides advanced management features like remote device management, conditional access policies, and detailed device analytics.

  Teams Rooms Pro is a great fit for medium and enterprise organizations, as well as smaller organizations with larger room counts or more advanced needs. Teams Rooms Pro licenses can be used to license both certified Teams Rooms systems and Teams Panels.

• Microsoft Teams Rooms Basic provides core meeting experiences to organizations that purchase a certified Microsoft Teams Rooms system, at no additional cost. The Teams Rooms Basic license includes scheduling, joining meetings, content sharing, and collaborative white boarding, as well as basic security and management capabilities out-of-the-box.

• A Teams Rooms Basic license can be used to license a single certified Teams Rooms system in a room. If you want to log into more than one Teams Rooms system in a room using the same resource account, you need to use a Teams Rooms Pro license.

• You can assign up to 25 Microsoft Teams Rooms Basic licenses to Teams Rooms systems in your organization. If you need to license more than 25 Teams Rooms systems, those additional licenses need to be Teams Rooms Pro licenses. Teams Rooms Basic licenses can be used to license Teams Rooms systems only and not Teams Panels.

References: Microsoft Teams Rooms licenses

Explanation:

You can use a naming policy to enforce a consistent naming strategy for Microsoft 365 groups and teams created by users in your organization. A naming policy can help you and your users identify the function of the group, membership, geographic region, or who created the group. The naming policy can also help categorize groups in the address book. You can use the policy to block specific words from being used in group names and aliases.

The naming policy is applied to groups that are created across all groups workloads (like Outlook, Microsoft Teams, SharePoint, Planner, Viva Engage, etc.). It gets applied to both the group name and group alias. It also gets applied when a user creates a group and when the group name, alias, description, or avatar is edited for an existing group.

The group naming policy consists of the following features:

• Prefix-Suffix naming policy: You can use prefixes or suffixes to define the naming convention of groups (for example: "US_My Group_Engineering"). The prefixes/suffixes can either be fixed strings or user attributes like [Department] that are substituted based on the user who is creating the group.

• Custom Blocked Words: You can upload a set of blocked words specific to your organization that would be blocked in groups created by users. (For example: "CEO, Payroll, HR").

Reference: Microsoft 365 Groups and Microsoft Teams naming policy