How do I fix a failed deployment when making a sql database?

Hi @Josseline Gonzalez

From your screenshot i understand may be db exist in your Azure SQL database. so first check below points

1. Go to SQL servers → bus3393jg → Databases.
2. If a database with the same name exists, delete it or rename your new one.
3. Use a new database name (e.g., BUS3DB_2026) and redeploy. Conflicts often clear when the name is unique.
4. Azure for Students subscriptions have limited SQL quotas. So, Go to Subscription → Usage + quotas → SQL Database and confirm you haven’t exceeded limits.
5. If the region is temporarily restricted for your subscription, try deploying in another region (e.g., East US or West Europe).
6. Open Activity log → Filter by resource group bus3393jg → Error details. show search or look like Database creation failed due to existing resource or operation conflict.
7. If the server was created but the database failed:
   • Delete the server and recreate it.
   • Or use Azure CLI: az sql server delete --name bus3393jg --resource-group bus3393jg

Thanks.

Hello @Josseline Gonzalez

Thank you for reaching out to us

The Azure SQL Database deployment failed during the database provisioning phase. Based on the deployment details, the Azure SQL logical server and associated firewall rules were created successfully; however, the database creation operation encountered an error and ultimately transitioned to a terminal provisioning state of "Failed."

The error shown in the Azure portal is a generic deployment failure message and does not provide the specific cause of the issue. To determine the underlying reason for the failure, it is necessary to review the deployment operation details and the corresponding Azure Activity Log entries for the failed deployment.

Such failures can occur due to several factors, including transient platform provisioning issues, resource conflicts, subscription or quota limitations, Azure Policy restrictions, or unsupported configuration selections during deployment.

As a next step, we recommend reviewing the deployment's Error Details and Activity Log entries to identify the specific error code generated during the database provisioning process