- Managed Instance is the Azure SQL option for moving existing SQL Server applications with few changes: it keeps instance-level features that Azure SQL Database lacks.
- It is deployed into a dedicated subnet of your virtual network; a public endpoint is optional.
- Pricing is per instance by vCore (minimum 4 vCores), with 32 GB of storage included; General Purpose costs far less than Business Critical, and Azure Hybrid Benefit, reservations and stop/start reduce the bill.
- Migration options include the Managed Instance link, Log Replay Service, Azure Database Migration Service and native RESTORE FROM URL from .bak files in Azure Storage.
What is Azure SQL Managed Instance?
Azure SQL Managed Instance (also called SQL MI, or SQL Server managed instance) is a platform as a service version of a complete SQL Server instance. Microsoft describes it as having near 100% compatibility with the latest Enterprise Edition SQL Server Database Engine, with a native virtual network implementation and a business model aimed at existing SQL Server customers. Microsoft handles patching, version updates, automated backups and high availability, while you get the instance-scoped features that a single Azure SQL database does not offer.
It sits between the other two Azure SQL options. Azure SQL Database is scoped to individual databases and suits new cloud applications; SQL Server on Azure VMs gives full control but leaves operating system and SQL Server maintenance to you. Managed Instance targets lift-and-shift migrations: Microsoft's migration guide calls it the optimal choice when applications regularly use instance-level and cross-database functionality.
When Managed Instance beats Azure SQL Database
The main reason to choose Managed Instance is compatibility. Microsoft's feature comparison shows these differences, among others:
| Feature | Azure SQL Database | SQL Managed Instance |
|---|---|---|
| SQL Server Agent | No (use elastic jobs) | Yes |
| Cross-database queries and transactions | No (elastic queries) | Yes, within the instance |
| Linked servers | No | Yes, to SQL Server and SQL Database |
| CLR | No | Yes, without file system access |
| Database Mail | No | Yes |
| Service Broker | No | Yes |
| Distributed transactions (MS DTC) | No (elastic transactions) | Yes |
| User-initiated backups | No | Copy-only backups to Azure Blob storage |
| Restore a .bak from SQL Server | No | Yes, from Azure Blob storage |
| Restore back to SQL Server | No (BACPAC or BCP) | Yes, to SQL Server 2022 or 2025 depending on update policy |
What still differs from SQL Server
Managed Instance is not identical to an on-premises instance. Microsoft lists key differences: high availability is built in, only automated backups plus copy-only backups are available, full physical paths are not supported (so RESTORE does not support WITH MOVE and BULK INSERT reads from Azure blobs only), connections use TCP only, and SSIS packages run on an Azure-SSIS Integration Runtime in Azure Data Factory. Reporting Services is not provided as a service. For a broader comparison, see Azure SQL Database vs Managed Instance.
Networking: virtual network, endpoints and connections
A managed instance is placed inside your Azure virtual network, in a subnet dedicated to SQL managed instances. Applications connect through one of three endpoint types: the VNet-local endpoint (the default, on port 1433, resolving to an address in the subnet), an optional public endpoint, or private endpoints. Clients can reach the instance from the same or a peered virtual network, or from on-premises over VPN or ExpressRoute.
This design is what makes Managed Instance attractive to security teams and also what makes it heavier to set up than Azure SQL Database: you need to plan the subnet and network rules before deployment. Microsoft advises always connecting with the endpoint's domain name, because the underlying IP address can change. Login failures surface as the usual SQL Server errors, such as error 18456.
Service tiers and hardware
Managed Instance uses the vCore model with two service tiers. General Purpose is for typical performance and I/O latency; an upgraded Next-gen General Purpose option offers better storage performance and lets you add memory and IOPS without adding vCores. Business Critical is for low I/O latency and minimal impact from maintenance. Hardware choices are standard-series (Gen5) with 5.1 GB of RAM per vCore (4 to 80 vCores), premium-series with 7 GB per vCore (up to 128 vCores) and premium-series memory-optimised with 13.6 GB per vCore (up to 64 vCores).
Ways to reduce cost that Microsoft documents include Azure Hybrid Benefit for SQL Server licences with Software Assurance, reservations (Microsoft quotes savings of up to 80%), instance pools for several small instances, stopping the instance when it is not needed (you then pay only for storage) and a licence-free secondary replica designated for disaster recovery only.
Migrating SQL Server to Managed Instance
Microsoft's migration guide lists these recommended methods:
- SQL Server migration in Azure Arc: assess and migrate Arc-enabled SQL Server instances from the Azure portal.
- Azure Database Migration Service: migration with near-zero downtime.
- Managed Instance link: near real-time replication from SQL Server for minimal-downtime cut-over.
- Log Replay Service (LRS): continuously restores log backups uploaded to Azure Blob Storage, with minimal downtime.
- Native backup and restore: back up to Azure Blob Storage and run
RESTORE DATABASE ... FROM URL; simple, but it needs downtime proportional to the database size.
Two points from the guide are easy to miss: databases protected with TDE need their certificate migrated before a native restore, and system databases cannot be restored, so instance-level objects in master and msdb (logins, Agent jobs) must be scripted and recreated. Managed Instance supports databases from SQL Server 2008 onwards; databases migrated from SQL Server 2005 are raised to the 2008 compatibility level.
Azure SQL Managed Instance free offer
Microsoft offers one free General Purpose, standard-series (Gen5) managed instance per subscription for the first 12 months: 4 vCores and 720 vCore hours of compute a month, 64 GB of storage, and up to 500 databases. To conserve hours, the free instance is scheduled by default to run from 9 a.m. to 5 p.m. Monday to Friday in the time zone you set at creation (UTC if none). The schedule can be changed, and the instance can be upgraded to a paid offer from the portal; after upgrading, the free offer cannot be reapplied to that instance. For the separate, non-expiring free offer for single databases, see the Azure SQL Database free offer.
Pricing
Prices from the provider's official pricing pages, checked 8 October 2026, region East US, in USD, excluding tax. List prices only; discounts, commitments and your actual usage change the bill.
Pay-as-you-go list prices for a single managed instance on standard-series (Gen5) hardware with locally redundant storage, from the Azure SQL Managed Instance pricing page. Each instance price includes the first 32 GB of storage. Prices include the SQL Server licence; Azure Hybrid Benefit lowers them if you bring licences with Software Assurance.
| Option | Size | List price |
|---|---|---|
| General Purpose (and Next-gen General Purpose) | 4 vCores, 20.4 GB memory | 736.378 USD per month |
| General Purpose | 8 vCores, 40.8 GB memory | 1,472.755 USD per month |
| Business Critical | 4 vCores, 20.4 GB memory | 1,983.951 USD per month |
| Additional storage, General Purpose | Per GB above the included 32 GB | 0.115 USD per GB per month |
| Additional storage, Business Critical | Per GB above the included 32 GB | 0.25 USD per GB per month |
| Additional IOPS, Next-gen General Purpose | Per IOPS above the free amount | 0.038 USD per IOPS per month |
| Backup storage beyond the free amount | Locally redundant / read-access geo-redundant | 0.10 / 0.20 USD per GB per month |
General Purpose instance, 4 vCores, 256 GB storage
- 4 vCores, standard-series (Gen5), running all month
- 256 GB of storage, of which 32 GB is included
- Backups within the free amount; excludes outbound data transfer, Azure Hybrid Benefit and reservations
| Item | Basis | Estimated per month |
|---|---|---|
| Instance (includes 32 GB) | 736.378 USD per month | 736.38 USD |
| Additional storage | 224 GB x 0.115 USD | 25.76 USD |
| Estimated total | 762.14 USD per month |
Business Critical instance, 4 vCores, 256 GB storage
- Same size and storage as above, Business Critical tier
- Excludes backups beyond the free amount, outbound data transfer and discounts
| Item | Basis | Estimated per month |
|---|---|---|
| Instance (includes 32 GB) | 1,983.951 USD per month | 1,983.95 USD |
| Additional storage | 224 GB x 0.25 USD | 56.00 USD |
| Estimated total | 2,039.95 USD per month |
Worked examples are estimates calculated from the list prices above; they are not quotes or measured bills.
Frequently asked questions
What is the difference between Azure SQL Managed Instance and Azure SQL Database?
Managed Instance is a whole SQL Server instance in your virtual network with near-complete compatibility (SQL Server Agent, cross-database queries, CLR, linked servers, native restore). Azure SQL Database is scoped to databases and drops those instance features in exchange for a lighter setup, serverless compute and lower entry prices.
Does Azure SQL Managed Instance support SQL Server Agent?
Yes. SQL Server Agent is supported, with some documented differences from on-premises SQL Server. Azure SQL Database does not have SQL Server Agent and uses elastic jobs instead.
Can I restore a .bak file to Managed Instance?
Yes. Upload the backup to Azure Blob Storage (or back up directly to URL) and use RESTORE DATABASE ... FROM URL with a SAS credential. System databases cannot be restored, and TDE-protected databases need their certificate migrated first.
Is there a free Azure SQL Managed Instance?
Yes, for 12 months: one General Purpose instance per subscription with 4 vCores, 720 vCore hours a month and 64 GB of storage, scheduled by default to run during working hours.
Can I stop a managed instance to save money?
Yes. Microsoft documents stop and start for managed instances; while the instance is stopped you pay only for storage.
Sources
- Microsoft Learn: What is Azure SQL Managed Instance?
- Microsoft Learn: Features comparison, SQL Database and SQL Managed Instance
- Microsoft Learn: Connectivity architecture for SQL Managed Instance
- Microsoft Learn: Migration guide, SQL Server to SQL Managed Instance
- Microsoft Learn: Try Azure SQL Managed Instance for free
- Azure SQL Managed Instance pricing
Checked 8 October 2026.
How we research cloud database guides: our editorial method. CodeWithSQL earns nothing from the providers mentioned.