microsoft / microsoft/powerplatform-vscode
Non-interactive Windows auth (WAM) fails in AzDO pipelines / headless environments — needs docs/workaround
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 277
- Forks
- 60
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 14
Description
On Windows in Azure DevOps pipelines and other non-interactive environments, the extension's auth flow triggers Windows Authentication Manager (WAM) which requires a UI prompt. This fails silently or throws in headless mode. Related to #914 but the specific gap: no documentation on how to authenticate in CI/non-interactive Windows scenarios.
Request: document the workaround (service principal + env vars, or --auth none flag) and/or add detection to surface a helpful error message instead of a cryptic WAM exception.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the extension's Windows Authentication Manager flow and existing authentication documentation. Document the service-principal and environment-variable workaround or the --auth none option for Azure DevOps and other headless environments; if detection is pursued, done means replacing the cryptic WAM failure with a helpful error message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100