Skip to content

[ISSUE] Account-level authentication failed for az cli + sp #1147

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
nkvuong opened this issue Feb 13, 2025 · 1 comment
Open

[ISSUE] Account-level authentication failed for az cli + sp #1147

nkvuong opened this issue Feb 13, 2025 · 1 comment
Labels
Bug The issue is a bug. Regression Used with the “Bug” label to indicate that the bug did not exist in previous versions. Triaged The issue has been reviewed. Issues without a “Triaged” label require triage/review.

Comments

@nkvuong
Copy link
Contributor

nkvuong commented Feb 13, 2025

Description
See issues databricks/terraform-provider-databricks#4063 for more details

Reproduction
Account-level provider + sp auth using az cli

Expected behavior
Should work, but now failed with

│ Error: cannot read user: failed during request visitor: default auth: azure-cli: cannot get access token: WARNING: Could not retrieve credential from local cache for service principal e0da535f-4aa5-45fd-ad10-0817c932b48c under tenant common. Trying credential under tenant 1e98afad-8153-4889-a48f-60dc77bc87a8, assuming that is an app credential.
│ ERROR: AADSTS50059: No tenant-identifying information found in either the request or implied by any provided credentials. Trace ID: 3e7f0d70-f60c-4276-bbcb-996f4dac2200 Correlation ID: fbb9e0db-dfdc-44f5-95a7-68b18f7d64a6 Timestamp: 2024-10-01 15:50:11Z
│ Interactive authentication is needed. Please run:
│ az login

Is it a regression?
This failed in v0.44, likely in PR #910

@nkvuong nkvuong changed the title [ISSUE] Account-level failed for az cli + sp [ISSUE] Account-level authentication failed for az cli + sp Feb 13, 2025
@tanmay-db tanmay-db added Bug The issue is a bug. Regression Used with the “Bug” label to indicate that the bug did not exist in previous versions. Triaged The issue has been reviewed. Issues without a “Triaged” label require triage/review. labels Mar 3, 2025
@dloiacono
Copy link

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug The issue is a bug. Regression Used with the “Bug” label to indicate that the bug did not exist in previous versions. Triaged The issue has been reviewed. Issues without a “Triaged” label require triage/review.
Projects
None yet
Development

No branches or pull requests

3 participants