Skip to content

Commit cb865aa

Browse files
authored
Update azure-sql/database/sql-database-vulnerability-assessment-storage.md
Removed number
1 parent b376a83 commit cb865aa

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ If you're limiting access to your storage account in Azure for certain VNets or
2727

2828
When you use the Azure portal to save SQL VA settings, Azure checks if you have permission to assign a new role assignment for the managed identity as [Storage Blob Data Contributor](/azure/role-based-access-control/built-in-roles#storage-blob-data-contributor) on the storage. If permissions are assigned, Azure uses SQL Server managed identity, otherwise Azure uses the key method.
2929

30-
1. If using Azure Storage lifecycle management policies, avoid moving files on the container used by VA to the archive access tier. Reading scan results or baseline configurations stored in archive access tier isn't supported.
30+
If using Azure Storage lifecycle management policies, avoid moving files on the container used by VA to the archive access tier. Reading scan results or baseline configurations stored in archive access tier isn't supported.
3131

3232
## Enable Azure SQL Database VA scanning access to the storage account
3333

0 commit comments

Comments
 (0)