You have 2,500 users who are assigned Microsoft Office 365 Enterprise E3 licenses. The licenses are assigned to individual users. From the Groups blade in the Microsoft Entra admin center, you…

Question

Options

• Athe Licenses blade in the Microsoft Entra admin center
• Bthe Set-WindowsProductKey cmdlet
• Cthe Identity Governance blade in the Microsoft Entra admin center
• Dthe Update-MgUser cmdlet

• A
  83% (52)
• B
  5% (3)
• C
  3% (2)
• D
  10% (6)

Explanation

Explanation

Option A is correct because the Licenses blade in the Microsoft Entra admin center allows administrators to bulk-select all 2,500 users who have directly assigned E3 licenses and remove them in a single operation, requiring minimal administrative effort without scripting or complex workflows.

Why the distractors are wrong:

• Option B (Set-WindowsProductKey) is a PowerShell cmdlet used for Windows OS product key activation - it has no relevance to Microsoft 365 license management whatsoever.
• Option C (Identity Governance blade) handles access reviews, entitlement management, and privileged identity management - it is not designed for bulk license removal tasks.
• Option D (Update-MgUser cmdlet) could technically remove licenses via PowerShell scripting, but it would require writing and running a script against 2,500 individual users, which is significantly more effort than a GUI-based bulk action.

Memory Tip

Think "License problems → Licenses blade" - when a question involves managing, assigning, or removing licenses at scale in Entra, the Licenses blade is almost always the most direct GUI path. If a PowerShell option is offered alongside a GUI option and the question asks for least administrative effort, the GUI bulk tool typically wins over scripting individual records.

No community discussion yet for this question.