Usage Location Change by Assigning Licence

%3CLINGO-SUB%20id%3D%22lingo-sub-1157181%22%20slang%3D%22en-US%22%3EUsage%20Location%20Change%20by%20Assigning%20Licence%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1157181%22%20slang%3D%22en-US%22%3E%3CP%3Ehi%20all%2C%20I've%20noticed%20some%20odd%20behaviour%20when%20assigning%20(normally)%20Power%20BI%20License's%20to%20users.%20It%20seems%20to%20change%20the%20usage%20location%20value%20in%20AAD%2FOffice%20365.%20Mailbox%20and%20OneDrive%20seem%20to%20stay%20in%20original%20region%20but%20not%20the%20Usage%20Location.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESituation%3C%2FP%3E%3CP%3E*%20AADConnect%20synced%20AD%20Users%3C%2FP%3E%3CP%3E*%20Users%20existing%20in%20Office%20365%20longer%20than%2012%20months%3C%2FP%3E%3CP%3E*%20Users%20Always%20set%20to%20AU%20Usage%20location%3C%2FP%3E%3CP%3E*%20Assign%20PowerBI%20Pro%20Licence%20(usually%20using%20admin.microsoft.com%20%3CU%3ENewer%3C%2FU%3E%20Assign%20Licences%20Method%20from%20Licencing%20Screen%3C%2FP%3E%3CP%3E*%20Cannot%20guarantee%20I%20haven't%20used%20the%20legacy%20method%20of%20just%20going%20into%20a%20user%20in%20admin.microsoft.com%20and%20assigning%20it%20directly%3C%2FP%3E%3CP%3E*%20Some%20time%20later%2C%20Usage%20Location%20US%20(Or%20in%202%20users%20cases%20GB)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt's%20taken%20me%20awhile%20to%20figure%20out%20it%20was%20a%20PowerBI%20Change%20but%20the%202%20GB%20users%20never%20got%20PowerBI%20and%20they%20changed%20at%20some%20point%20as%20well%2C%20so%20I%20don't%20think%20its%20Power%20BI%20Licences%20exclusively%20but%20it%20seems%20to%20be%20after%20adding%2Fchanging%20some%20licences%20via%20some%20method%20results%20in%20a%20Usage%20Location%20Change.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAAD%20Audit%20log%20for%20the%20two%20most%20recent%20users%20is%20doesn't%20say%20anything%20about%20location%20change%20in%20the%20log.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20leaning%20towards%20it%20being%20the%20newer%20admin.microsoft.com%20assign%20Licence%20to%20User%3CU%3Es%3C%2FU%3E%2C%20vs%20the%20more%20legacy%20Assign%20User%20to%20Licence%3CU%3Es%3C%2FU%3E%20but%20haven't%20isolated%20it%20down%20to%20that%20level.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnyone%20else%20experienced%20this%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1157181%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdmin%20center%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EUsage%20Location%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1157214%22%20slang%3D%22en-US%22%3ERe%3A%20Usage%20Location%20Change%20by%20Assigning%20Licence%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1157214%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F40416%22%20target%3D%22_blank%22%3E%40Tim%20Lourey%3C%2FA%3E%26nbsp%3BWe%20are%20experiencing%20something%20similar!%26nbsp%3B%20We%20have%20just%20moved%20to%20Teams%20for%20calling%20and%20we%20noticed%20that%20some%20of%20our%20users%20had%20reverted%20to%20the%20US%20from%20the%20UK.%26nbsp%3B%20It%20makes%20a%20difference%20in%20teams%20when%20making%20a%20call%20if%20you%20are%20in%20the%20wrong%20location.%26nbsp%3B%20Thanks%20for%20posting%20this%2C%20tomorrow%20if%20I%20have%20time%20I%20will%20change%20a%20couple%20of%20licences%20and%20see%20if%20I%20get%20the%20same%20result%20as%20you.%26nbsp%3B%20We%20are%20also%26nbsp%3B%3CSPAN%3EAADConnect%20synced%20AD%20Users%20its%20been%20baffling%20us%20for%20a%20few%20weeks%20now.%26nbsp%3B%20Will%20post%20back%20with%20results.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1157229%22%20slang%3D%22en-US%22%3ERe%3A%20Usage%20Location%20Change%20by%20Assigning%20Licence%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1157229%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F2552%22%20target%3D%22_blank%22%3E%40Tanya%20Denton%3C%2FA%3E%26nbsp%3Breally%20grateful%20I'm%20not%20going%20insane.%20I%20didn't%20think%20about%20Teams%20voice%20as%20we%20are%20not%20using%20it.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIts%20hunch%20but%20I%20think%20its%20to%20do%20with%20the%20Newer%20looking%20flyouts(%3F)%20like%3C%2FP%3E%3CP%3E*%20admin.microsoft.com%20--%26gt%3B%20Users%20--%26gt%3B%20Active%20Users%3C%2FP%3E%3CP%3E*%20admin.microsoft.com%20--%26gt%3B%20Billing%20--%26gt%3B%20Licences%20--%26gt%3B%20Assign%20Licence%20Screen%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Evs%20the%20older%20looking%20ones%20like%3C%2FP%3E%3CP%3E*%20admin.microsoft.com%20--%26gt%3B%20Search%20for%20a%20user%20from%20very%20first%20page%20--%26gt%3B%20User%20--%26gt%3B%20Edit%20Licences%3C%2FP%3E%3CP%3E*%20admin.microsoft.com%20(Classic%20mode)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ebut%20again%20that's%20just%20a%20hunch.%20Looking%20forward%20to%20your%20results!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1157244%22%20slang%3D%22en-US%22%3ERe%3A%20Usage%20Location%20Change%20by%20Assigning%20Licence%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1157244%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F40416%22%20target%3D%22_blank%22%3E%40Tim%20Lourey%3C%2FA%3E%26nbsp%3Bwell%20I%20would%20not%20be%20surprised%20if%20I%20was%20going%20insane%20its%20been%20confusing%20us%20for%20a%20few%20weeks%20now!%20Do%20you%20mean%20this%20screen%3F%26nbsp%3B%20If%20so%20I%20have%20just%20made%20some%20licence%20changes%20to%20a%20user%20so%20I%20will%20see%20what%20happens%20in%20the%20next%2024hrs.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%222020-02-06_22-51-49.png%22%20style%3D%22width%3A%20760px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F169540iBFAA0E1B8DBDE237%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%222020-02-06_22-51-49.png%22%20alt%3D%222020-02-06_22-51-49.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1157255%22%20slang%3D%22en-US%22%3ERe%3A%20Usage%20Location%20Change%20by%20Assigning%20Licence%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1157255%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F2552%22%20target%3D%22_blank%22%3E%40Tanya%20Denton%3C%2FA%3E%26nbsp%3BYes%20that%20screen%20is%20the%20'Newer'%20flyout(%3F)%20%2F%20screen.%20I%20think%20it%20came%20along%20with%20newer%20version%20of%20admin.microsoft.com.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20if%20you%20use%20the%20search%20on%20the%20very%20first%20page%20at%20the%20top%20in%20admin.microsoft.com%20and%20browse%20a%20user%2C%20it%20shows%20you%20the%20older%20(Classic%3F)%20looking%20user%20management%20flyout(%3F)%20%2F%20screen%20which%20I%20%3CEM%3E%3CU%3ETHINK%3C%2FU%3E%3C%2FEM%3E%20doesn't%20have%20the%20issue.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1157274%22%20slang%3D%22en-US%22%3ERe%3A%20Usage%20Location%20Change%20by%20Assigning%20Licence%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1157274%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F40416%22%20target%3D%22_blank%22%3E%40Tim%20Lourey%3C%2FA%3E%26nbsp%3B%20how%20long%20did%20it%20take%20yours%20to%20change%20after%20making%20the%20licence%20change%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1157303%22%20slang%3D%22en-US%22%3ERe%3A%20Usage%20Location%20Change%20by%20Assigning%20Licence%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1157303%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F2552%22%20target%3D%22_blank%22%3E%40Tanya%20Denton%3C%2FA%3E%26nbsp%3BI%20haven't%20timed%20it%20as%20I%20was%20just%20running%20the%20query%20every%20few%20weeks%20and%20fixed%20some%20up%20a%20few%20weeks%20ago.%20Only%20reason%20I%20figured%20it%20out%20was%20two%20users%20were%20now%20showing%20US%20instead%20of%20AU%20and%20those%20specific%20users%20got%20the%20PowerBI%20License%20which%20made%20me%20look%20down%20that%20path.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

hi all, I've noticed some odd behaviour when assigning (normally) Power BI License's to users. It seems to change the usage location value in AAD/Office 365. Mailbox and OneDrive seem to stay in original region but not the Usage Location. 

 

Situation

* AADConnect synced AD Users

* Users existing in Office 365 longer than 12 months

* Users Always set to AU Usage location

* Assign PowerBI Pro Licence (usually using admin.microsoft.com Newer Assign Licences Method from Licencing Screen

* Cannot guarantee I haven't used the legacy method of just going into a user in admin.microsoft.com and assigning it directly

* Some time later, Usage Location US (Or in 2 users cases GB)

 

It's taken me awhile to figure out it was a PowerBI Change but the 2 GB users never got PowerBI and they changed at some point as well, so I don't think its Power BI Licences exclusively but it seems to be after adding/changing some licences via some method results in a Usage Location Change. 

 

AAD Audit log for the two most recent users is doesn't say anything about location change in the log. 

 

I'm leaning towards it being the newer admin.microsoft.com assign Licence to Users, vs the more legacy Assign User to Licences but haven't isolated it down to that level.

 

Anyone else experienced this? 

6 Replies
Highlighted

@Tim Lourey We are experiencing something similar!  We have just moved to Teams for calling and we noticed that some of our users had reverted to the US from the UK.  It makes a difference in teams when making a call if you are in the wrong location.  Thanks for posting this, tomorrow if I have time I will change a couple of licences and see if I get the same result as you.  We are also AADConnect synced AD Users its been baffling us for a few weeks now.  Will post back with results.

Highlighted

@Tanya Denton really grateful I'm not going insane. I didn't think about Teams voice as we are not using it. 

 

Its hunch but I think its to do with the Newer looking flyouts(?) like

* admin.microsoft.com --> Users --> Active Users

* admin.microsoft.com --> Billing --> Licences --> Assign Licence Screen

 

vs the older looking ones like

* admin.microsoft.com --> Search for a user from very first page --> User --> Edit Licences

* admin.microsoft.com (Classic mode)

 

but again that's just a hunch. Looking forward to your results!

Highlighted

@Tim Lourey well I would not be surprised if I was going insane its been confusing us for a few weeks now! Do you mean this screen?  If so I have just made some licence changes to a user so I will see what happens in the next 24hrs.

2020-02-06_22-51-49.png

Highlighted

@Tanya Denton Yes that screen is the 'Newer' flyout(?) / screen. I think it came along with newer version of admin.microsoft.com. 

 

However, if you use the search on the very first page at the top in admin.microsoft.com and browse a user, it shows you the older (Classic?) looking user management flyout(?) / screen which I THINK doesn't have the issue. 

 

Highlighted

@Tim Lourey  how long did it take yours to change after making the licence change?

Highlighted

@Tanya Denton I haven't timed it as I was just running the query every few weeks and fixed some up a few weeks ago. Only reason I figured it out was two users were now showing US instead of AU and those specific users got the PowerBI License which made me look down that path.