Azure Service Decision Map, Command Reference, Certification Path, Glossary, and Next Steps

Azure is too broad for one person or book to memorize, and the catalog changes continuously. Master durable decisions: identity, scope, network, data, compute, integration, observability, security, governance, cost, and recovery. Then use current Microsoft Learn product pages, service limits, pricing, region availability, and API references for implementation details.

How do you choose an Azure service?

Ask in this order:

1. What user/business outcome and SLO are required?
2. What data classification, residency, and recovery apply?
3. What is the workload shape: HTTP, batch, event, stream, database, analytics, AI?
4. What operating responsibility can the team own?
5. Which regions, features, quotas, identities, and private networking are available?
6. What is the measured total cost and exit/migration path?

Azure compute and application map

Azure data and storage map

Integration and API map

AI and machine learning map

Network and hybrid map

Identity, security, management, and developer map

What are the essential Azure command-line references?

Ways to build

Choose the Azure tool you want to use. The underlying resource stays the same.

Azure CLIAzure PowerShell

Azure CLI

bash

WrapCopy

# Context az login az account list --output table az account set --subscription "SUBSCRIPTION_NAME_OR_ID" az account show --output table # Discovery az find "az storage account create" az provider list --output table az resource list --output table az graph query -q "Resources | summarize count() by type | order by count_ desc" # Resource group az group create --name RESOURCE_GROUP --location LOCATION az group show --name RESOURCE_GROUP --output jsonc az group delete --name RESOURCE_GROUP --yes --no-wait # Deployment az deployment group validate --resource-group RESOURCE_GROUP --template-file main.bicep az deployment group what-if --resource-group RESOURCE_GROUP --template-file main.bicep az deployment group create --resource-group RESOURCE_GROUP --template-file main.bicep # Operations az monitor activity-log list --offset 1d --output table az role assignment list --scope RESOURCE_ID --all --output table az resource show --ids RESOURCE_ID --output jsonc

Use --help, JMESPath --query, --output table/jsonc/tsv, and --only-show-errors. Do not put secrets in arguments.

Azure PowerShell

powershell

WrapCopy

Connect-AzAccount Get-AzSubscription Set-AzContext -Subscription "SUBSCRIPTION_NAME_OR_ID" Get-AzContext Get-AzResourceGroup Get-AzResource Get-AzRoleAssignment -Scope "RESOURCE_ID" Get-AzActivityLog -StartTime (Get-Date).AddDays(-1) New-AzResourceGroupDeployment -ResourceGroupName "RESOURCE_GROUP" -TemplateFile "main.bicep"

Use Get-Help COMMAND -Full, -WhatIf where supported, -Confirm, structured object filtering, and noninteractive federated identities in automation.

Portal search terms worth memorizing

Subscriptions, Resource groups, Microsoft Entra ID, Cost Management + Billing, Policy, Defender for Cloud, Microsoft Sentinel, Service Health, Monitor, Network Watcher, Private DNS zones, Key vaults, Storage accounts, App Services, Container Apps, Kubernetes services, Microsoft Foundry, AI Search, Advisor, Backup center.

How do you approach Azure certifications?

Microsoft changes exam names, scopes, and retirement dates. Use the live Microsoft Credentials catalog. A durable learning progression is:

1. Fundamentals: cloud/Azure concepts and security/data/AI fundamentals as relevant.
2. Role skills: administrator, developer, data, security, AI, DevOps, or network.
3. Architecture: solution tradeoffs and operating models.
4. Applied skills: scenario-based labs for current technologies.

Certification is a structured syllabus, not a substitute for labs, incident response, cost review, restore tests, or production ownership.

Plain-English glossary

How do you keep this book current?

Before production work, check:

1. Microsoft Learn page last-updated date.
2. Service availability by region.
3. Current stable API/provider/CLI version.
4. Quotas and limits.
5. Pricing and free-offer terms.
6. Retirement/migration notices.
7. Security baseline and Well-Architected guidance.
8. Release notes for SDK/model/Kubernetes/database versions.

Search current documentation; do not infer from an old screenshot.

Your next 90 days

• Days 1–15: complete Start Here and Foundations; build the beginner capstone.
• Days 16–35: choose App Service/Functions/containers plus one database and messaging path.
• Days 36–55: complete Foundry/RAG/evaluation and the AI capstone.
• Days 56–70: automate with Bicep or Terraform and CI/CD.
• Days 71–80: monitoring, security, backup, cost, and failure drills.
• Days 81–90: perform the Well-Architected review and present one architecture decision record.

Continue beyond the book

• Use the Azure Architecture Center for reference architectures and patterns.
• Use the Cloud Adoption Framework for organizational adoption.
• Use the Azure Well-Architected Framework for workload decisions.
• Read Digital FTEs: Engineering for systematic AI engineering and AI-Native Sales for business adoption.
• Explore AI Native Consulting, Forward Deployed Engineering, or book a strategy call for complex enterprise delivery.