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.
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 noneflag) and/or add detection to surface a helpful error message instead of a cryptic WAM exception.