MS-700 · Question #173
MS-700 Question #173: Real Exam Question with Answer & Explanation
This question tests knowledge of Azure AD (Microsoft Entra ID) Group Naming Policy, specifically how to configure prefixes and suffixes using both dynamic user attributes and fixed custom strings to enforce a consistent naming convention for Microsoft 365 Groups backing Teams.
Question
You have a Microsoft 365 E5 subscription that uses Teams. You need to implement a consistent team naming strategy that meets the following requirements: - All team names must start with the department name of the user that created the team. - All team names must be followed by the word Department. How should you configure the group naming policy? To answer, drag the appropriate configurations to the correct requirements. Each configuration may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content. Note: Each correct selection is worth one point.
Explanation
This question tests knowledge of Azure AD (Microsoft Entra ID) Group Naming Policy, specifically how to configure prefixes and suffixes using both dynamic user attributes and fixed custom strings to enforce a consistent naming convention for Microsoft 365 Groups backing Teams.
Approach. The Group Naming Policy in Azure AD supports two types of prefix/suffix tokens: Azure AD user attributes (e.g., [Department], [Country]) and fixed custom strings. For requirement 1 - names must START with the creating user's department - you configure a PREFIX using the Azure AD attribute '[Department]', which dynamically pulls the value from the team creator's profile. For requirement 2 - names must be FOLLOWED by the word 'Department' - you configure a SUFFIX using a fixed custom string 'Department'. The resulting team name format becomes: [Department]<TeamName>Department, e.g., 'EngineeringProjectAlphaDepartment'.
Concept tested. Azure AD / Microsoft Entra ID Group Naming Policy configuration - distinguishing between dynamic attribute-based tokens (e.g., [Department]) used as prefixes and fixed custom string literals used as suffixes, and mapping each to the correct policy field (Prefix vs. Suffix) in the Microsoft 365 Admin Center or Azure portal.
Reference. Microsoft Learn: Enforce a naming policy for Microsoft 365 groups in Azure Active Directory - https://learn.microsoft.com/en-us/entra/identity/users/groups-naming-policy
Topics
Community Discussion
No community discussion yet for this question.