Office 365 Usage Location and Skype for Business Online

Questions often arise in Skype for Business Online (SfBO) administration regarding the a user’s registered “location”.  In the SfBO admin center we see it as the location field in the user listing as shown here:


This subtle setting is important for the voice Phone System calling plan (PSTN) service configuration in SfBO because it restricts what phone numbers can be assigned to a user, and their associated emergency location.  Specifically, only registered emergency locations (addresses) that belong to the same country as a users’ location can specified for that user. In addition, when assigning phone numbers to a user, only acquired numbers in the same country are available for assignment.

This is usually only confusing for multi-national companies when the location attribute is not accurate, or when user relocations occur.

So Where does this Location Come from and How is it Set?

Like many user configuration properties, this Location property is sourced from the underlying Office 365 tenant user configuration, which is sourced from the underlying associated Azure AD tenant.

In Office 365 it is known as the UsageLocation attribute.  It is an important attribute in Office 365 because it determines what Office 365 Licenses and and associated features can be assigned to a user based on geographic availability and laws. For example, a Calling Plan add-on service might not be available in Australia, and if a user has an Office 365 Location of Australia, that user account cannot be assigned the Domestic and International Calling Plan add-on available to the tenant license.

Where is this setting in the Office 365 Portal?

Note, the UsageLocation setting is different from the address configured in the Contact Information configured on the user (and it does not have to be the same). Because this setting directly impacts what Office 365 licenses are available to a user, it is the first setting displayed in the O365 Admin Portal by navigating to Users | Active users | select a user | Edit Product Licenses as shown here:


Where did the Value for this Setting Originally Come From?

This is a common question because the UsageLocation was usually set without explicit attention to what the default value should have been when the Office 365 tenant was originally provisioned.

There are two primary origins for the user value of UsageLocation:

  1. Local Active Directory
    • If the underlying Azure AD tenant is synchronized from on-premises AD (e.g. using AAD Connect), this value was likely set from the directory synchronization.
    • By default, I believe AAD Connect configuration uses the on-premises msExchUsageLocation attribute to populate the UsageLocation by default, but do more research on that because that can depend on the environment. Either way, you can customize an AAD Connect synchronization rule to use whatever attribute you want.  A good article on doing that is available here:
  2. A Default Setting in the Office 365 Tenant
    • With a pure online Office 365 tenant, there was default setting for the tenant location that was the default UsageLocation of users that corresponded to the country tenant Organization profile.  I can no longer find this setting in the Office 365 Admin Center. I believe it is moved to the “Country or region” setting in the associated Azure AD tenant as shown here in the AAD Admin Portal:


How do I change it?

If it is a one-off change, or only a few users need that Location updated, it can be done through the Office 365 Admin Portal as shown above.

There is a good chance you will need to use PowerShell for anything more than a handful of user changes.  There are plenty of PowerShell examples of doing this, and/or assigning Office 365 licenses, so I won’t re-hash it here, but for reference, the Office 365 / Azure AD v1 (aka MSOnline) module has two cmdlet’s that can be used to read and write this setting on a user:

> Get-MsolUser -UserPrincipalName | select UserPrincipalName, UsageLocation

> Set-MsolUser -UserPrincipalName –UsageLocation <2 letter ISO Country Code>

There are equivalent cmdlet’s in the Microsoft Azure AD v2 PowerShell Module.

Leave a Reply

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>