Three ways to run SQL Server in Azure
- Azure SQL Database is a single managed database. Microsoft takes care of the engine, patches, backups and high availability. You manage the database, not the server.
- Azure SQL Managed Instance is a managed instance with several databases, close to a full SQL Server: SQL Server Agent, cross-database queries and Database Mail are available.
- SQL Server on an Azure VM is your own SQL Server on a virtual machine. Everything works as on premises, but you keep managing the server yourself.
Azure SQL Database is versionless: it always runs the newest SQL Server engine, so you do not choose a version and do not have to plan upgrades. Managed Instance has an update policy instead: its engine stays aligned with SQL Server 2022 or SQL Server 2025, or follows Always-up-to-date; Microsoft applies the updates either way. Compatibility levels still let your database keep its old behaviour where needed.
What does not work in Azure SQL Database
Azure SQL Database is the most managed option, and therefore the most restricted. Server-level features are not available. Each has an alternative in Azure, but it means a change to the application or the way it is run:
- SQL Server Agent jobs: use Elastic Jobs, Azure Automation or Logic Apps
- Queries across databases and the
USEstatement: merge the databases, or use elastic query - Linked servers, CLR assemblies, Service Broker and FILESTREAM
xp_cmdshell, OLE Automation and access to files on the server- Windows authentication: use Microsoft Entra ID authentication
- Database Mail: use Logic Apps or Azure Communication Services
When Managed Instance is the better fit
Managed Instance is designed for lift-and-shift of existing applications. SQL Server Agent, cross-database queries, Database Mail, distributed transactions and server triggers work. CLR, Service Broker and linked servers are available with restrictions. FILESTREAM and xp_cmdshell are not available.
If your application consists of several databases that query each other, or relies on Agent jobs, Managed Instance usually saves a lot of rework compared to Azure SQL Database.
Size limits
Azure SQL Database in the General Purpose and Business Critical tiers goes up to 4 TB per database; the Hyperscale tier goes up to 128 TB. Managed Instance goes up to 32 TB in the next-generation General Purpose tier and 16 TB in Business Critical. Check these limits against the current size and growth of your database.
Migration methods
- To Azure SQL Database: Azure Database Migration Service, a .bacpac export and import, or transactional replication to keep downtime short. A native .bak backup cannot be restored.
- To Managed Instance: native backup to a URL and restore, the Log Replay Service, the Managed Instance link (based on availability group technology, for near-zero downtime) or Azure Database Migration Service.
Remember everything outside the database: logins, Agent jobs, linked servers, SSIS packages and Reporting Services reports need their own plan. SSIS can move to Azure Data Factory with the Azure-SSIS integration runtime; reports can move to Power BI paginated reports.
How the free scan helps
The scan collects the structure of your SQL Server database with a read-only script and compares it with Azure SQL Database, Hyperscale and Managed Instance side by side. You see per target which objects use features that are not available, with a score, so the choice is based on your own database instead of a general checklist. The analysis runs in your browser; nothing is uploaded.
Questions
Which SQL Server version does Azure SQL run?
Azure SQL Database has no version you choose: it always runs the newest SQL Server engine. For Managed Instance you choose an update policy: SQL Server 2022, SQL Server 2025 or Always-up-to-date. In both cases your database can keep an older compatibility level.
Can I restore a .bak file in Azure SQL Database?
No. Azure SQL Database does not accept native backups. Use a .bacpac, Azure Database Migration Service or replication. Managed Instance can restore native backups from Azure Blob Storage.
My application uses several databases. Which option?
Queries across databases do not work in Azure SQL Database. Managed Instance supports them, so it is usually the more natural target, unless you merge the databases into one.
Is a virtual machine not simpler?
SQL Server on an Azure VM has the fewest compatibility issues, but you keep the patching, backups and high availability yourself, and you do pick a version, which needs upgrading in time.
Compare Azure SQL Database, Hyperscale and Managed Instance for your own database: run the read-only script, paste the result and see the issues per target. Free, and nothing is uploaded.
Start the free scan