You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please, can you assist, as I have been having login issues on my GitHub Codespaces terminal, which is not allowing me to log in/select the subscription to use on Azure CLI, but it works online. see screenshot below.
Hi avatarrok, thanks for reporting this. To reproduce the Codespaces login/subscription-selection failure, please share:
The screenshot's exact command/flags and error or prompt as text.
Azure CLI version (az version), Codespaces OS, and shell.
Steps leading to the failure, and whether “works online” means Azure portal or Cloud Shell.
CLI version / OS / shell:
Command:
Error or prompt:
Steps:
Working online environment:
Please redact credentials, tokens, device codes, and account/tenant/subscription identifiers. This issue will be picked up automatically after you reply.
CLI version / OS / shell: 2.90.0-*64
Command: az login
Error or prompt: I press enter to select the active subscription (as there is only 1 available) but it generate the below:
[Announcements]
With the new Azure CLI login experience, you can select the subscription you want to use more easily. Learn more about it and its configuration at https://go.microsoft.com/fwlink/?linkid=2271236
[Warning] The login output has been updated. Please be aware that it no longer displays the full list of available subscriptions by default.
Steps: Trying to login to my Github codespaces account to do the frontier week hack but it took over 2 weeks to respond and i have missed a learning opportunity. I have followed the links provided in the response it returned but it does not seem to work.
Working online environment: GitHub Codespaces/Azure CLI on windows
Hi avatarrok, thanks for the details, and sorry this disrupted your learning session. The [Announcements] and [Warning] text you pasted does not itself indicate that login failed.
To identify what is still failing, please share:
After pressing Enter, does the terminal return to its normal command prompt, or remain stuck?
In that same terminal, run az account show --query "{state:state,isDefault:isDefault}" -o json and share the result or exact error. This query omits account, tenant, and subscription identifiers.
If that succeeds, share the first subsequent command that fails and its exact error, with credentials and personal/resource identifiers removed.
You ran az login in GitHub Codespaces, pressed Enter for the only subscription, and returned to the normal shell prompt. Your follow-up check returned isDefault: true and state: Enabled; you also supplied CLI 2.90.0-*64 and the announcement/output warning. Thank you for those details.
To understand the remaining blocker, could you clarify:
Is returning to the prompt itself the concern, or does a subsequent Azure CLI operation fail? If an operation fails, please share that exact command and its error or unexpected output, with sensitive values removed.
What outcome did you expect instead?
There is no need to repeat the environment or output already provided. Automation will resume after your reply.
Hi avatarrok, following up on the remaining question. The enabled default subscription and return to the shell prompt you reported are consistent with a completed login.
Is returning to the prompt the concern, or is a subsequent Azure CLI command still failing? If a command fails, please share that command, its error or unexpected output with sensitive values removed, and what you expected instead. There is no need to repeat the version or account-status output already supplied.
Hi avatarrok, the output you shared points to az login completing normally rather than failing at subscription selection. In the subscription selector, pressing Enter keeps the default subscription; login then sets it active and prints those announcements and the warning before returning to the terminal. The isDefault: true and state: Enabled result you provided is consistent with an active subscription. The warning is informational, not an error (a similar report was resolved in #32359).
Please continue with the Azure CLI command you were trying to run in that Codespace. If that command fails, its exact command and error output would identify a separate access problem; the notices shown here do not indicate one.
Activity
yonzhan commentedon Sep 3, 2026
Thank you for opening this issue, we will look into it.
x-engineering-agent commentedon Sep 17, 2026
Hi avatarrok, thanks for reporting this. To reproduce the Codespaces login/subscription-selection failure, please share:
az version), Codespaces OS, and shell.Please redact credentials, tokens, device codes, and account/tenant/subscription identifiers. This issue will be picked up automatically after you reply.
avatarrok commentedon Sep 18, 2026
CLI version / OS / shell: 2.90.0-*64
Command: az login
Error or prompt: I press enter to select the active subscription (as there is only 1 available) but it generate the below:
[Announcements]
With the new Azure CLI login experience, you can select the subscription you want to use more easily. Learn more about it and its configuration at https://go.microsoft.com/fwlink/?linkid=2271236
If you encounter any problem, please open an issue at https://aka.ms/azclibug
[Warning] The login output has been updated. Please be aware that it no longer displays the full list of available subscriptions by default.
Steps: Trying to login to my Github codespaces account to do the frontier week hack but it took over 2 weeks to respond and i have missed a learning opportunity. I have followed the links provided in the response it returned but it does not seem to work.
Working online environment: GitHub Codespaces/Azure CLI on windows
x-engineering-agent commentedon Sep 18, 2026
Hi avatarrok, thanks for the details, and sorry this disrupted your learning session. The
[Announcements]and[Warning]text you pasted does not itself indicate that login failed.To identify what is still failing, please share:
az account show --query "{state:state,isDefault:isDefault}" -o jsonand share the result or exact error. This query omits account, tenant, and subscription identifiers.I'll pick this up automatically once you reply.
avatarrok commentedon Sep 18, 2026
After pressing Enter, the terminal return to its normal command prompt - avatarrok ➜ /workspaces/FrontierWeekHack (main) $
see the response below for the script you told me to run -
{
"isDefault": true,
"state": "Enabled"
}
avatarrok ➜ /workspaces/FrontierWeekHack (main) $
x-engineering-agent commentedon Sep 23, 2026
You ran
az loginin GitHub Codespaces, pressed Enter for the only subscription, and returned to the normal shell prompt. Your follow-up check returnedisDefault: trueandstate: Enabled; you also supplied CLI2.90.0-*64and the announcement/output warning. Thank you for those details.To understand the remaining blocker, could you clarify:
There is no need to repeat the environment or output already provided. Automation will resume after your reply.
x-engineering-agent commentedon Sep 26, 2026
Hi avatarrok, following up on the remaining question. The enabled default subscription and return to the shell prompt you reported are consistent with a completed login.
Is returning to the prompt the concern, or is a subsequent Azure CLI command still failing? If a command fails, please share that command, its error or unexpected output with sensitive values removed, and what you expected instead. There is no need to repeat the version or account-status output already supplied.
I'll pick this up automatically once you reply.
x-engineering-agent commentedon Oct 25, 2026
Hi avatarrok, the output you shared points to
az logincompleting normally rather than failing at subscription selection. In the subscription selector, pressing Enter keeps the default subscription; login then sets it active and prints those announcements and the warning before returning to the terminal. TheisDefault: trueandstate: Enabledresult you provided is consistent with an active subscription. The warning is informational, not an error (a similar report was resolved in #32359).Please continue with the Azure CLI command you were trying to run in that Codespace. If that command fails, its exact command and error output would identify a separate access problem; the notices shown here do not indicate one.
Posted by x-engineering-agent (Fixer)