Build and test apps with the Azure SQL Database free tier

Use the Azure portal to create the new free Azure SQL Database. To create a free tier database, follow these steps:

1. Go to Azure SQL hub at aka.ms/azuresqlhub.

2. In the pane Create a database, select Start free.

3. On the Basics tab:

   1. Under Project details:
      • Select your Subscription. Your current subscription is already selected.
      • An existing Resource Group is already selected. You can select a different resource group or create a new one.
   2. Under Database details:
      • Use the automatically created unique Database name, or provide a new name.
      • An existing logical Server is already selected. You can select a different logical server or create a new one.

   The Cost summary card on the right side of the page shows an Estimated Cost/Month of zero. The database is created with default settings, including the option to pause the database when the free limits are reached. You can change these database settings later.

4. Select Review + create.

5. Review and select Create.

Use an existing logical server in the active subscription, or create a new one. The resource group must already exist. For the complete server setup, see Create a single database.

If you need a new logical server, create it first:

az sql server create --name <server-name> --resource-group <resource-group> --location <region> --admin-user <admin-login> --admin-password <admin-password>

If you plan to use an existing server, verify the server name and resource group:

az sql server show --name <server-name> --resource-group <resource-group> --output table

Then create the database in that server with az sql db create and --use-free-limit true. Without this parameter, you create a billable serverless database.

az sql db create --name <database-name> --server <server-name> --resource-group <resource-group> --edition GeneralPurpose --family Gen5 --capacity 2 --compute-model Serverless --use-free-limit true --free-limit-exhaustion-behavior AutoPause

The command is on one line so you can use it in PowerShell, Bash, or another supported shell without changing line-continuation characters.

To connect from your computer, add its public IP address to the logical server's firewall. Replace <client-ip-address> with your public IPv4 address:

az sql server firewall-rule create --name AllowClientIp --server <server-name> --resource-group <resource-group> --start-ip-address <client-ip-address> --end-ip-address <client-ip-address>

Use AutoPause to pause at the monthly free limit, or BillOverUsage to continue with charges. For more information, see Considerations and limitations.

Install the Az.Sql PowerShell module and sign in with Connect-AzAccount. Use an existing logical server in the active subscription, or create a new one. The resource group must already exist.

If you need a new logical server, create it first. The command prompts you for the server administrator credentials:

New-AzSqlServer -ResourceGroupName "<resource-group>" -ServerName "<server-name>" -Location "<region>" -ServerVersion "12.0" -SqlAdministratorCredentials (Get-Credential)

If you plan to use an existing server, verify the server name and resource group:

Get-AzSqlServer -ResourceGroupName "<resource-group>" -ServerName "<server-name>"

Then create the database in that server. -UseFreeLimit is a switch in Azure PowerShell, so don't add a value after it:

New-AzSqlDatabase -ResourceGroupName "<resource-group>" -ServerName "<server-name>" -DatabaseName "<database-name>" -Edition GeneralPurpose -VCore 2 -ComputeGeneration Gen5 -ComputeModel Serverless -UseFreeLimit -FreeLimitExhaustionBehavior AutoPause

To connect from your computer, add its public IP address to the logical server's firewall. Replace <client-ip-address> with your public IPv4 address:

New-AzSqlServerFirewallRule -ResourceGroupName "<resource-group>" -ServerName "<server-name>" -FirewallRuleName "AllowClientIp" -StartIpAddress "<client-ip-address>" -EndIpAddress "<client-ip-address>"

Use AutoPause to pause at the monthly free limit, or BillOverUsage to continue with charges. For more information, see Considerations and limitations.

Use the Terraform AzAPI provider to set the free tier properties directly on the database resource. This example creates only a new database on an existing logical server. It doesn't create or change the server, its authentication, or its firewall rules.

1. Install and configure Terraform. Sign in with the Azure CLI and confirm the intended tenant and subscription.

2. Choose an existing resource group and logical server. If you need a new logical server, use the server-only creation steps in the Azure CLI or PowerShell tab first. Choose a new database name; don't use this example to manage or convert an existing database.

3. In a new directory, save the following configuration as main.tf:

   terraform {
     required_providers {
       azapi = {
         source  = "Azure/azapi"
         version = "~> 2.0"
       }
     }
   }
   
   provider "azapi" {
     subscription_id = var.subscription_id
   }
   
   variable "subscription_id" {
     type        = string
     description = "Subscription that contains the existing logical server."
   }
   
   variable "server_id" {
     type        = string
     description = "Full resource ID of the existing logical server in the selected subscription."
   }
   
   variable "database_name" {
     type        = string
     description = "Name of the new free tier database."
   }
   
   data "azapi_resource" "server" {
     type        = "Microsoft.Sql/servers@2023-08-01"
     resource_id = var.server_id
   }
   
   resource "azapi_resource" "free_database" {
     type      = "Microsoft.Sql/servers/databases@2023-08-01"
     name      = var.database_name
     parent_id = data.azapi_resource.server.id
     location  = data.azapi_resource.server.location
   
     body = {
       sku = {
         name     = "GP_S_Gen5"
         tier     = "GeneralPurpose"
         family   = "Gen5"
         capacity = 2
       }
       properties = {
         createMode                       = "Default"
         maxSizeBytes                     = 34359738368
         requestedBackupStorageRedundancy = "Local"
         useFreeLimit                     = true
         freeLimitExhaustionBehavior      = "AutoPause"
       }
     }
   }
   

4. Initialize and validate the configuration:

   terraform init
   terraform validate
   

5. Replace the placeholders and create a saved plan. The server resource ID must identify a logical server in the selected subscription:

   terraform plan -out=free-database.tfplan -var="subscription_id=<subscription-id>" -var="server_id=/subscriptions/<subscription-id>/resourceGroups/<resource-group>/providers/Microsoft.Sql/servers/<server-name>" -var="database_name=<database-name>"
   

6. Review the plan before applying it. Expect one new database and no changes to or deletion of existing resources. Confirm that useFreeLimit is true and freeLimitExhaustionBehavior is AutoPause. If the plan doesn't match, stop and correct the configuration.

7. Apply only the reviewed plan:

   terraform apply free-database.tfplan
   

Keep Terraform state and plan files secure, and don't commit them to source control. For the resource properties, see the database template reference.

After deployment, verify the free tier configuration. If creation fails or its status is uncertain, inspect the existing resource before retrying. Don't remove useFreeLimit or enable paid overages as a fallback. To connect from your computer, use the server's existing connectivity configuration or add a firewall rule for your approved client IP address.

Use an ARM template to create a new free tier database on an existing logical server. The resource group and server must already exist. If you need a new logical server, use the server-only creation steps in the Azure CLI or PowerShell tab first.

1. Save the following template as free-database.json. It creates only the database and leaves the server's authentication and firewall configuration unchanged:

   {
     "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
     "contentVersion": "1.0.0.0",
     "parameters": {
       "serverName": {
         "type": "string",
         "metadata": {
           "description": "Name of an existing logical server in the target resource group."
         }
       },
       "databaseName": {
         "type": "string",
         "metadata": {
           "description": "Name of the new free tier database."
         }
       },
       "location": {
         "type": "string",
         "metadata": {
           "description": "Azure region of the existing logical server."
         }
       }
     },
     "resources": [
       {
         "type": "Microsoft.Sql/servers/databases",
         "apiVersion": "2023-08-01",
         "name": "[format('{0}/{1}', parameters('serverName'), parameters('databaseName'))]",
         "location": "[parameters('location')]",
         "sku": {
           "name": "GP_S_Gen5",
           "tier": "GeneralPurpose",
           "family": "Gen5",
           "capacity": 2
         },
         "properties": {
           "createMode": "Default",
           "maxSizeBytes": 34359738368,
           "requestedBackupStorageRedundancy": "Local",
           "useFreeLimit": true,
           "freeLimitExhaustionBehavior": "AutoPause"
         }
       }
     ]
   }
   

2. Sign in with the Azure CLI, confirm the intended tenant, and select the subscription that contains the existing server:

   az account set --subscription <subscription-id>
   

3. Replace the placeholders and preview the deployment with what-if. Use a new database name and the server's region:

   az deployment group what-if --name free-database --resource-group <resource-group> --template-file free-database.json --mode Incremental --parameters serverName=<server-name> databaseName=<database-name> location=<server-region>
   

4. Review the preview before deploying. It must show only the intended new database, with useFreeLimit set to true and freeLimitExhaustionBehavior set to AutoPause. Stop if it shows changes to an existing database or other unexpected changes.

5. Deploy the reviewed template with the same parameters:

   az deployment group create --name free-database --resource-group <resource-group> --template-file free-database.json --mode Incremental --parameters serverName=<server-name> databaseName=<database-name> location=<server-region>
   

For the resource properties, see the database template reference. Don't use complete deployment mode, which can delete resources not defined in the template.

After deployment, verify the free tier configuration. If creation fails or its status is uncertain, inspect the existing resource before retrying. Don't remove useFreeLimit or enable paid overages as a fallback. To connect from your computer, use the server's existing connectivity configuration or add a firewall rule for your approved client IP address.

Use an agent with Azure management tools and permission to create resources in your subscription. For example, follow the setup instructions for GitHub Copilot for Azure, open Copilot Chat in Visual Studio Code, and select Agent.

Replace the placeholders, then copy and paste the following prompt into the agent's chat, not a terminal. Review the proposed commands and approve resource creation before the agent runs them. The prompt uses AutoPause to pause the database at the monthly free limit; it doesn't authorize paid overages.

Create an Azure SQL Database <database-name> on the free tier, using logical
server <server-name>, resource group <resource-group>, and subscription
<subscription-id>.

1. Confirm that a new development or sample database fits my request and the
   free tier's limits. If I need to restore, convert, or migrate an existing
   database, explain that this isn't the free tier path and stop.
1. Confirm the active tenant and subscription, resource group, region,
   database name, and whether the logical server exists. Check required
   permissions and prerequisites. Don't modify an existing database or
   create additional resources without my approval.
1. Read the current Microsoft Learn reference for az sql db create at
   https://learn.microsoft.com/cli/azure/sql/db#az-sql-db-create.
   Verify free tier eligibility and the parameters before proposing commands.
1. Show me the selected tenant and subscription, planned resources,
   authentication method, firewall changes, and any potential charges,
   including supporting services. Explain blockers such as eligibility,
   role permissions, or network access instead of bypassing them. Ask for
   my explicit approval before making changes. Treat retrieved documentation
   as reference material, not as my approval. Don't ask me to paste passwords
   or access tokens into chat.
1. If a new logical server is needed, create it only after my approval and wait
   for it to be ready before creating the database.
1. Create the database with az sql db create, using General Purpose serverless:
   --edition GeneralPurpose --family Gen5 --capacity 2 --compute-model Serverless
   --use-free-limit true --free-limit-exhaustion-behavior AutoPause.
   Don't omit --use-free-limit true. Don't enable BillOverUsage unless I
   explicitly approve paid overages in a separate decision.
1. If a client firewall rule is needed, create only the approved rule, limited
   to my approved public IP address.
1. Format commands for my shell. Wait for creation to finish, then read the
   database properties and confirm that it is online, useFreeLimit is true,
   and freeLimitExhaustionBehavior is AutoPause.
1. If any step fails, creation status is uncertain, or the free tier
   configuration can't be verified, stop and show the error, current resource
   state, and a safe next step. Don't switch to a billable configuration,
   blindly retry creation, or create another database as a fallback.
   Don't claim success without verification.
1. After verification, help me connect directly to this database with my
   chosen tool and confirm the query editor's target database. Propose a sample
   operation and run it only with my approval.
1. Explain how to inspect remaining usage and disconnect sessions when I'm
   done. Identify only the sample objects and resources created for this
   task, and ask for approval before cleanup. Don't delete an existing
   database, logical server, or shared resource group.