Struggling to grasp the key concepts of Microsoft Azure Fundamentals (AZ-900)? Don’t waste hours going through endless documentation! Our expertly crafted Cheat Sheet gives you:

Concise, exam-focused notes – everything you need, nothing you don’t.
Key concepts, definitions, and services in an easy-to-read format.
Quick recall sections & memory aids to boost retention.
Real-world examples to solidify understanding.
Perfect for last-minute revision—cram smarter, not harder!

Whether you’re new to cloud computing or want to pass on your first try, this cheat sheet is your shortcut to success.

💡 Get yours now and pass AZ-900 with confidence!

A) Describe cloud concepts

Iaas: Infrastructure as a service, such as IIS, SQL Server on Azure VMs, Virtual machines (VMs), and Virtual networks 

Paas: Platform as a service, such as Microsoft Entra ID, Azure App Service, Azure SQL Database, Azure Cosmos DB, and Azure Storage options/accounts

Saas: Software as a service, such as Microsoft Office 365, Dynamics 365, and Outlook

Azure Arc: It provides a centralized, unified way to manage your entire environment together by projecting your existing non-Azure and/or on-premises resources into Azure Resource Manager.

Azure expenditure models:

1. Capital expenditures (CapEx):

It is used to purchase, upgrade, or maintain physical assets

It is generally nonrecurring

It results in permanent assets

Example: Azure Reserved Instances (Azure RI)

2. Operational expenditure (OpEx): 

Cloud computing costs fall under operational expenditure

Ongoing costs of doing business

Used for day-to-day operations

Example: Azure on-demand or pay-as-you-go

3. Consumption-based model: This model allows customers to pay for the IT resources they use and not the costs for the physical infrastructure, electricity, security, or anything else associated with maintaining a data centre.

Vertical scaling in Azure (Scaling up): With vertical scaling, you can vertically scale up to add more CPUs or RAM to a virtual machine. 

Horizontal scaling in Azure (Scaling out): With horizontal scaling, you can deploy more resources either automatically or manually by adding additional virtual machines or containers.

B) Describe Azure architecture and services

B1) Describe the core architectural components of Azure

Region pair > Region > Availability Zone > Datacentre > Availability set (VMs)

Region pairs: Azure regions are paired with another region within the same geography for the replication of resources across a region, which helps reduce the likelihood of interruptions. Most regions are paired in two directions, meaning they are the backup for the region that provides a backup for them 

Azure Regions: A region is a geographical area on the planet that contains at least one and potentially multiple data centres (availability zones) that are nearby and connected with a low-latency link.

Sovereign regions: They are instances of Azure that are isolated from the main instance of Azure, like the Azure US government and China.

Availability Zone: Availability zones are physically separated data centres within an Azure region.

Each availability zone comprises one or more data centres equipped with independent power, cooling, and networking. If one zone goes down, the other continues working

Data transfer within the same Availability Zone in Azure is free of charge; you only incur costs when transferring data between different Availability Zones within the same region

Azure Datacentres: They are grouped into Azure Regions or Azure Availability Zones that are designed to help you achieve resiliency and reliability for your business-critical workloads

Azure management infrastructure: 

Azure AD Tenant (Main account) > Management groups > Subscriptions > Resource groups > Resources

Azure AD Tenant: A Microsoft Azure tenant is a dedicated instance of Microsoft Entra ID that represents an organisation, identity, or person. Tenant names typically end with “onmicrosoft.com”.

Azure Management Groups: Subscriptions can be managed in containers called management groups, just like the departments of an organisation.

Notes:

• Management groups can be nested
• The root management group is the top management group
• 10,000 management groups can be supported in a single directory
• A management group tree can support up to 6 levels of depth
• Each management group and subscription can support only one parent

Azure Subscription: In Azure, subscriptions are a unit of management, billing, and scale. It also allows users to provision resources. We can use the subscriptions to configure different billing models and apply different access management policies.

Subscription boundaries: 

1. Billing boundary: This subscription type determines how an Azure account is billed for using Azure. You can create multiple subscriptions for different types of billing requirements.
2. Access control boundary: Azure applies access-management policies at the subscription level. You can create separate subscriptions to reflect different organisational structures. 

Azure Resource Group: Resource groups are simply groupings of resources. 

Note: A single resource can only be in one resource group at a time.

Resources: A resource is the basic building block of Azure, like VMs, virtual networks, and databases. 

Note: Resource access control occurs at the subscription level.

Access to Azure resources: Azure portal, Azure PowerShell cmdlets, and the cross-platform Azure CLI (Bash)

Azure Service Level Agreements (SLA): It is Microsoft’s commitment to uptime and availability for individual Azure Services.

To read the rest of the article, you need to purchase and then download the ebook with the provided link below.

How to buy and download the digital file of this article?

Easillyy works with PayPal to facilitate the transaction process. After finishing the payment process, which can be seen on the payment guideline page, the file will be automatically sent to your email. To finish the payment process, you only need to have a valid debit or credit card and provide your details.