Best practices for handling confidential submissions in Power Apps + Power Automate?
I’m building a Power App that collects confidential information through a form, and I want to design it so that neither I (the developer) nor anyone else without explicit permission can view the submitted data.
My goal is to treat the data as sensitive from the start, so even though I’m building the app and flows, I don’t want to accidentally create a situation where admins or developers can easily access submissions.
Right now my rough idea is:
• Power App form submission
• Power Automate flow processes the submission
• Data stored somewhere secure (SharePoint list, Dataverse, or another option)
What I’m unsure about is the best architecture to enforce confidentiality, such as:
• Preventing app builders from viewing stored submissions
• Restricting access so only a specific role/team can see the data
• Whether Dataverse, SharePoint, or another storage option is better for this
• If there are ways to mask or encrypt data during the flow
For people who have built confidential reporting tools, HR forms, or ethics hotlines in the Power Platform, what are the best practices?
Appreciate any guidance or architecture examples. Yes, AI was used for this post.
Posted Mar 6, 2026, 9:49 PM UTC