Offboard CSP customers - PREVIEW ONLY
You can offboard CSP customers from Azure Resource Manager if needed. For example, you may need to offboard a customer if they were accidentally assigned to an incorrect N-able customer or site.
When you offboard customers, the customer data is deleted from the application and the application no longer acts on the customer’s tenant, but the application and the GDAP relationship are not deleted from the customer's tenant.
To delete the application and the GDAP relationship manually from your customer's tenant, in Microsoft Azure remove the application from Enterprise Applications and terminate the GDAP relationship from the Partner Center.
To offboard a customer from Azure Resource Manager:
In the left-hand navigation menu, click Administration > Cloud Commander Setup
A list of the Microsoft tenants associated with your partner service account display indicating the current integration status for each tenant.
For every customer you are offboarding, select -- for N-able customer and -- for N-able site. The integration status for the customer changes to Ignored.
- When you are finished removing the N-able customer and N-able site mappings, select Apply
The customers are unmapped and their integration statuses change to Not Configured.
The customer data is deleted from the application and the application no longer acts on the customer’s Microsoft tenant, but the application and the GDAP relationship are not deleted from the customer's Microsoft tenant.
If the application and the GDAP relationship are not manually deleted from the customer's Microsoft tenant, and you onboard the tenant again, Azure Resource Manager detects the existing relationship and the integration status proceeds immediately to Approved.
We track and display the status of the GDAP relationship workflow between the Microsoft tenant and your N-able customer.
|Not configured||GDAP relationship not established
This status occurs when:
|If you want to onboard the customer, select your N-able customer and site that maps to the Microsoft tenant|
|Needs approval||Customer mapping is selected but the GDAP relationship is not yet customer approved||When prompted, click the Copy approval link to send to your customer|
|In-progress||Transitional state||No action required, but you can refresh the page to get an updated status|
|Finalize||GDAP relationship is approved by the customer||When prompted, click the Finalize approval link|
|Approved||GDAP relationship is properly established. Azure Resource Manager can now ingest data from the cloud.||No action required|
|Error||GDAP relationship reports an error||Resolve the issue causing the error, then use the Reset Approval link to try the customer mapping process again|
|Pending relationship||Customer mapping exists in N-able but the GDAP relationship is terminated in Microsoft||Offboard the customer (unmap) and onboard them again|
|Ignored||Customer mapping existed but is now removed||No action required|
|Issues found||GDAP relationship cannot be created or can be created with but without all the required access permissions||When prompted, click the Accept relationship link and then choose one:
|Approval with limitations||Status applied when you accept the GDAP relationship after it had a previous status of Issues found||No action required|