Azure / Azure/azure-powershell
[Authentication] Fallback to DeviceCode if Browser is unavailable
Open
Authentication
Contains Breaking Change
feature-request
- Dominant language
- C#
- Stars
- 4.8k
- Forks
- 4.3k
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 54
Description
## Description of the new feature
Since Az.Accounts 2.x the default auth method has been changed from DeviceCode to Interactive(Browser), it results in error if Browser is unavailable. Some customers are expecting to switch to DeviceCode auth if browser is unavailable.
## Proposed implementation details (optional)
Contributor guide
Research direction
The issue names Az.Accounts and the Interactive(Browser)/DeviceCode authentication flow, but provides no files, tests, or entry points. Start by locating the authentication implementation and existing tests for these flows. Done means browser-unavailable environments fall back to DeviceCode without breaking the current interactive behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, powershell
- Domain
- authentication, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100