Set "Entra Usage Location" in Huntress
under review
Dru DuBay
It seems that Huntress just wants this Entra Usage Location set so they can use it as a datapoint, setting it per user it tedious. MSP and IT also use JIT accounts which can create accounts on the fly. As an MSP, we are getting these alerts for every JIT account being created.
For all our clients, we could simply just tell you (in settings) that USA is the only Usage Location, vs setting this on a per user basis. Above that, if there was a single user in say Japan, it would be better for us to set that usage location on their identity in Huntress, not in Entra.
J
John Hardwick
I don't understand why all users aren't checked when the tenant is onboarded and I would assume for 99% of your customer base, you'd probably be able to assume one country for the entire tenant so perhaps asking for that during setup?
T
Tanner Stine
We are seeing alerts pour in for JIT accounts and accounts for ImmyBot integration.
J
Joe Cimino
We can go further and say 'Just check where the tenant was created and make that the default for that tenant'. US tenants are created in the US; Chinese tenants in China, etc. etc. etc.. May not work for all countries, but most of them.
----
#Connect to Exchange Online
Connect-ExchangeOnline -ShowBanner:$false
#Get the geography of Exchange data
Get-OrganizationConfig | Select-Object -ExpandProperty DefaultMailboxRegion
----
The Entra Location isn't something I'm actually going to act on. I'm just leaving the escalations accumulating until something happens.
Rich Mozeleski
under review