Kamil Rithaler

Thank you @Adam-it for taking the time to review it. I considered a token option as it is in PnP PowerShell. However, in M365 Cli there might be a command...

Azure CLI is shell-agnostic as well. It can be a part of CLI GH actions, but then it is not available in Azure DevOps. I guess, more enterprises still favour...

@waldekmastykarz good idea, that is even better as it would introduce many more authentication options and standardize existing ones. The login command would create the ```ChainedTokenCredential``` based on the provided...

I did some tests using @azure/identity with developer tools authentication options. Here are my observations: * Using the 1st party service principals results in very limited permission grants. They can...

```@azure/identity``` does not provide only chained credentials but is an abstraction on top of MSAL simplifying authentication. You can use credentials like ```DeviceCodeCredential```, ```UsernamePasswordCredential``` or ```ClientCertificateCredential```. For example ```InteractiveBrowserCredential``` listens...

I agree, it is good idea to support more that just Azure CLI and let users use other dev tools. You are right, the implementation should use the lib instead...

Not ideal name but it looks like there is no good one. Let it be `azureClis` then. Are you ok with me opening a PR just for the CLIs? After...