🔒 Guided

Pre-launch preview. Authorised access only.

Incorrect code

Guided by A Guide to Cloud
Explore AB-900 AI-901
Guided AZ-104 Domain 1
Domain 1 — Module 6 of 6 100%
6 of 27 overall

AZ-104 Study Guide

Domain 1: Manage Azure Identities and Governance

  • Microsoft Entra ID: Your Identity Foundation Free
  • Users, Groups & Licenses Free
  • RBAC: Who Can Do What in Azure Free
  • Subscriptions, Resource Groups & Management Groups Free
  • Azure Policy & Resource Locks Free
  • Tags, Cost Management & Azure Advisor Free

Domain 2: Implement and Manage Storage

  • Storage Accounts & Redundancy
  • Securing Storage: Keys, SAS & Firewalls
  • Blob Containers & Storage Tiers
  • Blob Lifecycle, Versioning & Soft Delete
  • Azure Files: Shares, Snapshots & Recovery

Domain 3: Deploy and Manage Azure Compute Resources

  • ARM Templates & Bicep: Infrastructure as Code
  • Virtual Machines: Create & Configure Free
  • VM Disks, Encryption & Migration
  • Availability Sets, Zones & Scale Sets
  • Containers: ACR, ACI & Container Apps
  • App Service Plans & Scaling
  • App Service: Slots, Certificates & Networking

Domain 4: Implement and Manage Virtual Networking

  • Virtual Networks & Subnets
  • VNet Peering & User-Defined Routes
  • NSGs & Application Security Groups
  • Azure Bastion, Service & Private Endpoints
  • Azure DNS & Load Balancers

Domain 5: Monitor and Maintain Azure Resources

  • Azure Monitor: Metrics & Logs
  • Alerts, Insights & Network Watcher
  • Azure Backup & Vaults
  • Azure Site Recovery & Disaster Recovery

AZ-104 Study Guide

Domain 1: Manage Azure Identities and Governance

  • Microsoft Entra ID: Your Identity Foundation Free
  • Users, Groups & Licenses Free
  • RBAC: Who Can Do What in Azure Free
  • Subscriptions, Resource Groups & Management Groups Free
  • Azure Policy & Resource Locks Free
  • Tags, Cost Management & Azure Advisor Free

Domain 2: Implement and Manage Storage

  • Storage Accounts & Redundancy
  • Securing Storage: Keys, SAS & Firewalls
  • Blob Containers & Storage Tiers
  • Blob Lifecycle, Versioning & Soft Delete
  • Azure Files: Shares, Snapshots & Recovery

Domain 3: Deploy and Manage Azure Compute Resources

  • ARM Templates & Bicep: Infrastructure as Code
  • Virtual Machines: Create & Configure Free
  • VM Disks, Encryption & Migration
  • Availability Sets, Zones & Scale Sets
  • Containers: ACR, ACI & Container Apps
  • App Service Plans & Scaling
  • App Service: Slots, Certificates & Networking

Domain 4: Implement and Manage Virtual Networking

  • Virtual Networks & Subnets
  • VNet Peering & User-Defined Routes
  • NSGs & Application Security Groups
  • Azure Bastion, Service & Private Endpoints
  • Azure DNS & Load Balancers

Domain 5: Monitor and Maintain Azure Resources

  • Azure Monitor: Metrics & Logs
  • Alerts, Insights & Network Watcher
  • Azure Backup & Vaults
  • Azure Site Recovery & Disaster Recovery
Domain 1: Manage Azure Identities and Governance Free ⏱ ~11 min read

Tags, Cost Management & Azure Advisor

Tags organise your resources for billing and management. Cost Management tracks spending. Azure Advisor gives optimisation recommendations. Together, they help you keep Azure costs under control and your environment healthy.

Resource tags

☕ Simple explanation

Tags are sticky labels you put on Azure resources to organise them.

Imagine you have 200 resources across multiple subscriptions. Some belong to Marketing, some to Finance, some are production, some are test. Tags let you label each resource: Department: Marketing, Environment: Production, CostCenter: CC1234.

Then you can filter, search, and generate cost reports by tag. “How much did the Marketing department spend last month?” → filter by tag. “Which resources are test and can be shut down?” → filter by Environment tag.

Resource tags are name-value pairs that you apply to Azure resources, resource groups, and subscriptions. They provide metadata for logical organisation beyond the resource hierarchy. Tags are critical for cost allocation, automation, and operational management.

Each resource can have up to 50 tag name-value pairs. Tag names are case-insensitive for operations but case-preserving. Tag values are case-sensitive. Tags are NOT inherited — a tag on a resource group does NOT automatically apply to resources inside it (but Azure Policy can enforce tag inheritance).

Tag rules and limits

RuleDetail
Max tags per resource50 name-value pairs
Tag name max length512 characters
Tag value max length256 characters
InheritanceTags are NOT inherited (use Policy to enforce)
Tag namesCase-insensitive for operations, case-preserving
Tag valuesCase-sensitive
Apply toResources, resource groups, subscriptions
💡 Exam tip: Tags are NOT inherited

This is a classic exam trap. Putting a tag on a resource group does NOT automatically tag the resources inside. If you need all resources in a group to have a specific tag, use Azure Policy with a Modify or Append effect to enforce tag inheritance.

For example, the built-in policy “Inherit a tag from the resource group if missing” automatically copies a specified tag from the parent resource group to new resources.

Enforcing tags with Azure Policy

Common tag policies (all built-in — no need to write custom JSON):

PolicyEffectWhat It Does
Require a tag on resourcesDenyBlocks resource creation if a specified tag is missing
Require a tag on resource groupsDenyBlocks RG creation without required tags
Inherit a tag from the resource groupModifyCopies a tag from the RG to new resources
Inherit a tag from the subscriptionModifyCopies a tag from the subscription to new RGs
Append a tag and its valueAppendAdds a default tag if not present
Real-world: TechCorp's tagging strategy

TechCorp Solutions uses these mandatory tags across all resources:

  • Environment — Production, Staging, Development, Test
  • CostCenter — maps to finance department codes
  • Owner — email of the responsible person
  • Project — project name for cost allocation

Alex configured a Deny policy requiring CostCenter and Environment tags on all new resources. A Modify policy inherits the Owner tag from the resource group. Within a month, their cost reports went from “which subscription spent what?” to “which project in which department spent what?”

Azure Cost Management

Azure Cost Management is built into the Azure portal and helps you track, analyse, and optimise cloud spending.

Key features:

  • Cost analysis — visualise costs by resource, resource group, tag, region, service
  • Budgets — set spending limits with alerts at thresholds (e.g., alert at 80%, 100%)
  • Alerts — email notifications when spending approaches or exceeds budgets
  • Recommendations — optimisation suggestions (powered by Azure Advisor)
  • Exports — schedule cost data exports to storage accounts for external analysis

Budgets and alerts

Budgets are the primary tool for cost governance:

  1. Create a budget — set a monthly or quarterly amount (e.g., $5,000/month)
  2. Set alert thresholds — trigger at percentage or actual amount (e.g., 50%, 80%, 100%)
  3. Configure actions — email notifications, action groups, or even automated shutdown
Budget SettingWhat It Controls
ScopeSubscription, resource group, or management group
AmountThe spending target (e.g., $5,000/month)
Reset periodMonthly, quarterly, annually
Alert thresholdPercentage or actual cost at which to trigger
Alert recipientsEmail addresses or action groups

Important: Budgets are alerts only — they do NOT automatically stop resources from being created or running when the budget is exceeded. For hard limits, you’d need automation via action groups or Azure Functions.

💡 Exam tip: Budgets don't automatically stop spending

A very common misconception: setting a $1,000 budget does NOT cap spending at $1,000. It sends alerts. Resources continue running and incurring costs. To actually stop spending, you’d need to configure an action group that triggers an Azure Function or Logic App to shut down resources.

Azure Advisor

Azure Advisor is a personalised recommendation engine that analyses your resource configuration and usage patterns.

Advisor recommendation categories:

CategoryWhat It RecommendsExample
CostReduce spending”Resize VM from D8 to D4 — it’s using only 20% CPU”
SecurityImprove security posture”Enable MFA for all admin accounts”
ReliabilityImprove availability”Add a second VM to your availability set”
Operational ExcellenceImprove management”Enable diagnostic logs on your SQL database”
PerformanceImprove speed”Move your storage to the same region as your app”
Real-world: CloudFirst Labs saves money with Advisor

CloudFirst Labs was spending $8,000/month on Azure. Alex checked Advisor’s cost recommendations and found:

  • 3 VMs were oversized (40% CPU average) → right-sizing saved $1,200/month
  • 5 unattached managed disks from deleted VMs → deleting them saved $150/month
  • Reserved Instances for their 2 always-on databases → saved $800/month

Total savings: $2,150/month (27% reduction) just from following Advisor recommendations. Now Alex checks Advisor weekly as part of his routine.

Question

Are resource tags inherited from a resource group to the resources inside it?

Click or press Enter to reveal answer

Answer

No. Tags are NOT automatically inherited. You must use Azure Policy (Modify effect) to enforce tag inheritance. The built-in policy 'Inherit a tag from the resource group if missing' can automate this.

Click to flip back

Question

What happens when an Azure budget threshold is exceeded?

Click or press Enter to reveal answer

Answer

An alert notification is sent (email or action group). The budget does NOT automatically stop resources or cap spending. Resources continue running. To enforce hard spending limits, you need automation (e.g., Azure Functions triggered by the alert).

Click to flip back

Question

What are the five Azure Advisor recommendation categories?

Click or press Enter to reveal answer

Answer

Cost (reduce spending), Security (improve security posture), Reliability (improve availability), Operational Excellence (improve management), and Performance (improve speed). Advisor analyses your actual resource usage to generate personalised recommendations.

Click to flip back

Question

How many tags can a single Azure resource have?

Click or press Enter to reveal answer

Answer

A maximum of 50 tag name-value pairs per resource. Tag names are limited to 512 characters and tag values to 256 characters.

Click to flip back

Knowledge check

Knowledge Check

TechCorp Solutions wants all resources in their Production subscription to have a 'CostCenter' tag. New resources without this tag should be blocked. What should Alex configure?

Knowledge Check

CloudFirst Labs set a $5,000 monthly budget with an alert at 80%. They've now spent $4,500. What happened?

Knowledge Check

Azure Advisor recommends that Meridian Financial resize a VM from Standard_D8s_v3 to Standard_D4s_v3. What category does this recommendation fall under?

🎬 Video coming soon

← Previous

Azure Policy & Resource Locks

Next →

Storage Accounts & Redundancy

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.