Incorrect "Sensitive data columns should be classified" report Every week I'm getting a failed "Vulnerability Assessment" email report from my Microsoft Azure SQL Database that is incorrect.
It complains about columns that have is_computed column in sys.columns set to 1.
It is not possible to add a classification for those columns.



Is it possible to stop the warning?
Basically it will not fade away when we approve it as a baseline. Sometimes it does. But in most cases we will get baseline mismatch where we should go inside the database to classify those data that we approved as the baseline in the azure portal.
For more details on how to classify the data inside SQL please follow the below links.Data discovery and classification
RDBMS security