SQL DB not Found

Question

SQL DB not Found

Shabir jan 21

~~Hi,~~

I have created SQL Server with multiple SQL Database in it, but when I try to click the Database in the Azure Portal, it says Resource Not Found, I can connect to the same database in the SQL Server Management Studio, I have also tried getting the usage of the server by running the Azure CLI command

az sql db list-usages --name 'db-name' --resource-group 'rg-dev' --server 'sqlserver-weu-nonprod'

And I am getting this in the terminal.

(ResourceNotFound) The Resource 'Microsoft.Sql/servers/sqlserver-weu-nonprod/databases/dbwtest' under resource group 'rg--weu-dev' was not found. For more details please go to https://aka.ms/ARMResourceNotFoundFix

Code: ResourceNotFound

Message: The Resource 'Microsoft.Sql/servers/sqlserver--weu-nonprod/databases/dbtest' under resource group 'rg-dev' was not found. For more details please go to https://aka.ms/ARMResourceNotFoundFix

0 comments

1 answer

Your answer

Answer 1

Deepesh Dhake 0

This usually means one of these situations is happening:

Wrong resource group
Wrong subscription
Database was restored/imported differently
Portal cache/desync issue
Typo/case mismatch in server or DB Name

The important clue is "You can connect successfully from SQL Server Management Studio".

That means:

Logical SQL endpoint is reachable
database with that name is responding via the SQL engine
connectivity/authentication is working

Akhil Gajavelly 1,825 Reputation points Microsoft External Staff Moderator

2026-05-27T05:06:40.04+00:00

Hi @Shabir jan

Thanks to the super user for the detailed troubleshooting guidance.

Since the database is accessible from SSMS, the SQL engine itself appears to be working correctly. This points more toward an Azure resource/metadata issue rather than a connectivity problem.

One additional check would be to run:

az sql db list --resource-group rg-dev --server sqlserver-weu-nonprod

to confirm whether the database appears under the expected Azure resource.

If the database is still accessible in SSMS but does not appear in Azure Portal or CLI results, it may require an Azure support ticket to investigate a possible backend ARM metadata inconsistency.

Thanks,
Akhil.

Share via

SQL DB not Found

1 answer

Your answer