cancel
Showing results for 
Search instead for 
Did you mean: 

Wishing the feature to be improved that could enable to modify connection name.

I have a comment on the feature regarding the connection name when creating the [connection] of  [Office 365 Outlook] along with Flow. Although I once found the account name displayed within its connection name, at this moment I am unable to recognize it due to all the connection name referred as [Office 365 Outlook]. This really causes me some troubles because I can't tell the difference between connection name and account one even if I am able to get accessed along with a different account from the previous one whish was available. Consequently,  I hope the relevant feature to be improved so as to modify or check connection name concerned.

img1.png

 

Status: Under Review
Comments
Memorable Member

I want to rename each connections to unique name for select connection.

 

Now, File System connections is same name which difference folder path, difference on-premisis data gateway, difference account.

 

1.png

 

 

 

Regards,

Yoshihiro Kawabata

Regular Visitor

This is totally needed. 100% Agreed.

Advocate II

Absolutely agree. And I've linked a related 'idea' below for anyone else interested, and to vote for both to be implemented.

 

https://powerusers.microsoft.com/t5/Flow-Ideas/Rename-actions-with-dependencies/idi-p/22407

Regular Visitor

Totally agree this is needed. for Microsoft to try and justify the flawed status quo would be absurd.

Kudo Kingpin

Any status on this?  Being unable to rename a connection for both MS Flow and PowerApps is very annoying.  

 

We have multiple connections to different environments - for instance Salesforce (a production, UAT, and development) and it is very difficult to ensure that the right one is chosen.  This is VERY annoying.

Power Automate
Status changed to: Under Review
 
Regular Visitor

Upvote!

Regular Visitor

I'd very much like to see this as well. We're using a shared flow running on a service account to create work items in Azure Devops and it's very difficult to tell which connector we have selected for any given task in Flow. (see screenshot below which includes two connectors that are configured under different accounts) Picking the wrong connection leads to issues.

 

screenshot.png

New Member

+1