Two clusters. Containers - the foundation, the tool that made them ubiquitous, where they run in production, the comparisons to help you pick, and how each side auto-scales. And identity - the Microsoft Entra family that decides who can sign in and what they can reach.
The runtime-agnostic foundation - what's inside one, how it differs from a virtual machine, and the Linux primitives (namespaces, cgroups, layered filesystems) that make it work.
Read it →The platform that turned containers usable - Engine, CLI, Desktop, Hub, Compose, and Buildx, plus the build-ship-run cycle every developer learns first.
Read it →The daemonless, rootless container engine - the same commands as Docker, minus the background service and the need for root, plus pods that mirror Kubernetes.
Read it →Serverless containers as long-lived services - HTTPS, autoscaling, rolling revisions, and a managed environment, without a Kubernetes cluster to operate underneath.
Read it →Serverless containers that start, do work, and exit - scheduled by cron, triggered by a queue, or kicked off on demand, on the same platform that runs your services.
Read it →Same platform, same image, two contracts. The dividing line between Apps and Jobs, the billing implications, and a four-question decision tree for picking the right one.
Read it →Two serverless ways to run bounded work on Azure - one ships a container, one ships a handler. Duration, programming model, billing, and which one fits the task.
Read it →Both auto-scale - but through different machinery and different units. The scale signal, the scale controller vs KEDA, scale to zero, and a worked burst.
Read it →A field guide to every product under the Microsoft Entra umbrella - what each one does, what problem it solves, and when you'd actually reach for it.
Read it →The umbrella for Microsoft's identity and network access portfolio - a family centered on Entra ID (formerly Azure AD) that secures who can sign in and what they can reach.
Read it →The cloud directory that Microsoft 365 and Azure both sit on - users, groups, and applications, formerly known as Azure Active Directory.
Read it →The unified identity service for everyone outside your org - consumers, business customers, and partner guests - and the successor to Azure AD B2C for new builds.
Read it →The managed customer identity service for sign-up and sign-in on consumer apps - local, social, and enterprise providers, hosted pages, MFA, and OAuth or OIDC tokens.
Read it →The unified REST API for Microsoft 365, Entra, and Windows - one endpoint and one auth contract for users, mail, calendars, files, Teams, groups, and devices.
Read it →