This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(92.8, 7.000000000000001%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHA%3C/text%3E%3C/svg%3E)
I've got a strange request from my IT Director. We have a 3rd party that routinely investigates our systems for vulnerability - and it's saying the SQL Server version on our PaaS Azure SQL Server is no longer supported.
Anyone have any ideas why that might be happening? Is there someone at Microsoft I can talk to about this?
An Azure relational database service.
@Harris, Allen Thank you for reaching out.
My understanding is that while running the VA you got an error message stating that he SQL Server version on our PaaS Azure SQL Server is no longer supported.
The error message you are seeing indicates that the version of Vulnerability Assessment (VA) installed on your Azure SQL Server is not compatible with the version of SQL Server running on the server or one of its underlying databases.
To resolve this issue, you will need to update the version of VA installed on your Azure SQL Server to a version that is compatible with the version of SQL Server running on the server or one of its underlying databases.
Manage vulnerability findings in your Azure SQL databases
Regards,
Oury
@Oury Ba-MSFT - I don't think the 3rd Party advisor is using the VA Azure feature, but I'll look into it. I think they do their own scans.
Yes, look like your third-party software is not using the VA assessment. So, then the comment above will only work if it is using VA.
Regards,
Oury
Answer accepted by question author
It seems to me the third party software is intended to inspect only SQL Server instances on Azure VMs or on-premises but not Azure SQL databases that are PaaS. Please verify that with the manufacturer. Azure SQL has its own version numbers independent of SQL Server versions, current version for Azure SQL is 12, but on the SQL Server side version 12 is a deprecated version.
Thanks! That's looking like what the problem is. The analysis apparently wasn't finished and my Director got it to me based on a partial analysis. We're checking to make sure, but I think the Azure vs On-Prem SQL Server version difference is what the problem is.
Maybe there is a newer version of that third-party tool compatible with databases on cloud services like Azure (Azure SQL, Hyperscale, SQL on Azure VMs, Azure Managed Instance).
Another thing your organization may consider is to acquire a new tool capable of analyze databases on cloud services IaaS and PaaS.
Hope it helps.
Thank you @Oury Ba-MSFT for your support, Have a wonderful day!