When growing Australian businesses ask whether they should be on Azure or AWS, the honest answer is usually: it depends, and far less than you might think. Both clouds run almost any workload you can imagine, both have a Sydney region, and both will let you over-spend if you are not careful.
This article focuses on the boring details that actually decide the question.
Start with where your workforce lives
Most Australian SMEs already run Microsoft 365 for email and collaboration. That alone often nudges the answer towards Azure for these reasons.
- Identity and SSO are simpler. Azure naturally integrates with Microsoft Entra ID. AWS works fine with Entra ID too via SAML and SCIM, but it is one more thing to configure and document.
- Endpoint, identity and SaaS telemetry can flow into Microsoft Sentinel without extra plumbing.
- Conditional Access policies you already use for SaaS apply naturally to Azure resources via Entra.
If you are a Linux-shop or your engineers prefer the AWS ecosystem, this point reverses. AWS has the deeper services catalogue and a more mature serverless stack today.
Region, residency and latency
Both clouds run a Sydney region. For most Australian SMEs that is enough. Things to check.
- Latency. Both regions land at sub-30 ms from Sydney CBD on a clean connection. From Perth, expect 50 to 60 ms.
- Data residency. Default to keeping production data in the Sydney region and prevent accidental egress to other regions via Service Control Policies (AWS) or Azure Policy.
- Disaster recovery. AWS Sydney has multiple availability zones and Asia Pacific peers. Azure offers Australia East as primary with Australia Southeast as a secondary; not all services have parity, so check before assuming.
Cost will surprise you (in both directions)
Headline list prices look comparable. Real spend is dominated by:
- Egress out of cloud: usually the biggest preventable line item. Cloudflare in front of either cloud often pays for itself.
- VM family choices. Newer AMD or ARM SKUs are typically 10 to 25 percent cheaper than older Intel SKUs at the same performance.
- Reserved capacity or Savings Plans. A one-year commitment pays back surprisingly quickly if your steady-state is predictable.
The right answer is to measure. We tag every resource by environment and workload from day one, so cost reports are grouped by something meaningful instead of resource type.
Operational fit
Pick the cloud whose default tooling matches the way your team already works.
- If your team writes mostly C# and uses Azure DevOps or GitHub Actions, Azure App Service, Functions and Container Apps will feel native.
- If your team writes mostly TypeScript or Python and enjoys writing infrastructure as code, AWS with Terraform or CDK is hard to beat.
- If you do not have a team and want managed everything, Azure plus a Microsoft partner usually costs less in operational overhead.
Security baselines
Both clouds need explicit hardening; neither is secure by default.
- Both require a thoughtful identity model. Use IAM Identity Center on AWS and Privileged Identity Management on Azure. Avoid long-lived access keys and standing admin.
- Both should sit behind a multi-account or multi-subscription topology with guardrails: AWS Organisations and Service Control Policies; Azure Management Groups and Policy.
- Both need centralised logging. Send CloudTrail and Defender for Cloud to one place, and review weekly.
So which is it?
For most Australian SMEs we work with, the practical pattern looks like this.
- Microsoft-centric workforce, Windows servers, line-of-business apps: lean Azure.
- Engineering-heavy teams shipping web or data products, especially in TypeScript, Python or Go: lean AWS.
- Mixed estate: it is fine. We help businesses run both, with shared identity through Entra and a single observability story through Sentinel or a third-party SIEM.
The wrong answer is to flip a coin. The right answer is a one-page architectural decision record that names the workload, its dependencies and the team running it, then picks the platform that minimises friction for the next 18 months.
If you would like help running that exercise, book a consultation.