🔒 Guided

Pre-launch preview. Authorised access only.

Incorrect code

Guided by A Guide to Cloud
Explore AB-900 AI-901
Guided AZ-900 Domain 2
Domain 2 — Module 11 of 11 100%
18 of 26 overall

AZ-900 Study Guide

Domain 1: Describe Cloud Concepts

  • What is Cloud Computing? Free
  • Cloud Models: Public, Private, and Hybrid Free
  • Cloud Pricing: Consumption, Serverless, and Pay-as-You-Go Free
  • High Availability and Scalability Free
  • Reliability, Security, and Manageability Free
  • IaaS, PaaS, and SaaS Explained Free
  • Choosing the Right Cloud Service Free

Domain 2: Describe Azure Architecture and Services

  • Azure Regions, Zones, and Datacenters
  • Resources, Resource Groups, and Subscriptions
  • Azure Virtual Machines
  • Azure Compute: Containers, Functions, and App Service
  • Azure Networking: VNets, Subnets, and Peering
  • Connecting to Azure: VPNs, ExpressRoute, and DNS
  • Azure Storage Services
  • Data Migration: Moving to Azure
  • Microsoft Entra ID: Your Identity Hub
  • Authentication and External Identities
  • Azure Security: RBAC, Zero Trust, and Defender

Domain 3: Describe Azure Management and Governance

  • What Affects Your Azure Bill
  • Pricing Calculators: TCO and Azure Pricing
  • Cost Management and Tags
  • Azure Governance: Purview, Policy, and Locks
  • The Azure Portal and Cloud Shell
  • Infrastructure as Code: ARM, Bicep, and Arc
  • Azure Advisor and Service Health
  • Azure Monitor: Logs, Alerts, and Insights

AZ-900 Study Guide

Domain 1: Describe Cloud Concepts

  • What is Cloud Computing? Free
  • Cloud Models: Public, Private, and Hybrid Free
  • Cloud Pricing: Consumption, Serverless, and Pay-as-You-Go Free
  • High Availability and Scalability Free
  • Reliability, Security, and Manageability Free
  • IaaS, PaaS, and SaaS Explained Free
  • Choosing the Right Cloud Service Free

Domain 2: Describe Azure Architecture and Services

  • Azure Regions, Zones, and Datacenters
  • Resources, Resource Groups, and Subscriptions
  • Azure Virtual Machines
  • Azure Compute: Containers, Functions, and App Service
  • Azure Networking: VNets, Subnets, and Peering
  • Connecting to Azure: VPNs, ExpressRoute, and DNS
  • Azure Storage Services
  • Data Migration: Moving to Azure
  • Microsoft Entra ID: Your Identity Hub
  • Authentication and External Identities
  • Azure Security: RBAC, Zero Trust, and Defender

Domain 3: Describe Azure Management and Governance

  • What Affects Your Azure Bill
  • Pricing Calculators: TCO and Azure Pricing
  • Cost Management and Tags
  • Azure Governance: Purview, Policy, and Locks
  • The Azure Portal and Cloud Shell
  • Infrastructure as Code: ARM, Bicep, and Arc
  • Azure Advisor and Service Health
  • Azure Monitor: Logs, Alerts, and Insights
Domain 2: Describe Azure Architecture and Services Premium ⏱ ~13 min read

Azure Security: RBAC, Zero Trust, and Defender

Azure security goes beyond passwords. Role-based access control, Zero Trust architecture, defence-in-depth, and Microsoft Defender for Cloud — the layers that keep your environment safe.

Security in layers

☕ Simple explanation

Think of a medieval castle.

A castle doesn’t rely on just one wall. It has a moat (network security), outer walls (firewalls), inner walls (access controls), locked rooms (data encryption), and guards (monitoring).

If an attacker gets past one layer, there’s another one waiting. This is defence-in-depth — multiple security layers so no single failure compromises everything.

Zero Trust takes this further: don’t trust anyone, even people inside the castle. Every person must show their ID at every door, every time. “Never trust, always verify.”

RBAC is how you decide who gets keys to which rooms. The cook can access the kitchen but not the treasury. The treasurer can access the treasury but not the armoury.

Defender for Cloud is the castle’s watchtower — constantly scanning for threats and telling you where your defences are weak.

Azure security is built on multiple complementary concepts:

Role-Based Access Control (RBAC) provides fine-grained access management for Azure resources. It uses roles (collections of permissions), security principals (users, groups, service principals), and scopes (management group, subscription, resource group, or resource) to control who can do what.

Zero Trust is a security model that assumes breach and verifies every request as though it originates from an untrusted network. Three principles: verify explicitly, use least privilege access, and assume breach.

Defence-in-depth uses multiple layers of security so that if one layer fails, subsequent layers provide protection. Layers include physical security, identity, perimeter, network, compute, application, and data.

Microsoft Defender for Cloud is a cloud security posture management (CSPM) and cloud workload protection platform (CWPP) that provides security recommendations, threat detection, and compliance monitoring across Azure, hybrid, and multi-cloud environments.

Azure RBAC — who can do what

RBAC controls access to Azure resources using three concepts:

ConceptWhat It IsExample
Security principalWHO is requesting accessUser, group, service principal, managed identity
RoleWHAT they can doOwner, Contributor, Reader, custom roles
ScopeWHERE the role appliesManagement group, subscription, resource group, or resource

Built-in roles

RolePermissions
OwnerFull access + can assign roles to others
ContributorFull access EXCEPT assigning roles
ReaderView-only access — can see but not change anything
User Access AdministratorManage user access to resources

How RBAC works at Summit Construction

PersonRoleScopeWhat They Can Do
IT ManagerOwnerProduction subscriptionEverything, including assigning roles
DeveloperContributorDev resource groupCreate/modify resources in dev
Project ManagerReaderProduction subscriptionView production resources, no changes
InternReaderDev resource groupView dev resources only

Key concept: RBAC permissions inherit down the hierarchy. A Contributor role assigned at the subscription level applies to ALL resource groups and resources within that subscription.

💡 Exam tip: Least privilege principle

Always assign the minimum permissions needed. If someone only needs to view resources, give them Reader, not Contributor. If they need to modify resources but not assign roles, give them Contributor, not Owner.

The exam tests this with scenarios like: “A developer needs to deploy code but should NOT be able to assign access to other users.” Answer: Contributor (not Owner).

Zero Trust — never trust, always verify

Zero Trust assumes that every request could be a threat, regardless of where it comes from or who is making it.

Three guiding principles:

PrincipleWhat It MeansExample
Verify explicitlyAlways authenticate and authorise based on all available dataCheck user identity, device health, location, and behaviour before granting access
Least privilege accessGive minimum permissions needed, for the minimum timeJust-in-time access, just-enough-access
Assume breachDesign as if attackers are already in your networkSegment access, encrypt everything, monitor continuously

Traditional model: Trust everyone inside the corporate network, block everything outside.

Zero Trust model: Trust nobody by default. Verify every access request, every time, regardless of network location.

Harbour Health applies Zero Trust: even a doctor on the hospital’s internal network must verify their identity, use MFA, and access only the patient records they’re authorised for. No blanket “inside the network = trusted” access.

Defence-in-depth — layered security

Defence-in-depth uses seven layers of security. An attacker must breach ALL layers to reach your data:

LayerWhat It ProtectsExample Controls
PhysicalDatacenter buildingsBiometric access, cameras, guards
IdentityWho can access the systemEntra ID, MFA, Conditional Access
PerimeterNetwork boundaryDDoS protection, firewalls
NetworkInternal network trafficNSGs, VNet segmentation, private endpoints
ComputeVMs and containersPatching, endpoint protection, secure boot
ApplicationYour softwareSecure coding, vulnerability scanning
DataYour informationEncryption at rest and in transit, access controls

Key exam concept: Data is at the centre — it’s what attackers ultimately want. Every layer exists to protect the data. Even if an attacker breaches the perimeter, they still face network, compute, application, and data layers.

Microsoft Defender for Cloud

Defender for Cloud is Azure’s security command centre:

FeatureWhat It Does
Security recommendationsTells you what’s misconfigured and how to fix it
Secure ScoreA percentage showing your overall security posture
Threat protectionDetects threats across Azure, hybrid, and multi-cloud
Compliance dashboardShows compliance against standards (ISO 27001, NIST, PCI DSS)
Just-in-time VM accessOpens VM ports only when needed, closes them after

How Harbour Health uses Defender for Cloud:

  • Secure Score shows 78% — they’re working to improve it
  • Recommendations flag 3 VMs missing encryption
  • Compliance dashboard confirms HIPAA alignment
  • Alerts notify security team of suspicious sign-in attempts
ℹ️ Defender for Cloud is free AND paid
  • Free tier (CSPM): Security recommendations, Secure Score, and basic assessments for Azure resources
  • Paid tier (CWPP): Enhanced threat detection, just-in-time access, adaptive controls, and multi-cloud coverage

The free tier alone provides significant value — every Azure subscription gets it automatically.

🎬 Video walkthrough

🎬 Video coming soon

Azure Security: RBAC, Zero Trust, and Defender — AZ-900

Azure Security: RBAC, Zero Trust, and Defender — AZ-900

~11 min

Flashcards

Question

What are the three principles of Zero Trust?

Click or press Enter to reveal answer

Answer

1. Verify explicitly (authenticate every request). 2. Least privilege access (minimum permissions needed). 3. Assume breach (design as if attackers are already in your network).

Click to flip back

Question

What is Azure RBAC?

Click or press Enter to reveal answer

Answer

Role-Based Access Control — assigns permissions to security principals (users, groups) at a specific scope (management group, subscription, resource group, resource). Built-in roles: Owner, Contributor, Reader.

Click to flip back

Question

What are the seven layers of defence-in-depth?

Click or press Enter to reveal answer

Answer

Physical → Identity → Perimeter → Network → Compute → Application → Data. Each layer protects if the previous one is breached. Data is at the centre — the ultimate target.

Click to flip back

Question

What is Microsoft Defender for Cloud?

Click or press Enter to reveal answer

Answer

Azure's security command centre providing: security recommendations, Secure Score (posture percentage), threat detection, compliance dashboards, and just-in-time VM access. Free tier available for all Azure subscriptions.

Click to flip back

Knowledge Check

Knowledge Check

A developer at Summit Construction needs to create and modify resources in the Development resource group but should NOT be able to assign access roles to other users. Which RBAC role should they receive?

Knowledge Check

Which Zero Trust principle states that users should receive only the minimum permissions they need to perform their job?

Knowledge Check

Harbour Health wants a dashboard showing their overall security posture as a percentage, along with recommendations for improvement. Which Azure service provides this?


🎉 You’ve completed Domain 2: Azure Architecture and Services! You now understand Azure’s infrastructure, compute, networking, storage, identity, and security. Next, we tackle cost management, governance, and monitoring tools.

Next up: What Affects Your Azure Bill — understanding the factors that drive your cloud costs.

← Previous

Authentication and External Identities

Next →

What Affects Your Azure Bill

Guided

I learn, I simplify, I share.

A Guide to Cloud YouTube Feedback

© 2026 Sutheesh. All rights reserved.

Guided is an independent study resource and is not affiliated with, endorsed by, or officially connected to Microsoft. Microsoft, Azure, and related trademarks are property of Microsoft Corporation. Always verify information against Microsoft Learn.