Short, honest write-ups of the ideas that come up in interviews and on the job. Each one teaches the concept properly, cites the Microsoft documentation, and points back to the class that drills it until it sticks.
The az commands you actually use, grouped: sign-in, resource groups, VMs, AKS, Key Vault — plus --query and -o table for output. Same in a terminal or a pipeline.
The portal where tenant identity lives — users, groups, roles, enterprise-app SSO, Conditional Access. Step-by-step least-privilege access and SSO setup.
Microsoft’s container-optimised distro (formerly CBL-Mariner): a small, hardened host OS for AKS nodes. Why it exists, how to choose it, and Ubuntu-vs-Azure-Linux.
A plain-English explanation of Git: the working directory, staging, and commit model, why "distributed" matters, and your first repo command by command.
git fetch downloads commits into your remote-tracking branch without touching your files; git pull fetches and then merges. The safe look-first workflow.
git stash push with a path sets aside only the files you name; -p stashes partial hunks. Naming, inspecting, and restoring with pop vs apply.
Merge keeps both histories with a merge commit; rebase replays commits into a linear history but rewrites hashes. The golden rule and how to handle conflicts.
The stages stay the same; the bottleneck moves from typing syntax to guiding and reviewing. Why CI/CD, tests, and scanning become the safety nets.
Describe intent in plain language, an AI writes and revises the code, you steer and review. Where the term came from, the workflow, and the honest limits.
An honest answer from a free one: do not pay five figures for the web-dev lane AI hit hardest. A project-first cloud track sidesteps the sunk cost.
For a beginner it is a false choice. Cloud is the enterable lane; most AI roles want senior depth. Learn cloud, then add AI-on-Azure.
Worth it because of AI, not despite it — more AI workloads land on Azure. But the payoff is a project you can demo, not a cert on a shelf.
An honest ROI answer, including who it is not worth it for. AI raises the payoff of cloud, because every model runs on infrastructure someone has to own.
Not "be adaptable" — a concrete skill mix. Move from running commands to owning outcomes: cost, security, incident judgment, stakeholder trust.
DevOps is automation, so an AI tool is your next hire, not your replacement. It writes the YAML; you own the 3am incident and the rollback call.
The fear is rational, but aimed at the wrong thing: the easy entry path narrowed while demand moved up to running the infrastructure AI depends on.
"AI can do cloud" swaps two jobs: generating a script versus owning what happens when it runs. The owning half is growing, and it is the career.
The value moved from producing code to judging it. Cloud work lives on the judging side and needs far less hand-written code than you fear.
The 30-second az webapp up, a static-vs-dynamic decision, custom domain plus free HTTPS, and what it actually costs per month.
Reuse your Windows Server and SQL licenses to drop the software fee — the Software Assurance catch, the vCore math, and how to toggle it.
Defender for Cloud secures your resources; Sentinel is your SIEM across everything. How they connect, and which you actually need.
File share (SMB) versus object store (HTTP) — pick by access pattern. Protocols, cost, and the scenarios where the answer is neither.
Most people start with AZ-900 — and the one case you skip it. Study time, cost, and the honest part: neither gets you hired alone.
What each tier is for, and the feature cliffs — Always On, slots, VNet — that force an upgrade. F1 to P1v3, side by side.
P1 for everyone, P2 for admins — and what is already free. The Free/P1/P2 feature ladder, and how not to overbuy.
Engineers build and run it; architects design it. The AZ-104 to AZ-305 path, salary reality as ranges, and the messy DevOps middle.
ACI runs a container; Container Apps runs a container service. Burst jobs versus scale-to-zero, cost, and the AKS off-ramp.
UDRs override Azure's default routing. System routes, next-hop types, forcing traffic through a firewall, and route precedence.
MFA is the what; Conditional Access is the when. Why you use both, Security Defaults versus CA, and the P1 licensing line.
One blueprint, one instance per tenant, one portal view. The mental model that finally makes Entra app identities click.
One short, honest Azure note at a time — plus the occasional hiring signal. No spam, no card, unsubscribe in one click.