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.

enter image description here

Is it possible to stop the warning?


You need to add those as a 'baseline', basically marking those items as ignorable items so that when the VA report runs again it ignores them.

See here for more information.

  • I have added those for all normal columns in the database. Took a bit of time, but not too much. The problem here is that the column is a calculated column, and you cannot add those to the baseline. Aug 13 '19 at 9:09
  • That's odd, I'm not seeing that behaviour at all. If I create a new Azure SQL DB, create a table with a column called "CreditCard" then run a VA scan, I get a warning about sensitive data column classification. If I then approve as baseline to eliminate that warning and run a new scan, that warning is not shown in the new scan.
    – HandyD
    Aug 14 '19 at 4:58
  • to that table, please add a column called CopyOfCreditCard as a calculated column: CopyOfCreditCard = (CreditCard) and try to add ADD SENSITIVITY CLASSIFICATION TO table.CopyOfCreditCard WITH (LABEL = 'Confidential', INFORMATION_TYPE = 'Financial') Then you'll see that this is not possible. Next time you get a Vulnerability Assessment email from Microsoft, it will tell you to fix the new column. And this is not possible, as you can see. Aug 14 '19 at 8:15
  • Approving the list of warnings as a baseline solves the problem with the warning on calculated columns, just as you wrote in your answer. It is just annoying that I have to do that for each and every time I add a calculated column. Thank you for your help. Sep 5 '19 at 7:37

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

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.