Considerations when using AzureDefaultCredential and proposed new connection type "azure-active-directory-cli"

[jamienich]

Proposing to add a new connection type "azure-active-directory-cli" the AzureDefaultCredential, 1 of 8 types that default credentials that could be selected. On Windows 10, a TypeScript package was using "azure-active-directory-default" and it was picking the correct AzureDefaultCredential but on Windows 11 it picked the wrong one.

Other users upgrading from WIndows 10 to Windows 11 may also start encountering this problem.

One workaround is to use AzureCliCredential directly, get a token for that credential and then pass that token to tedious using the token-credential option, but long term it would be nicer to update tedious.

I'll PR, if I get time.

https://github.com/jamienich/tedious

"DefaultAzureCredential is undoubtedly the easiest way to get started with the Azure Identity library, but with that convenience comes tradeoffs. Once you deploy your app to Azure, you should understand the app's authentication requirements. For that reason, replace DefaultAzureCredential with a specific TokenCredential implementation,...." from Microsoft Docs