On an Azure account's group row, the Details pane now describes the account:
field
from
name
token name
user (and "service principal")
az's account list
tenant: name · ID
az's account list (the name is borrowed from another entry in the same tenant when az left it out)
object ID
token oid; y on the row copies it
sign-in: MFA or not, and how
token amr
directory roles
token wids: built-in roles by name, others as role 1a2b3c4d, the default member role left out
subs: count · default
az's account list
cloud
az's account list, when not AzureCloud
Nothing is fetched for it: the claims are the ones from the token lazysecrets already gets for the account's own tenant, read without verification. The token itself is never stored or shown. Before the first token, only the az-list fields show. A failing account shows its sign-in problem there instead (from #4).
New optional provider.Accounts interface; azure.Provider implements it. Tests: the fields from claims and az's list, sign-in methods, the UI showing it on the group row only, and y copying the object ID. Checked against a real signed-in account (name, MFA · password, default subscription) and an expired one (az-list fields only, since there's no token).
On an Azure account's group row, the Details pane now describes the account:
| field | from |
|---|---|
| name | token `name` |
| user (and "service principal") | az's account list |
| tenant: name · ID | az's account list (the name is borrowed from another entry in the same tenant when az left it out) |
| object ID | token `oid`; `y` on the row copies it |
| sign-in: MFA or not, and how | token `amr` |
| directory roles | token `wids`: built-in roles by name, others as `role 1a2b3c4d`, the default member role left out |
| subs: count · default | az's account list |
| cloud | az's account list, when not AzureCloud |
Nothing is fetched for it: the claims are the ones from the token lazysecrets already gets for the account's own tenant, read without verification. The token itself is never stored or shown. Before the first token, only the az-list fields show. A failing account shows its sign-in problem there instead (from #4).
New optional `provider.Accounts` interface; `azure.Provider` implements it. Tests: the fields from claims and az's list, sign-in methods, the UI showing it on the group row only, and `y` copying the object ID. Checked against a real signed-in account (name, MFA · password, default subscription) and an expired one (az-list fields only, since there's no token).
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
On an Azure account's group row, the Details pane now describes the account:
nameoid;yon the row copies itamrwids: built-in roles by name, others asrole 1a2b3c4d, the default member role left outNothing is fetched for it: the claims are the ones from the token lazysecrets already gets for the account's own tenant, read without verification. The token itself is never stored or shown. Before the first token, only the az-list fields show. A failing account shows its sign-in problem there instead (from #4).
New optional
provider.Accountsinterface;azure.Providerimplements it. Tests: the fields from claims and az's list, sign-in methods, the UI showing it on the group row only, andycopying the object ID. Checked against a real signed-in account (name, MFA · password, default subscription) and an expired one (az-list fields only, since there's no token).🤖 Generated with Claude Code