Home

Set msoluser usagelocation

Set-MsolUserLicense : A parameter cannot be found that

  1. You can assign licenses only to user accounts that have the UsageLocation property set to a valid ISO 3166-1 alpha-2 country code. For example, US for the United States, and FR for France. OK, so US for United States
  2. Set the user location to France (Set-MsolUser -UsageLocation FR). Change properties for a specific set of user accounts To change properties for a specific set of user accounts, you can use a combination of the Get-MsolUser, Where, and Set-MsolUser cmdlets
  3. g it is a geographic location you want to set). New-MsolUser does use -UsageLocation that you can use to set the same thing when provisioning new users via PS
  4. Get-MsolUser -UserPrincipalName user1@contoso.com | Set-MsolUser -PreferredLanguage it-it Get-MsolUser -UserPrincipalName user1@contoso.com | Set-MsolUser -UsageLocation IT Synchronized identity model. To sync the settings by using an on-premises instance of Active Directory, run the following example cmdlets after you substitute the actual.
  5. 1) In O365 via Set-MsolUser (currently commented below). Your script will have to connect to O365, if you go this route. If you're using this in a licensing script, start a five-second sleep after you set UsageLocation; 2) In AD via Set-AdUser. Azure AD Connect subsequently will write the AD value of msExchUsageLocation to O365's UsageLocation

Configure Microsoft 365 user account properties with

Set-MsolUser user@domain.com $upn -UsageLocation US All countries follow the 2-letter ISO code standard - a list of those can be found here. Now, we're using PowerShell - we want to actually bulk assign licenses and locations, not just do single users. To assign the US location to all of your tenant users, use the following command Sync UsageLocation from Active Directory. Hello, When using Office 365, you need to have some kind of sync engine. the preferred one from Microsoft is Azure Active Directory Connect ().By default, it sync a lot of attributes, but each time you assign a license on a user, you still need to specify a Usage location, and then, a license SKU Set-Msoluser -UserPrincipalName $_.UPN -UsageLocation IE -Title Driver -ObjectId (Get-MsolUser -UserPrincipalName $_.UPN).objectid} OR If you want to edit all user Note for future reference: Open a persistant session to the exchange.$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri -Credential.

UsageLocation is a parameter for Set-MsolUser, for example: Set-MsolUser -UserPrincipalName user@domain.com -UsageLocation US If you need more help with the licensing process just do a quick search on the internet, there are lots of scripts published PS C:\> New-MsolUser -UserPrincipalName davidchew@contoso.onmicrosoft.com -DisplayName David -PreferredDataLocation EUR This command creates a user whose user principal name is jdavidchew@contoso.onmicrosoft.com, display name is David, and preferred data location is EUR

Office 365 UsageLocation, Bulk Powershell

UsageLocation. The Usage property contains a 2-letter ISO country code like 'US' or 'DE'. This attribute is the one needed while assigning a license to a user in office 365. Some features in Office 365 are not allowed in certain countries and Microsoft determines this with the help of the UsageLocation property After installing the MSOnline Sign-In Assistant and Azure PowerShell Module on a computer, go to start > search > type Windows Azure Active Directory Module, right click on the shortcut and then click Run As Administrator to open Azure PowerShell window in an elevated mode. Next, you'll need to use Connect-MSolservice to. Microsoft Azure Active Directory Module for Windows PowerShell . Contact Us. Terms of Us

Set-AzWebApp -name Anything Microsoft and other stuff on the side-Enc UTF8 -include Cloud,Security,Onprem | Set-MsolUser -UsageLocation FI -PreferredLanguage E The most frequest gripe I hear from customers regarding Office 365 is license management. Managing licenses manually through the MOP for one or two users is fine. Managing licenses for 15,000 users is a bit more involved. This post deals with bulk license assignment using a CSV input file. 1. Log on to a machin The Set-MsolUser cmdlet modifies a user object. Use this cmdlet only for updates to basic properties. Update the licenses, password, and User Principal Name for a user by using the Set-MsolUserLicense, Set-MsolUserPassword and Set-MsolUserPrincipalName cmdlets. EXAMPLES Example 1: Block credential for a use Posts about Set-MsolUserLicense written by Johan Dahlbom. Important note: The end of an era with licensing scripts is near and the beginning of a new one with Azure AD Group Based Licensing is here. Group Based Licensing is now in preview and currently requires a paid Azure AD Subscription Assign License to Office365. Okay what I'm trying to do is combine a script running on a Schedule Task and a manual script to one Schedule Task script. Each script works by themselves. Here is the script that runs on a task. Get-MsolUser -UnlicensedUsersOnly -MaxResult 20000 | Where { ($_.UserPrincipalName.EndsWith ( @domain.edu ))

This tutorial is about assigning Microsoft Office 365 Licenses through a Powershell Scipt in a Runbook in Azure Automation.If you are managing an Office 365 tenant with Microsoft Office 365 E5, E5 or Azure AD Premium (P1) you are in the lucky situation licenses can be based on groups. But if you are using another product (eg. the Micrsoft Office 365 Business Suites) you only can assign license. Problem with setting the user's UsageLocation attribute in Set-MsolUser cmdlet. Olevo asked on 10/14/2015. Microsoft 365 Azure. 5 Comments 1 Solution 599 Views Last Modified: 10/19/2015. The Azure Active Directory Sync tool (aka DirSync) already has been setup here to synchronize on-premises Active Directory users to Office 365

So, a million years and tens of thousands of lines of code ago, I wrote a script for a customer to populate the Office 365 UsageLocation property (Set-MsolUser -UsageLocation) with the ISO country codes from Active Directory. In Office 365, UsageLocation is used to determine what features are available to your users Set-MsolUser -UserPrincipalName John.smith@contoso.com -UsageLocation US Then set the license. Set-MsolUserLicense -UserPrincipalName John.smith@contoso.com -AddLicenses XXXXXXX:DEVELOPERPACK The above command will assign all the services assigned with this license option to user. You can check the assigned services in the office 365 portal

Set language and region settings for Office 365 - Office

  1. Set-MsolUser -UserPrincipalName username@office365domain.co.uk -UsageLocation UK You first need to set the users to their local location in my case UK. Set-MsolUserLicense -UserPrincipalName username@office365domain.co.uk -AddLicenses OFFICE365DOMAIN:O365_BUSINESS_ESSENTIALS This command assigns the licesnes you will nee
  2. when I run Set-MsolUser -UserPrincipalName user@domain.com-UsageLocation US I get access denied, I've tried with a few different users, I've also tried -assignlicenses with our correct sku My large plan is to be able to script assigning a o365 license to a group of users,but I always to to start small to make sure my basic commands working.
  3. Set-MsolUser -UserPrincipalName spdev001@spdevs001.onmicrosoft.com -LastName Mohan Bansal -DisplayName Prashant Mohan Bansal Usage Using this command we can modify an existing User in our O365 Account specified by parameter UserPrincipalName and providing its properties like Display Name, Last Name and so on that.
  4. I have lists of the UserPrincipalNames of each group that needs the licensing changed. I attempted the command: Get-Content C:\Scripts\grads.txt | Set-MsolUserLicense -UserPrincipalName $_.UserPrincipalName -AddLicenses xxxx:EXCHANGESTANDARD_STUDENT. (with our institution name in place of the x's)
  5. There are several scenarios where you might need to assign an Office 365 license to a user. The specific scenario in this blog article is that you're migrating an Exchange Server 2010 on-premises environment to Office 365
  6. istrator of a large tenant with several different e-mail domains for people in different countries. Manually setting a UsageLocation, which is required for license activation, for them all individually is unrealistic. PROBLE

Hi, Again Johan the author at 365lab.net wrote a nice script. It will change user license based on AD Group Membership. [crayon-60c780356135c168793437/ There's the additional bug (again, IMHO) of putting the UsageLocation in there twice. The shim doesn't like that either. Then the rest goes downhill from there. As a more immediate workaround, remove the resource assignments from this user for the two licenses. Then re-add one at a time. That should proces Set-MsolUser -UserPrincipalName {UserPrincipalName} -UsageLocation {UsageLocation} Set-MsolUserLicense -UserPrincipalName {UserPrincipalName} -AddLicenses {AccountSkuId} -LicenseOptions ${NewSkuDefinitionName} For example: Set-MsolUser -UserPrincipalName 365Test1@fqdn.com -UsageLocation GB Set-MsolUserLicense -UserPrincipalName 365Test1@fqdn.

Set-MsolUser : You must provide a required property: Parameter name: ObjectId At line:2 char:1 + Set-MsolUser -UserPrincipalName $_.UserPrincipalName -UsageLocation Set-MsolUserLicense: You must provide a required property: Parameter name: UsageLocation as shown in the following screenshot: You have to set the User Location (as can be seen in the GUI) and to achieve this you have to use the Set-MsolUser command. When the User Location is set you can assign a license

PowerShell (Part 4) - Commands - Samir Daoudi's Technical Blog

O365 UsageLocation & Country Codes - ExchangeMaste

  1. Centers in the left menu and open the Skype & teams ad
  2. get-msoluser | where{$_.userPrincipalName -like *@contoso.co.uk} | set-msoluser -Usagelocation GB When I run this in Azure, I get a failure as below: The term 'get-msoluser' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path.
  3. Set-MsolUser -userprincipalname -User@domain.com -UsageLocation GB I have a script that updates each users ad profile using csv, and wanted to incorporate the usagelocation in that, however as it stands, the ps script is the only way to update this. Any Ideas would be greatly appreciated
  4. set-msoluser-UserPrincipalName $ Userupn-usagelocation FI write-host Location for $ User. emailaddress has been set to Finland.-foregroundcolor Green. write-host ----- $ CurrentSKUs = (Get-MsolUser-UserPrincipalName $ Userupn). Licenses. AccountSKUID write-host $ User. emailaddress has $.
  5. es.
  6. Introduction. Bulk assigning customized licenses in office 365 using PowerShell is one of those rare asked that customer can ask you to do based on their business and technical requirements. I have been working with many enterprise customers and many of them come up with the same request to only assign the license for specific workloads in Office 365 as they do not prefer to assign the license.
  7. Office 365 includes two infrastructures that can manage by using PowerShell: Office 365 and Exchange Online. When we use the term Office 365 the meaning is the part that serves as an envelope to all other Office 365 Services/Applications. This part includes components such as user and group object (Windows Azure Active Directory.

Listing Office 365 cmdlets. This command returns all MSOnline module cmdlets. You can also list the number of cmdlets in the module with this command: (Get-Command -Noun *MSOL*).count. 1. (Get-Command -Noun *MSOL*).count. Total count of Office 365 cmdlets. Now we are ready to manage Office 365 licenses with PowerShell Get-Content C:\Users\Victor\Office365userlist.TXT | ForEach {Set-MSOLUser -user $_ -UsageLocation US; Set-MSOLUserLicense -user $_ -AddLicenses contoso:ENTERPRISEPACK} You can use a .TXT or a .CSV for this purpose, however for a TXT file you'll need to line separate them. For a CSV, you can comma delimit or use a delimiter.

Cómo dar de Alta Usuarios en Office 365 con PowerShellWindows Azure Active Directory Module for Powershell ile

Tag Archives: Set-MsolUser Office365. Password never expire in Office 365. January 23, 2015 jaapwesselius 5 Comments. When creating user accounts and Mailboxes in Office 365 the default Microsoft password policy is applied, which means you have to change your password every 90 days Then (without re-open the remote session) we execute some commands using set-msoluser for each and every user in the array, by meaning of a loop. However, after 15 processed users, we get the following error: set-MsolUser : You have exceeded the maximum number of allowable transactions. Please try again later

Get-MsolUser (MSOnline) Microsoft Doc

  1. --> Settings --> Org Settings --> Modern Authentication and make sure modern authentication is enabled for your tenant. Older tenants won't have this enabled by default
  2. Please specify one of the All or. MaxResults parameters. help. Hi, Use the following command. Get-MsolUser -All | Set-MsolUser -UsageLocation GB. The -All switch will bring back all of the users, at least then you won't have to know how many users you have to the specify a limit. GB = Location
  3. Sets mandatory attribute UsageLocation for the user in Office 365 based on local AD attribute Country (or default) If switch -MasterOnPremise has been used: Assigns Office 365 licenses to the user based on an AD-attribute and reports back to the same attribute if a license was successfully assigned. Set-MsolUser -UserPrincipalName user.
  4. Set-msoluser: why Access Denied? Ask Question Asked 3 years, 10 months ago. Active 3 years, 10 months ago. Viewed 6k times 1 I have an Azure account with a user rmuser that I've created specifically for automated shutdowns of VMs. That user's password expired so VMs stopped being shut down
  5. Hi Iwishiweresmarter, Yes, there is. You can try the following command: Get-Content c:\test\users.txt | ForEach {Set-MsolUser -UserPrincipalName $_ -UsageLocation US; Set-MsolUserLicense -UserPrincipalName $_ -AddLicenses tenant:ENTERPRISEPACK; Set-MailboxRegionalConfiguration -Identity $_ -Language 1033 -TimeZone Eastern Standard Time
  6. Issue For many organizations, different classes of users will get different Office 365 licenses and access to different services within each license. For large and medium organizations, object management software is normally the best option for managing user licensing in Office 365. Microsoft Identity Manager (MIM) is an application that can maintain Office 365 account licensing
Office 365 のユーザーのタイムゾーン / 言語設定を PowerShell で設定 at SE の雑記

Managing MS Online Users with PowerShell - TechNet

  1. Provisioning and Licensing Office 365 Accounts with PowerShell. The Office 365 platform provides a PowerShell module that can be used to provision and manage user accounts. You can even automate the process of assigning licenses to users in the cloud using the cmdlets in this module. However, the method you'll need to use to get your users.
  2. g user John Smith is located in the United States, you can run the following command to set the UsageLocation attribute: Set-MsolUser -UserPrincipalName JohnSmith@<tenant>.onmicrosoft.com -UsageLocation US Afterward, you can use the Set-MsolUserLicense cmdlet with the -AddLicenses parameter to assign the license, like this: Set.
  3. service and Exchange Online Services. I have tested the cmdlets such as Get-MsolUser and they work fine. However, when I try to run the comm..

Office 365 Usage Location and Skype for Business Online

Hi everyone, just came across this issue myself, and found an approach that might help others around this issue. (Of course, this should only be useful to those who have a compelling reason to keep using the AzureAD module, instead of the Microsoft Graph PowerShell module.). This workaround makes use of the fact that the ExtensionProperty parameter for Set-AzureADUser, which was probably. Set-MsolUser -UserPrincipalName $_.email -UsageLocation US -ErrorAction SilentlyContinue Set-MsolUserLicense -UserPrincipalName $_.email -AddLicenses $_.license -ErrorAction SilentlyContinue catc i've been playing around with this and found that it's the 'sharepointenterprise' entry that is causing the trouble. if i run the command with just that option it fails. if i run the command with just the exchange option it succeeds. however it looks to be spelled correctly, when i run this command just click edit side to role and assign Global Admin (Password admin if you select Customised Admin Rights), then click OK and close

Bulk Assign Licenses in Office 365 Using PowerShel

Contribute to Uninett/office365 development by creating an account on GitHub. You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window I am using this powershell script below to license bulk users in office365 by .csv file. The script will only work if the .csv file header is: UserPrincipalName. example@jackson.k12.ms.us. But our .csv is formatted: Alias,UPN

Sync UsageLocation from Active Directory - IT for

Edit MSOL user details using CSV and Powershell

Get-MsolUser -All -Department Administration -UsageLocation CH -UnlicensedUsersOnly | Set-MsolUserLicense -AddLicenses wechsler:ENTERPRISEPREMIUM. Now you have used the PowerShell to investigate the license allocation in a Microsoft 365 environment! Congratulations! I hope this article was useful. Best regards, Tom Wechsler Hi, Since Office 365 projects started, setting users` licenses with scripts has been somewhat of an issue. There are great scripts out there to automate assigning licenses to users, but the prerequisite of assigning an Office 365 license to a user is to choose the Usage Location for that user. When dealing with several dozens Continue reading Setting Office 365 UsageLocation value using. Set-MsolUser -UserPrincipalName BrianJ@MOD873457.onmicrosoft.com -UsageLocation US Set-MsolUserLicense -UserPrincipalName BrianJ@MOD873457.onmicrosoft.com -AddLicenses MOD873457:ENTERPRISEPREMIUM And in picture

Bulk Update User information in Microsoft 365 Exchange

Set MsolUser disable. The Set-MsolUserLicense cmdlet updates the license assignment for a user. This can include adding a new license, removing a license, updating the license options, or any combination of these actions Example 1: Remove a user (UsageLocation must be set) Set the Usage Location for a specific Office 365 User: Set-MsolUser -UserPrincipalName -UsageLocation . Get a list of Domain Names assigned to your Office 365 Tennant: Get-MsolDomain. Set a default Office 365 Domain Name: Set-MsolDomain -Name o365.davidatkin.com -IsDefault. Remove a Domain Name from your Office 365. Set-MsolUser -UserPrincipalName <UserPrincipalName of the User> Exchange: Couldn't find object <ObjectID>. Please make sure that it was spelled correctly or specify a different object. There is another object that is referenced from this object (such as permissions), and that object can't be found In order to help us do this, we need you to tell us which usageLocation (country code) is correct for your region. An up to date list of usageLocation's can be found on the link below (Office 365 uses the Alpha-2-code): If you need any assistance please do not hesitate to contact us at: support@iamcloud.com. Did you find it helpful

Configuring SAML SSO for Office 365

Office 365 UsageLocation, Bulk Powershell. Good afternoon Spiceheads!I am racking my brain on trying to use powershell to bulk change my O365 users usagelocation. The msExchangeUsageLocation is not an attribute in my AD i can changed/edit.I have spent a day or two googling, reading, testing UserPrincipalName} | Set-MsolUser-UsageLocation < your region > #assing a licence for each mailbox $ users | % {Set-MsolUserLicense-UserPrincipalName $ _. UserPrincipalName-AddLicenses your licence name} If you want to convert mailboxes to shared mailboxes make sure that the property LicenseReconciliationNeeded is set to false after the. This image was selected is show placement and can be replaced with another full slide image. The Amazing World of PowerShell with Office 365 (and Azure Part 3: Assign Office 365 License to your users via PowerShell. Step 1: Launch ' PowerShell ISA ' in elevated mode ( Run as Administrator) Step 2: Create or Save a CSV with the ' UserPrincipalName ' of the users you want to assign the license ( Example as below ). Step 3: Copy & Paste the PowerShell Script below on to your PowerShell. When you have done that, just to put in your O365 credentials and UsageLocation in the script and then you're all set to schedule the script. LicenseO365Users.ps1 #2016-01-07 - Updated the script with a new function to support nested groups. #Import Required PowerShell Modules #Note - the Script Requires PowerShell 3.0

License Enabling Script - social

The Basics Recently I've had to explore the dark art of license assignment using Powershell. It's not particularly well documented so this might help you Displaying a list of the current licensing assignment is pretty straightforward. Get-MsolUser can be used to return information on an individual or a list of users. Get-MsolUser -All run on [ Set-MsolUserLicense : A parameter cannot be found that matches parameter name 'UsageLocation'. Really, Microsoft? Is it a required parameter or is it not a parameter? Make up your minds! Turns out, it's a parameter of the Set-MsolUser cmdlet: PowerShell Commands Set-MsolUser -UserPrincipalName johndoe@example.com -UsageLocation U

Step 1: Launch ' PowerShell ISA ' in elevated mode ( Run as Administrator) Step 2: Create or Save a CSV with the ' UserPrincipalName ' of the users you want to assign the license ( Example as below ). Step 3: Copy & Paste the PowerShell Script below on to your PowerShell ISA window & Run the script. For Usage Location, Microsoft Follows. PowerShell: Set Location. Office 365 requires all users to have a Location before we can assign a license. Feel free to leverage Export and Import CSV. Commandlet: Set-MsolUser -UsageLocation. For a specific user the command will be: Command: Set-MsolUser -UserPrincipalName youruser@yourdomain.com -UsageLocation NO. With Imported CSV get-msoluser | where{$_.userPrincipalName -like *@contoso.co.uk} | set-msoluser -Usagelocation GB When I run this in Azure, I get a failure as below: The term 'get-msoluser' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path. You can bulk assign licenses to all users in your MSOL subscription if needed from a single script. But are you sure you'd want to? Would you really want to indiscriminately license every MSOL user with the same SKU and usage location? You do? No you don't! I'd strongly recommend bulk assigning licenses from CSV file instead, but if you're happy to proceed then use the following procedure

New-MsolUser (MSOnline) Microsoft Doc

New-MsolUser.xlsx. FirstName,LastName,DisplayName,UserPrincipalName,UsageLocation,AccountSkuId,MobilePhone,PhoneNumber,Title,Department,StreetAddress,PostalCode,City. @Kaspar_Danielsen The simplest method is via portal.azure.com. Navigate to Azure Active Directory->Users, then click Multi-Factor Authentication in the upper menu bar.Search for the username, then select it. You can then click Disable under quick steps. If you're using Conditional Access policies to enforce MFA, then the settings above are not used. In this case, you can remove MFA via Po You can also set a phone number for the account by running the following command: PowerShell Copy. Set-MsolUser -UserPrincipalName <upn> -PhoneNumber <phone number>. The device account needs to have a valid Microsoft 365 or Office 365 license, or Exchange and Microsoft Teams or Skype for Business will not work Microsoft have made it really easy to perform bulk migrate migrations and assign licenses in Exchange Online.You can export a csv and use it twice. The first csv will have the following headingsemailaddresssean.ofarrell@contoso.comciaran.ofarrell@contoso.comdean.jones@contoso.comtecnicalfellow@contoso.com You can then upload the file then via the following option in Exchange Online And then to.

Country code - Microsoft Communit

Skype for Business Online (Plan 2) MCOSTANDARD. Office Online (can't be assigned without Sharepoint Online) SHAREPOINTWAC. SharePoint Online (Plan 2) (include Onedrive) SHAREPOINTENTERPRISE. Exchange Online (Plan 2) EXCHANGE_S_ENTERPRISE. E1 Service Plans same Issue empty results . i need to share some thoughts with you. Get-MsolUser does not contains CustomAttribute7 Property but Get-mailbox . so what i did is get the UserPrincipalName from Get-MsolUser then bind it to the Get-mailbo First published on TECHNET on Dec 29, 2017 *** 7/2/2018 - Update - just to address some confusion - the guest access to Project Online does not allow the guest to also have access to and download the Project Online Desktop Client application - that requires a full paid license. If you try to navig..

Get-MsolUser -UserPrincipalName user1@contoso.com | Set-MsolUser -UsageLocation IT. And wait. It can take a few hours to sweep through and do everything. Last Words. As you can see, unless you live in the US or, possibly, Canada, regionalisation is a bit of a mess. To ally this Microsoft seem to have assumed that the friendly date format is. set-MsolUser -UserPrincipalName <UserUPN> -UsageLocation CA But wait CA is a the country identifier for Canada, but a Language identifier for Catalan (Spain)! So we looked at the following ways we could quickly update all our client's users

In Information, Scripting. Be the first to vote! Here are some handy one-liners that you may find useful when managing Office 365. Ok, some of them are a few lines, but they're still handy. Connecting to things. Connect to the Microsoft Online Services interface for account management tasks. Connect to the Microsoft Exchange Online interface. Hi, we are rolling out MS Teams to our users. In doing so we are only enabling users with a E3 license and ONLY MS Teams. We got that going with scripts and Powershell. Now we want to add Streams to these users. I could not find a way or command to add that to users that are already enabled. Go.. Now that we've set an attribute to be excluded by the filter, let's make the dynamic group in Azure to assign those licenses to. Since I'm a Shell kindof guy, here's a sample to create the group. New-AzureADMSGroup -DisplayName Licensing - E3 `. -Description Dynamic group created to automatically assign licenses to mail. is there a script or command by power shell that we can allocate Exchange Online license alone in Office 365 Enterprise E3 for a group of people The purpose of this script is to automate the process of setting the location and Office 365 license for users, using a local Active Directory to specify the users. You can of course just get all unlicensed users in Office 365 and licensed them, but this script is designed to allow you to control exactly which users are being licensed using.

Assign Office 365 License via PowerShell. Ákos Bakos September 9, 2015 0. You can assign a license to a user using the Microsoft Portal, just select the user and in the Action Pane select USERS -> Active Users. Depending on the licenses you got available you can assign it (in this example a Visio pro Office) and set the user's location (in. Azure Active Directory Licensing Microsoft has made significant strides with licensing options for Office 365. Licensing options can be found in the new Active Directory snap-in within Azure. This new snap-in allows organizations to control both licensing options and their associated services. The Azure Active Directory snap-in can be accessed by following these steps: Loginpos Get-MsolUser -All | Set-MsolUser -UsageLocation GB The -All switch will bring back all of the users, at least then you won't have to know how many users you have to the specify a limit GB = Location If you want to check what is currently set, use the first part of the command before the PIPE (|) James