Map multiple M365 tenants to a single Huntress Org
A
Andrew Barton
This is fairly common for us as well with some clients having 10 or more tenants. Users are often duplicated between tenants so it would be nice to also have a way to tie an identity across multiple tenants so rules could be applied to a user who has multiple accounts instead of having to recreate the rules for each instance.
P
Phill Wade
We have a customer in this situation. As a workaround, I mapped both the Huntress orgs to the same PSA org in the integration, and this has been working for us. But I agree it would be better to have visibility of the link, maybe child orgs within the portal, for better visibility.
E
Evan Swendsen
I agree with Brett and Blaine. We will run into this same challenge!
M
Mungo Bright
Nice one Brett, Good suggestion
B
Blaine Kahle
I'm with Brett. They're one entity to us, but are separated across multiple M365 orgs. The short term workaround of making 1-1 ratios with additional Huntress Orgs will work, but breaks all our other 1-to-1 company matching processes, which is expecting 1 name in our RMM, 1 in our PSA, and 1 in Huntress, not 3 or 7.