Microsoft & Azure · Managed service
Azure AI Search
Search
Microsoft Azure; search and retrieval service
When to consider it
Consider it for full-text, vector, and hybrid retrieval over content indexed from an authoritative source. It is useful when search relevance and Azure service integration are central to the application.
What to check
Plan document ingestion, index updates, capacity, and reindexing. Search results can lag source transactions; the search index should not silently become the system of record.
Official documentation ↗Microsoft & Azure · Managed service
Azure Cosmos DB
Document / Key-value
Microsoft Azure; distributed NoSQL service
When to consider it
A candidate for partitioned document or key-oriented application data when Azure integration and regional distribution matter. Choose the API, partition key, and consistency model around specific access patterns.
What to check
Request units and hot partitions affect cost and performance. Accounts with multiple write regions cannot use strong consistency; transactions and query behavior have API-specific boundaries.
Official documentation ↗Microsoft & Azure · Managed service
Azure Database for MySQL
Relational
Microsoft Azure; managed MySQL
When to consider it
A managed hosting option for MySQL applications in Azure. Consider it when retaining the MySQL engine and existing client libraries matters more than adopting SQL Server-specific features.
What to check
Check supported MySQL versions, migration restrictions, networking, high availability, and parameter access. Managed infrastructure does not remove query tuning or the need to rehearse recovery.
Official documentation ↗Microsoft & Azure · Managed service
Azure Database for PostgreSQL
Relational
Microsoft Azure; managed PostgreSQL
When to consider it
A practical option for PostgreSQL applications hosted in Azure that need managed patching, backup facilities, and integration with Azure networking and identity. Compare it with SQL Server-based services when engine compatibility is still undecided.
What to check
Check supported PostgreSQL versions, extensions, connection limits, and high-availability configuration. Managed hosting still leaves schema design, query tuning, and recovery validation with your team.
Official documentation ↗Microsoft & Azure · Managed service
Azure Managed Redis
Cache / Key-value
Microsoft Azure; managed Redis service
When to consider it
An Azure option for frequently accessed data, session storage, and cache-aside designs. It can reduce infrastructure work when an application already uses Redis-compatible client access.
What to check
Validate supported commands, tier capabilities, clustering, memory policies, and persistence. Keep critical records in an authoritative store unless the selected durability model has been explicitly justified.
Official documentation ↗Microsoft & Azure · Managed service
Azure SQL Database
Relational
Microsoft Azure; managed database service using SQL Server technology
When to consider it
A candidate for new or modernized applications that need managed relational storage in Azure. It offers a database-focused operating model while Microsoft manages the underlying platform.
What to check
It is not a full SQL Server instance under your control. Validate server-level features, cross-database dependencies, service-tier limits, and migration compatibility.
Official documentation ↗Microsoft & Azure · Managed service
Azure SQL Managed Instance
Relational
Microsoft Azure; managed SQL Server-compatible instance
When to consider it
Consider Managed Instance when an existing SQL Server estate needs broader instance-level compatibility than Azure SQL Database provides. It can reduce refactoring for applications with established database dependencies.
What to check
Near-full compatibility still requires an assessment. Review unsupported features, networking, provisioning, maintenance behavior, and the cost of the selected service configuration.
Official documentation ↗Microsoft & Azure · Analytics platform
Microsoft Fabric Warehouse
Analytics
Microsoft Fabric; analytical warehouse integrated with OneLake
When to consider it
A candidate for teams building a Microsoft Fabric analytics environment with SQL warehousing and shared data workflows. Assess it alongside other warehouses using representative reporting and ingestion workloads.
What to check
Fabric Warehouse is distinct from SQL database in Fabric and from SQL Server OLTP. Evaluate T-SQL support, capacity sharing, ingestion design, and governance requirements.
Official documentation ↗Microsoft & Azure · Database engine
Microsoft SQL Server
Relational
Self-managed servers or cloud VMs; managed services also available
When to consider it
A core choice for existing T-SQL applications, Microsoft tooling, and enterprise workloads that depend on SQL Server features. Evaluate the installed engine separately from Azure services built on its technology.
What to check
Check edition, licensing, operating platform, and feature requirements. Stored procedures, server-level integrations, and administrative jobs can make migration more involved than moving tables.
Official documentation ↗