Free MS-700 Practice Test

Guest access in Microsoft Teams is fundamentally governed by Azure Active Directory's (Azure AD) External collaboration settings. To restrict guest invitations to a single, specific domain such as fabrikam.com, the most direct and effective method is to configure these settings in the Azure AD admin center. By setting the policy to "Allow invitations only to the specified domains" and adding "fabrikam.com" to the list, you ensure that only users from this domain can be added as guests across the organization, thereby meeting the requirement precisely.

B. Modifying Office 365 groups settings is a general on/off switch for guest access in groups but lacks the specific domain-level control required.
C. External access settings in the Teams admin center manage federation for chat/calls with other organizations, which is different from guest access (team membership).
D. Turning off org-wide guest access would prevent all guest invitations, which contradicts the goal of allowing guests from a specific domain.

- Microsoft Entra ID Documentation. (2023). B2B collaboration overview. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/entra/external-id/b2b-collaboration-overview. (See section "Manage external collaboration settings").

- Microsoft Teams Documentation. (2024). Collaborate with guests in a team. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/microsoftteams/guest-access. (See section "Configure guest access in the Azure AD admin center").

- Microsoft Teams Documentation. (2024). Use guest access and external access to collaborate with people outside your organization. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/microsoftteams/communicate-with-users-from-other-organizations. (See section "Compare external and guest access").

To block all apps from a specific third-party publisher, the administrator should use the 'Manage apps' page in the Microsoft Teams admin center. This page serves as the central catalog for all applications available to the organization. An administrator can filter the app list by the publisher's name, select all the apps from that publisher, and then use the 'Block' action to prevent them from being used across the entire organization. This is the most direct and efficient method for this task.

A. Org-wide app settings control high-level permissions, such as allowing or blocking all third-party apps, but managing apps from a specific publisher is done on the Manage apps page.
B. Policy packages are used to bundle and assign a set of policies to users with similar roles, not for blocking specific apps or publishers.
C. Permission policies define which apps users can access. While you could block apps here, you would have to add each app individually, which is less efficient than blocking them from the central 'Manage apps' page.

1. Microsoft Docs. (2023). Manage your apps in the Microsoft Teams admin center. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/microsoftteams/manage-apps. (This document describes the 'Manage apps' page as the central location to "allow or block specific apps for your organization" and details the available actions.)

2. Microsoft Docs. (2023). Manage app permission policies in Microsoft Teams. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/microsoftteams/teams-app-permission-policies. (This explains that while policies control user access, the global allow/block status of an app is set on the 'Manage apps' page.)

This solution requires two distinct policy configurations targeted at the Sales group. First, an app setup policy must be created to control the user experience by pinning the required apps (Activity, Shifts, Chat, Calling) to the Teams app bar. Second, an app permission policy must be created to control which apps users can install. This policy would be configured to block users from adding other apps. Both of these newly created policies would then be assigned specifically to the users in the Sales group, leaving the global policies unaffected for the rest of the organization.

A. Modifying the global app setup policy would change the pinned apps for all users in the company, not just the Sales group.
B. Modifying the global app permission policy would prevent all users in the company from adding apps, not just the Sales group.
D. Org-wide Teams settings manage tenant-level app permissions (e.g., allowing or blocking all third-party apps), not granular pinning or user-specific installation rights.

- Microsoft. (2023). Manage app setup policies in Microsoft Teams. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/microsoftteams/teams-app-setup-policies. (This document explains that app setup policies are used to "customize Teams to highlight the apps that are most important for your users" by pinning them to the app bar.)

- Microsoft. (2023). Manage app permission policies in Microsoft Teams. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/microsoftteams/teams-app-permission-policies. (This document states that app permission policies are used to "control what apps are available to Microsoft Teams users in your organization.")

- Microsoft. (2023). Assign policies to your users in Microsoft Teams. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/microsoftteams/policy-assignment-overview. (This document explains the process of creating and assigning custom policies to specific groups of users.)

The ability for users to create private channels within a team is controlled by a Teams policy. By default, the global (Org-wide default) policy allows private channel creation. To prevent specific users from this action, an administrator must create a new custom Teams policy where the "Create private channels" setting is turned off. This new policy is then assigned directly to the specific users who should be restricted, overriding the global default for them.

B: A meeting policy controls features available within Teams meetings, such as screen sharing, recording, and transcription, not channel creation. C: A setup policy is used to customize the Teams app experience for users, such as pinning specific apps to the navigation bar. D: A permission policy controls which apps (e.g., third-party, custom) users are allowed to install or use within Teams.

1. Microsoft Learn. (2024). Manage Teams policies in Microsoft Teams. The documentation states, "You can use the global (Org-wide default) policy or create and assign custom policies. Users in your organization will get the global policy unless you create and assign a custom policy."

2. Microsoft Learn. (2024). Private channels in Microsoft Teams. Section: "Private channel creation". It specifies, "As an admin, you can use policies to control which users in your organization are allowed to create private channels... This is controlled by the Create private channels setting in the Teams policy."

The Azure Active Directory (Azure AD) admin center's "External collaboration settings" manage identity-level controls for guest users, such as who can invite guests and what domains are allowed. These settings do not extend to in-application device permissions for Microsoft Teams meetings. Control over camera usage during meetings is managed through Microsoft Teams meeting policies, which are configured in the Microsoft Teams admin center, not Azure AD.

This is a Yes/No question, so there are no other options to evaluate as incorrect.

1. Microsoft. (2023). Manage meeting policies in Microsoft Teams. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/microsoftteams/meeting-policies-in-teams. See the "Audio & video" settings section, which includes the "IP video" control.

2. Microsoft. (2023). Configure external collaboration settings. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/azure/active-directory/external-identities/external-collaboration-settings-configure. This document outlines the scope of Azure AD settings, which do not include device management for Teams.

To enable users for PSTN calling with a Microsoft Calling Plan, three main configuration steps are required via PowerShell. First, assign the necessary licenses (Phone System and a Calling Plan) using a licensing cmdlet like Set-AzureADUserLicense. Second, enable the user for Enterprise Voice, which is done using Set-CSUser -EnterpriseVoiceEnabled $true. Third, assign a phone number to the user from Microsoft's number inventory using Set-CsOnlineVoiceUser. This combination of cmdlets fulfills all the requirements to make a user PSTN-capable with a Calling Plan.

A. This option is missing Set-CsOnlineVoiceUser, which is essential for assigning the actual phone number to the user.
B. Grant-CsOnlineVoiceRoutingPolicy is used for configuring Direct Routing, not Microsoft Calling Plans, making this option incorrect for the scenario.
C. This option incorrectly includes Grant-CsOnlineVoiceRoutingPolicy, which is for Direct Routing, and omits the necessary licensing cmdlet.

1. Microsoft Learn. (2024). Set up Calling Plans. Under the "Configure users" section, it outlines the steps of assigning licenses and phone numbers. Retrieved from https://learn.microsoft.com/en-us/microsoftteams/set-up-calling-plans

2. Microsoft Learn. (2024). Set-CsUser. This document details the -EnterpriseVoiceEnabled parameter, which is required to enable a user for Teams Phone voice features. Retrieved from https://learn.microsoft.com/en-us/powershell/module/skype/set-csuser

3. Microsoft Learn. (2024). Set-CsOnlineVoiceUser. This document describes how to use the cmdlet to assign phone numbers to users for Calling Plans or Direct Routing. Retrieved from https://learn.microsoft.com/en-us/powershell/module/skype/set-csonlinevoiceuser

4. Microsoft Learn. (2024). Assign Microsoft 365 licenses to users. This page details methods for assigning licenses, including using PowerShell cmdlets like Set-AzureADUserLicense or the newer Set-MgUserLicense. Retrieved from https://learn.microsoft.com/en-us/microsoft-365/enterprise/assign-licenses-to-user-accounts

While the Microsoft Teams admin center is the correct location to manage meeting policies, the term "External collaboration settings" is not the specific policy area for this control. To prevent guests from using cameras, an administrator must create and assign a specific Microsoft Teams meeting policy. This policy would have the "IP video" setting turned off. This policy must then be assigned to guest users, which often requires a separate process, such as using PowerShell. The general guest access settings do not include this granular control.

This is a Yes/No question, so there are no other options to evaluate as incorrect.

1. Microsoft. (2023). Manage meeting policies in Microsoft Teams. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/microsoftteams/meeting-policies-in-teams. This document details the "IP video" setting within meeting policies, which controls camera usage.

2. Microsoft. (2023). Guest access in Microsoft Teams. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/microsoftteams/guest-access. This document shows that the general guest access settings do not include camera control.

For a user to make Public Switched Telephone Network (PSTN) calls from Microsoft Teams, two core components are required. First, the user must be assigned a "Microsoft Teams Phone" (formerly Phone System) license, which enables PBX capabilities in Microsoft 365. Second, the user's account must be enabled for Enterprise Voice. The absence of the dial pad in the Teams client is a direct symptom that one or both of these requirements have not been met for the specific user.

A. Modifying caller ID properties only changes the number displayed to the recipient; it does not enable the ability to make calls.
C. A SIP address is primarily used for federation and integration with SIP devices, not for enabling the core PSTN calling feature.
D. An app setup policy controls which apps are pinned to the Teams client's navigation bar, not the features available within the Calls app itself.

1. Microsoft Docs. (2024). What is Phone System? Microsoft Learn. "To use Phone System features, your users need a Phone System license." Section: "Phone System features".

2. Microsoft Docs. (2024). Assign, change, or remove a phone number for a user. Microsoft Learn. "Before you can assign a phone number to a user, you must assign a Teams Phone license to the user." Step 3.

3. Microsoft Docs. (2024). Enable users for Direct Routing. Microsoft Learn. "When a user is properly configured for Direct Routing... The user must be assigned a Teams Phone license... The user must be in TeamsOnly mode... The user must be enabled for Enterprise Voice by running the command Set-CsUser -Identity -EnterpriseVoiceEnabled $true". Section: "Steps".

In Islands mode, Microsoft Teams and Skype for Business operate as separate, parallel applications. A chat sent from Teams can only be received in Teams, and a chat from Skype for Business can only be received in Skype for Business. The "missed chat conversation" emails are sent by Teams when a user receives a chat but does not view it in the client. This indicates users are not actively running or monitoring the Teams client. The solution is to ensure the Teams client is installed and to instruct users to run and sign into both clients simultaneously to avoid missing communications from either platform.

B. User permissions within the Teams client do not control the fundamental delivery of messages or the need to have the client running to receive them in real-time.
C. An app setup policy controls which apps are pinned in the Teams client's navigation bar; it does not ensure the client is running or that users are signed in.
D. An app permission policy governs which apps a user is allowed to use within Teams; it is unrelated to receiving native chat messages.
E. The problem is missed Teams chats, which implies users are not running the Teams client. Installing the Skype for Business client is irrelevant and counterintuitive.

1. Microsoft Docs. (2023). Coexistence with Skype for Business - Islands mode. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/microsoftteams/coexistence-islands. "In Islands mode... Users are expected to run both clients at all times to ensure they can communicate with other users."

2. Microsoft Docs. (2023). Guidance for organizations in Islands mode. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/microsoftteams/islands-mode-guidance. "To have a complete experience in Islands mode, users need to run both clients continuously."

A Microsoft Team is built upon a Microsoft 365 Group. When a team is deleted, the underlying group is soft-deleted and can be restored within 30 days. The correct procedure using PowerShell is to first identify the deleted group using the Get-AzureADMSDeletedGroup cmdlet. Then, using the Object ID of that deleted group, you run the Restore-AzureADMSDeletedDirectoryObject cmdlet to restore the group, which in turn restores the associated team and its content.

B. Get-Team only lists active teams, and Restore-ADObject is for on-premises Active Directory, not Azure AD.
C. Restore-ADObject is for on-premises Active Directory and cannot be used to restore an Azure AD object.
D. Get-AzureADGroup only lists active groups, not soft-deleted ones, so it cannot find the group to restore.
E. Get-Team cannot find a deleted team; you must find the underlying soft-deleted Microsoft 365 Group.

- Microsoft. (2023). Restore a deleted Microsoft 365 group. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/microsoft-365/admin/create-groups/restore-deleted-group. (See section "Restore a group using PowerShell").

- Microsoft. (2023). Restore-AzureADMSDeletedDirectoryObject. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/powershell/module/azuread/restore-azureadmsdeleteddirectoryobject. (See cmdlet description and examples).

- Microsoft. (2023). Get-AzureADMSDeletedGroup. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/powershell/module/azuread/get-azureadmsdeletedgroup. (See cmdlet description).