Landing zone first
Before deploying a single workload, design the landing zone: management groups, subscriptions, naming conventions, tagging policy and network topology. The Azure landing zone accelerators (CAF) give a defensible starting structure. Separate subscriptions by environment (dev/test/prod) or by workload, and apply policy at management-group level so new subscriptions inherit guardrails automatically.
- Management groups for policy inheritance across subscriptions
- Dedicated subscriptions per environment or per workload
- Mandatory tagging policy (cost centre, environment, owner)
- Hub-spoke network topology with shared firewall and DNS
Azure Virtual Machines deployment
Right-size VMs from day one and use autoscale for variable workloads. Prefer Premium SSD or SSD for production; standard HDD only for dev. Place VMs in availability sets or availability zones for SLA. Use managed disks, never unmanaged storage. Enable Azure Backup on every production VM and Boot Diagnostics for troubleshooting.
az vm create \
--resource-group rg-prod-app \
--name vm-app01 \
--image UbuntuLTS \
--size Standard_D4s_v5 \
--zone 1 \
--os-disk-type Premium_LRS \
--data-disk-sizes-gb 128 \
--tags env=prod owner=infra costcenter=1001Azure App Services
App Service is the managed PaaS for web apps and APIs. Use App Service Plans sized to workload, enable autoscale rules, and deploy to deployment slots for zero-downtime swaps. For containerised apps, use Web App for Containers. Front-end with Application Gateway or Front Door for WAF and global routing.
Azure SQL Database
Azure SQL Database gives managed SQL with built-in HA, backups and tuning. Choose the right purchasing model: DTU for predictable small workloads, vCore for larger or variable ones. Enable Transparent Data Encryption, configure geo-replication or active geo-redundant backups for DR, and use Azure SQL Managed Instance when you need near-full SQL Server feature parity.
| Option | Best for | HA/DR |
|---|---|---|
| Azure SQL Database (single) | New cloud-native apps | Built-in, geo-redundant backups |
| Azure SQL Managed Instance | Lift-and-shift SQL Server | Auto-failover groups |
| SQL Server on VM | Full OS + SQL control | Always On AGs (manual) |
| Elastic pools | Many small SaaS databases | Shared eDTU/vCore |
Azure Storage and networking
Use the right storage account type — GPv2 for general use, BlockBlobStorage for high-transaction block blobs, FileStorage for premium Azure Files. Always configure private endpoints so storage is not reachable over the public internet. For networking, use a hub-spoke topology with Azure Firewall in the hub, User Defined Routes in spokes, and Private DNS zones for name resolution of private endpoints.
- Private endpoints for Storage, SQL, Key Vault — no public access
- Hub-spoke VNets with Azure Firewall and UDRs
- Private DNS zones for private endpoint resolution
- Network Security Groups on every subnet, default-deny
Azure monitoring and cost management
Azure Monitor is the unified telemetry layer — metrics, logs (Log Analytics), alerts and Application Insights for apps. Define diagnostic settings on every resource to send logs to a central Log Analytics workspace. For cost, use Cost Management + Billing, set budgets and alerts, and review the cost analysis views monthly. Tag everything so cost can be attributed to a cost centre.
az consumption budget create \
--budget-name prod-monthly \
--amount 5000 \
--time-grain Monthly \
--start-date 2026-09-01 \
--category Cost \
--resource-group rg-prod-appAzure security and compliance
Microsoft Defender for Cloud gives posture management and workload protection. Enable Defender for Servers, SQL, Storage and Key Vault. Apply the regulatory compliance dashboards (ISO 27001, SOC 2, HIPAA) and remediate findings through Azure Policy. Use Key Vault for all secrets and enable soft-delete and purge protection.
Lessons learned
- Design the landing zone before deploying workloads
- Use private endpoints — never expose storage or SQL to the public internet
- Tag every resource for cost attribution and policy
- Set budgets and alerts early; cost surprises are the top cloud complaint
Written by
Jamshed Alam
Global MSP & IT Infrastructure Consultant with 20 years across Exchange, Microsoft 365, Azure, security and automation. Available for project and contract work worldwide.