Last updated
Was this helpful?
Last updated
Was this helpful?
MSPs may encounter a situation where they need to set up multiple instances of the same integration, when that integration doesn’t support . These integrations include the following - note that all Microsoft integrations are now part of our :
N-Able - the deprecated version of the integration is only still used by a few longer-term Rewst customers.
This is most often experienced with the Microsoft CSP integration, via one of the following scenarios. For the purposes of documentation, the example in this page will use the Microsoft CSP integration.
An MSP acquires another MSP, and inherits their customers. That newly acquired MSP may or may not have been an existing user of Rewst. This creates one MSP using two Microsoft CSP accounts.
An MSP manages clients in multiple geographic regions, such as the United States and also Europe, which means meeting different legal requirements for each bucket of clients, possibly with different Microsoft CSP licenses for each region.
Before proceeding with these steps, we strongly recommend checking in with your CSM. They can point you to the correct Rewst team to discuss if it’s the right fit for your situation and goals.
Identify the initial MSP parent organization in the Rewst platform.
Make sure you have login credentials and the admin role for this parent account.
Identify each of the separate CSP accounts you’ll need to integrate into Rewst.
Create a separate child organization for every CSP account. For example, if integrating two separate CSP accounts into Rewst, you would create two child organizations.
Give each child organization a descriptive name, to clearly label which organization will be for which CSP account.
Log in to each of the child organizations in Rewst
When adding Crates or components, remember to add them to both MSP Child organizations separately, to ensure consistency.
Any workflows you create should be established at the parent-level organization. This allows for easy cloning and management within the child organizations.
separately for each child organization created, each configured to meet their individual needs. Note that this integration is now part of the Microsoft Cloud Bundle.
Create customer within each of the MSP child organizations.