Skip to content
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

[Feature]: Make GET Subscription REST Operation Optional in Connect-AzAccount #26827

Open
rui-hi opened this issue Dec 4, 2024 · 0 comments
Open
Assignees
Labels
Accounts Issues in Az.Accounts except authentication related customer-reported feature-request This issue requires a new behavior in the product in order be resolved.

Comments

@rui-hi
Copy link

rui-hi commented Dec 4, 2024

Description of the new feature

Currently, the Connect-AzAccount command performs the Subscriptions - Get operation during the login process. This behavior occurs regardless of whether the -access-token parameter or the -subscription parameter is used.

Making the Subscriptions - Get operation mandatory has caused issues in the past. For instance, during an Azure Resource Graph (ARG) outage, the Subscriptions - Get operation failed, which in turn caused the Connect-AzAccount command to fail completely.
This resulted in business-critical PowerShell commands being unable to log in to Azure at all.

Therefore, I request that the Connect-AzAccount command be modified to create an authentication context object without requiring the success of the Subscriptions - Get operation. This change would allow subsequent commands to execute even if the Subscriptions - Get operation fails.

For my customer's case, the subsequent command after Connect-AzAccount was as follows:
https://learn.microsoft.com/en-us/powershell/module/az.datafactory/invoke-azdatafactoryv2pipeline?view=azps-13.0.0&viewFallbackFrom=azps-12.3.0

Proposed implementation details (optional)

No response

@rui-hi rui-hi added feature-request This issue requires a new behavior in the product in order be resolved. needs-triage This is a new issue that needs to be triaged to the appropriate team. labels Dec 4, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added customer-reported and removed needs-triage This is a new issue that needs to be triaged to the appropriate team. labels Dec 4, 2024
@VeryEarly VeryEarly assigned VeryEarly and msJinLei and unassigned VeryEarly Dec 5, 2024
@VeryEarly VeryEarly added the Accounts Issues in Az.Accounts except authentication related label Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accounts Issues in Az.Accounts except authentication related customer-reported feature-request This issue requires a new behavior in the product in order be resolved.
Projects
None yet
Development

No branches or pull requests

3 participants