Update sql-azure-vulnerability-assessment-manage.md

Added information to Troubleshooting section
-------
cc: @bmansheim

Author: CESANU

articles/defender-for-cloud/sql-azure-vulnerability-assessment-manage.md

@@ -250,6 +250,8 @@ To change an Azure SQL database from the express vulnerability assessment config
                -RecurringScansInterval Weekly `
                -ScanResultsContainerName "vulnerability-assessment"
    ```
+   
+   You may have tweak `Update-AzSqlServerVulnerabilityAssessmentSetting` according to [Store Vulnerability Assessment scan results in a storage account accessible behind firewalls and VNets](/azure/azure-sql/database/sql-database-vulnerability-assessment-storage?toc=%2Fazure%2Fdefender-for-cloud%2Ftoc.json&view=azuresql).
 
 ### Errors
 
@@ -264,6 +266,7 @@ Possible causes:
 - Switching to express configuration failed due to a database policy error. Database policies aren't visible in the Azure portal for Defender for SQL vulnerability assessment, so we check for them during the validation stage of switching to express configuration.
 
    **Solution**: Disable all database policies for the relevant server and then try to switch to express configuration again.
+   Cosnider using the [provided PowerShell script](powershell-sample-vulnerability-assessment-azure-sql.md) for assistance.
 
 ### [Classic configuration](#tab/classic)