Unanswered

Connector created and signed in by a colleague but I can't use it

(0) Share

Report

Posted on by PitawatN

I created a cloud flow that uploads files to Azure Blob Storage. The team intended that the Azure Blob Storage connector uses Azure AD authentication (a service account that isn't in an employee's name). I shared the flow to that service account which makes it co-owner of the flow then another colleague logged to Power Automate designer with that service account, added Azure Blob Storage connector and signed in with that service account. He tested it and it worked fine.

However, when I opened the designer under my account and tested the flow, it still asks that I sign in to that Azure Blob Storage connector.

I don't have the credentials of that service account and I'm not allowed to have it. How do I continue the development from this point? Do I have to ask my colleague to sign in again from my laptop? This seems like an inefficient way to collaborate though.

One thing to note is that when my colleague created the connector, the flow was outside a solution. A few moments later I moved it into an existing solution. Not sure if this has anything to do with my issue though.

Thanks.

Categories:

Using connectors

I have the same question (0)

All responses (3)

Answers (0)

Sort by

v-jefferni Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @PitawatN ,

If it's an instant button flow, anyone who needs to use the flow requires an account with privilege of using that connection, either the user's account or the service account is OK. So, there are two options, share credential of service account to all users or give users' accounts the privilege.

Best regards,

Was this reply helpful? Yes No
PitawatN 43 on at

Like (0)

Report
Copy link

Link copied!

Hi @v-jefferni ,

Thank you for your reply.

The flow uses Power Apps trigger, does that make any difference? (User clicks on a button in Power Apps and it triggers this flow)

I mentioned that I and other users are not allowed to have the credentials of the service account, so the only option is to give users the privilege. Does this mean that I have to grant everyone read/write permissions on the Azure Storage Account? (Storage Blob Data Contributor, to be precise)

Are there other ways that app users can trigger the flow without using the above methods? How about changing the Azure Blob Storage connector authentication to service principal?

Thanks again.

Was this reply helpful? Yes No
v-jefferni Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @PitawatN ,

Workarounds I can think of:

1. uploading files to a specific folder in SharePoint library, then the owner of service account can create an Automated flow, trigger by new file created in the folder and then do everything in your current flow.

2. In PowerApps, send an Email to the service account with files as attachments. Create a flow that When new Email arrives.

However, both of above scenarios require using the service account to create flow.

Best regards,

Was this reply helpful? Yes No