Skip to content

AZ-900 Azure management and governance

The third AZ-900 skill area, Describe Azure management and governance, is worth 30-35% of the exam (skills outline as of July 20, 2026). It answers four questions an organization asks once it runs real workloads: what will this cost, how do we keep it compliant, how do we deploy and manage it, and how do we know it is healthy.

The running example is the invented OrdersPortal app (ordersportal.example.test), whose production resources live in the rg-ordersportal-prod resource group.

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. Run them in Azure Cloud Shell or a local Azure CLI after az login.

Topic What the exam expects
Cost management Cost factors, pricing calculator, Cost Management, budgets and alerts
Tags Purpose of tags
Microsoft Purview Purpose of Microsoft Purview
Azure Policy and resource locks Purpose of Azure Policy and resource locks
Service Trust Portal and compliance Where Microsoft publishes compliance information
Azure portal and Cloud Shell The portal and Cloud Shell
Azure CLI and Azure PowerShell Command-line tools
Azure Arc Managing non-Azure resources
Infrastructure as code IaC, Azure Resource Manager, ARM templates and Bicep
Monitoring tools Azure Advisor, Service Health, Azure Monitor, Log Analytics, alerts, Application Insights

Microsoft Learn lists six factors that affect cost:

  • Resource type: the service, its tier and settings (a premium storage account costs more than standard; a VM’s size, OS license and disks all count).
  • Consumption: pay-as-you-go by default, with discounts for commitment (reservations and savings plans) and Spot pricing for interruptible work, covered in cloud pricing models.
  • Maintenance: deleting a VM can leave its disks and IP addresses behind, still billing.
  • Geography: prices differ by region, and outbound data transfer is priced by billing zone. Some inbound transfer is free.
  • Subscription type: a free account includes some services free for 12 months, credit for the first 30 days, and more than 25 always-free products.
  • Azure Marketplace: third-party solutions bill for the vendor’s software or service on top of the Azure resources they run on.

The Azure pricing calculator estimates the cost of resources before you deploy them: pick services, region, tier, redundancy and expected usage, and it produces a monthly estimate. Nothing is provisioned. The separate Total Cost of Ownership (TCO) calculator has been retired, according to the current Microsoft Learn module.

Microsoft Cost Management tracks actual spend: cost analysis breaks costs down by subscription, resource group, service, region or tag; budgets set a spending limit for a scope; and cost alerts cover budget alerts (when spend reaches a threshold you choose), credit alerts (at 90% and 100% of Enterprise Agreement prepayment) and department spending quota alerts (EA). Budgets can also trigger automation, such as shutting down non-production VMs.

OrdersPortal sets a monthly budget on rg-ordersportal-dev with an alert at 80%, so the team investigates before the development environment overspends.

Pitfalls

  • A budget alerts; it doesn’t stop resources on its own unless you attach automation through an action group.
  • Pricing calculator results are estimates. Real bills depend on actual usage, data transfer and discounts.

Tags are name-value pairs (for example env=prod, app=OrdersPortal, costCenter=CC-1001) that you attach to resources, resource groups and subscriptions. They organize resources for cost reporting (group spend by cost center), resource management (find everything for one workload), operations (mark business criticality), security (classify data sensitivity), governance and compliance (require tags with Azure Policy) and automation (schedule shutdowns by tag).

Terminal window
# Add or merge tags on an existing resource group (fragment, not run here)
az group update \
--name rg-ordersportal-prod \
--set tags.owner=orders-team tags.dataClass=confidential

Pitfall: resources don’t inherit tags from their resource group by default. Use Azure Policy (for example, an “inherit a tag from the resource group” policy) if every resource must carry the tag.

Microsoft Purview is a family of data governance, risk and compliance solutions that gives a unified view of data across on-premises, multicloud and SaaS sources. It provides automated data discovery, sensitive data classification and end-to-end data lineage. Its two solution areas are risk and compliance (protecting sensitive data across Microsoft 365 services such as Teams, OneDrive and Exchange, and managing regulatory requirements) and unified data governance (a map of your data estate, including Azure, SQL and Hive databases and Amazon S3, showing where sensitive data lives and who can use it).

Older AZ-900 notes mention Azure Information Protection for labeling documents and email; that labeling capability is now part of Microsoft Purview Information Protection.

Pitfall: Purview governs data. Azure Policy governs resource configuration. Questions often contrast the two.

Azure Policy creates, assigns and manages rules that audit or enforce resource configuration: allowed regions, allowed VM sizes, required tags, disallowed public network access. It evaluates existing resources and flags non-compliant ones, can deny non-compliant deployments, and can remediate some, such as adding a missing tag. Policies can be grouped into initiatives (for example, a set of security baseline policies), and assignments are inherited from management groups down to resources. Built-in definitions cover storage, networking, compute, security and monitoring.

Resource locks prevent accidental deletion or change, even by users whose RBAC role allows it. There are two types: Delete (CanNotDelete in the CLI: read and modify allowed, delete blocked) and ReadOnly (read allowed, update and delete blocked, similar to restricting everyone to the Reader role). Locks can be applied to a resource, a resource group or a subscription and are inherited. To change a locked resource you must first remove the lock, whatever your role.

Terminal window
# Protect OrdersPortal's production resource group from deletion (fragment, not run here)
az lock create \
--name lock-ordersportal-prod \
--lock-type CanNotDelete \
--resource-group rg-ordersportal-prod
# Allow deployments only in two US regions for that resource group
definition=$(az policy definition list \
--query "[?displayName=='Allowed locations'].name" --output tsv)
az policy assignment create \
--name ordersportal-allowed-locations \
--policy "$definition" \
--scope "/subscriptions/<subscription-id>/resourceGroups/rg-ordersportal-prod" \
--params '{"listOfAllowedLocations": {"value": ["eastus2", "centralus"]}}'

Pitfalls

  • A ReadOnly lock can break normal operations, because some “read” actions in a service are POST requests (for example, listing storage account keys).
  • Policy and RBAC answer different questions: RBAC decides who can act; Policy decides what configurations are allowed.

The Microsoft Service Trust Portal (servicetrust.microsoft.com) publishes Microsoft’s security, privacy and compliance documentation: audit reports, certifications and details of the controls that protect Microsoft cloud services. Some documents require signing in with a Microsoft Entra work or school account and accepting a non-disclosure agreement; My Library lets you save documents and get notified of updates. It replaces the “Azure Trust Center” in older study notes.

Azure’s compliance offerings include programs such as ISO/IEC 27001 and 27018, SOC reports, NIST SP 800-53, HIPAA, GDPR, CSA STAR, FedRAMP and CJIS (the full list, by region and industry, is in the Azure compliance documentation). A program being available means Azure has the certification or attestation; your workload still has to be configured and operated to meet the requirement.

Pitfall: “Azure is HIPAA compliant” is a shared-responsibility statement, not a guarantee that your app is.

The Azure portal (portal.azure.com) is a web-based console for building, managing and monitoring everything from a single web app to a complex deployment, with customizable dashboards and accessibility options. It is present in every Azure datacenter, so it is resilient to single-datacenter failures and is updated continuously with no maintenance downtime. Copilot in Azure is an AI assistant in the portal that can explain services and draft commands; validate its suggestions before applying them.

Azure Cloud Shell is a browser-based shell, opened from the portal toolbar, that is already authenticated with your Azure credentials and needs no local installation. You choose Bash (with the Azure CLI) or PowerShell (with Azure PowerShell).

Pitfall: Cloud Shell runs with your permissions. It is not a sandbox; commands affect real resources.

The Azure CLI (az commands) and Azure PowerShell (cmdlets such as New-AzResourceGroup) are functionally equivalent: both call the Azure REST API, both can be scripted for repeatable setup and teardown, and both install on Windows, macOS and Linux as well as being preinstalled in Cloud Shell. The choice mainly comes down to which language your team knows. Azure PowerShell returns .NET objects you can pipe to other cmdlets; the CLI returns JSON you can filter with --query.

Terminal window
# The same task in each tool (fragments, not run here)
az group create --name rg-ordersportal-test --location eastus2
Terminal window
New-AzResourceGroup -Name rg-ordersportal-test -Location eastus2

Visual Studio Code, a free cross-platform editor, has Azure extensions (including the Bicep extension) that make it a common place to write these scripts and templates.

Pitfall: scripts are imperative: running a “create” script twice can fail or create duplicates. Declarative templates (next sections) describe the desired end state instead.

Azure Arc extends Azure Resource Manager to resources outside Azure, so you can govern and monitor on-premises and multicloud resources with the same tools. It projects non-Azure resources into Azure Resource Manager and currently manages servers, Kubernetes clusters, Azure data services, SQL Server and virtual machines (preview) hosted outside Azure. Once a server is Arc-enabled you can apply Azure Policy, RBAC, tags, Azure Monitor and Defender for Cloud to it.

OrdersPortal still has a reporting server in its old datacenter; Arc lets the team apply the same tagging and allowed-configuration policies to it as to Azure VMs.

Pitfall: Arc doesn’t move workloads to Azure. It brings Azure management to where the workloads already are.

Infrastructure as code (IaC) means defining infrastructure in code and templates kept in source control, instead of configuring it by hand. It ranges from CLI and PowerShell scripts to declarative templates.

Azure Resource Manager (ARM) is the deployment and management service for Azure. Every request, from the portal, CLI, PowerShell, SDKs or REST API, goes through Resource Manager, which authenticates and authorizes it (this is where RBAC is enforced) and passes it to the service. That is why every tool gives consistent results. Resource Manager lets you deploy resources as a group, apply RBAC and tags, and define dependencies so resources deploy in the right order.

ARM templates are declarative JSON files describing the resources you want. Resource Manager validates the template, then deploys resources in dependency order and in parallel where possible; templates are repeatable, modular and can call deployment scripts. Bicep is a simpler declarative language that compiles to the same ARM deployments:

// storage.bicep: OrdersPortal invoice storage (fragment, not deployed here)
param location string = resourceGroup().location
resource invoices 'Microsoft.Storage/storageAccounts@2023-05-01' = {
name: 'stordersportalinv'
location: location
sku: { name: 'Standard_ZRS' }
kind: 'StorageV2'
properties: {
minimumTlsVersion: 'TLS1_2'
allowBlobPublicAccess: false
}
tags: { app: 'OrdersPortal', env: 'prod' }
}

Deploy it with az deployment group create --resource-group rg-ordersportal-prod --template-file storage.bicep. Running it twice leaves one storage account in the declared state, because template deployments are idempotent.

Pitfall: changes made by hand in the portal drift from the template. Make changes in code and redeploy.

Azure Advisor evaluates your resources and gives personalized recommendations in five categories: Reliability, Security, Performance, Operational Excellence and Cost. You can act on, postpone or dismiss each recommendation and be notified of new ones.

Azure Service Health combines three views, from broad to narrow: Azure status (global health of all services and regions), Service Health (outages, planned maintenance and health advisories for the services and regions you use, with alerts) and Resource Health (the health of an individual resource, such as one VM, and whether a problem is on Azure’s side).

Azure Monitor collects, analyzes and acts on metrics and logs from Azure, on-premises and multicloud resources and applications:

  • Log Analytics is the portal tool for writing and running queries (in Kusto Query Language) against the collected log data.
  • Azure Monitor alerts fire when a metric or log condition is met; an action group decides who is notified and what automation runs. Action groups are reusable by Service Health and Advisor too.
  • Application Insights monitors web application performance and usage (request rates, response times, failure rates, dependency calls, page loads), in Azure, on-premises or another cloud, through an SDK or an agent without code changes, and can run availability tests that send synthetic requests.

For OrdersPortal: Application Insights tracks checkout latency, an alert fires when the API’s failure rate passes 5%, Service Health notifies the team of maintenance in East US 2, and Advisor suggests resizing an underused VM.

Pitfall: Service Health reports Azure platform problems; Azure Monitor reports how your own resources and apps behave. You need both.

  1. Which tool estimates the monthly cost of resources you haven’t deployed yet? The Azure pricing calculator. Cost Management analyzes costs you have already incurred.

  2. A user with the Owner role can’t delete a storage account. What is the most likely cause? A Delete (CanNotDelete) or ReadOnly resource lock on the account, its resource group or its subscription. Locks apply regardless of RBAC role; the lock must be removed first.

  3. Which service would you use to make sure that VMs can only be created in approved regions? Azure Policy, for example the built-in “Allowed locations” definition with a deny effect.

  4. Which service lets you apply Azure Policy and monitoring to servers running in another cloud provider? Azure Arc.

  5. What are the five Azure Advisor recommendation categories? Reliability, Security, Performance, Operational Excellence and Cost.

  6. Scenario: OrdersPortal’s finance team wants monthly costs by cost center, the security team wants every production resource deployed in approved regions and protected from accidental deletion, and operations wants to know about Azure outages affecting their region. Design the setup. Require a costCenter tag with Azure Policy (deny or modify effect) and group cost analysis by that tag, with a budget and alert per cost center. Assign the Allowed locations policy at the production management group or subscription so every subscription below inherits it, and put a CanNotDelete lock on the production resource groups. Deploy through Bicep from source control so the configuration is repeatable. Create a Service Health alert for the services and regions in use, routed through an action group to the operations team.