Please remove the advertisement "(name) used Microsoft Flow to automate this notification" when using Flow to Post a Message on Teams. It is very distracting.
+1, we would like this connector to be white-label, it is distracting and unnecessary for Flow to self-promote in the messages it posts.
Would also like this when posting to channel, not just when sending message.
I don't agree with this - if a user unintentionally created a broken Flow that is now spamming teams, and you don't know where it's coming from, isn't that worse?
@Anonymous agree that would be worse, but even in the current state, there isn't direct action anyone can take - this self-promo footer doesn't include a link to the flow that created it, only the user who owns that Flow.
Maybe a link to the Flow that generated it in the footer, instead of the "(name) used Microsoft Flow to automate this notification"?
I agree that a short message providing traceability to the originating Flow would be good practice in case of 'spamming' but an advertisement to learn more about Flow is inappropriate for recipients.
I like this feature. I think it is good. and i think its furhter benificial to expose people to the flow and the possibilites. I see the downside as very minimial. Lets suppose a few people learned of flow that did not already know of it. What is bad about people learning that you use the microsoft generic workflow engine to send notifications?
But, other people in my organizatin have balked at this prominent branding by microsoft. And they see Flow as universally adjustable and so they have the expecation that this must be an option that can be turned off or taken out of the code.
+1 it looks ugly and cluttered. Looking for other alternatives at the moment, because this just adds a ton of noise. I'd be fine with a short link on the footer (near the reply/collapse area), but this is almost unusable.
To the people saying "I disagree with this" -- at the very least Microsoft could make this an opt-out setting. No need to force this functionality on everyone. We're using Flow to pass on SMS codes for Multi-Factor Authentication to a dedicated Teams channel, so the constant spamming really clutters up the channel.
To echo the thoughts of others; I'd really like to see this reviewed or better still removed.
It adds clutter and confuses users into thinking it's part of the message being communicated to them, they then go off to flow/power automate and start playing with things they arguably shouldn't (not trying to stifle creativity but the reality is I don't want to be advertising flow to employees off the back of an entirely unrelated message.).
I get that it identifies the user sending the message but either this could be done in a far more discreet way or perhaps better still the connector in flow/logic apps could allow private messages to be sent as the account the connector is running under vs a generic "Flow" account? This can be done already with several connectors and I think would be far more desirable anyway. For example, "send an email" sends the email as the account setting up the flow/connector, it doesn't send emails out as "Flow".
This could be hidden behind a + link where we can learn about the origin of the flow if we need to but as it is today it takes up too much space (as many thing in Teams do)
Approaching a year since this concern was raised. In all my use cases, Flow's self-promotion helps no one and accounts for 25% of my card space.
I have trouble imagining an organization that is a latent pool of "citizen developers" who have the interest and ability to make/maintain Flows but are just unaware of the tools available to them.
I suspect in most cases involving "the flow bot", the person who "used Power Automate" to send the notification will be irrelevant. To the recipient it will just be "someone in IT", "the automation guy in marketing", or a meaningless service account.
Furthermore, when "the flow bot" is used, it's obvious Flow was used to send the notification and no further explanation should be necessary.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.