MS-203 Microsoft 365 Groups and Collaboration 2 — Questions and Answers
Question 1: An administrator needs to add a naming policy that appends a department prefix to all newly created Microsoft 365 Groups. Where is this configured?
- Exchange Admin Center > Recipients > Groups
- Microsoft 365 Admin Center > Settings > Org settings > Microsoft 365 Groups
- Azure Active Directory > Groups > Naming policy (Correct answer)
- PowerShell using New-TransportRule
Correct answer: Azure Active Directory > Groups > Naming policy
Microsoft 365 Groups naming policies are configured in Azure Active Directory under Groups settings, where administrators can define prefix/suffix patterns and blocked words.
Question 2: Which property must be configured on a Microsoft 365 Group to prevent non-members from sending email to the group?
- Set-UnifiedGroup -ModerationEnabled $true
- Set-UnifiedGroup -RequireSenderAuthenticationEnabled $true (Correct answer)
- Set-UnifiedGroup -AccessType Private
- Set-UnifiedGroup -HiddenFromAddressListsEnabled $true
Correct answer: Set-UnifiedGroup -RequireSenderAuthenticationEnabled $true
RequireSenderAuthenticationEnabled set to $true ensures only authenticated internal users can send to the group, preventing anonymous and external senders from emailing the group.
Question 3: A Microsoft 365 Group is set to Private. What does this mean for discoverability and membership?
- The group is hidden from the Global Address List and only invited members can join
- The group appears in search results but requires owner approval or invitation to join (Correct answer)
- The group is only visible to members and cannot be found by non-members
- The group cannot receive external email and blocks all non-member access
Correct answer: The group appears in search results but requires owner approval or invitation to join
A Private Microsoft 365 Group is visible in search results and the GAL, but users must request membership which requires owner approval, or be directly invited by an owner.
Question 4: Which PowerShell cmdlet is used to convert an existing distribution group to a Microsoft 365 Group?
- Set-DistributionGroup -RecipientTypeDetails GroupMailbox
- Upgrade-DistributionGroup (Correct answer)
- New-UnifiedGroup -MigrateFrom
- Convert-DistributionGroup -ToUnifiedGroup
Correct answer: Upgrade-DistributionGroup
The Upgrade-DistributionGroup cmdlet converts eligible classic distribution groups to Microsoft 365 Groups, preserving membership while adding the full collaboration workspace.
Question 5: What is the maximum number of members that can be added to a Microsoft 365 Group?
- 1,000 members
- 10,000 members
- 100,000 members (Correct answer)
- There is no hard limit
Correct answer: 100,000 members
Microsoft 365 Groups support up to 100,000 members, which is a key consideration when choosing between a Microsoft 365 Group and other group types for large organizations.
Question 6: An administrator wants to prevent a specific Microsoft 365 Group from appearing in the Exchange Global Address List. Which cmdlet accomplishes this?
- Set-UnifiedGroup -HiddenFromAddressListsEnabled $true
- Set-UnifiedGroup -HiddenFromExchangeClientsEnabled $true (Correct answer)
- Set-AddressList -ExcludedGroups <GroupName>
- Set-UnifiedGroup -ShowInAddressList $false
Correct answer: Set-UnifiedGroup -HiddenFromExchangeClientsEnabled $true
Set-UnifiedGroup -HiddenFromExchangeClientsEnabled $true hides the group from all Exchange clients including the GAL in Outlook, while HiddenFromAddressListsEnabled only hides it from address book lookups.
Question 7: Which Microsoft 365 Groups feature allows administrators to classify groups (e.g., Confidential, Internal) for governance and compliance purposes?
- Group Labels
- Sensitivity Labels (Correct answer)
- Retention Labels
- Information Barriers
Correct answer: Sensitivity Labels
Sensitivity Labels (from Microsoft Purview) can be applied to Microsoft 365 Groups to enforce classification-based protections such as privacy settings, guest access restrictions, and Teams channel controls.
MS-203 Microsoft 365 Groups and Collaboration 2
An administrator needs to add a naming policy that appends a department prefix to all newly created Microsoft 365 Groups.
Where is this configured?