Usage location is a per-user property recording the country where the user consumes services. Some Microsoft services cannot legally be provisioned without it, so a missing usage location can make a license assignment fail even though seats are available and the group is configured correctly.
Why it exists#
Service availability and compliance rules differ by country, so Microsoft requires the property before provisioning certain services. For directly assigned licenses an administrator often hits the requirement interactively; with group-based licensing the assignment is processed in the background, and the failure lands silently on the user object.
The operational pattern#
The tell is a subset of a group's members stuck in a licensing error state while the rest are fine. New accounts created by automation are a common cause: the provisioning flow sets everything except usage location, and every group-licensed service that requires it fails for exactly those accounts.
VisualizerEngine
In VisualizerEngine
Because users, memberships, and license assignments are mirrored together, the affected population is visible as a structural query rather than a per-user hunt: which direct members of licensed groups lack successful assignments. Saved searches keep the check repeatable after every onboarding batch.