Unanswered

I am unable to share sharepoint connection

(0) Share

Report

Posted on by Community Power Pla...

I tried to share the sharepoint connection with my org or user but it gives error.

The permission with id '/providers/Microsoft.PowerApps/apis//connections//permissions/' in the put collection requires either the id or the email for the principal.

The connection with id '/providers/Microsoft.PowerApps/apis/shared_sharepointonline/connections/' of type 'sharepointonline' cannot be shared.

Categories:

Building Power Apps

I have the same question (0)

All responses (5)

Answers (0)

Akash17 549 Super User 2024 Season 1 on at

Like (0)

Report

Hi @Anonymous
Please refer
https://www.sharepointdiary.com/2019/04/fix-sharing-failed-sharing-to-external-users-is-not-supported.html

Was this reply helpful? Yes No
rb 835 Super User 2024 Season 1 on at

Like (0)

Report

Hi @Anonymous,

You never need to share a SharePoint connection. When a SharePoint data source is being used, each user will automatically create their own SharePoint connection, and they will access the data source with the access and security of their identity.

There is a lot of documentation on different types of connectors, here is a good page which talks specifically about the type of authentication the SharePoint connector uses (Azure AD SSO): https://docs.microsoft.com/en-us/power-apps/maker/canvas-apps/connections-list#azure-ad-integrated

Was this reply helpful? Yes No
Brandon-Pattern 2 on at

Like (0)

Report

How is an Administrator supposed to fix connections when a service account has a password change?
This whole interface is built so that Administrators have almost no visibility and no access unless specifically granted, and now it seems that we CAN'T grant certain permissions, so Admin's really aren't able to administer anything.

Are we supposed to login and log out over and over again of various accounts and then navigate through the interface over and over for each account to change a password?
We have to now share service account credentials to anyone who will manage a flow/connection/PowerApp that runs as a service account?

this seems like an incredibly poor design.

--edit--

Example Scenario:

A developer who has access to multiple service accounts credentials embedded in multiple flows/connections/apps leaves the company, potentially on bad terms and has malicious intent.

We now have the duty to change the service account passwords.

How do we do this for many service accounts in a short amount of time?

Was this reply helpful? Yes No
rb 835 Super User 2024 Season 1 on at

Like (0)

Report

@Brandon-Pattern, this is something which is certainly difficult to manage in Power Platform. I will note that we've been trying to build some system-system or unattended/service style Flows, but I am starting to understand that Power Platform is better leveraged for user triggered / user owned / user output flows, whereas Logic Apps might be a more suitable tool for building, orchestrating and managing unattended/service workflows.

Maybe check it out as an alternative? We are still investigating but it looks like it will be a better fit for us and the Flows we have built to extend the functionality of our apps using triggered Power Automate flows.

Was this reply helpful? Yes No
Suggested answer

AK-01051611-0 4 on at

Like (0)

Report

I spent days trying to figure it out and after long hours spent, I opened MS ticket trying to get it resolved but no answer from them.

Then I just looked at the difference in API version and then I tried with the latest version and it worked like a charm

By default when you add the Edit Connection Role Assignment, it puts the API version 2016-11-01 and according to Microsoft Documentation here Use a connection reference in a solution with Microsoft Dataverse - Power Apps | Microsoft Learn the version number must be 2020-06-01. When you change the version, the problem is resolved.

-Ashar

Was this reply helpful? Yes No