Skip to content

Commit ed9a088

Browse files
authored
Update sql-database-vulnerability-assessment-storage.md
1 parent 4c3ef31 commit ed9a088

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-sql/database/sql-database-vulnerability-assessment-storage.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ If you are limiting access to your storage account in Azure for certain VNets or
2121
If you have configured your VA storage account to only be accessible by certain networks or services, you'll need to ensure that VA scans for your Azure SQL Database are able to store the scans on the storage account. You can use the existing storage account, or create a new storage account to store VA scan results for all databases on your [logical SQL server](logical-servers.md).
2222

2323
> [!NOTE]
24-
> Vulnerability Assessment service cannot access a storage account behind firewall/VNet using a storage access key.
24+
> The vulnerability assessment service can't access storage accounts protected with firewalls or VNets if they require storage access keys.
2525
2626
Go to your **Resource group** that contains the storage account and access the **Storage account** pane. Under **Settings**, select **Firewall and virtual networks**.
2727

0 commit comments

Comments
 (0)