Instead deploy an Azure SQL database that uses the Business Critical service tier and Availability Zones.
Note: Premium and Business Critical service tiers leverage the Premium availability model, which integrates compute resources (sqlservr.exe process) and storage (locally attached SSD) on a single node.
High availability is achieved by replicating both compute and storage to additional nodes creating a three to four-node cluster.
By default, the cluster of nodes for the premium availability model is created in the same datacenter. With the introduction of Azure Availability Zones, SQL Database can place different replicas of the Business Critical database to different availability zones in the same region. To eliminate a single point of failure, the control ring is also duplicated across multiple zones as three gateway rings (GW).
Reference:
https://docs.microsoft.com/en-us/azure/azure-sql/database/high-availability-sla

Explanation:
https://docs.microsoft.com/en-us/azure/azure-sql/database/purchasing-models
https://docs.microsoft.com/en-us/azure/azure-sql/database/single-database-create-arm-template- quickstart

Explanation:
Box 1: Azure Cosmos DB
A rapidly iterating cloud-based solution that integrates multiple software as a service (SaaS) solutions.
For a rapidly iterating, cloud-based SaaS integration solution, Azure Cosmos DB is a strong recommendation. It offers a schemaless, multi-model database that supports flexible data modeling and querying, which is crucial for agile development and integrating diverse SaaS solutions. Its global distribution and automatic scaling capabilities also ensure high availability and performance as your application grows.
Box 2: Azure SQL Managed Instance
The migration of an existing on-premises Microsoft SQL Server 2019 database to Azure.
Project2 must minimize malware threats to the underlying operating system that hosts the migrated database.
Azure SQL Managed Instance minimizes malware threats to the underlying operating system by leveraging a multi-layered security approach, including threat detection, encryption, and network isolation. It achieves this by handling the operating system and underlying infrastructure at the PaaS level, reducing the attack surface accessible to malicious actors.
Box 3: SQL Server on Azure on VM
An app that supports multiple 20-TB databases.
If you need to store more than 16 TB of data, you should consider moving to Azure SQL Database Hyperscale or SQL Server on Azure Virtual Machines.
Reference:
https://learn.microsoft.com/en-us/azure/architecture/guide/multitenant/service/cosmos-db
https://learn.microsoft.com/en-us/azure/azure-sql/database/security-overview

Automated Patching depends on the SQL Server infrastructure as a service (IaaS) Agent Extension. The SQL Server IaaS Agent Extension (SqlIaasExtension) runs on Azure virtual machines to automate administration tasks. The SQL Server IaaS extension is installed when you register your SQL Server VM with the SQL Server VM resource provider.
To utilize the SQL IaaS Agent extension, you must first register your subscription with the Microsoft.SqlVirtualMachine provider, which gives the SQL IaaS extension the ability to create resources within that specific subscription.
Reference:
https://docs.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/sql-server-iaas- agent-extension-automate-management https://docs.microsoft.com/en-us/azure/azure-sql/virtual- machines/windows/sql-agent-extension-manually-register-single-vm?tabs=bash%2Cazure-cli