Closed
Description
openedon Mar 29, 2023
Feature Request
Currently, the DefaultAzureCredentialOptions
will always try each defined auth method in the fixed order. Imagine I have a VM and want to run some Go code on it to interact with ARM using this SDK, it will always try the MSI (i.e. the VM's identity) instead of falling back to using Azure CLI (i.e. my user account). The request sent from my App will then fail since I didn't give enough role to the VM, which I deliberately want to avoid.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment