Support Managed Identity Auth for Azure Data Explorer #21924
Comments
|
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
|
Hello @ben-childs-docusign, will pick this up for use with managed Identity as well. We're planning to have a couple of PR's, one for MI and the other for go-sdk update |
|
Hi @ag-ramachandran do you have any estimate for when you would be able to implement this? |
|
Hello @ben-childs-docusign, Apologies for not picking this up yet. We're thinking of picking this up early next week. The fix should not be too hard itself, we can try a dev complete and submit for review next week!. Would that timeline work. |
|
hello @ben-childs-docusign , Quick update : we should have the PR out by this Friday on this |
**Description:** Add support for ManagedIdentity. This enables passwordless config for the ADX sink **Link to tracking Issue:** #21924 **Testing:** Manually tested **Documentation:** Updated README documentation
|
Hi @ben-childs-docusign, the feature is completed. Can you close this issue please. |
|
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
|
Closing based on #21924 (comment) |
Component(s)
exporter/azuredataexplorer
Is your feature request related to a problem? Please describe.
Currently the azure data explorer exporter requires an App ID + Secret in order to authenticate to ADX. For services running in Azure that can use Azure Managed Identity it would be more convenient to just configure an App ID and authenticate using managed identity.
Describe the solution you'd like
azuredataexplorer exporter should support specifying just Application ID rather than Application ID + Client ID + Tenant ID. When only the Application ID is specified it should pass this to azure-kusto-go client using "WithUserManagedIdentity".
it could also optionally support providing no credentials at all in which case it could use "UseDefaultAzureCredential"
Describe alternatives you've considered
No alternatives were considered. Using application + client secret auth requires us to manage additional secrets and rotate them, managed identity would allow us to authenticate without having to manage additional secrets.
Additional context
No response
The text was updated successfully, but these errors were encountered: