Skip to main content

Notifications

Community site session details

Community site session details

Session Id : muuAdrwJPXBL3P72A3RkqH
Power Automate - Building Flows
Suggested answer

Workflow Post to a channel when a webhook How to change the default name or owner of the workflow

Like (1) ShareShare
ReportReport
Posted on 13 Aug 2024 20:59:45 by 15
Starting to move from Microsoft Teams O365 connector to Workflow as directed by Microsoft
 
Able to get a workflow working, but the message shows up in Teams from being sent by me.  How do I change that? I tried changing the primary owner, but there is a message 'This is a non-solution flow. The owner cannot be changed' and selecting the 'Learn more' link sends me to a page full of marketing nonsense trying to sell me something.  
 
For security reasons, our system/admin level user accounts have no access to create/manage anything Azure, so it's not feasible to create a special user account when all we need is to change who 'owns' the Workflow (ideally, a team and not an individual) and what is displayed in the Teams message.
 
 
  • Mathias Langlet Profile Picture
    11 on 16 Aug 2024 at 10:54:48
    Workflow Post to a channel when a webhook How to change the default name or owner of the workflow
    Hi, I'm facing similar issues trying to migrate away from the Microsoft Teams O365 connector.
     
    > Then in the Flow, you would change the Connection on that action to be one using that service accounts details. I didnt say service principal although you could do that too.
     
    How can I run the connection using the service principal? When I try to change the connection to be run using the service principal it requires me to enter login credentials for a user.
  • Toasty Profile Picture
    15 on 14 Aug 2024 at 14:02:41
    Workflow Post to a channel when a webhook How to change the default name or owner of the workflow
    @FLMike  Thanks for the response.  After fumbling around the UI, I was able to create a solution, add the existing flow, change the owner, but the message received in Microsoft Teams still shows as being sent by me (using PostMan and no credentials, C# app+HttpClient and no credentials).
     
    Tried to change the connection (shows my email address), but it is not clear what connection I am supposed to use.
     
    It seems like the forced migration from O365 to Workflow isn't ready for 'prime time' and wonder if I should wait. I can't imagine folks with hundreds of these types O365 connectors fighting this kind of complexity with trying to post a message to Teams.  
     
    Keep it simple Microsoft...keep it simple.
     
    Thanks again for the response and if you have any advice, throw it in a reply for me and future admins+devs+grandmas+etc.
     
     
     
     
     
  • Suggested answer
    Michael E. Gernaey Profile Picture
    41,623 Super User 2025 Season 1 on 13 Aug 2024 at 23:35:21
    Workflow Post to a channel when a webhook How to change the default name or owner of the workflow
    Hi,
     
    You dont need to buy anything to put your stuff in a solution.
     
    Its literally just
     
    1) go to Power Apps
    2) Create a new solution
    3) Open it
    4) Click on the Add Existing on the menu top
    5) Select the existing flow
     
    now that its added to the flow, when you publish it is now a Solution Aware flow and can be re-homed to someone else.
     
    however, the issue is the Connector you are using. The Owner can be anyone (the flow), but what you need is a service account that you use to Send the messages so that its not you.
     
    Then in the Flow, you would change the Connection on that action to be one using that service accounts details. I didnt say service principal although you could do that too.
     
    But that's how you would change it.
     
     

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,745 Most Valuable Professional

#2
RandyHayes Profile Picture

RandyHayes 76,287 Super User 2024 Season 1

#3
Pstork1 Profile Picture

Pstork1 66,091 Most Valuable Professional

Leaderboard
Loading started