Azure SQL vs Google Cloud SQL for SQL Server (2026)

Quick verdict

Short answer

For SQL Server, choose Azure SQL when you want the widest choice: Azure SQL Database for new cloud applications, Managed Instance for migrations that need SQL Server Agent, CLR, Service Broker, Database Mail or cross-database queries, and SQL Server on Azure VMs for full control. Choose Cloud SQL for SQL Server when your applications already run on Google Cloud and your databases fit its managed instance model, which includes SQL Server Agent, linked servers and .bak import and export but not CLR, FILESTREAM, Database Mail or sysadmin. If you also run MySQL or PostgreSQL, Cloud SQL covers all three engines in one service, whereas Azure uses separate services for them.

How we know: This comparison is research-based: products, supported features, versions, high availability, backups, maintenance and pricing models were checked against Microsoft Learn and Google's Cloud SQL documentation in October 2026. Google's Cloud SQL pricing page could not be read in full, so no Cloud SQL list prices are quoted. We have not run performance or cost tests.

Azure SQL is a family of three products built on the SQL Server Database Engine. Azure SQL Database is a database-scoped PaaS service (single databases and elastic pools) on the latest stable engine. Azure SQL Managed Instance is PaaS with a whole instance; Microsoft describes it as having "near 100% compatibility with the latest Enterprise Edition SQL Server Database Engine" and positions it for lift-and-shift migrations. SQL Server on Azure VMs is IaaS: full SQL Server and operating system control, with optional automated backup and patching through the free SQL IaaS Agent extension. Microsoft runs MySQL and PostgreSQL as separate services, Azure Database for MySQL and Azure Database for PostgreSQL (flexible server).

Cloud SQL is Google Cloud's managed relational database service for MySQL, PostgreSQL and SQL Server. Each instance belongs to the Enterprise or Enterprise Plus edition, and both editions support all three engines. Cloud SQL for SQL Server supports SQL Server 2017, 2019, 2022 and 2025, in Standard, Enterprise and Express editions, plus Web edition on 2017 to 2022. You get a managed instance with no operating system access and no sysadmin role.

Which Azure product to compare. Cloud SQL for SQL Server is an instance, so its closest Azure match is Azure SQL Managed Instance. Azure SQL Database is the simpler, more restricted option, and SQL Server on Azure VMs is the self-managed option (on Google Cloud the equivalent is SQL Server on Compute Engine). The table below compares the Azure SQL family as a whole and names the product where it matters.

Side by side

Aspect	Azure SQL	Cloud SQL
Products	Azure SQL Database (PaaS, database scoped), SQL Managed Instance (PaaS, instance), SQL Server on Azure VMs (IaaS)	One service, Cloud SQL, in Enterprise and Enterprise Plus editions
Engines	SQL Server only; MySQL and PostgreSQL are separate Azure services	MySQL, PostgreSQL and SQL Server in the same service
SQL Server version	Database and Managed Instance: latest stable engine (Managed Instance can follow a SQL Server 2022 or 2025 update policy); VMs: 2016 to 2025 images	You choose 2017, 2019, 2022 or 2025
SQL Server Agent	Managed Instance and VMs: yes. SQL Database: no (Elastic jobs)	Yes
Cross-database queries and linked servers	Managed Instance and VMs: yes. SQL Database: no	Linked servers supported
CLR, Service Broker, Database Mail	Managed Instance and VMs: yes. SQL Database: no	CLR assemblies and Database Mail not available
Native .bak backups	Managed Instance: restore from Azure Blob storage, copy-only backups; VMs: full control. SQL Database: no	Import .bak and .sql files; export .bak files
sysadmin and OS access	VMs only	Neither; sysadmin and procedures that need it are unavailable
Windows authentication	VMs: yes. Managed Instance: Windows authentication for Microsoft Entra principals (preview). SQL Database: no	Through Managed Service for Microsoft Active Directory or a customer-managed AD
High availability	Built into Database and Managed Instance; zone redundancy optional. VMs: you configure availability groups or FCIs	Optional regional (HA) instance: standby in a second zone, about 60 seconds to fail over, standby not readable
Licence options	Licence included or Azure Hybrid Benefit (Database vCore, Managed Instance, VMs)	SQL Server licence charged with the instance; committed use discounts do not cover it
Main trade-off	Three products to choose between, and SQL Server only	Fewer SQL Server features than Managed Instance, and no self-managed tier inside the service

Key differences

SQL Server feature coverage

This is the biggest difference for SQL Server workloads. Azure SQL Managed Instance supports, among other things, SQL Server Agent, Database Mail (external SMTP), Service Broker, transactional replication, cross-database queries and transactions, linked servers, CLR modules and native restore from Azure Blob storage, according to Microsoft Learn. Backups taken on Managed Instance can be restored to SQL Server 2022 or SQL Server 2025, depending on the instance's update policy. SQL Server on Azure VMs is the full product with no service restrictions.

Cloud SQL for SQL Server supports SQL Server Agent, linked servers, .bak and .sql import, .bak export and BACPAC through SqlPackage, read replicas, HA and up to 64 TB of storage. Google lists as unavailable SQL Server Analysis Services, CLR assemblies, FILESTREAM, Database Mail and the sysadmin role. SSIS and SSRS are supported only on a separate host that connects to Cloud SQL; you cannot host or run packages on the Cloud SQL instance itself.

Azure SQL Database supports the fewest instance features of the three Azure options: no SQL Server Agent, no three-part-name cross-database queries, no linked servers, CLR, Service Broker or Database Mail, and no BACKUP or RESTORE statements. See Azure SQL Database vs Managed Instance for that trade-off in detail.

-- T-SQL on Azure SQL Managed Instance: native restore from Azure Blob storage
-- (needs a credential with a SAS token for the container)
RESTORE DATABASE SalesDb
FROM URL = 'https://myaccount.blob.core.windows.net/backups/SalesDb.bak';

# Cloud SQL for SQL Server: import a .bak from Cloud Storage with gcloud
gcloud sql import bak my-instance gs://my-bucket/SalesDb.bak --database=SalesDb

Engine coverage: one service or several

Cloud SQL puts MySQL (5.6, 5.7, 8.0, 8.4 and 9.7), PostgreSQL (9.6 to 18) and SQL Server under one service, one edition model and one set of documentation for backups, HA and maintenance. If your organisation runs a mix of engines on Google Cloud, that consistency is a real advantage.

On Azure, the Azure SQL family is SQL Server only. MySQL runs on Azure Database for MySQL flexible server (MySQL 5.7, 8.0 and 8.4, according to Microsoft Learn) and PostgreSQL on Azure Database for PostgreSQL flexible server, each with its own Burstable, General Purpose and Memory Optimized compute tiers, backups (1 to 35 days, 7 by default) and HA options. They work well, but they are separate products with different feature sets from Azure SQL.

High availability and backups

In Azure SQL Database and Managed Instance, high availability is built in: General Purpose separates compute from storage, Business Critical runs replicas using technology similar to Always On availability groups (with a free read-only replica in Azure SQL Database), and zone redundancy is an option. Azure SQL Database offers point-in-time restore for 1 to 35 days (7 by default) and long-term retention of up to 10 years; Managed Instance has configurable retention and allows copy-only backups. On Azure VMs you build HA with availability groups or failover cluster instances, as on premises.

Cloud SQL HA is an option per instance. A regional instance replicates every write synchronously to disks in two zones; failover takes about sixty seconds according to Google, the standby cannot serve reads, and Google states an HA instance costs twice as much as a standalone one. Automated backups are incremental and can be kept for up to 10 years with enhanced backups, but point-in-time recovery is limited to 7 days in Enterprise and 35 days in Enterprise Plus. For SQL Server, read replicas require Enterprise edition (up to 8 per primary), and cascading replicas require Enterprise Plus.

Versions, updates and maintenance

Azure SQL Database and Managed Instance do not have version upgrades in the usual sense: Microsoft keeps them on the latest stable engine. Managed Instance lets you choose an update policy (Always-up-to-date, SQL Server 2022 or SQL Server 2025), which also decides which SQL Server version its backups can be restored to. Maintenance windows let you move impactful updates to a weekday or weekend overnight slot. On Azure VMs, Marketplace images deploy at RTM and you patch them yourself or through Azure Update Manager; the IaaS Agent extension can deliver extended security updates for up to three years after end of support.

Cloud SQL for SQL Server keeps you on the major version you choose and applies minor updates during maintenance. You set a one-hour maintenance window, can deny maintenance for up to 90 days, and get at least a week's notice. Planned maintenance downtime is under 60 seconds on Enterprise and under 1 second on Enterprise Plus, per Google. Google has announced that new SQL Server 2017 instances cannot be created from 12 April 2027.

Licensing

Azure is built around existing SQL Server licences. Azure Hybrid Benefit lets customers with Software Assurance apply licences to Azure SQL Database (vCore, except new Hyperscale databases), Managed Instance and SQL Server VMs, and on VMs you can switch between pay-as-you-go and Azure Hybrid Benefit without downtime. Managed Instance also offers a licence-free disaster recovery replica and the ability to stop and start the instance so that only storage is billed.

Cloud SQL for SQL Server charges a SQL Server licence component with the instance, and Google's committed use discounts explicitly exclude licensing. The Cloud SQL documentation we checked does not describe a bring-your-own-licence option; Google documents bring-your-own-licence for SQL Server on Compute Engine VMs instead.

Pricing and licensing

Azure SQL. Azure SQL Database is billed per database or pool, in vCore (provisioned per hour, or serverless per second) or DTU; Microsoft Learn states prices start from USD 5 per month for the Basic DTU tier. Managed Instance is billed for vCores, storage and licence (unless Azure Hybrid Benefit applies), and Microsoft says reservations can save up to 80%. SQL Server on Azure VMs is billed for the VM, disks and, with pay-as-you-go images, the SQL Server licence. Free offers per Microsoft Learn in October 2026: Azure SQL Database, up to 10 General Purpose serverless databases per subscription, each with 100,000 vCore seconds, 32 GB of data and 32 GB of backup storage per month; Managed Instance, 720 vCore hours on a General Purpose instance with up to 100 databases for the first 12 months.

Cloud SQL. Cloud SQL bills instance CPU and memory, storage, backups, IP addresses, network egress and, for SQL Server, the licence. Google's committed use discounts are 25% for 1 year and 52% for 3 years on CPU and memory, but not on licensing, storage, backups, egress or shared-core machines. HA doubles the instance cost, and read replicas are charged as standard instances. We could not read Google's pricing page reliably, so no list prices are quoted; use the Google Cloud pricing calculator.

For SQL Server the licence is often the largest line in both clouds, so whether you can use Azure Hybrid Benefit usually matters more than the compute rate. Price the same vCPU count, edition, HA choice and region in both calculators.

Pricing checked on the vendors' official pages on 7 October 2026. Prices change; confirm before buying.

Where each one leads

Azure SQL strengths

Three ways to run SQL Server: database-scoped PaaS, managed instance and full IaaS
Managed Instance supports nearly all SQL Server features, including Agent, CLR, Service Broker, Database Mail and cross-database queries
Azure Hybrid Benefit across Database, Managed Instance and VMs, plus a licence-free DR replica on Managed Instance
Built-in HA on the PaaS options, and serverless and Hyperscale in Azure SQL Database
Free offers for both Azure SQL Database and Managed Instance

Cloud SQL strengths

MySQL, PostgreSQL and SQL Server under one service and one edition model
You choose the SQL Server major version (2017 to 2025) and edition
SQL Server Agent, linked servers and .bak import and export on a managed instance
Enterprise Plus offers a 99.99% SLA including maintenance and sub-second planned maintenance downtime
Deny maintenance periods of up to 90 days

Limitations

Azure SQL limitations

Choosing between three products adds a decision step, and features differ sharply between them
Azure SQL Database lacks Agent, cross-database queries, CLR and native backups
MySQL and PostgreSQL are separate services with different tooling and options
SQL Server on Azure VMs leaves patching, HA and backups to you

Cloud SQL limitations

No CLR, FILESTREAM, Database Mail, SSAS or sysadmin on SQL Server instances
SSIS and SSRS must run on a separate host
HA doubles the instance cost and the standby cannot serve reads
No bring-your-own-licence option documented for Cloud SQL; licences are charged with the instance

When to choose each

Choose Azure SQL if

Your SQL Server applications use Agent jobs, CLR, Service Broker, Database Mail or cross-database queries
You own SQL Server licences with Software Assurance and want Azure Hybrid Benefit
You want built-in HA, serverless compute or Hyperscale for new SQL Server applications
You need a self-managed fallback in the same cloud (SQL Server on Azure VMs)

Choose Cloud SQL if

Your applications run on Google Cloud
You run SQL Server alongside MySQL or PostgreSQL and want one managed service for all of them
Your SQL Server databases need Agent and linked servers but not CLR, FILESTREAM or Database Mail
You want to choose and hold a specific SQL Server major version

When neither is right

Your applications run on AWS: see AWS RDS vs Azure SQL Database and AWS RDS vs Google Cloud SQL.
You need SQL Server with sysadmin, OS access or SSAS on Google Cloud: run SQL Server yourself on Compute Engine VMs. On premises, see Azure SQL Database vs SQL Server.
Your workload is PostgreSQL rather than SQL Server: on Google Cloud compare Google Cloud SQL vs AlloyDB, and for engine choice see SQL Server vs PostgreSQL.

Final recommendation

Bottom line

For SQL Server, Azure SQL is the more complete platform: Managed Instance covers almost every SQL Server feature as PaaS, Azure SQL Database covers new cloud applications with serverless and Hyperscale, and Azure VMs cover the rest, all with Azure Hybrid Benefit. Cloud SQL is a solid managed SQL Server instance with Agent, linked servers and .bak support, and it is the better fit when you are on Google Cloud or want MySQL, PostgreSQL and SQL Server in one service. Before choosing Cloud SQL for an existing SQL Server estate, check its databases for CLR, FILESTREAM, Database Mail and sysadmin-dependent code.

Frequently asked questions

Does Google Cloud SQL support SQL Server Agent?

Yes. Google lists SQL Server Agent as enabled on Cloud SQL for SQL Server, along with linked servers and .bak import and export. Azure SQL Managed Instance also supports SQL Server Agent; Azure SQL Database does not.

Which SQL Server versions does Cloud SQL support?

SQL Server 2017, 2019, 2022 and 2025. SQL Server 2025 is offered in Standard, Enterprise and Express editions, and 2017 to 2022 also in Web edition. Google says new SQL Server 2017 instances cannot be created from 12 April 2027.

What is the Azure equivalent of Cloud SQL for SQL Server?

Azure SQL Managed Instance is the closest match, because both give you a managed SQL Server instance. Managed Instance supports more SQL Server features, such as CLR, Service Broker and Database Mail. Azure SQL Database is database scoped and more restricted.

Can I bring my own SQL Server licence?

On Azure, yes: Azure Hybrid Benefit applies to Azure SQL Database (vCore, not new Hyperscale databases), Managed Instance and SQL Server VMs. For Cloud SQL, the documentation we checked describes licence charges with the instance and no bring-your-own-licence option; Google documents bring-your-own-licence for SQL Server on Compute Engine.

Does Azure SQL support MySQL or PostgreSQL?

Not within the Azure SQL family, which is SQL Server only. Microsoft offers Azure Database for MySQL and Azure Database for PostgreSQL (flexible server) as separate services. Cloud SQL runs MySQL, PostgreSQL and SQL Server in one service.

Sources

Checked October 2026.

How we research comparisons: our editorial method.