AZ-900 Glossary
Key terms and acronyms for the AZ-900 exam, explained in plain language.
- Availability set
- A grouping of virtual machines across fault domains and update domains inside one datacenter, so maintenance or a hardware failure affects only some VMs. Two or more VMs in an availability set carry a 99.95% SLA.
- Availability zone
- A physically separate datacenter (or group of datacenters) within an Azure region, with independent power, cooling, and networking. Regions with zones have at least three. VMs spread across zones carry a 99.99% SLA.
- Azure Advisor
- A service that analyses your Azure resources and gives personalised recommendations in five categories: reliability, security, performance, operational excellence, and cost.
- Azure Arc
- A service that extends Azure management — including Policy, monitoring, and the portal — to servers, Kubernetes clusters, and data services running on-premises or in other clouds, without moving them to Azure.
- Azure CLI
- A cross-platform command-line tool (the az commands) for managing Azure resources from Windows, macOS, or Linux, scriptable and automation-friendly.
- Azure Cloud Shell
- A browser-based shell built into the Azure portal, offering Bash or PowerShell with the Azure CLI and Azure PowerShell preinstalled and files stored persistently in Azure storage.
- Azure Cost Management
- The tool for analysing and controlling Azure spending: cost analysis, budgets, alerts, recommendations, and exports.
- Azure DNS
- A service that hosts DNS domains in Azure, resolving domain names to IP addresses using Microsoft's global network of name servers.
- Azure ExpressRoute
- A private, dedicated connection between an on-premises network and Azure, provided through a connectivity partner, that never crosses the public internet.
- Azure Functions
- Azure's serverless compute service: code runs in response to events, billing is per execution, and the service scales to zero when idle.
- Azure Migrate
- The hub for assessing and migrating on-premises servers, applications, and data to Azure, including discovery and cost estimation.
- Azure Monitor
- The monitoring service for Azure resources, collecting metrics and logs, with alert rules and action groups to notify or automate responses.
- Azure Policy
- A service that creates and enforces rules for Azure resources (effects include Deny, Audit, Append, Modify, and DeployIfNotExists), with a compliance dashboard and initiatives that group policies.
- Azure portal
- The web-based graphical interface (portal.azure.com) for managing Azure resources, with dashboards and visual tools.
- Azure PowerShell
- The Az module of PowerShell cmdlets for managing Azure resources from PowerShell scripts and sessions.
- Azure Resource Manager (ARM)
- The deployment and management layer for Azure: every request to create, update, or delete a resource passes through ARM.
- Azure Service Health
- The service reporting the health of the Azure platform itself: Azure status, service issues affecting your subscriptions, planned maintenance, and Resource Health.
- Azure Virtual Network (VNet)
- An isolated, private network in Azure, scoped to one region, where resources communicate with each other, the internet, and on-premises networks. Divided into subnets.
- Azure VPN Gateway
- A service that connects an on-premises network to Azure over the public internet through an encrypted tunnel (site-to-site or point-to-site VPN).
- Blob Storage
- Azure's object storage service for unstructured data such as text, images, video, and backups, with Hot, Cool, Cold, and Archive access tiers.
- CapEx (capital expenditure)
- Upfront spending on physical infrastructure (servers, datacenters) that is owned and depreciated over time. The cloud shifts spending from CapEx to OpEx.
- Conditional Access
- Microsoft Entra ID's policy engine: if a sign-in matches conditions (user, device, location, risk), then enforce controls such as requiring MFA or blocking access.
- Consumption-based model
- Paying for cloud services based on actual usage, with no upfront cost — you pay for what you use, when you use it, and stop paying when you stop.
- Defender for Cloud
- Microsoft Defender for Cloud: Azure's cloud security posture management and threat-protection service, providing a secure score, recommendations, and security alerts.
- Defense in depth
- A security strategy using multiple layers of protection (physical, identity and access, perimeter, network, compute, application, data) so that if one layer fails, the next still stands.
- Elasticity
- The ability of a system to scale resources automatically as demand changes — adding capacity when demand rises and removing it when demand falls.
- Entra ID (Microsoft Entra ID)
- Microsoft's cloud-based identity and access management service (formerly Azure Active Directory), storing user accounts and controlling access to Azure, Microsoft 365, and other applications.
- Hybrid cloud
- A cloud model combining a public cloud and a private cloud, bound together so data and applications can move between them.
- IaaS (infrastructure as a service)
- A cloud service type where the provider supplies virtualised infrastructure (VMs, networks, storage) and the customer manages the operating system and above.
- Log Analytics
- The Azure Monitor workspace where logs are stored and queried with the Kusto Query Language (KQL) to investigate issues across resources.
- Management group
- A container for subscriptions at the top of the Azure resource hierarchy, used to apply governance (policies, access) across many subscriptions at once.
- MFA (multifactor authentication)
- Authentication requiring two or more verification factors — something you know, something you have, or something you are — so a stolen password alone is not enough.
- OpEx (operational expenditure)
- Ongoing spending on services as they are consumed, typically billed monthly. Cloud computing shifts IT spending from CapEx to OpEx.
- PaaS (platform as a service)
- A cloud service type where the provider supplies the platform (hardware, OS, runtime) and the customer supplies only the application code and data. Examples: Azure App Service, Azure SQL Database.
- Private endpoint
- A private IP address inside your virtual network assigned to an Azure service, so traffic to that service stays on the private network and never crosses the internet.
- Region pair
- Two Azure regions linked together (at least 300 miles apart, same geography where possible) for platform-update sequencing, geo-replication, and data residency.
- Resource group
- A container for Azure resources within a subscription. A resource belongs to exactly one group; groups cannot nest; deleting a group deletes its contents.
- Resource lock
- A setting that prevents accidental deletion (CanNotDelete) or any modification (ReadOnly) of a resource, resource group, or subscription, applying to all users including administrators.
- RBAC (role-based access control)
- Azure's access-control system: a role assignment combines a security principal (who), a role definition (what), and a scope (where). Built-in roles include Owner, Contributor, Reader, and User Access Administrator.
- SaaS (software as a service)
- A cloud service type where the provider supplies a finished application (for example Microsoft 365) and the customer simply uses it, managing only its data, accounts, and access.
- Serverless
- A computing model where the provider manages all servers and the customer supplies only code that runs in response to events, paying per execution and scaling to zero when idle.
- SLA (service level agreement)
- A published commitment for a service's availability or performance, usually expressed as an uptime percentage (for example, 99.99% for VMs across availability zones).
- Subscription
- The unit of billing and access control in Azure. Every resource belongs to one subscription; subscriptions sit below management groups and above resource groups in the hierarchy.
- Tag
- A name-value pair attached to a resource, resource group, or subscription for organisation and cost reporting (for example, Department: Finance). Tags are metadata only and are not inherited automatically.
- Zero Trust
- A security model that assumes no implicit trust: verify explicitly, use least privilege access, and assume breach. Every access request is authenticated and authorised based on identity, device, and risk signals.
Advertisement