How to fix the Loading error when creating a server

You may try following checks:

1. Resource provider registration - In Subscriptions then your subscription then Resource providers, find Microsoft.Sql. If it isn't Registered, click Register, wait a few minutes, and reload the create page.
2. Allowed-locations policy - In Policy then Assignments, look for "Allowed locations." If it's there, open its Parameters to see which regions are allowed, and create both the server and its resource group in one of those regions.
3. Region access for your subscription - Some subscriptions can't create SQL servers in certain regions, which shows up as a "does not have access to create a server in the selected region" error. Try a different region, or open a support ticket to request access.

To find out which one it is, run this in Cloud Shell (the >_ icon):

az sql server create -n <unique-name> -g <rg> -l <region> \
  --admin-user <user> --admin-password '<password>'

It will either create the server or return the exact error, and that error points to which of the three causes applies.

Hi @Ayush Buch

Since the Location field remains at Loading... and you've reproduced the issue in another browser, first determine whether the Azure portal is failing to retrieve the available Azure SQL locations.

Please check that the subscription is registered with the Microsoft.Sql resource provider. Microsoft.Sql/register/action registers the subscription for Azure SQL Database and enables SQL Database resource creation.

Also verify that your account has sufficient Azure RBAC permissions. The SQL Server Contributor, Contributor, or Owner roles can provision an Azure SQL logical server.

If both are correct, reproduce the problem and press Ctrl+Alt+A in the Azure portal. This generates PortalDiagnostics.json, which contains the portal session ID and diagnostic metadata. I recommend capturing the browser Network/Console trace when troubleshooting Azure portal failures.

As an isolation test, you can also try creating the logical server using Azure CLI or PowerShell.

If non-portal creation works while the Location field consistently remains stuck, provide the PortalDiagnostics.json and sanitized browser trace to Microsoft Support.

I cannot find verified Microsoft documentation identifying a current Azure SQL incident specifically associated with this Location → Loading... symptom.

References:

Azure Permissions for Databases

Create server with Microsoft Entra-only authentication enabled in Azure SQL

Capture a browser trace for troubleshooting

Create and manage servers and single databases in Azure SQL Database

Help make this community better for everyone: If this answer helped or resolved your issue, please accept it or upvote it. If not, share more details in a comment so we can continue the discussion and find the right solution. Thank you.