Skip to content

AZ-900 storage, identity, access and security

This page covers the second half of Describe Azure architecture and services (35-40% of the AZ-900 exam, skills outline as of July 20, 2026): Azure storage services, and Azure identity, access and security. The running example is the invented OrdersPortal app (ordersportal.example.test), which stores product images and invoice PDFs and signs in staff and partner users.

The Azure CLI fragments were not run here (no Azure subscription is available to this site’s build); their syntax was checked against the Azure CLI reference and Microsoft Learn samples.

Topic What the exam expects
Storage accounts Storage account types, naming and endpoints
Storage redundancy LRS, ZRS, GRS, GZRS and read-access variants
Storage services Blobs, Files, Queues, Disks, Tables; comparing them
Access tiers Hot, cool, cold and archive
Moving and migrating data AzCopy, Storage Explorer, Azure File Sync, Azure Migrate, Data Box
Directory services Microsoft Entra ID and Microsoft Entra Domain Services
Authentication methods SSO, MFA, passwordless
External identities B2B collaboration, B2B direct connect, External ID for customers
Conditional Access Signals, decisions and enforcement
Role-based access control Roles, scopes and inheritance
Zero Trust The three guiding principles
Defense in depth The seven layers
Microsoft Defender for Cloud Posture management and threat protection

A storage account gives your Azure Storage data a unique namespace reachable over HTTP or HTTPS from anywhere. Its name must be 3-24 characters of lowercase letters and numbers and unique across Azure, because it forms the service endpoints, such as https://<account>.blob.core.windows.net, https://<account>.file.core.windows.net, .queue., .table. and .dfs. (Data Lake Storage) endpoints.

The account type decides which services and redundancy options you get:

Type Services Redundancy
Standard general-purpose v2 Blobs (including Data Lake Storage), Queues, Tables, Azure Files LRS, GRS, RA-GRS, ZRS, GZRS, RA-GZRS
Premium block blobs Block and append blobs LRS, ZRS
Premium file shares Azure Files (SMB and NFS) LRS, ZRS
Premium page blobs Page blobs only LRS

Standard general-purpose v2 is recommended for most scenarios; premium types use SSDs for high transaction rates and low latency.

Terminal window
# OrdersPortal's media account: zone-redundant with geo-replication, HTTPS only
# (fragment, not run here)
az storage account create \
--name stordersportalmedia \
--resource-group rg-ordersportal-prod \
--location eastus2 \
--kind StorageV2 \
--sku Standard_GZRS \
--access-tier Hot \
--min-tls-version TLS1_2 \
--allow-blob-public-access false

Pitfall: the account name is global. stordersportalmedia fails if anyone else in Azure already uses it.

Azure Storage always keeps three copies of your data in the primary region. The redundancy option decides where those copies live and whether there is a second region.

Option Copies Protects against Durability per year (at least)
Locally redundant storage (LRS) 3 in one datacenter Drive and rack failures 11 nines
Zone-redundant storage (ZRS) 3 across three availability zones A zone (datacenter) outage 12 nines
Geo-redundant storage (GRS) LRS in the primary region + LRS in the secondary region A regional outage 16 nines
Geo-zone-redundant storage (GZRS) ZRS in the primary region + LRS in the secondary region Zone and regional outages 16 nines

Replication to the secondary region is asynchronous, so a regional disaster can lose the most recent writes; the recovery point objective (RPO) is typically under 15 minutes, with no SLA on replication time. By default, secondary data can’t be read until a failover. RA-GRS and RA-GZRS add read access to the secondary region at any time, which suits apps that can serve slightly stale data during an outage.

Pitfalls

  • LRS is cheapest but a datacenter-level disaster can destroy all three copies.
  • Read-access options don’t make the secondary writable; writes need a failover.
Service What it stores Typical use
Azure Blobs Unstructured objects (text or binary) Images and documents served to browsers, video streaming, backups and archives, data for analytics (with Data Lake Storage Gen2)
Azure Files Managed file shares over SMB or NFS Replacing on-premises file servers, shared configuration, lift-and-shift apps that expect a file share
Azure Queues Messages up to 64 KB, millions per queue Decoupling components and asynchronous work, often with Azure Functions
Azure Disks Block-level managed disks Operating system and data disks for VMs
Azure Tables NoSQL key-attribute data Large volumes of structured, non-relational data

All data written to Azure Storage is encrypted by the service, and data is reachable through REST APIs, SDKs, the Azure CLI, Azure PowerShell, the portal and Storage Explorer.

Beyond Azure Storage, the database services that come up alongside it are Azure Cosmos DB (globally distributed NoSQL with several APIs), Azure SQL Database and Azure SQL Managed Instance (managed SQL Server engine), and Azure Database for PostgreSQL and Azure Database for MySQL (managed open-source engines). The service once called Azure SQL Data Warehouse is now the dedicated SQL pool in Azure Synapse Analytics.

OrdersPortal keeps product images and invoice PDFs in Blobs, puts “generate invoice” messages on a queue, and keeps orders in Azure SQL Database.

Pitfall: Azure Files is the answer when an app needs a mounted share; Blob storage is object storage reached by URL or API.

Blob data can live in four access tiers that trade storage cost against access cost and latency:

Tier For data that is Minimum storage duration
Hot Accessed frequently (website images) None
Cool Infrequently accessed 30 days
Cold Infrequently accessed 90 days
Archive Rarely accessed, with flexible latency (long-term backups) 180 days

Hot, cool and cold can be set as the account default; archive can only be set per blob. Archive has the lowest storage price but the highest access cost, and archived blobs must be rehydrated to an online tier before they can be read, which takes up to 15 hours at standard priority (high priority can finish in under an hour for blobs under 10 GB). Lifecycle management rules can move blobs to cooler tiers automatically, but can’t rehydrate from archive.

Pitfall: moving a blob out of cool, cold or archive before its minimum duration incurs an early-deletion charge.

For individual files and folders:

  • AzCopy: a command-line utility to upload, download, copy between accounts and synchronize. Its sync is one-way, from the source you name to the destination.
  • Azure Storage Explorer: a desktop app for Windows, macOS and Linux that gives a graphical interface to blobs and files; it uses AzCopy underneath.
  • Azure File Sync: installs on Windows Server and keeps a local file server in bidirectional sync with an Azure file share, with cloud tiering so frequently used files stay local.

For whole environments:

  • Azure Migrate: a hub for discovering, assessing and migrating on-premises servers, databases and web apps to Azure, with integrated and partner tools.
  • Azure Data Box: a rugged physical device (up to 80 TB usable) shipped to your datacenter for offline transfer of large datasets into or out of Azure when network bandwidth is the bottleneck. Disks are wiped to NIST 800-88r1 standards after an import.
Terminal window
# Upload a folder of product images to OrdersPortal's blob container
# (fragment, not run here; assumes `azcopy login` or a SAS URL)
azcopy copy "./product-images" "https://stordersportalmedia.blob.core.windows.net/products" --recursive

Pitfall: AzCopy sync never deletes or updates the source based on the destination. Use Azure File Sync for two-way sync with a Windows file server.

Microsoft Entra ID (formerly Azure Active Directory) is Microsoft’s cloud identity and access management service. It provides authentication (including self-service password reset, MFA, banned-password lists and smart lockout), single sign-on, application management and device management, and it is the directory behind every Azure subscription and Microsoft 365 tenant. Microsoft Entra Connect synchronizes users from on-premises Active Directory so people use one identity everywhere.

Microsoft Entra Domain Services provides managed domain services (domain join, Group Policy, LDAP and Kerberos or NTLM authentication) without you deploying domain controllers. It is meant for legacy applications that can’t use modern authentication. Azure deploys two domain controllers (a replica set) and manages them; synchronization runs one way, from Microsoft Entra ID into the managed domain.

Pitfall: Microsoft Entra ID is not Active Directory Domain Services in the cloud. Use Entra Domain Services when an app needs Kerberos, LDAP or domain join.

  • Single sign-on (SSO): sign in once and use many applications. It reduces password sprawl and simplifies removing access, but SSO is only as secure as the initial authenticator.
  • Multifactor authentication (MFA): requires two or more factors from different categories: something you know (a password), something you have (a phone or key) and something you are (a fingerprint or face). Microsoft Entra multifactor authentication offers phone calls and app notifications, among other methods.
  • Passwordless: replaces the password with a trusted device plus a PIN or biometric. Microsoft Entra ID supports Windows Hello for Business (for a user’s own Windows PC), the Microsoft Authenticator app (phone sign-in with number matching) and FIDO2 security keys (phishing-resistant hardware keys built on WebAuthn).

Pitfall: two passwords are not MFA. The factors must come from different categories.

An external identity is a person, device or service outside your tenant. Microsoft Entra External ID covers three capabilities:

  • B2B collaboration: partners sign in with their own work, social or other identities and appear in your directory as guest users.
  • B2B direct connect: a mutual trust with another Microsoft Entra tenant, currently for Teams shared channels; those users are not added to your directory.
  • External ID for customers (formerly Azure AD B2C): identity for consumer-facing apps you publish.

Access reviews let guests or their sponsors recertify whether guests still need access. OrdersPortal invites its logistics partner’s staff as B2B guests instead of creating local accounts for them.

Pitfall: the external identity provider authenticates the guest, but you still authorize what the guest can do.

Microsoft Entra Conditional Access evaluates signals at sign-in (who the user is, their location, their device, the application and risk), makes a decision and enforces it: allow access, require MFA, or block. Common policies require MFA for administrators, allow access only from managed devices or approved client apps, and block sign-ins from unexpected locations.

Pitfall: Conditional Access is part of Microsoft Entra ID (it requires Microsoft Entra ID P1 or higher licensing); it is not configured on individual Azure resources.

Azure role-based access control (Azure RBAC) grants permissions by assigning roles (built-in ones such as Owner, Contributor and Reader, or custom roles) to users, groups, service principals or managed identities at a scope: a management group, subscription, resource group or single resource. Assignments are inherited by child scopes, and RBAC uses an allow model: if one assignment grants read and another grants write, you have both. RBAC is enforced on actions that pass through Azure Resource Manager (the control plane); it doesn’t control access inside your application.

Terminal window
# Let the OrdersPortal API's managed identity read product images, nothing more
# (fragment, not run here)
az role assignment create \
--assignee "<api-managed-identity-principal-id>" \
--role "Storage Blob Data Reader" \
--scope "/subscriptions/<subscription-id>/resourceGroups/rg-ordersportal-prod/providers/Microsoft.Storage/storageAccounts/stordersportalmedia"

Pitfall: assigning Owner at the subscription to “make it work” breaks least privilege. Grant the narrowest role at the narrowest scope.

Zero Trust assumes breach and verifies every request as though it came from an uncontrolled network. Its three guiding principles:

  • Verify explicitly: always authenticate and authorize using all available signals.
  • Use least privilege access: just-in-time and just-enough access, risk-based adaptive policies and data protection.
  • Assume breach: minimize blast radius, segment access, verify end-to-end encryption and use analytics for threat detection.

Traditional security trusted anything inside the corporate network; Zero Trust grants access based on identity, device and risk rather than location.

Pitfall: Zero Trust is a model, not a product. Conditional Access, MFA and RBAC are tools that implement it.

Defense in depth layers protections so that if one fails, the next slows the attack and raises alerts. From the outside in, the seven layers are:

  1. Physical security: datacenter buildings and hardware (Microsoft’s responsibility).
  2. Identity and access: SSO, MFA, auditing of sign-ins and changes.
  3. Perimeter: DDoS protection and perimeter firewalls such as Azure Firewall.
  4. Network: segmentation, deny by default, limited inbound and outbound access (network security groups).
  5. Compute: secure VM access, endpoint protection, patching.
  6. Application: secure code, secrets in Azure Key Vault (which stores secrets, encryption keys and certificates).
  7. Data: access control and encryption at rest and in transit.

Related services from the older AZ-900 notes: Azure DDoS Protection (free, always-on infrastructure protection for every public IP address, plus the paid Network Protection and IP Protection tiers; older study material calls the free layer Basic and the plan Standard), Azure Firewall (a managed, stateful network firewall), and Application Gateway with Web Application Firewall for HTTP traffic.

Pitfall: attackers are almost always after the data layer. Encrypting data and controlling access to it matters even when the outer layers look strong.

Microsoft Defender for Cloud is a security posture management and threat protection service for Azure, on-premises (through Azure Arc), and other clouds such as AWS and Google Cloud. It does three things:

  • Continuously assess: vulnerability assessment for VMs, container registries and SQL servers.
  • Secure: recommendations based on the Microsoft cloud security benchmark, grouped into a secure score, built on Azure Policy.
  • Defend: security alerts with remediation steps, correlated across the attack chain, plus protections such as just-in-time VM access.

Pitfall: Defender for Cloud recommends and alerts; it doesn’t replace configuring RBAC, network rules and encryption yourself.

  1. Which redundancy option keeps three copies across availability zones in one region, with no secondary region? Zone-redundant storage (ZRS).

  2. Which blob tier has the lowest storage cost but requires rehydration before data can be read? Archive.

  3. Which tool keeps an on-premises Windows file server in two-way sync with Azure Files? Azure File Sync. AzCopy only syncs one way.

  4. What are the three categories of authentication factors? Something you know, something you have and something you are.

  5. A user has Reader at the subscription and Contributor on one resource group. What can they do in that resource group? Create and manage resources there (Contributor), because RBAC is additive: the union of all assignments applies. They can read everything else in the subscription.

  6. Scenario: OrdersPortal must let a partner’s staff upload delivery documents, keep the documents for seven years at the lowest cost, survive a regional outage, and stop staff from signing in from unmanaged devices. What do you use? Invite the partner’s staff as B2B guests in Microsoft Entra ID and grant them a narrow data role (such as Storage Blob Data Contributor) on one container through RBAC. Store the documents in a GZRS (or RA-GZRS) account, and use a lifecycle rule to move them to cool, then archive after the period when they are still read. Enforce a Conditional Access policy that requires a compliant or hybrid-joined device for staff, with MFA for everyone.