MS-102 Practice Question: An admin needs to bulk assign licenses to 200…

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Use Microsoft Entra ID PowerShell script

  Why it's wrong here

  While a PowerShell script using the Microsoft Graph or MSOnline module can loop through users and assign license SKUs, this approach demands solid scripting expertise to handle authentication, pagination, error handling, and SMTP/IP deduplication—far more complex than the question warrants. The existing note correctly warns that scripting knowledge is required; but even for an experienced admin, a hand-rolled script doesn't provide declarative or automatic license management for future membership changes, making it less robust than a built-in, policy-driven method. For this bulk assignment to 200 users, it's unnecessarily error-prone and maintenance-heavy.

• ✗

  Use Azure admin center bulk operations

  Why it's wrong here

  The Azure admin center's 'bulk operations' are specifically designed for user lifecycle tasks like bulk create, bulk invite, bulk delete, and bulk restore—not for license assignment. While you can multi-select users in the Users blade and open a license panel, that is not a true bulk operation and still requires manual scrolling, scrolling, and applying to each selected user; it does not accept a CSV or an automated input to assign licenses in one step. As the existing note says, bulk operations are limited; this method becomes unwieldy and time-consuming for 200 users and lacks the self-service scalability of group-based licensing.

• ✓

  Use group-based licensing in Microsoft Entra ID

  Why this is correct

  Group-based licensing in Microsoft Entra ID is the correct, scalable approach: you create or select a security group, assign the appropriate license SKUs to that group, and Azure automatically assigns the licenses to every member of the group—and to any users added later. This declarative method eliminates the need for per-user scripting or manual clicks, and it also auto-removes licenses when users leave the group, keeping license allocation aligned with membership. For 200 users, you simply add them to the group and Azure handles the rest, making it the most efficient and maintainable solution.

• ✗

  Assign licenses one by one in admin center

  Why it's wrong here

  Manually assigning a license to each of the 200 users via the Azure admin center is not only extremely slow—requiring hundreds of navigations, searches, and confirmation clicks—but it's also highly susceptible to human error, such as selecting the wrong SKU or overlooking a user. This method provides zero automation and no ongoing management, so any future user additions or removals require repeating the same tedious process. As the existing note indicates, it is too slow; it completely fails to meet the needs of a bulk assignment scenario.

Go deeper

Related to this question