Why should we use the Batchtool to transition from DAP to GDAP and not a Rest-API?
Until October 2022, we have to transition all old DAP relationships to GDAP relationships using the batchtool (https://github.com/microsoft/PartnerCenter-GDAPTransition).
I'm wondering why we should use this batch tool and can't use a Rest-API for it.
We already have a lot of Java code that makes Rest-API calls anyway. We implemented that for the NCE migration and other things. And our Java code already supports authentication, CSV-processing, logging, error handling and parallelization. It would be much easier if we could just reuse that and then call a Rest-API.
On the other hand, I was not able to compile the C# code of the batchtool, because I do not have a license for Visual Studio, and I am not allowed to use the free license for Visual Studio Express, because my company has more than 250 PC and an annual sales of more than 1 million USD.
This Batchtool internally calls the following Rest-API:
This Rest-API expects in the request body a delegatedAdminRelationship object (documented here: https://docs.microsoft.com/en-us/graph/api/tenantrelationship-post-delegatedadminrelationships?view=graph-rest-beta&tabs=http).
I was able to test this Rest-API successfully. The only thing is that there is no official documentation of this REST-API.
Then why do we have to use this batch tool, when there is also this Rest-API available?
@UweStahl As Partner you also have Visual Studio Subscriptions as MPN benefit - don't know if they have been consumed within your org already.
Will forward this question internally and check if I can get an answer if the API is intended to be opened for the public (meaning, documented). Since this migration option (without customer consent) will only last until October 31, 2022, I guess there are no plans for that.
Receive consultations via Technical Presales and Deployment Services team