Best Approach for Managing User-Level and Row-Level Security in Power Apps with Azure SQL

Hi Everyone,

I’m currently building a CRM application using Power Apps connected to an Azure SQL database for my company, which has multiple retail stores. The application is designed with the following access needs:

Sales Table: Each store should only see their own sales data (read-only)
Product Table: Viewable by all stores (read-only)
Customer Table: Stores should be able to search, view, add, and edit customer data
Back Office: Full access to add/edit products and customer data.

I’ve seen a lot of great content online that shows how to connect Power Apps to Azure SQL at the developer level, but I haven't come across a clear explanation on how to manage user-level or row-level security once the connection is made at the user level.

My questions are:

Where should user-level and row-level security be managed — in Power Apps or directly in Azure SQL?
If it’s best handled in SQL, what’s the recommended way to create and manage security roles for Power Apps users?

I would really appreciate any guidance, especially if anyone has faced a similar use case.

Thanks in advance!

3 comments