Google Cloud vs Azure

Google Cloud and Azure both organise work into containers that sit under a billing arrangement, but they draw the lines in different places. The practical question is how much structure you want to carry before the first server is running.

Configurations and prices in the catalogue

Both tables are generated from the live product records, so they match the product pages exactly.

Projects against tenants and subscriptions

Google Cloud uses the project as its working unit. A project holds resources, carries its own quota allocation, and attaches to a billing account. Creating another one is cheap, and deleting one removes everything inside it.

Azure separates the identity directory from the billing container. A tenant holds the identities, a subscription holds the resources and the spend, and resource groups organise what is inside a subscription.

Google Cloud therefore gives you one thing to record when handing an environment over. Azure gives you two, which is more to track but also a cleaner split when identity is managed by someone other than the person paying.

Where each one tends to fit

Google Cloud suits

• Teams that want fast, disposable isolation per client or per experiment.
• Data and analytics work that leans on managed services.
• Anyone who prefers quota and billing visibility at the project level.

Azure suits

• Organisations whose staff already sign in with Microsoft identity.
• Windows workloads and existing licensing arrangements.
• Setups where a spending limit on a subscription is a useful guard rail.

What to check before you buy

• Which configuration above carries the balance or capacity your project needs.
• Whether the regions you need are enabled and whether quotas cover the instance sizes you plan to run.
• Who else holds directory or organisation level access to the environment.
• Your plan for rotating credentials and recording ownership on day one.

More written guidance is in the Planning and Comparison topic of the Cloud Library.

Questions