Pass the Microsoft Microsoft 365 Certified: Teams Administrator Associate MS-700 Questions and answers with CertsForce

To ensure that the Approvals app is pinned to the top of the app bar of the Teams client for all members of the Retail team, you need to create a custom app setup policy and assign it to the Retail team members. Here are the steps to follow:

Sign in to the Teams admin center with your admin credentials.

Go to Teams apps > Setup policies.

Select Add.

Provide a name and description for the policy, such as Retail App Policy.

Optionally, turn on User pinning to allow users to pin apps and change the order of the pinned apps.

Under Pinned apps, select Add apps.

Search for the Approvals app and add it to the list of pinned apps. You can also add other apps that you want to pin for the Retail team members.

Click Save to create the policy.

To assign the policy to the Retail team members, go to Users on the left menu and select the users that belong to the Retail team. You can use the filters or the search box to find them.

On the right pane, under Policies, select Edit next to App setup policy.

Choose the Retail App Policy from the drop-down list and click Apply.

To restrict external Teams communication for both calling and personal chat to only organizational users that use the microsoft.com domain, you need to use the Teams admin center to configure the external access settings. Here are the steps to follow:

Sign in to the Teams admin center with your Microsoft 365 username and password.

In the left navigation, go to Org-wide settings > External access.

Under External access, turn on the toggle for Users can communicate with other Skype for Business and Teams users.

Under Cross-tenant access settings, click Manage settings.

In the Cross-tenant access settings pane, under Calling and chat, select Allow specific domains and then enter microsoft.com in the box below. This will allow your users to communicate with Microsoft users via calling and chat.

Click Save.

Note: You also need to make sure that microsoft.com has configured their external access settings to allow communication with your domain. See Communicate with users from other organizations for more details.

To ensure that a team named US Sales automatically contains all the users that have the department attribute set to Sales, you need to create a dynamic team based on Azure AD group dynamic membership rules. Here are the steps to follow:

Create a new team in Microsoft Teams as you would to create a normal team. Name it US Sales. If the team already exists, you can skip this step.

Sign in to the Azure portal with your admin credentials.

Go to Azure Active Directory > Groups. Find the group that corresponds to the US Sales team and select it.

On the group details page, select Properties on the left menu and change the membership type to Dynamic user. Click Save.

On the same page, select Dynamic membership rules on the left menu and add an expression that dynamically retrieves the users that have the department attribute set to Sales. In this case, the expression is user.department -eq "Sales". Click Save.

That’s it. You have successfully created a dynamic team for US Sales. This means that only users with the department attribute set to Sales will be added or removed from the team automatically. You can also modify the expression to include other criteria, such as location, job title, or manage

To prevent users from deleting messages posted in private chats and channels, you need to manage the messaging policies in Teams. Here are the steps to follow:

Sign in to the Teams admin center with your admin credentials.

Go to Teams apps > Messaging policies.

Select the policy that you want to modify, such as the global (Org-wide default) policy or a custom policy.

Turn off the following settings: Owners can delete sent messages, Users can delete sent messages, and Users can edit sent messages.

Click Save to apply the changes.

To ensure that only users from litwareinc.com can be added to Teams as guest users, you need to configure the guest access settings in Azure Active Directory (AAD). Here are the steps to follow:

Sign in to the Azure portal with your admin credentials.

Go to Azure Active Directory > External identities > External collaboration settings.

Under Collaboration restrictions, select Allow invitations only to the specified domains (most restrictive).

In the Allow invitations to these domains box, enter litwareinc.com. You can also add more domains if you want, separated by commas.

Click Save to apply the settings.

That’s it. You have successfully restricted the guest access in Teams to a specific domain. This means that only users with email addresses from litwareinc.com can be invited as guests to your teams. You can also prevent guests from being added to a specific team by using sensitivity labels1 or PowerShell2.

To configure a virtual receptionist for your company’s main office, you can use the Teams admin center to create and assign an auto attendant. An auto attendant is a voice menu system that allows callers to be transferred to an extension or a queue without speaking to an operator or receptionist. Here are the steps to create and assign an auto attendant that meets your requirements:

Sign in to the Teams admin center with your Microsoft 365 username and password.

In the left navigation, go to Voice > Auto attendants.

Click Add (+) to create a new auto attendant.

In the Basics tab, enter a name and an optional description for the auto attendant, such as “Main Office Receptionist”.

Under Phone number, select Assign and then choose a service number from the list or click Add new number to get a new one. A service number is a type of phone number that can handle hundreds of simultaneous calls and is used for services such as audio conferencing, auto attendants, and call queues.

Click Apply and then Next.

In the Greeting and menu tab, under Greeting, select Custom and then click Upload audio file to upload a recorded greeting message for the callers, such as “Welcome to Microsoft. Please listen carefully to the following options.”

Under Menu options, click Add (+) and then select Key press from the drop-down menu.

In the Key press box, enter 1 and then select Dial by name from the Action drop-down menu. This will allow callers to press 1 for the company directory to lookup by name.

Click Add (+) again and then select Key press from the drop-down menu.

In the Key press box, enter 0 and then select Play audio file from the Action drop-down menu. This will allow callers to press 0 to hear the company address.

Click Upload audio file and then upload a recorded message with the company address, such as “Our main office is located at 1 Microsoft Way, Redmond.”

Under Menu options, turn on the toggle for Repeat menu until caller hangs up or presses #. This will offer the same menu at all times.

Click Next.

In the Business hours tab, under Business hours, select 24/7 from the drop-down menu. This will make the auto attendant available at all times.

Click Next.

In the Review tab, review your settings and then click Save.

Now, you have configured a virtual receptionist for your company’s main office that meets your requirements.

To provide only Adele Vance with the ability to turn on and off Teams preview features, you need to create and assign a custom update policy for her. Here are the steps to do so:

Sign in to the Microsoft Teams admin center with your Microsoft 365 username and password1.

In the left navigation, go to Teams > Teams Update policies.

Select Add to create a new policy or select an existing policy to open Update policy.

Name the update policy, add a description, and select Enabled from the drop-down menu for Allow public preview. This option enables Teams Public Preview regardless of whether a user is enrolled in Office Current Channel (Preview). The end user must also opt in to Teams public preview in their Teams app2.

Click Save and then Close.

In the left navigation, go to Users and then search for Adele Vance from the list of users.

In the user details page, go to Policies and then click Edit next to Assigned policies.

In the Assigned policies pane, under Update policy, select the policy that you created or modified in step 4 from the drop-down menu.

Click Apply and then Close.

Now, Adele Vance can turn on and off Teams preview features by following these steps in her Teams app3:

Select the three dots to the left of your profile to display the Teams menu.

Select About > Public preview.

Select Switch to Public preview or Switch back to standard version.

To enable shared channel collaboration with microsoft.com, you need to use the Teams admin center to configure the channel policy and the cross-tenant access settings. Here are the steps to follow:

Sign in to the Teams admin center with your Microsoft 365 username and password1.

In the left navigation, go to Teams > Teams update policies.

Select an existing policy or create a new one by clicking Add.

In the Update policy pane, under Shared channels, turn on the toggles for Allow shared channel creation and Allow external shared channel participation. This will allow users to create shared channels and participate in shared channels created by microsoft.com.

Click Save and then Close.

In the left navigation, go to Org-wide settings > External access.

Under Cross-tenant access settings, click Manage settings.

In the Cross-tenant access settings pane, under Shared channels, select Allow specific domains and then enter microsoft.com in the box below. This will allow users to invite Microsoft contacts to shared channels created by your company.

Click Save.

Note: You also need to make sure that microsoft.com has configured their cross-tenant access settings to allow shared channel collaboration with your domain. See Collaborate with external participants in a channel2 for more details.

To ensure that all unused teams expire and are deleted automatically, you need to configure a Microsoft 365 group expiration policy. This policy applies to teams because they are backed by groups. Here are the steps to follow:

Sign in to the Microsoft 365 admin center with your admin credentials.

Go to Groups > Expiration.

Turn on the Enable expiration toggle.

In the Group lifetime box, enter 365 days or select it from the drop-down list. This means that the teams will expire 365 days from their creation date.

In the Select group types to apply the policy section, check the Teams box. You can also select other group types if you want.

In the Choose how to handle owners of groups without owners section, enter adminLOD-Se551723.onmicrosoft.com as the email address to receive notifications for the expiration of orphaned teams. You can also add more email addresses if you want.

Click Save to apply the policy.

That’s it. You have successfully configured a group expiration policy for teams. This policy will automatically delete the teams that are not renewed by their owners before the expiration date. You can also view and restore the deleted teams within 30 days from the Deleted groups page in the admin center.

To restrict Teams bandwidth by network range, you can use the Network Roaming Policy feature1. This feature allows you to define different media bit rate settings for different network locations based on the IP address ranges. Here are the steps to accomplish your task:

Create a new network roaming policy with the desired media bit rate settings. For example, you can use the following PowerShell cmdlet to create a policy named “MiamiPolicy” with a maximum bit rate of 1000 Kbps for audio and video:

New-CsTeamsNetworkRoamingPolicy -Identity "MiamiPolicy" -MaxMediaBitRateKb 1000

Assign the network roaming policy to the network range of the Miami office. You can use the following PowerShell cmdlet to assign the policy to the 10.10.10.0/24 network range:

New-CsTeamsNetworkRoamingPolicyAssignment -PolicyName "MiamiPolicy" -IPAddressRange "10.10.10.0/24"

Verify that the policy is applied correctly by using the Get-CsTeamsNetworkRoamingPolicyAssignment cmdlet. You should see something like this:

Identity : 10.10.10.0/24

PolicyName : MiamiPolicy

IPAddressRange : 10.10.10.0/24

EffectiveTime : 8/1/2023 1:18:24 PM

LastUpdateTime : 8/1/2023 1:18:24 PM

LastUpdateBy : admin@XXXXXXXXXXX.onmicrosoft.com

LastUpdateBySid : S-1-5-21-XXXXXXXXXX-XXXXXXXXXX-XXXXXXXXXX-XXXXX

Note: You may need to wait for some time for the policy to take effect.