How to authenticate data source by service principal rather than the logged in user

(0) Share

Report

Posted on by SverreFalch

I have made an app which connects to a sharepoint list to retrieve and write data.

So far I have not found any way to avoid giving access to end users directly to the actual Microsoft List.

This give them access to open up the list directly in Sharepoint and they have the possibility of entering/deleting data directly from this GUI.

What I want to have, is the end users authenticating with their org.user to my app, then Power Apps is using a service principal to authenticate to the Microsoft List.

This keeps the control of the list entries to me (admin) while users have the ability to insert/amend their records through the developed app in Power Apps.

I am aware of the Power Automate workaround, but this is very tedious and complicated way of achieving this simple task.

Let me know if there is any alternative solution.

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

WarrenBelz 156,100 Most Valuable Professional on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @SverreFalch

Quite simply, any connections to data sources in Power Apps are run in the context of the logged-in user and are authenticated when the user first opens the app, meaning the logged-in user must have appropriate permissions in SharePoint. There are a couple of things you can do in SharePoint - one is as per this blog of mine and simply stop the user changing anything.

The other is to give them a Custom Permission in SharePoint based on Contribute with View Application Pages unchecked. This should prevent them from accessing any view on the applicable List/s.

Please click Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it a Like.
MVP (Business Applications) Visit my blog Practical Power Apps LinkedIn

Was this reply helpful? Yes No
Suggested answer

Artur Stepniak 1,539 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

Hello,

as Warren said, that's it. You can workaround it by using a flow to perform CRUD operations on the list. And I'd argue that it's a complicated way, just instead of Patch() you're using Run() with input parameters.

In case of any other questions, let me know. If the answer helped you, mark it, so that others can benefit from it.

Best regards,

Artur Stepniak

Interested in GenAI? Visit my site!

Was this reply helpful? Yes No
WarrenBelz 156,100 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

@SverreFalch,

A quick follow-up to see if you received the answer you were looking for or if you need further assistance.

Please click Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it a Like.
MVP (Business Applications) Visit my blog Practical Power Apps LinkedIn

Was this reply helpful? Yes No