Hey there, just wondering when there will be support for using "Express" configuration with SQL Server Vulnerability Assessments? The existing vulnerability assessment configuration using storage is a nightmare when also using identity on the server and in fact I simply don't think it works at all through Pulumi having fought it for the entire day... Here is the information about the new way to do assessment configuration: https://learn.microsoft.com/en-us/azure/defender-for-cloud/sql-azure-vulnerability-assessment-overview#what-are-the-express-[…]lassic-configurations In the Azure Portal you cannot use the legacy way either which is why I suspect it has minimal support for identity auth to the storage account along with the strange error messages. Here's what that configuration area looks like now (single button)

The code for the Azure Native provider is actually auto-generated from Azure's published ARM API spec! If they haven't published an updated spec for this feature, then there's no way for Pulumi to make use of it. That said, if there is a published version of the API, even a preview one, then you can address it directly. (The default ARM API spec that Azure Native targets is not going to be bleeding edge, which is why you may not see the ability to target this feature in your code). In C#, which I am most familiar with, you'd do it like so:

// The default provider version doesn't have the feature I want
using Pulumi.AzureNative.Database;

// This explicit version has the one I want!
using Pulumi.AzureNative.Database.V20230731Preview;

(This is an imaginary example; you'll need to check the available versions of your provider to see if it's there. If not, try updating your Azure Native dependency!)