Comments on: Using PowerShell to Post Channel Messages with Teams Workflows

By: Tony Redmond

Tony Redmond — Tue, 10 Sep 2024 19:26:01 +0000

In reply to Gustavo.

It depends on how your workflows function. Here’s the licensing FAQ: https://learn.microsoft.com/en-us/power-platform/admin/power-automate-licensing/faqs Probably worth a chat with your local Microsoft licensing specialist.

By: Gustavo

Gustavo — Tue, 10 Sep 2024 14:15:29 +0000

Great post. Just a quick question, if my company wants to use this, there’s some kind of extra cost if we currently have a teams suscription?

By: Tony Redmond

Tony Redmond — Mon, 15 Jul 2024 21:52:20 +0000

In reply to Jeff. Given that I don't work for Microsoft, I can't say what they might do in the future to plug what seems to be a big gap. I have asked them to comment, but these things take time and could take months before a response appears.

By: Jeff

Jeff — Mon, 15 Jul 2024 21:31:01 +0000

In reply to Tony Redmond.

Any update on this? I did find a workaround – I use the Power Automate web tool to change ‘Post As’ from Flow bot to User and that will work on a Shared Channel. The one downside is now each posted message comes from *me* as the User, not optimal.

By: Tony Redmond

Tony Redmond — Thu, 11 Jul 2024 14:35:34 +0000

In reply to Nataliia Chaika. That user account (Azure Management account) is simply a licensed utility account (Office 365) that I use to run workflows instead of tying the workflows to a user account. Hopefully, Microsoft will allow organizations to use service principals (apps) for this in future, but it's not there now.

By: Nataliia Chaika

Nataliia Chaika — Thu, 11 Jul 2024 10:47:05 +0000

hello, thanks for provided information! what kind of auto-user have you created on figure 3? how to do it? should it be created in Microsoft entra id? what kind of permissions are required?
Could you please share this info?

By: Tony Redmond

Tony Redmond — Wed, 10 Jul 2024 13:01:18 +0000

In reply to Eri. When you set up the workflow to post an item to a Teams channel, Power Automate creates a webhook (URL) for you to use.

By: Eri

Eri — Wed, 10 Jul 2024 12:52:03 +0000

In reply to Tony Redmond. Apologies if the answer is obvious (as I'm using this the first time), but where / how do I configure the webhook and use this with workflows?

By: Tony Redmond

Tony Redmond — Wed, 10 Jul 2024 03:31:49 +0000

In reply to Jeff. Let me check with Microsoft about the shared channel restriction.

By: Jeff

Jeff — Tue, 09 Jul 2024 21:35:45 +0000

One pain point in migrating is that my existing webhook connector is posting to a Shared Teams Channel. But it seems that with the workflow webhook method of doing the same thing, the Teams channel MUST be a Public channel. Anyone else have this same issue? Any possible solutions? Thanks!

By: Tony Redmond

Tony Redmond — Tue, 09 Jul 2024 20:20:48 +0000

In reply to Lars Böttcher. The only property I used with the workflow is the webhook URL. I didn't have to configure type or attachments.

By: Lars Böttcher

Lars Böttcher — Tue, 09 Jul 2024 09:41:13 +0000

To run the workflow the frist time you have to fill out the fields “type” and “attachments”. What data or information I have to set in these fields ? I can’t get the flow installed

By: Tony Redmond

Tony Redmond — Tue, 18 Jun 2024 12:35:37 +0000

In reply to Peter Holdridge.

According to some contacts in Microsoft, application users are the answer: https://learn.microsoft.com/en-us/power-platform/admin/manage-application-users?WT.mc_id=M365-MVP-9501

I have not tried this out yet.

By: Tony Redmond

Tony Redmond — Mon, 17 Jun 2024 12:20:02 +0000

In reply to Peter Holdridge. Yep, there's definitely some work to be done to make workflow automation more automated and robust than it is today.

By: Peter Holdridge

Peter Holdridge — Mon, 17 Jun 2024 10:37:24 +0000

Great work. I need to figure out how to perform automation like this that isn’t statically set on one authentication account. I need a team to be able to use it and if someone leaves, it won’t break the automation. I haven’t figured out yet how to get automation to behave like an app so that it uses the context of the team members or can perform automation without a user authentication. Over-permissioned “service accounts” is the concern and on the other hand, creating a ton of service accounts isn’t a good either.

It would be great if Microsoft created a service principal for each workflow to run autonomously and isn’t shared among automations. It would be easier to manage if Microsoft took care of the dirty details of this setup. Right now, Power Platform services are a very manual process to setup and trial and error like you said.