Azure AD weird sync and usage location attribute mismatch

Question

Hello,

I am facing really strange behavior from one of our test accounts. This account was created in on-premises and synced to Azure AD, then licenses for Microsoft 365 E5 and Microsoft Teams Domestic and International Calling Plan have been assigned via Azure Portal. Before assignment of licenses user must have location specified, so I selected United States in Azure AD. And now fun begins:

1. I wanted to assign voice number in admin.teams.microsoft.com console to that test user so I checked that user is there and that location is correct, the number is correct (unassigned, correct US emergency address, available usage, license usage etc. -> everything correct -> US configured everywhere).
2. So I tried to assign the number but I have got an error -> 
   So I started to wonder if Microsoft Teams really cares about case sensitive letters or what is going on.
3. I went to admin.microsoft.com to check user settings there and just to make comparison with other working accounts and I noticed that this test account has us but others have US in usage location.
4. I checked details of user setting in Licences and apps blade and Licence location was empty. So I selected United States and saved. Going back there but it was empty again ....
5. I created new cloud only user and did the same as for previous test account (only difference is that this account is not synced from on-premises).
6. I assigned licences via admin.microsoft.com. I didn't specified usage location in Azure AD.
7. Then I was able to assign number to second test account because it has US in usage location.

So please have you experienced such issues with small and big letters in Azure AD and other M365 portals? This is really crazy and I am not able to find a root cause why this is happening.

Thank you.

Answer 1

Hello @Sandeep G-MSFT I found the root cause of the issue. I hope that text explanation below will be sufficient if not we can make a call.

1. User is synced from on-premises AD with Azure AD connect.
2. When I modify user properties / Usage location in Azure AD it will modify also Usage location in Admin portal but in a wrong way! See screenshots below:
   Azure AD properties set to Czechia which should lead to CZ in Admin portal:
   
   But in admin portal are small letters which is wrong and makes troubles in other M365 applications -> Teams, Exchange, etc.
   
   And at the same time in user properties in Admin portal in Licenses and app is location completely different
   

And if I go opposite way so I set location in Admin portal it has completely different effect than when I select location in Azure AD:
I changed user location to Sweden in Admin portal:


But when I go to Azure AD there is nothing:

So this seems to like some mismatch between modification of User properties from Azure AD and from Admin portal and not consistent info on the same users database.
Can you please take a look on that?
Thanks

Answer 2

Ok, I was able to fix the location using PowerShell - and then assign the phone number to the account:

connect-msolservice
Get-MsolUser -UserPrincipalName blah@soodyogesh .com | select userprincipalnmae, usagelocation

set-MsolUser -UserPrincipalName blah@soodyogesh .com -UsageLocation US

Cheers,
Mike

Answer 3

I am having the exact same issue at the moment. Seems like an issue in their logic for assigning numbers. Let me know if you have a fix as I am actively pursing this as well - will do the same.

Cheers,
Mike

Answer 4

Hi @Oldrich Srubar Suggestion, Try to set these properties from onprem AD since its an onprem account. I have seen weird issues in the past.