Microsoft 365 Certified: Administrator ExpertDeploy and manage a Microsoft 365 tenantMedium
A Microsoft 365 administrator is planning to implement a new policy for Microsoft 365 Groups. The policy requires that all new groups created must have a specific prefix ('PROJ-') and suffix ('-GR') to ensure consistency and easy identification. Additionally, a list of specific words (e.g., 'Confidential', 'HR') must be blocked from being used in group names. Which feature should the administrator configure?
- AAzure AD Conditional Access policies
- BMicrosoft Purview Data Loss Prevention (DLP)
- CAzure AD Naming Convention for Microsoft 365 Groups
- DMicrosoft 365 sensitivity labels
Show answer & explanationAnswer & explanation
Correct answer: C. Azure AD Naming Convention for Microsoft 365 Groups
Azure AD Naming Convention for Microsoft 365 Groups allows administrators to enforce a consistent naming policy for new groups, including specifying a prefix, suffix, and a list of blocked words. This directly matches all the requirements.
Why the other options are wrong
- A. Conditional Access policies control access to resources based on conditions, not group naming.
- B. DLP policies prevent sensitive data from being shared, not control group naming conventions.
- D. Sensitivity labels classify and protect content within groups, but do not enforce naming conventions for the groups themselves.
Azure AD Naming Convention for Microsoft 365 Groups
A feature in Azure AD that enforces a naming policy for Microsoft 365 Groups, allowing administrators to define prefixes, suffixes, and a list of blocked words for group names.
- Ensures consistent naming for easier identification and management.
- Prevents inappropriate or sensitive words in group names.
- Applies to groups created in various Microsoft 365 applications.
Memory trick: Think of the Naming Convention as the 'name tag' police for your Microsoft 365 Groups.