Licensing needed for SharePoint connection to PowerApps?

(0) Share

Report

Posted on by Meneghino

6,949

Hi, I can create a user in our domain who has a trial license for PowerApps but no license for Office365.

They can run an app that has a connection to an Azure SQL DB.

They can view our SharePoint Online sites and document libraries etc.

However, when I add a connection to SharePoint in PowerApps, they are not allowed to go further since the Allow button is disabled (see below).

Is this by design?

Does it mean that a user needs an Office365 license in order to use a PowerApp that connects to SharePoint Online?

Many thanks for any insight.

PS I read this illuminating exchange by @audrieg and @sarafankit but it did not help with my particular issue.

Categories:

Building Power Apps

All responses (5)

Answers (2)

Sort by

sarafankit Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Can you please provide us the session id where you are seeing this issue? If you use PowerApps mobile player or studio for windows, you can get that via Account > Debug > Session Id

If you cannot find the session id, please provide the email-id of the user you have created.
Meneghino 6,949 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi Sarafankit, thanks for getting back to me.
The session id is as follows,
Session ID: 131a2ce4-37b7-1e12-567e-7b1c04b0105a
In a desperate attempt to get this working I even bought a license, but it disn't hellp.
Please help me!
Verified answer

sarafankit Microsoft Employee on at

Like
a
(1)

Report
Copy link

Link copied!
Thanks for the information, are you or were you using the Office365Users connection as well in the app?

Can you please:
Open the app in PowerApps Studio
If you have the Office365Users connection, remove it & add it again. Or if you don't have it just add it once.
Save & Publish the app
Now run the app with the new user
Let's see if this gets you unblocked, I am still trying to figure out what is happening, it doesn't seem like a licensing issue per se.
Steelman70 873 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi Sarafankit, thanks for the quick follow-up.
I was using the Office365 Users connection in an earlier version of the app, but removed it since the new user was not licensed at the time.
I am back in the office on Monday and will try what you suggest.
Thanks again for the quick follow-up.
Verified answer

Meneghino 6,949 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @sarafankit
Apologies, my mistake. Indeed the issue was not with the SharePoint connection or with the Office365Users connection, but with the SQL Server connection. I had forgotten that this type of connection is not shared automatically when the app is shared, but needs to be shared as well.
Many thanks for the quick and useful help!