Jeroen ter Heerdt

@ZippyV: It is absolutely safe. The classification engine scans your database and identifies columns containing potentially sensitive data. Sensitivity classification labels can be persistently tagged on columns using metadata attributes in the SQL Engine. It doesn’t change the database schema or data in it so behavior of the applications shouldn’t change. Let me know if you have any other questions!

@htaki: thanks! I am glad you like it.

@tesseract1919: hi! there is an episode about Data Virtualization here: https://channel9.msdn.com/Shows/Data-Exposed/Introducing-Data-Virtualization

@deltalmg911: if you try to restore from bacpac that uses features that are not supported, your backup will fail. I would recommend using Data Migration Assistant to get an idea of what is the right target before 'blindly' trying this. More info here: https://docs.microsoft.com/en-us/sql/dma/dma-assess-sql-data-estate-to-sqldb?view=sql-server-ver15

@asgar: Azure Data Factory will need Allow Access to Azure Services to be ON unless using self hosted Integration Runtime ( which will have a well defined IP address range)
More info here https://docs.microsoft.com/en-us/azure/data-factory/connector-azure-sql-database.

Thanks!

@ArneG: I am not sure what you mean here - care to elaborate?

@Ymer: Setting Allow access to Azure services button on the Portal (Firewall settings page) to ON shall allow traffic to/from resources ( e.g. Azure VM) or PaaS services( e.g. Web App) hosted inside Azure - within same subscription or from another subscription as well. Hope this helps.