-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Example of the lake connection string #11
Comments
These instructions will connect to the source and destination clusters using the specified service principal credentials for authentication. To use a service principal for authentication, follow these step-by-step instructions to set up the connection string and resources using the Azure portal:
To include the connection string with the AppClientId, AppKey, and Authority Id in the command line, you need to replace the source and destination cluster URLs with their corresponding Kusto-style connection strings. Here's an example:
Replace {sourceAppClientId}, {sourceAppKey}, {sourceAuthorityId}, {destinationAppClientId}, {destinationAppKey}, and {destinationAuthorityId} with the respective values for your source and destination clusters. To get the values for {sourceAppClientId}, {sourceAppKey}, {sourceAuthorityId}, {destinationAppClientId}, {destinationAppKey}, and {destinationAuthorityId}, you need to create and configure two Azure Active Directory (AAD) applications, one for the source cluster and one for the destination cluster. Follow these steps to create an AAD application and get the required values:
Repeat the above steps for both the source and destination clusters to get their respective values. Now, replace {sourceAppClientId}, {sourceAppKey}, {sourceAuthorityId}, {destinationAppClientId}, {destinationAppKey}, and {destinationAuthorityId} in your Kusto Copy command line with the values you've obtained from the Azure portal. Keep in mind that you should also grant the necessary permissions to the AAD applications on the source and destination Kusto clusters and the storage account, as explained in the previous instructions. Since you want to grant access to your application using its Application (Client) ID, you should choose the first option: "User, group, or service principal". This option allows you to assign the "Storage Blob Data Contributor" role to the service principal associated with your application. Here's a recap of the steps:
|
Hi!
We are attempting to migrate multiple ADX cluster's data to new environments. This tool popped in the Google and looked like should be worth to try.
The lake connection string however is currently causing some issues. It seems like it is not any kind of standard storage connection string... I tried to look at the code as well but don't also want to spend too much time just looking at an issue when I can try to ask :)
Could you give an example of the lake connection string that should work?
The text was updated successfully, but these errors were encountered: