How to Bulk Import Entra Users into Dynamic Groups by Department?
You have a Microsoft Entra tenant. You plan to perform a bulk import of users. You need to ensure that imported user objects are added automatically as the members of a specific group based on each user's department. The solution must minimize administrative effort. Which two actions should you perform? Each correct answer presents part of the solution. NOTE: Each correct selection is worth one point.
Community Insight
The question tests dynamic group membership for automatic department-based assignment, and the trap is assuming manual assignment or an XML file will satisfy the minimal-effort bulk import requirement.
Learn how to automatically add bulk-imported Microsoft Entra users to groups based on department. This page establishes that dynamic user groups (C) and a PowerShell import script (D) are the correct actions for the AZ-104 scenario when the CSV file option is missing.
Many learners choose the Assigned membership type (A) because it seems straightforward, but it requires manual member management, which directly contradicts the minimize-administrative-effort requirement.
Community Discussion (9 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Dynamic User groups (C) are the only option that automatically adds users based on their department attribute, directly fulfilling the requirement to minimize administrative effort for ongoing membership. For the bulk import itself, the standard Entra portal method uses a CSV file, but that option is absent here; option D (write a PowerShell script that parses an import file) is the remaining functional import mechanism. Together, C and D enable bulk user creation and automatic department-based grouping without manual intervention.Why the Other Options Are Wrong
Option A (Assigned membership) requires manual member additions, violating the minimal-effort goal. Option B (ARM template) cannot create Microsoft Entra user objects because ARM targets Azure resources, not directory users. Option E (XML file) is incorrect because Microsoft Entra bulk import exclusively supports CSV-formatted files; an XML file will not be accepted by the bulk import feature. Thus E cannot be part of a valid solution.Community Comment Notes
Several learners, including behradcld and Mark74, vote for “CF” — dynamic groups plus a CSV file — indicating the original question likely had a CSV option that is missing from this list. As michael1msc noted, “the only option is PowerShell + CSV” when no direct CSV upload option exists, which supports choosing D in this truncated option set. Ponpon3185 added that the question does not mention the Azure portal, so “a script is needed,” reinforcing D as the practical import action among the choices given.Official Reference
Exam Strategy
Focus on the 'minimize administrative effort' phrase: it signals that automated membership (dynamic groups) beats manual assignment or custom scripting for ongoing management. Always verify file-format requirements for bulk operations—Entra bulk import uses CSV, not XML.
Frequently Asked Questions
Why are dynamic user groups better than assigned groups for department-based membership?
Dynamic groups automatically add or remove members based on attributes like department, eliminating manual updates and minimizing administrative effort.
Can an XML file be used for Microsoft Entra bulk user import?
No, Microsoft Entra bulk import only supports CSV files. XML is not a supported format for creating multiple users.
Related Analysis
Practice All AZ-104 Questions
Access 100 questions with complete answers and detailed explanations.
View Full AZ-104 Practice Test →