M365 & contact handling across divisions in a shared tenant
We have three related customers (divisions) operating within the same Microsoft 365 tenant. Each division needs to be billed separately through Gorelo (We're currently using Connectwise and it's a mostly manual process). While each division has its own domain, those domains aren't actively used for email or identity separation. Each employee belongs to only one division, and the customer does not want to split the divisions into separate tenants.
We recently got CIPP working and linked the M365 tenant to all three divisions in Gorelo, but that seems to have backfired—every employee is now associated with all three divisions in Gorelo, which breaks our billing logic.
Historically, we've used the "Department" field under M365 user contact details to distinguish employees by division. We could also consider changing users' primary domains to match their division assignments.
Our goal is to automate contact management and M365 license billing as much as possible within this shared-tenant setup.
Has anyone tackled this kind of scenario?
If I un-map will that remove the contacts that have been created? If I remove the extra contacts will the integration re-add them?
How are you separating users by division for billing in Gorelo?
Are you using CIPP, custom attributes, or something else to drive automation?
Any best practices for managing this cleanly without splitting the tenant?
We recently got CIPP working and linked the M365 tenant to all three divisions in Gorelo, but that seems to have backfired—every employee is now associated with all three divisions in Gorelo, which breaks our billing logic.
Historically, we've used the "Department" field under M365 user contact details to distinguish employees by division. We could also consider changing users' primary domains to match their division assignments.
Our goal is to automate contact management and M365 license billing as much as possible within this shared-tenant setup.
Has anyone tackled this kind of scenario?
If I un-map will that remove the contacts that have been created? If I remove the extra contacts will the integration re-add them?
How are you separating users by division for billing in Gorelo?
Are you using CIPP, custom attributes, or something else to drive automation?
Any best practices for managing this cleanly without splitting the tenant?
Solution
Hi mate,
If all users are in the same M365 tenant then they will need to be under the same client in Gorelo.
You can then bill based on Security Groups in their M365 tenant.
Easiest approach would be to create a dynamic security group in M365 based on their department attribute and then tie this to the line item on each contract via dynamic quantities.
If you also need to break out labor by department then you’ll need to do this based on ‘Locations’ under the Client. You would need to associate each contact with their specific location and then have each contract also associated with that location.
Let me know if you’d like to jump on a call for this one.
If all users are in the same M365 tenant then they will need to be under the same client in Gorelo.
You can then bill based on Security Groups in their M365 tenant.
Easiest approach would be to create a dynamic security group in M365 based on their department attribute and then tie this to the line item on each contract via dynamic quantities.
If you also need to break out labor by department then you’ll need to do this based on ‘Locations’ under the Client. You would need to associate each contact with their specific location and then have each contract also associated with that location.
Let me know if you’d like to jump on a call for this one.
