OnCallReadyStart learning

Azure I: CLI, Identity & Data Planes: glossary

105 terms, in plain words, with where each one is taught.

--auth-mode login (auth-mode, AZURE_STORAGE_AUTH_MODE)
Tells az storage commands to use your Entra token and data role, instead of silently fetching the account key. Lesson 29.29
AADSTS (AADSTS7000215, AADSTS70021)
The prefix of Entra ID sign-in error codes. An AADSTS error is an authentication problem; no role assignment fixes it. Lesson 29.8
ABAC (attribute-based access control, RBAC condition, role assignment condition)
Conditions on a role assignment based on properties of the request, such as "only blobs in this container" or "only assign these roles". Lesson 29.18
access policy (Key Vault) (enableRbacAuthorization)
Key Vault's older permission model: a list on the vault itself. Contributor can add itself to it. Use the RBAC model instead. Lesson 29.23
access review (access reviews)
The periodic check of who has access and whether they still need it. Lesson 29.18
access tier (accessTier, Cool tier, Archive tier)
How a blob is stored: Hot for often-read data, Cool/Cold/Archive cheaper to keep and dearer to read.
actions (RBAC) (notActions, operation string)
The control-plane operations a role allows, written like Microsoft.Network/virtualNetworks/write. notActions subtracts from them but is not a deny. Lesson 29.13
ADLS
Azure Data Lake Storage: a storage account with a real folder hierarchy (hierarchical namespace) for big-data tools. Lesson 29.29
allowBlobPublicAccess (public blob access)
Whether containers may be made readable by anyone on the internet. Keep it false.
app registration (app registrations, az ad app, application object)
The definition of an application in Entra ID: its name, credentials and requested permissions. It has an appId. Lesson 29.8
appId (client ID, clientId, application ID)
The ID an application or identity uses to say who it is when it signs in. Not the ID RBAC grants to. Lesson 29.8
ARM (Azure Resource Manager, management.azure.com)
Azure Resource Manager, the front door at management.azure.com for creating, changing and deleting resources. The control plane. Lesson 29.1
authorisation
Deciding what you may do, once it is known who you are. In Azure, RBAC does it for each request. Lesson 29.8
AuthorizationFailed
The error ARM returns when your identity has no role allowing the action at that scope. It names the principal, the action and the scope. Lesson 29.1
az config (defaults.group, az config set)
Stores az defaults in ~/.azure/config, such as a default resource group. Convenient by hand, a trap in scripts. Lesson 29.1
az output format (--output, -o table, -o tsv)
The -o flag: chooses how az prints its JSON result: json, table, tsv, yaml or none. Lesson 29.3
az tag update (--operation merge, --operation replace)
Adds or replaces tags on one resource. merge keeps existing tags; replace throws them away.
Azure compute (App Service, Azure Functions, Container Apps)
Azure services that run your code: VMs, VM scale sets, App Service (web apps), Functions, Container Apps, Kubernetes clusters. Lesson 29.9
Azure Files (Azure Files share, azurefile-csi)
Network file shares (SMB or NFS) served by a storage account. Many machines can mount one at once. Lesson 29.29
Azure RBAC
Azure's permission system: who (a principal) gets which role at which scope. Grants apply to the scope and everything inside it. Lesson 29.13
Azure resource (Azure resources)
One thing you created in Azure: a virtual network, a cluster, a Key Vault, a storage account. Each has one resource ID. Lesson 29.1
Azure tenant (tenantId, Entra tenant)
Your organisation's directory in Entra ID: users, groups, apps. It says who exists; resources do not live in it. Lesson 29.1
azure/login (azure/login@v2)
The ready-made GitHub step that exchanges the job's OIDC token for an Azure token, given client-id, tenant-id and subscription-id.
blade (blades)
Azure portal word for a panel: Overview, Tags, Access control.
CLI
Command-line interface: a program you drive by typing commands, like az, kubectl or terraform, rather than clicking in a website. Lesson 29.1
client secret (client secrets, app password)
A password for a service principal. It can leak and it expires (default one year); the last resort among credentials. Lesson 29.8
cluster add-on (cluster add-ons)
An optional cluster feature Microsoft installs and updates for you, with its own identity, such as the Key Vault secrets driver. Lesson 29.9
control plane (control-plane)
In Azure: managing a resource itself (create a vault, scale a node pool) through ARM. Being allowed here does not let you touch what is inside. Lesson 29.1
create-for-rbac (az ad sp create-for-rbac)
The az command that creates an app, its service principal and optionally one role assignment, and prints the secret once. Lesson 29.8
custom role (custom roles, AssignableScopes)
A role definition you write yourself, with only the actions a job needs. AssignableScopes limits where it can be assigned. Lesson 29.18
dataActions (dataAction, notDataActions)
The data-plane operations a role allows, such as reading a secret value or writing a blob. Owner and Contributor have none. Lesson 29.13
DefaultAzureCredential
The Azure SDK helper that tries, in order, environment variables, workload identity, managed identity and your az login. Same code on a laptop and in Azure. Lesson 29.9
deny assignment (deny assignments)
An explicit "no" that beats any role. Only Azure creates them, for a few managed features. Lesson 29.13
device code flow (--use-device-code, device code)
Signing in from a box with no browser: the CLI prints a URL and a code, you enter the code on another device, and the CLI receives the token. Lesson 29.1
effective access (effective permissions)
What a principal can really do: the union of every assignment at the target scope and above, including through groups. Lesson 29.13
Entra role (Entra roles, directory role, Application Administrator)
A permission over the directory itself, such as registering apps. Separate from Azure roles like Owner, which are about resources. Lesson 29.8
Entra token (Azure token, OAuth token)
A short-lived signed string from Entra ID that says who you are and which service it is for. az and the SDKs send it with every request. Lesson 29.1
environment (GitHub) (GitHub environment, environment: dev)
A named deploy target a GitHub job declares, such as dev or prod. It can require reviewers, and it appears in the OIDC subject.
Event Grid
Azure's service that delivers "something happened" events, such as a secret nearing expiry, to whoever subscribes.
expression reference
In JMESPath, &name hands a function like sort_by the expression to evaluate on each element, rather than a value. Lesson 29.4
FailedMount
The Kubernetes event on a pod whose volume could not be mounted. The pod stays in ContainerCreating; the message carries the real error. Lesson 29.27
federated credential (federated credentials, federated identity credential, FIC)
A trust rule on an identity: tokens from this issuer, for this subject and audience, count as this identity. No secret is stored anywhere. Lesson 29.8
filter expression (JMESPath filter)
In JMESPath, [?condition] keeps only the elements where the condition is true, like jq's select. Lesson 29.4
FinOps
The practice (and the people) tracking and cutting cloud spending.
ForbiddenByRbac (ForbiddenByFirewall)
Key Vault's 403 when no role grants the data action. ForbiddenByFirewall means your IP is blocked instead; no role fixes that. Lesson 29.23
GitHub workflow (workflow file, .github/workflows)
A YAML file in .github/workflows/ that GitHub runs on its own machines when you push: jobs made of steps.
GUID (GUIDs)
A globally unique ID: 32 hex digits in five groups, like 00000000-1111-2222-3333-444444444444. Azure gives every tenant, subscription and identity one. Lesson 29.1
HDD (Standard HDD)
Hard disk drive: a spinning magnetic disk. Cheapest storage, slowest for random reads and writes. Lesson 29.31
hierarchical namespace (ADLS Gen2, Data Lake Storage)
A storage account option with real directories instead of / in blob names, sold as ADLS Gen2. Lesson 29.29
id-token: write (permissions: id-token)
The GitHub workflow permission that lets a job ask GitHub for an OIDC token.
IMDS (Instance Metadata Service)
The Azure metadata service at 169.254.169.254 inside every VM; code asks it for a managed identity token. Lesson 29.9
JMESPath (--query)
The query language az's --query uses to pick and reshape parts of the JSON before printing. The same job as jq, different syntax. Lesson 29.4
Key Vault Reader
A role that reads vault and secret metadata only - names, dates - never values, despite its name. Lesson 29.23
Key Vault Secrets Officer
The role that creates, updates and deletes secrets. For people and automation that manage them. Lesson 29.23
kubelet identity (agentpool identity, kubeletidentity)
The managed identity every node of a Kubernetes cluster on Azure uses, mainly to pull images. Shared by every pod - never grant it app access. Lesson 29.9
KV
Short for Key Vault, often used in resource names (kv-shop-prod). Lesson 29.23
lifecycle management (lifecycle rule)
Storage rules that move blobs to cheaper tiers or delete them by age, automatically. Lesson 29.29
managed disk (managed disks, Azure Disk, az disk)
Azure's virtual hard disk: a block device attached to one VM at a time. managedBy names that VM. Lesson 29.31
management group (management groups)
An optional folder above subscriptions, so one policy or role can apply to many subscriptions at once. Lesson 29.1
MC_ group (node resource group, MC_rg-oncall-lab_aks-sysop_westeurope)
The resource group Azure creates next to a Kubernetes cluster to hold the cluster's own machines, disks and load balancer. Lesson 29.4
MFA (multi-factor authentication)
Multi-factor authentication: a second proof of identity on top of the password, like a phone prompt. Lesson 29.18
Microsoft Graph (graph.microsoft.com)
The API for directory objects: users, groups, apps. az ad calls it; az role calls ARM. Lesson 29.8
multiselect (hash multiselect, list multiselect)
In JMESPath, {Key:expr} builds a new object per element and [a, b] a list. The way to choose your own table columns or tsv fields. Lesson 29.4
nested group (nested groups)
A group that is a member of another group. Its members get the outer group's roles too. Lesson 29.18
object ID (objectId, oid, object id)
The GUID of one identity (user, group, service principal) in Entra ID. Role assignments point at this ID. Lesson 29.1
orphaned role assignment (orphan (RBAC), Identity not found)
A role assignment whose principal was deleted. It grants nothing; its Principal column is empty.
out-of-band change (out-of-band)
A change made outside Terraform, by a portal click or an az command. The next apply undoes it.
Owner role (Azure Owner)
The built-in Azure role that can do everything on the control plane, including granting access. No data access. Lesson 29.13
paired region
A second region Azure pairs with yours for geo-redundant copies, such as westeurope with northeurope. Lesson 29.29
PIM (Privileged Identity Management, eligible assignment)
Privileged Identity Management: roles you hold only as eligible and activate for a few hours, with a reason, logged. Just-in-time access. Lesson 29.18
projection (projections, JMESPath projection)
In JMESPath, [] or [*] over a list: the rest of the expression runs once per element. "For each element, take ...". Lesson 29.4
ProvisioningState (provisioningState, Succeeded)
Whether Azure finished creating or changing a resource: Succeeded, Updating, Failed. Lesson 29.3
purge (Key Vault) (az keyvault purge)
Deleting an item from the recycle bin for good. Lesson 29.23
raw string literal (JMESPath string)
In JMESPath, text in single quotes is a string. Text in double quotes is a field name, which is why "prod" silently matches nothing. Lesson 29.4
RBAC inheritance (--include-inherited)
A role on a scope also applies to everything inside it. Never upwards, never sideways. Lesson 29.13
RBAC propagation (propagation time)
The minutes it can take for a new role assignment to take effect everywhere. The first 403 after a grant proves nothing. Lesson 29.9
Reader role (Azure Reader)
The built-in Azure role that can see everything and change nothing. Lesson 29.13
refresh token (refresh tokens)
A longer-lived token used to get new access tokens without signing in again. That is why ~/.azure/msal_token_cache.json is a credential. Lesson 29.1
resource provider (provider namespace, Microsoft.KeyVault, Microsoft.Storage)
The Azure service that owns a kind of resource, named like Microsoft.KeyVault. It is the /providers/ part of a resource ID. Lesson 29.1
RG
Short for resource group, often used in names (rg-shop-prod). Lesson 29.1
Role Based Access Control Administrator (RBAC Administrator)
A role that can grant access, and supports conditions like "may only assign these two roles". The safer way to let automation grant access. Lesson 29.13
role definition (role definitions, az role definition)
A named list of allowed operations: actions, notActions, dataActions, notDataActions. Lesson 29.13
SAS (SAS token, shared access signature, user delegation SAS)
A URL with a signature appended: whoever has it may do what it allows until it expires. A user delegation SAS is signed via Entra ID instead of a key. Lesson 29.29
scope (Azure) (RBAC scope)
Where a role assignment applies: a management group, subscription, resource group or resource, given as a resource ID. Lesson 29.13
secret expiry (--expires, attributes.expires, SecretNearExpiry)
A date stored on a Key Vault secret. Azure does not act on it; something else must rotate the secret.
secret version (secret versions, list-versions)
Every secret set creates a new version of the secret; the old ones stay. Readers get the latest unless they pin one. Lesson 29.23
SecretProviderClass
The Kubernetes object that tells the Secrets Store driver which vault, which identity and which secrets. Lesson 29.27
security group (security groups, Entra group, az ad group)
An Entra ID group used for access. Grant a role to the group once; then only membership changes. Lesson 29.18
showback
Showing each team what it spends in the cloud, without charging it. Built on resource tags.
SMB
The Windows file-sharing protocol (port 445). Azure Files shares are mounted over SMB or NFS. Lesson 29.31
SP
Short for service principal: the identity an app or automation uses to sign in to Entra ID. Lesson 29.8
SSD (Premium SSD, Standard SSD)
Solid-state drive: flash storage, much faster than spinning disks. Azure managed disks come as Standard HDD, Standard SSD, Premium SSD and Ultra. Lesson 29.31
subject claim (OIDC subject)
The field in a token saying which workload it is, such as repo:org/repo:environment:dev or system:serviceaccount:ns:name. Must match exactly. Lesson 29.8
table transformer
A built-in choice of columns an az command uses for -o table. Without one, only top-level plain values are shown and nested fields disappear. Lesson 29.3
token audience (audience)
The service a token is valid for. A token for Key Vault is useless against Storage. Lesson 29.9
token cache (msal_token_cache.json, ~/.azure)
The file where az keeps your access and refresh tokens. Anyone who can read it can act as you. Lesson 29.1
token claim (token claims)
One field inside a token: who issued it, who it is about, which groups, when it expires. Lesson 29.8
token exchange (api://AzureADTokenExchange)
Trading one token for another: the pod's Kubernetes token for an Entra token. api://AzureADTokenExchange is the audience it uses. Lesson 29.9
token issuer (issuer URL, OIDC issuer)
Who signed a token, as a URL. A federated credential only trusts tokens from its exact issuer. Lesson 29.8
UI (user interface)
User interface: the screens a person clicks through, such as the Azure portal.
unattached disk (diskState, Unattached)
A managed disk no VM is using. Still billed every hour. Lesson 29.31
UPN (user principal name)
A user's sign-in name in Entra ID, written like an email address: [email protected]. Lesson 29.8
URI
Uniform resource identifier: a full address of a thing, such as https://kv-shop-prod.vault.azure.net/secrets/db-password. Lesson 29.23
User Access Administrator (UAA)
The built-in role that can grant access but not build. Whoever holds it can make themselves Owner. Lesson 29.13
workload identity (azure.workload.identity/use, azure.workload.identity/client-id)
Letting one Kubernetes ServiceAccount act as one Azure identity: the cluster signs a token, Entra ID trusts it through a federated credential. Lesson 29.9