The Row and Column Level Security and Table ACLs defined in Databricks Unity Catalog do not carry over when exporting data to Azure SQL Database, regardless of whether the export is done via JDBC, pipelines, or notebooks.

The reason behind this is Unity Catalog’s security model is enforced only at query time within Databricks. The access rules are not stored as metadata within the data itself, so once the data is exported, it becomes plain data in Azure SQL DB, with no security context.

To maintain similar security in Azure SQL Database, you need to define access controls again, using native Azure SQL DB features.

Below I've shown an example how I manually added RLS in SQL database:

Firstly, I created RLS predicate function to ensure users only see rows matching their region:

Then, created the Security Policy:

Lastly, Simulated access for a specific region:

This ensures users only see the rows for their assigned region.