In this article, we shall discuss “how to create a new Azure SQL Database [PaaS]” using the Azure Portal, highlighting the key steps, the most relevant configuration options, and the architectural considerations to keep in mind from the very beginning. Please, see How to create a two-way Active Directory Trust, [AZURE] Restore MSSQL Server on Azure Virtual Machines Using Azure Backup, and MSSQL Server Error 833: A Synthesis of Real-World Case Studies.

In the context of modern cloud solutions, Azure SQL Database stands out as one of the most mature and reliable PaaS services offered by Microsoft for managing relational databases. By offloading critical operational tasks such as maintenance, patching, backups, and high availability to the platform, IT teams can focus more on delivering business value and optimizing application performance.

The goal is to provide a clear and practical guide, useful both for those approaching Azure SQL Database for the first time and for professionals looking to reinforce best practices in enterprise scenarios.

This is the information to request from the customer for the deployment of an Azure SQL Database.

Also, see how to Pull and Push Commvault Images to Azure Container Registry, [AZURE] Security Service Edge (SSE) and Microsoft Entra ID, and Install SQL Server Always On & Configure Veeam Plug‑in for SQL.

Azure SQL Database PaaS

Information about the database

Azure Subscription
Resource group
Database name
Elastic Pool (yes/no)
Compute + Storage (Service tier e.g. ‘general purpose’; compute tier e.g. ‘provisioned’ (GEN5) 2vcpu, 32GB; already have a SQL Server licence? (yes/no); Database zone redundant? (yes/no)
Backup (Grs/Zrs/Lrs)
Data source (none/backup/sample)
Database collation
Maintenance windows
Tags (indicate name and value for each tag)

Here are some information about the logical server to which the database is associated

Server Name: If the server already exists, fill in only this field; if the server is new, fill in the following fields as well
Location (Region)
Server admin login
• Password
Deny public network access (Yes/no)
Allow Azure services and resources to access this server (yes/no)
Connection policy (Default/Proxy/Redirect)
Private endpoints ( YES/NO , if YES, see next section)
Minimum Tls Version (1.0/1.1/1.2)
Tags (indicate name and value for each Tag)

Information regarding the private endpoint

Resource Group
Location (region)
Name
Target sub resource
Virtual network
Subnet
Private DNS integration option

From the Azure portal, go to the ‘SQL databases’ app.

So ‘create’

There are the following tabs to fill in with all the information provided by the customer

Tab Basic

Populate the information as it is applicable to you.

In this case, select ‘General Purpose’, but it depends on your requirements, GEO Redundant (Backup storage Redundancy)

In my case, I select Serverless. Also, see how to Resolve New WDAC Policy Issues in Azure Stack.

The Serverless compute tier for Azure SQL Database is an execution model designed for variable or intermittent workloads, where resource utilization is not constant over time. In summary, this feature provides:

Automatic compute scaling: CPU and memory are automatically allocated and released based on actual workload demand, with no manual intervention.
Usage-based billing: costs are calculated per second based on the resources actually consumed, rather than on pre-allocated capacity.
No infrastructure management: Microsoft handles compute provisioning, scaling, and maintenance.

The Serverless tier is particularly well suited for development and test environments, applications with unpredictable workloads, or solutions used only during specific time windows. It is not recommended for workloads with continuous and predictable usage, where a provisioned compute tier is generally more efficient.

Set the vCore resources required for your database.

Auto-pause and auto-resume: The database can automatically pause after a period of inactivity and resume when a new request is received, further reducing costs.