Q: 7
Note: This question is part of a series of questions that present the same scenario. Each question in
the series contains a unique solution that might meet the stated goals. Some question sets might
have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these
questions will not appear in the review screen.
Your company has a Microsoft 365 subscription.
You plan to configure the environment to allow external users to collaborate in Microsoft Teams by
using guest access.
The company implements a new security policy that has the following requirements:
Only guest users from specific domains must be allowed to connect to collaborate by using Microsoft
Teams.
Guest users must be prevented from inviting other guests.
You need to recommend a solution to meet the security policy requirements.
Solution: From PowerShell, you run the New-AzureADPolicy and Set-AzureADPolicy cmdlets.
Does this meet the goal?
Options
Discussion
Its B. Those PowerShell cmdlets only set general Azure AD external policies, but they can’t specifically limit Teams guest access to certain domains or stop guests from inviting others. Teams requires separate controls for those details. Pretty sure about this, but open if someone’s set it up differently.
I don’t think it’s A. B.
B, Doesn’t hit the Teams guest restrictions, just covers general AAD policies. Teams-specific controls are needed for those requirements.
A? Maybe those PowerShell commands do enough at the Azure AD level here.
Not quite A, it should be B. Those PowerShell cmdlets set the general AAD external collaboration policy, but they can't enforce Teams-specific guest controls or limit domains directly. I think the trick here is that you still need to configure Azure AD settings or use the Teams admin center for those requirements. Let me know if anyone has actually done this differently.
B
Skip A, B. . Those cmdlets don't allow guest domain restrictions in Teams by themselves.
D , had something like this in a mock and picked A.
Doesn't look like this solution fully meets the Teams requirements. B. Those PowerShell cmdlets set basic Azure AD guest policies, but not the Teams-specific controls for domains or invite restrictions. I think it's a trap if you miss the product scope, but happy to discuss if someone has another angle.
Had something like this in a mock, pretty sure it's B.
Be respectful. No spam.
