Please confirm:
Problem Statement
The mappings between CIPP & Halo are quite annoying from this side, they can get forgotten about when new clients come on, as we have to wait for CIPP to detect the new tenant (which means we can't do it all in a single process). We don't get any notification/warning if there are unmatched tenants, so it takes a little while to map them.
In my opinion, automating this mapping exercise would be a low-cost but high-benefit improvement.
I think it's fair to say that most HaloPSA partners will already map the clients using Halo's Microsoft CSP integration, as this is needed for user sync anyway. This is exposed in a few places in the HaloPSA API. For example, in a client object, there is an "azure_tenants" array, and each object has its own "azure_tenant_id".
Could these tenant IDs be used to match instead?
NB: if this is fixed, I think there's a similar comment with the Hudu sync. Client names are synced between HaloPSA and Hudu, so that should be quite trivial. Hudu also has an API where you can get the Halo client IDs of each Hudu client.
Benefits for MSPs
This automates a commonly repeated task, reduces risk of human error but also means the action is completed in real-time, rather than waiting.
Value or Importance
This is a nice-to-have, but I think would impact a lot of MSPs (well, anyone using HaloPSA!)
PowerShell Commands (Optional)
No response
Please confirm:
Problem Statement
The mappings between CIPP & Halo are quite annoying from this side, they can get forgotten about when new clients come on, as we have to wait for CIPP to detect the new tenant (which means we can't do it all in a single process). We don't get any notification/warning if there are unmatched tenants, so it takes a little while to map them.
In my opinion, automating this mapping exercise would be a low-cost but high-benefit improvement.
I think it's fair to say that most HaloPSA partners will already map the clients using Halo's Microsoft CSP integration, as this is needed for user sync anyway. This is exposed in a few places in the HaloPSA API. For example, in a client object, there is an "azure_tenants" array, and each object has its own "azure_tenant_id".
Could these tenant IDs be used to match instead?
NB: if this is fixed, I think there's a similar comment with the Hudu sync. Client names are synced between HaloPSA and Hudu, so that should be quite trivial. Hudu also has an API where you can get the Halo client IDs of each Hudu client.
Benefits for MSPs
This automates a commonly repeated task, reduces risk of human error but also means the action is completed in real-time, rather than waiting.
Value or Importance
This is a nice-to-have, but I think would impact a lot of MSPs (well, anyone using HaloPSA!)
PowerShell Commands (Optional)
No response