Map multiple M365 tenants to a single Huntress Org | Voters

Map multiple M365 tenants to a single Huntress Org

under review

Brett Faulder

Please add functionality to map multiple Microsoft 365 tenants into a single Huntress organization.

We have clients that are acquiring competitors. We need to be able to feed M365 MDR data into Huntress while billing our clients under the parent organization.

November 5, 2024

Rich Mozeleski

Merged in a post:

Map M365 to Multiple Organizations

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.

A day ago

Gregory Marchand

Yes, please we have a client who is in this scenario now, they are merging them in the future, but we have some time where both are needed.

Chris Ba

YES. Please allow for multiple Microsoft (or Google Workspace) tenants to be added to a single Huntress Account (customer). We have at least five customers will multiple O365/GWS tenants -- and being required to create multiple Huntress orgs only for the purpose of ITDR just add noise. All endpoints, SIEM sources, etc are going to be in one Huntress Account, but ITDR will be split between two.

Please add the capability to have multiple O365/GWS tenants pointing to one Huntress Account!

Rich Mozeleski

marked this post as

under review

Peter Franklin

Also upvoting for the same reasons as articulated by those already.

Doug Cramer

Please add this. We have clients with multiple 365 tenants.

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.

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

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.

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!

→