Workflow-webhook not tied to user
Hello! We are developing applications in AWS (sorry, guys), and some workloads require posting to Teams channels using webhooks via Workflows (the new webhook way). We are also using webhooks to notify in Teams when Github actions finish or need interactions. However, when creating the webhook in Workflows it only seems possible to tie the webhook to a regular user. Are there any ways to use a Service Account / Service principal as the webhook/workflow owner? Using a regular user account as the webhook owner is a major drawback, eg. the need to rewrite all webhooks if the user quits the company and is disabled in Entra ID. Regards globus68Random timeouts at webhook connectors to MS Teams
In my company we are using Elastic Watcher to monitor various system indicators. These watchers are sending notifications to our MS Teams via a webhook (https://<mycompany>.webhook.office.com:443/<channel-uri>). Most the time this works perfectly, but every now and then we are getting a socket exception ("Connection Timeout" or "Connection Reset"). Teams does not respond with a HTTP error code, but this is an exception on the sending system (Elastic). The messages are far below 10 KB in size. Unfortunately I don't have any more information, so it's hard to identify the root cause. But for me this soundy like an issue on the receiver side. I appreciate any hints how to identify the cause and solve the problem.
Incoming Webhook Action Messages
I am using an incoming webhook to trigger some automated jobs (from an on-premise powershell script) and am curious that when someone clicks the action in the message card how can I find out on the action endpoint who clicked the button (it's a .net core web api receiving the action event)? Need to be able to get this so we can properly assign the tickets in our system to the person who approved or rejected the job. Would like to avoid using a text input on the card to have the person type in their user ID which is prone to failure.
MS Teams Webhook problem
Hello! We have a problem with Teams webhooks. We lost part of log when we send a webhook from Azure Data Explorer via MS Flow or from Elastic. For example: Full log - "ASA: Group <groupname> User <user> IP <ip> assigned to session". And in Teams it looks like - "ASA: Group User <user> IP <ip> assigned to session". (without <groupname>). Any solutions? Thanks! Regards, Nikita Larin.
Regarding Outgoing webhook
Hi guys, I have two questions about Teams outgoing webhook. Could you tell me about below question please? How to create outgoing webhook now? Actually, I created outgoing webhook referencing https://support.office.com/en-ie/article/create-and-add-an-outgoing-webhook-in-teams-8e1a1648-982f-4511-b342-6d8492437207 before July 2019, but I cannot find "Create an outgoing webhook" link now. Can I create outgoing webhook without limitation? Thanks Nagashio
