Allow Multiple MSPs to Manage Same Microsoft Tenant
L
Lava Puma
Currently, when attempting to onboard a new client that was previously managed by another MSP that also uses Rewst the client's tenant will not display in the Microsoft Bundle integration. These migrations require a ticket to be opened with the ROC and my understanding is that the developers have to update a table to manually move the tenant ID from the old MSP to the new MSP. For those unaware of this limitation, it can seem like there are issues with the integration or Microsoft not showing a new GDAP relationship.
Given the growth of the platform and overall industry trend towards both acquisition and turnover of MSPs, I would like to see something developed that allows a more seamless transition that doesn't require manual intervention.
Log In
V
Venetian yellow Lynx
I also ran into this issue after spending more than a day trying to work out why the company wasn’t appearing in the Microsoft integration bundle. It only became clear after raising a support request. At the very least, there should be an error message indicating that the customer is currently linked to another MSP, which prevents it from being associated with your tenant, along with an option to raise a support ticket for investigation.
In practice, there will be cases where a company maintains relationships with multiple MSPs at different levels, all of whom may want to use Rewst. How do we accommodate this? Should Rewst allow more than one MSP relationship, or does it need a defined way of determining the correct ‘primary’ MSP when updating records after a back-end change is requested?