MS-700 Exam Dumps - Managing Microsoft Teams

To set Microsoft SharePoint as the only cloud storage option for all teams, you need to use the Teams admin center to disable the third-party cloud storage services. 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 Org-wide settings > Services & add-ins.

Under Cloud file storage, click Manage.

In the Cloud file storage pane, turn off the toggles for Box, Dropbox, Google Drive, and Citrix ShareFile. This will disable these services for all teams and users in your organization.

Click Save.

Now, Microsoft SharePoint will be the only cloud storage option for all teams. Users will be able to access SharePoint files from the Files tab in each team channel or from the Files app on the left side of Teams.

To add a disclaimer to all Teams meeting invites, you can use the Exchange admin center to create a mail flow rule that applies the disclaimer to meeting requests. Here are the steps to follow:

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

In the left navigation, go to Mail flow > Rules.

Click Add (+) and then select Create a new rule.

In the New rule pane, enter a name for the rule, such as “Meeting disclaimer”.

Under Apply this rule if, select A message header includes any of these words.

In the Specify header name box, enter X-MS-Exchange-Calendar-Meeting-Request. This is a special header that identifies meeting requests2.

In the Specify words or phrases box, enter True. This means that the rule will apply to any message that has the header set to True.

Click Add and then OK.

Under Do the following, select Append the disclaimer.

In the Specify disclaimer text box, enter the disclaimer text that you want to add to the meeting invites, such as:

Disclaimer: This meeting may be recorded for quality and training purposes.

Click Enter text and then OK.

Under Choose a mode for this rule, select Enforce.

Click Save.

Now, when you or anyone in your organization schedules a Teams meeting, the disclaimer will be added to the meeting invites automatically.

To prevent guest users from calling your company’s Teams users, you need to turn off the calling capability for guests in the Teams admin center. Here are the steps to follow:

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

Go to Users > Guest access.

Turn off the Make private calls setting. This will disable the peer-to-peer calling feature for guests.

Click Save to apply the changes

To ensure that when users join a meeting by using a phone, they are prompted to record their name, you need to enable the meeting entry and exit notifications in the Teams admin center. Here are the steps to follow:

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

Go to Meetings > Conference Bridges.

At the top of the Conference Bridges page, select Bridge settings.

Enable the Meeting entry and exit notifications toggle.

Choose Names for the Entry/exit announcement type.

Turn on the toggle for Ask callers to record their name before joining a meeting.

Click Save to apply the settings.

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.

To prevent incoming Teams call notifications when users are already on a Teams call or in a Teams meeting, you can use the Teams admin center to enable the Mute notifications during meetings and calls option. This option will suppress the incoming call notifications without rejecting the call. The caller will still hear the ringing tone and the callee can still answer the call from the Teams app or the taskbar. Here are the steps to enable this option:

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 Meetings and calls, turn on the toggle for Mute notifications during meetings and calls.

Click Save and then Close.

Note: You can assign different update policies to different users or groups of users. For more information, see Manage update policies in Microsoft Teams2.

To acquire a dedicated Microsoft dial-in bridge number from either 431 or 343 area codes in Canada, you need to use the Teams admin center to request and assign a service number. 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. 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 Voice > Phone numbers.

Click Add (+) and then select New service numbers.

In the New service numbers pane, select the country or region as Canada, the number type as Toll or Toll-free, and the location as Manitoba (for 431 area code) or Ontario (for 343 area code).

Enter the quantity of numbers that you need and then click Next.

Review your order details and then click Submit request.

Wait for an email confirmation that your request has been processed. This may take up to 24 hours.

After you receive the confirmation email, go back to the Teams admin center and click Refresh on the Phone numbers page. You should see the new service numbers that you requested.

To assign a service number to your audio conferencing bridge, go to Meetings > Conference bridges and then click Edit next to Default toll or toll-free number.

In the Edit default toll or toll-free number pane, select one of the new service numbers that you acquired from the drop-down menu and then click Apply.

Now, you have acquired and assigned a dedicated Microsoft dial-in bridge number from either 431 or 343 area codes in Canada.

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 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.

ation:

To prevent unauthenticated users from joining Teams meetings, you need to turn off the anonymous meeting join feature in Teams. Here are the steps to follow:

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

Go to Meetings > Meeting settings.

Under Participants, set Anonymous participants can join a meeting to Off.

Click Save to apply the changes.

To ensure that users can perform the following actions:

Record Teams calls and Teams meeting.

Transcribe Teams calls and Teams meeting.

You need to do the following:

Turn on the recording and transcription settings in the Teams admin center. This will allow users to start and stop recording and transcription during a meeting or call. The recording and transcription will be stored in OneDrive or SharePoint and available in the meeting chat or channel conversation. For more details, see Record a meeting in Microsoft Teams.

Turn on the transcription and captions settings in the Teams admin center. This will enable automatic transcription and captions for meeting recordings. Users can play back the recordings with closed captions and review the transcript in the Recording & Transcripts tab in Teams. For more details, see Configure transcription and captions for Teams meetings.

Turn on the live transcription settings in the Teams admin center. This will allow users to view live transcription during a meeting or call. Users can also download the transcript after the meeting or call. For more details, see View live transcription in Microsoft Teams meetings.

To ensure that content on Microsoft SharePoint Online sites can be shared only with new and existing guest users, you need to limit the external sharing settings in the SharePoint admin center. Here are the steps to follow:

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

Go to Policies > Sharing.

Under External sharing, drag the SharePoint slider down to New and existing guests. (The OneDrive slider is dependent on SharePoint and will also be set to New and existing guests.)

Under More external sharing settings, check the box Allow only users in specific security groups to share externally and select Manage security groups.

Add the security groups that contain the users who are allowed to share content with guest users. You can also create a new security group if needed.

Click Save to apply the settings.

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 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 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 deploy the Microsoft Viva Connections app to Teams and install the app as the first item on the app bar of the Teams client for all users, you need to use the Teams admin center and PowerShell. 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 apps > Manage apps.

Click Upload and then select the Viva Connections app package that you created using PowerShell2. If you have not created the app package yet, you can follow the instructions in this article to do so.

After uploading the app package, click on the app name and then click Publish.

In the left navigation, go to Teams apps > Setup policies.

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

In the Setup policy pane, under Installed apps, click Add apps and then select the Viva Connections app from the list.

Drag and drop the Viva Connections app to reorder it as the first item on the app bar.

Click Save and then Close.

To assign the setup policy to all users, you can use PowerShell to run the following cmdlet:

Get-CsOnlineUser | Grant-CsTeamsAppSetupPolicy -PolicyName "YourPolicyName"

Replace “YourPolicyName” with the name of the policy that you created or modified in step 6.

Note: It may take up to 24 hours for the changes to take effect.

Now, you have deployed and installed the Microsoft Viva Connections app to Teams as the first item on the app bar for all users.

To ensure that when users dial emergency numbers, the call is routed based on the user’s current location, you need to enable the external location lookup mode in Teams. This mode allows Teams to use the location services of the device’s operating system to suggest an emergency address for the user. The user can then confirm, edit, or enter a new address, which will be used to route the emergency call to the appropriate Public Safety Answering Point (PSAP). Here are the steps to follow:

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

Go to Voice > Emergency policies.

Select Add.

Enter a name for the emergency calling policy, for example, “E911WFH”.

Turn on External location lookup mode.

Select Apply to create the policy.

To assign the policy to the users who need it, go to Users on the left menu and select the users that you want to apply the policy to. You can use the filters or the search box to find them.

On the right pane, under Policies, select Edit next to Emergency calling policy.

Choose the policy that you created from the drop-down list and click Apply.

To create a Microsoft 365 group named TeamsAdmin that can manage Teams Phone configurations without being able to manage teams and channels, you need to use PowerShell to create the group and assign the Teams Communications Administrator role to it. Here are the steps to follow:

Install the Azure Active Directory PowerShell for Graph module by running the following cmdlet:

Install-Module -Name AzureAD

Connect to Azure Active Directory by running the following cmdlet and entering your Microsoft 365 username and password:

Connect-AzureACreate a new Microsoft 365 group named TeamsAdmin by running the following cmdlet:

New-AzureADMSGroup -DisplayName "TeamsAdmin" -Description "Group for managing Teams Phone configurations" -MailEnabled $false -MailNickName "TeamsAdmin" -SecurityEnabled $true -GroupTypes "Unified"

Get the object ID of the new group by running the following cmdlet:

Get-AzureADMSGroup -Filter "DisplayName eq 'TeamsAdmin'"

Copy the object ID from the output and assign it to a variable, such as $groupID, by running the following cmdlet:

$groupID = "your-object-iInstall the Microsoft Teams PowerShell module by running the following cmdlet:

Install-Module -Name MicrosoftTeams

Connect to Microsoft Teams by running the following cmdlet and entering your Microsoft 365 username and password:

Connect-MicrosoftTeams

Get the role ID of the Teams Communications Administrator role by running the following cmdlet:

Get-CsOnlineRole -Identity "Teams Communications Administrator"

Copy the role ID from the output and assign it to a variable, such as $roleID, by running the following cmdlet:

$roleID = "your-role-id"

Assign the Teams Communications Administrator role to the TeamsAdmin group by running the following cmdlet:

New-CsOnlineRoleAssignment -SecurityGroupId $groupID -RoleDefinitionName $roleID

Now, you have created a Microsoft 365 group named TeamsAdmin that can manage Teams Phone configurations without being able to manage teams and channels. You can add members to this group by using the Azure Active Directory admin center or PowerShell.

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 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

https://docs.microsoft.com/en-us/azure/active-directory/b2b/delegate-invitations

https://docs.microsof t.com/en-us/microsoftteams/manage-external-access https://doc s.microsoft.com/en-us/azure/active-directory/b2b/allow-deny-list

https://docs.microsoft.com/en-us/microsoft-365/a dmin/create-groups/compare-groups?view=o365-worldwide

http://blog.schertz.name/2019/07/cus tomizing-microsoft-teams-meeting-invitations/

https://docs.microsof t.com/en-us/microsoftteams/cloud-recording

Create information barrier segments first, then create information barrier policy based on the segments then start the information barrier application.

https://docs .microsoft.com/en-us/microsoftteams/messaging-policies-in-teams

Microsoft Teams admin center > Org-wide settings > Guest access > Make private calls = off.

https://docs.microsoft.com/en-us/microsoftteams/teams-add-on-licensing/microsoft-teams-add-on-licensing

https://support.microsoft.com/en-us/ office/create-a-team-from-an-existing-group-24ec428e-40d7-4a1a-ab87-29be7d145865

According to the Microsoft documentation4, external access settings in the Microsoft Teams admin center are used to control how users in your organization can communicate with users from other domains that use Teams or Skype for Business. External access settings do not affect how guest users in your tenant can use cameras during Teams meetings.

To prevent guest users in your tenant from using cameras during Teams meetings, you need to create and assign a custom meeting policy that has the Allow IP video setting turned off. You can do this by using the Microsoft Teams admin center or PowerShell. For example, to create and assign a custom meeting policy by using PowerShell, you can use the New-CsTeamsMeetingPolicy and Grant-CsTeamsMeetingPolicy cmdlets.

1.The Microsoft Team admin center

2. The Set-csUser cmdlet

https://docs.microsoft.com/en-us /microsoftteams/assign-change-emergency-location-user