Introduction to Azure
Microsoft Azure is a comprehensive cloud computing platform offering 200+ services for compute, storage, networking, databases, AI, and DevOps. Organizations use Azure to build, deploy, and manage applications across on-premises, hybrid, and multi-cloud environments — especially when already invested in the Microsoft ecosystem.
What Is Cloud Computing on Azure?
Azure delivers IT resources over the internet on a pay-as-you-go basis. Instead of buying physical servers, you rent capacity from Microsoft’s global data centers and scale on demand.
| Traditional | Azure Cloud |
|---|---|
| CapEx — buy hardware upfront | OpEx — pay monthly for usage |
| Weeks to provision servers | Minutes to deploy VMs or PaaS services |
| Over-provision for peak load | Auto Scale matches demand |
| Single data center | Global regions with paired DR regions |
Azure Global Infrastructure
| Concept | Description |
|---|---|
| Region | Geographic area (e.g., eastus, westeurope). Choose based on latency, compliance, and service availability. |
| Availability Zone | Physically separate data centers within a region. Deploy across zones for high availability. |
| Region Pair | Each region paired with another for disaster recovery (e.g., East US ↔ West US). |
| Edge Locations | Azure CDN and Front Door cache content closer to users. |
# List available regions
az account list-locations --query "[].{Name:name, Display:displayName}" --output table
# Check your default location
az configure --list-defaults
Core Service Categories
| Category | Key Services | Typical Use |
|---|---|---|
| Compute | Virtual Machines, App Service, AKS, Functions, Container Apps | Hosting applications |
| Storage | Blob, File, Queue, Table, Disk | Data persistence and messaging |
| Databases | Azure SQL, Cosmos DB, PostgreSQL, MySQL | Managed relational and NoSQL |
| Networking | Virtual Network, Load Balancer, Application Gateway, Front Door | Connectivity and traffic |
| Identity | Entra ID, RBAC, Managed Identities, Conditional Access | Authentication and authorization |
| DevOps | Azure DevOps, GitHub Actions, ARM/Bicep | CI/CD and infrastructure as code |
| AI/ML | Azure OpenAI, Cognitive Services, Machine Learning | Intelligent applications |
Azure’s Hybrid Advantage
Azure excels at hybrid cloud — connecting on-premises infrastructure with cloud resources:
| Service | Purpose |
|---|---|
| Azure Arc | Manage on-premises, multi-cloud, and edge resources from Azure Portal |
| Azure Stack | Run Azure services in your data center |
| ExpressRoute | Private dedicated connection to Azure (not over internet) |
| Site-to-Site VPN | Encrypted tunnel from on-premises to Azure VNet |
| Entra ID Connect | Sync on-premises Active Directory to cloud identity |
Organizations running Windows Server, SQL Server, and Active Directory find Azure integration seamless.
The Shared Responsibility Model
| Microsoft Responsibility | Your Responsibility |
|---|---|
| Physical data center security | Network security groups and firewalls |
| Hypervisor and host infrastructure | OS patching (IaaS) or app security (PaaS) |
| Managed service patching (PaaS) | Application code and data |
| Global network infrastructure | Identity, access control, encryption |
Real-World Scenario: Enterprise Web Application
A typical Azure three-tier architecture:
- Azure Front Door — global load balancing and WAF
- App Service — web frontend (auto-scaling PaaS)
- Azure Functions — background processing and APIs
- Azure SQL Database — managed relational database
- Blob Storage — static assets and file uploads
- Azure Monitor — metrics, logs, and alerts
This pattern scales from a Free tier App Service to enterprise-grade multi-region deployment.
Getting Started Checklist
- Create a free account at azure.microsoft.com/free — $200 credit for 30 days
- Install Azure CLI:
brew install azure-cli - Sign in:
az login - Create a resource group:
az group create --name rg-learning --location eastus - Set up billing alerts in Cost Management + Billing
- Enable Microsoft Defender for Cloud (free tier) for security recommendations
az login
az account list --output table
az account set --subscription "Your Subscription Name"
az group create --name rg-learning-dev --location eastus --tags environment=dev
Azure vs AWS vs GCP
| Feature | Azure | AWS | GCP |
|---|---|---|---|
| Enterprise identity | Entra ID (best-in-class) | IAM | Cloud IAM |
| Hybrid cloud | Strongest (Arc, Stack) | Outposts | Anthos |
| Windows/.NET | Native support | Good | Good |
| Kubernetes | AKS | EKS | GKE (origin) |
| Data/AI | Azure OpenAI, Synapse | SageMaker | BigQuery, Vertex AI |
| Licensing | Hybrid Benefit (save on existing licenses) | — | — |
Common Mistakes for Beginners
- Using personal Microsoft account for production — use work accounts with proper governance
- No resource tagging — impossible to track costs by team/project without tags
- Single subscription for everything — separate dev/staging/prod subscriptions
- Ignoring Azure Policy — enforce standards from day one
- Leaving default NSG rules — restrict inbound traffic explicitly
- No spending limits or budgets — configure Cost Management alerts immediately
Troubleshooting Tips
| Problem | Likely Cause | Fix |
|---|---|---|
AuthorizationFailed |
Insufficient RBAC role | Check role assignments with az role assignment list |
| Quota exceeded | Default limits per region | Request quota increase in Azure Portal |
| Resource not found | Wrong subscription or resource group | Verify with az account show and az group list |
| Unexpected charges | Forgotten resources running | Use Cost Management → Cost analysis |
Best Practices from Day One
- Use Management Groups and multiple Subscriptions for environment isolation
- Apply tags (
Environment,Project,Owner) to every resource - Enable Microsoft Defender for Cloud for security posture management
- Use Managed Identities instead of storing credentials in code
- Prefer PaaS (App Service, Azure SQL) over IaaS unless you need OS-level control
- Document architecture with Azure Architecture Center reference patterns
Next: Azure Account Setup.