Map M365 to Multiple Organizations
R
Ryan Sipes
We've got some clients with multiple site locations, and the different locations are configured as different organizations in Huntress for management/billing purposes. Their 365 tenants are the same across all sites. It would be great if we could have the 365 tenant mapped to multiple organizations in Huntress, especially as Huntress begins to leverage endpoint data to assist with 365 detections.
P
Peter Franklin
Also upvoting for the same reasons as articulated by those already.
A
Abe Safa
Upvoting this post. With the new ITDR feature to disable and re-enable AD synced identities, we cannot leverage that feature if we have multiple companies in Huntress that use the same M365 tenant
W
Wendell Tucker
This feature is necessary for us to use Defender for Endpoint for over 80%, 2000+, of our EDR/MDR devices. The ability to Map a single MS365 tenant to multiple Huntress organizations, using the MS365 'Department' contact field as a filter to map the correct devices to the to correct Huntress Org...would get the job done!
A
Andrew Ames
Adding a 3rd to this. We also have a customer with multiple locations all under 1 domain we'd like identities mapped accordingly. I believe we could do this by adding using a tag within the users Entra identitiy properties (like you do with location) and a filter/sort tag on the Huntress side so when it sync's it sorts based to each org based on that tag. If no tag it can generate an alert just like login location not being set does. Just an idea.
N
Neil O'Sullivan
I just wanted to add a "second" here regarding the ability to map/associate multiple organizations to the same company. In addition to the O365 mapping, our endpoint agents are distributed across multiple sites and it would be great to organize them in a hierarchy that groups agents/accounts accordingly. Thanks!