Schema Compare retains the sensitivity classifications when table is deleted

Question

Hi,

We've got a sql project that we use for CICD deployments from DEV to TST/PRD.

Recently we had added some classifications to the tables in DEV as we were trialling purview.

During schema compare and update to the solution repo, I have noticed that the project retains the classification despite the table being deleted. This results in the project build failing. I have recreated the table with classification, and the project builds fine. I then proceeded to remove the classifications (retained table) and updated the target repo. The project builds fine. While deployment, I noticed that the classifications were retained and the solution deployed. Basically the classifications have been deleted from source but retained in target. We are in the process of changing some data load patterns (batch to incremental and vice versa) to optimise costs.

Is this a limitation on the Visual Studio side or am I missing something?