We use a single Microsoft Defender for Endpoint tenant across multiple endpoint populations that need to be separated into different Huntress organizations for operational and policy requirements.

Currently, Huntress allows an MDE tenant to be mapped to only one Huntress organization. As a result, when Huntress agents are moved into a second organization, MDE Device Discovery can no longer associate those endpoints with their active Huntress agents and reports them as Agent Missing.

It would be helpful if a single MDE tenant could be associated with multiple Huntress organizations, with Device Discovery correlating each MDE endpoint to the Huntress organization containing its corresponding agent.

Our use case is separating shoreside and vessel endpoints into different Huntress organizations while both populations remain within the same Microsoft MDE tenant. The Huntress agents and EDR remain active in both organizations, but Device Discovery cannot accurately represent coverage across both because of the current one-tenant-to-one-organization mapping limitation.