[Feature request]: Azure SQL resources are missing from Azure browse experience

[croblesm]

Please add Azure SQL resources to the Azure VS Code extension Browse experience to ensure parity with other first-party database services.

Problem Statement

The Azure VS Code extension does not surface Azure SQL resources (Azure SQL Database, Azure SQL Server, Hyperscale, Dedicated SQL Pools) in the Azure Resources tree.

This creates a significant discoverability and usability gap, especially given that Azure SQL is one of Azure’s most widely used data services.

Observed Behavior

• Under Azure → Resources, the extension lists:
  • PostgreSQL (Single / Flexible)
  • Cosmos DB (NoSQL, MongoDB)
  • DocumentDB
  • Other compute and app services
• Azure SQL resources are completely absent, even when:
  • The subscription contains many Azure SQL databases
  • Azure Portal clearly shows these resources
  • Filtering by resource type confirms their existence

Resource view from Azure Resource Group extension:

As a result, users cannot:

• Browse Azure SQL databases
• Discover existing SQL servers or databases
• Perform common SQL workflows from VS Code

Expected Behavior

The Azure VS Code extension should list Azure SQL resources similarly to other database services, including:

• Azure SQL Server
• Azure SQL Database
• Azure SQL Database – Hyperscale
• Dedicated SQL Pool (formerly SQL DW)

These should appear under Azure → Resources with:

• Proper grouping (Server → Databases)
• Subscription and resource group awareness
• Standard resource actions

Evidence

• Azure Portal shows multiple Azure SQL databases in the same subscription
• Azure VS Code extension resource tree does not show any Azure SQL resources
• Azure Portal resource filtering confirms:
  • SQL database
  • Azure SQL Database Hyperscale
  • Dedicated SQL pool (formerly SQL DW)

Resource view from Azure Portal (Same subscription, filtering "Azure SQL" resource types):

Impact

• Azure SQL users cannot manage or discover their databases from VS Code
• Inconsistent experience compared to PostgreSQL and Cosmos DB
• Reduced adoption of Azure SQL in IDE-centric workflows
• Missed opportunity to promote Azure SQL usage directly from VS Code

From a user perspective, this behaves like a functional bug.

cc @amthomas46