Skip to main content

Notifications

Community site session details

Community site session details

Session Id : HFdF+icH5zTq+O8c9J2tmj
Power Automate - General Discussion
Unanswered

Sharing Power Automate in Developer Type Environment

Like (0) ShareShare
ReportReport
Posted on 11 Aug 2023 23:43:00 by 2

Hi community,

 

does anyone know if Power Automate can be shared in the Developer type environment?

 

I have a power automate that uses premium connector and I was not able to share the flow even turning the trial license on.

 

A message popped up said it’s disabled and stated to try this action in default. 

Is there anyway that I can share Power Automate flows in the developer type environment?

Categories:
  • PowerUserLL Profile Picture
    2 on 12 Aug 2023 at 16:10:59
    Re: Sharing Power Automate in Developer Type Environment

    Hello, thank you for answering but your answer does not address the question and issue.

     

    This is a developer environment and there are more than 1 developers that are collaborating and building flows together. The recommendation of using one service account where all developers use the same credential to sign in and do work doesn’t sound like best practices to me.

     

    However, I do agree that the service account will need to own the solution and any work that is done for organization level isn’t tied to an individual account.

     

    once again, my problem and question is that it seems like power automated cannot be shared in the developer environment.

    I am just wondering if others have experienced the same? Is this the limitation of the developer environment where power automate cannot be shared? 

    IMG_9889.jpeg

  • SamLed Profile Picture
    2,332 Moderator on 12 Aug 2023 at 07:36:10
    Re: Sharing Power Automate in Developer Type Environment

    Hi,

     

    Building flow under your identity should be only done for personal flow. If you start building for your organization you must avoid that, create a service account as flow owner. There are many benefits:

    • One owner identity for all flows, just have to share account credentials to your team.
    • Service account can have a mailbox, just give any users who will trigger the flow send permission to it if flow sends mail.
    • If you leave your organization, nothing to change (owner, mailbox, license, ..)
    • You can give extended permissions to that service account you wouldn't give to a standard user.  
    • As flows run under owner account context, you just need to purchase premium connector license for the service account 

    ______________________________________________________________

    If I have answered your question, please Accept the post as solution.
    If you like my response, please Thumbs Up.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Understanding Microsoft Agents - Introductory Session

Confused about how agents work across the Microsoft ecosystem? Register today!

Warren Belz – Community Spotlight

We are honored to recognize Warren Belz as our May 2025 Community…

Congratulations to the April Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
WarrenBelz Profile Picture

WarrenBelz 146,731 Most Valuable Professional

#2
RandyHayes Profile Picture

RandyHayes 76,287 Super User 2024 Season 1

#3
Pstork1 Profile Picture

Pstork1 66,079 Most Valuable Professional

Leaderboard
Loading started
Loading complete