[FEATURE] Support Azure Cli credential

[konjac]

Use Case / Problem

Current auth methods supported by fabric-cli are very limited.

In typical workflows, credentials could be passed along with the context rather than requiring a separate login.

Proposed Solution

Adding support for Azure CLI credentials as an authentication method would be a significant improvement.

This would allow fabric-cli to leverage any authentication mechanism supported by Azure CLI and save your effort to dup the implementation.

Alternatives Considered

No response

Impact Assessment

• This would help me personally
• This would help my team/organization
• This would help the broader fabric-cli community
• This aligns with Microsoft Fabric roadmap items

Implementation Attestation

• I understand this feature should maintain backward compatibility with existing commands
• I confirm this feature request does not introduce performance regressions for existing workflows
• I acknowledge that new features must follow fabric-cli's established patterns and conventions

Implementation Notes

No response

[HasanAboShally]

/triaged

Hi @konjac,

Thanks for opening this feature request!

I'd love to better understand your use case here. Could you help us out by providing a bit more detail on:

• What specific workflow or scenario you're trying to enable with Azure CLI credentials?
• How you envision this working in practice (e.g., would this be automatic credential sharing where Fabric CLI reads from Azure CLI's token cache, or something else)?
• Are there specific authentication mechanisms from Azure CLI that you need that aren't currently available in Fabric CLI?

For context, we currently support several authentication methods:

• Interactive authentication (device code flow)
• Service principal with secret
• Service principal with certificate
• Service principal with federated credential
• Managed identity authentication

I'm guessing you might be looking for a seamless experience where you authenticate once with az login and Fabric CLI automatically picks up those credentials (similar to how Azure's DefaultAzureCredential works)? Or perhaps you're working in CI/CD pipelines where Azure CLI is already authenticated and you'd like Fabric CLI to leverage that?

Understanding your specific scenario will help us evaluate the best path forward and prioritize accordingly.

Thanks!

[HasanAboShally]

/needinfo

[konjac]

@HasanAboShally

My scenario is just automatic credential sharing where Fabric CLI reads from Azure CLI's token cache. Azure CLI credential is just the recommended way to reuse the cache https://learn.microsoft.com/en-us/python/api/azure-identity/azure.identity.azureclicredential?view=azure-python

Since Azure CLI supports multiple authentication methods across various environments, sharing its token cache allows Fabric CLI to seamlessly inherit these capabilities. This means Fabric CLI can support all those authentication methods with minimal additional effort.

[HasanAboShally]

/triaged

Hey @konjac ,

Thanks for your reply and explanation.
I get the rational and see the value in your proposal.
We're adding this to our backlog and will work to deliver it soon ⚡️.

Also, I'd love to hear what you're building with the Fabric CLI and how's your experience with it so far.

We're here to help whenever needed, and thanks again for your contribution!