MS Teams webhooks: deprecated O365 webhook will break on August 15th, 2024 / October 1st, 2024 #13276

@sommerf-lf commented on GitHub (Jul 11, 2024):

to clearify:

will break at October 1st, 2024
can't create new endpoints at August 15th, 2024

@sommerf-lf commented on GitHub (Jul 11, 2024): to clearify: - will break at October 1st, 2024 - can't create new endpoints at August 15th, 2024

GiteaMirror commented

@sw2io commented on GitHub (Jul 17, 2024):

i got a same error
#31645

@sw2io commented on GitHub (Jul 17, 2024): i got a same error #31645

GiteaMirror commented

@sommerf-lf commented on GitHub (Jul 18, 2024):

Update from microsoft:

Update 07/17/2024: Due to customer feedback received around the footer message, it will be removed from the cards that are posted within Microsoft Teams.

It will still break, just not show the error warning any more

@sommerf-lf commented on GitHub (Jul 18, 2024): Update from [microsoft](https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/): > Update 07/17/2024: Due to customer feedback received around the footer message, it will be removed from the cards that are posted within Microsoft Teams. It will still break, just not show the error warning any more

GiteaMirror commented

https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/

@silverwind commented on GitHub (Jul 23, 2024):

Deprecation was extended to December 2025 with a URL change, otherwise December 2024.

@silverwind commented on GitHub (Jul 23, 2024): Deprecation was extended to December 2025 with a URL change, otherwise December 2024. https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/

GiteaMirror commented

@bbenouarets commented on GitHub (Jul 24, 2024):

If other system administrators are having difficulties locating the affected teams:
I have written a small tool in Golang that uses the Graph API to output the affected teams.

Teams Webhook Finder

This has helped us enormously, as Microsoft does not offer its own solution for reading the affected channels and teams. We have over 350 teams in our company, which we would otherwise have had to search through manually.

@bbenouarets commented on GitHub (Jul 24, 2024): If other system administrators are having difficulties locating the affected teams: I have written a small tool in Golang that uses the Graph API to output the affected teams. [Teams Webhook Finder](https://github.com/SecNex/teams-webhook-finder) This has helped us enormously, as Microsoft does not offer its own solution for reading the affected channels and teams. We have over 350 teams in our company, which we would otherwise have had to search through manually.

GiteaMirror commented

@PehDeh commented on GitHub (Jul 25, 2024):

There is also a neat Powershell Script which could list also other Connectors in Teams:
https://github.com/12Knocksinna/Office365itpros/blob/master/Report-TeamsApps.PS1
https://office365itpros.com/2024/07/10/teams-office-connectors/

Teams Webhook Finder

@PehDeh commented on GitHub (Jul 25, 2024): There is also a neat Powershell Script which could list also other Connectors in Teams: https://github.com/12Knocksinna/Office365itpros/blob/master/Report-TeamsApps.PS1 https://office365itpros.com/2024/07/10/teams-office-connectors/ > [Teams Webhook Finder](https://github.com/SecNex/teams-webhook-finder)

GiteaMirror commented

@bbenouarets commented on GitHub (Jul 25, 2024):

There is also a neat Powershell Script which could list also other Connectors in Teams:

https://github.com/12Knocksinna/Office365itpros/blob/master/Report-TeamsApps.PS1

https://office365itpros.com/2024/07/10/teams-office-connectors/

Teams Webhook Finder

That is correct. However, there are various dependencies. Modules must be installed and PowerShell is also required. With the Teams Webhook Finder, all I have is a small config and an executable file.
In addition, the cmdlets used to list the app definitions are only in preview, which does not guarantee a reliable application.

@bbenouarets commented on GitHub (Jul 25, 2024): > There is also a neat Powershell Script which could list also other Connectors in Teams: > > https://github.com/12Knocksinna/Office365itpros/blob/master/Report-TeamsApps.PS1 > > https://office365itpros.com/2024/07/10/teams-office-connectors/ > > > > > [Teams Webhook Finder](https://github.com/SecNex/teams-webhook-finder) > > That is correct. However, there are various dependencies. Modules must be installed and PowerShell is also required. With the Teams Webhook Finder, all I have is a small config and an executable file. In addition, the cmdlets used to list the app definitions are only in preview, which does not guarantee a reliable application.

GiteaMirror commented

@yp05327 commented on GitHub (Aug 13, 2024):

You can create a new webhook in workflow, and it seems that the API is the same, they just added the permission control.
https://support.microsoft.com/en-us/office/post-a-workflow-when-a-webhook-request-is-received-in-microsoft-teams-8ae491c7-0394-4861-ba59-055e33f75498

@yp05327 commented on GitHub (Aug 13, 2024): You can create a new webhook in `workflow`, and it seems that the API is the same, they just added the permission control. https://support.microsoft.com/en-us/office/post-a-workflow-when-a-webhook-request-is-received-in-microsoft-teams-8ae491c7-0394-4861-ba59-055e33f75498

GiteaMirror commented

@jordanweschler commented on GitHub (Aug 20, 2024):

The API isn't exactly the same, it seems that the new structure expects the payload to be wrapped in an array. See the following error that occurs when Workflows attempts to create a card:

ExpressionEvaluationFailed. The execution of template action 'Send_each_adaptive_card' failed: the result of the evaluation of 'foreach' expression '@triggerOutputs()?['body']?['attachments']' is of type 'Null'. The result must be a valid array.

Annoyingly, teams responds with a 202 and then fails to post the event to a channel. To see the error you need to go into Manage Workflow and view the event history.

@jordanweschler commented on GitHub (Aug 20, 2024): The API isn't exactly the same, it seems that the new structure expects the payload to be wrapped in an array. See the following error that occurs when Workflows attempts to create a card: ``` ExpressionEvaluationFailed. The execution of template action 'Send_each_adaptive_card' failed: the result of the evaluation of 'foreach' expression '@triggerOutputs()?['body']?['attachments']' is of type 'Null'. The result must be a valid array. ``` Annoyingly, teams responds with a `202` and then fails to post the event to a channel. To see the error you need to go into `Manage Workflow` and view the event history.

GiteaMirror commented

@yp05327 commented on GitHub (Aug 21, 2024):

I didn't find any documents about this new webhook api. Does MS have it?

@yp05327 commented on GitHub (Aug 21, 2024): I didn't find any documents about this new webhook api. Does MS have it?

GiteaMirror commented

@jordanweschler commented on GitHub (Aug 26, 2024):

I found this page: https://learn.microsoft.com/en-us/connectors/teams/?tabs=text1%2Cdotnet#microsoft-teams-webhook

@jordanweschler commented on GitHub (Aug 26, 2024): I found this page: https://learn.microsoft.com/en-us/connectors/teams/?tabs=text1%2Cdotnet#microsoft-teams-webhook

GiteaMirror commented

see: https://github.com/prometheus/alertmanager/issues/3920

@yp05327 commented on GitHub (Aug 27, 2024):

It is not compatibility. So it will be a bug in the future.

@yp05327 commented on GitHub (Aug 27, 2024): It is not compatibility. So it will be a `bug` in the future. see: https://github.com/prometheus/alertmanager/issues/3920

GiteaMirror commented

@thecicco commented on GitHub (Aug 29, 2024):

Hello everyone,
I was able to find a possible workaround for this problem:

All you need to do is:

create the workflow from the template: [When a Teams webhook request is received].
edit the template
delete all the steps under the action [When a Teams webhook request is received].
add the action [Initialize variable] and edit it as in the picture: PS: don't forget the type=object:
add the json that extracts the parameters coming from the webhook and converts them to: [AdaptiveCard] so that they can be printed correctly on teams

{
  "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
  "type": "AdaptiveCard",
  "msteams": {
    "width": "Full"
  },
  "body": [
    {
      "type": "TextBlock",
      "text": "@{triggerBody()?['title']}",
      "size": "ExtraLarge",
      "weight": "Bolder"
    },
    {
      "type": "FactSet",
      "facts": [
        {
          "title": "Repository:",
          "value": "@{triggerBody()?['sections'][0]['facts'][0]['value']}"
        },
        {
          "title": "@{triggerBody()?['sections'][0]['facts'][1]['name']}",
          "value": "@{triggerBody()?['sections'][0]['facts'][1]['value']}"
        },
        {
          "title": "Author:",
          "value": "@{triggerBody()?['sections'][0]['activitySubtitle']}"
        }
      ]
    }
  ],
  "actions": [
    {
      "type": "Action.OpenUrl",
      "title": "View in Gitea",
      "url": "@{triggerBody()?['potentialAction'][0]['targets'][0]['uri']}"
    }
  ]
}

add the action [Publish card in a chat or channel] and set the message of the previous action as [Adaptive Card]
after doing this save and test.

The end result will look like this:

I hope it will be useful for you,
Riccardo.

@thecicco commented on GitHub (Aug 29, 2024): Hello everyone, I was able to find a possible workaround for this problem: All you need to do is: 1) create the workflow from the template: [`When a Teams webhook request is received`]. 2) edit the template 3) delete all the steps under the action [`When a Teams webhook request is received`]. 4) add the action [`Initialize variable`] and edit it as in the picture: **PS: don't forget the type=object:** <img width="1171" alt="Screenshot 2024-08-29 alle 15 46 10" src="https://github.com/user-attachments/assets/d13ee8d6-fb1d-4840-833f-471114ff0849"> 5) add the json that extracts the parameters coming from the webhook and converts them to: [`AdaptiveCard`] so that they can be printed correctly on teams ```json { "$schema": "http://adaptivecards.io/schemas/adaptive-card.json", "type": "AdaptiveCard", "msteams": { "width": "Full" }, "body": [ { "type": "TextBlock", "text": "@{triggerBody()?['title']}", "size": "ExtraLarge", "weight": "Bolder" }, { "type": "FactSet", "facts": [ { "title": "Repository:", "value": "@{triggerBody()?['sections'][0]['facts'][0]['value']}" }, { "title": "@{triggerBody()?['sections'][0]['facts'][1]['name']}", "value": "@{triggerBody()?['sections'][0]['facts'][1]['value']}" }, { "title": "Author:", "value": "@{triggerBody()?['sections'][0]['activitySubtitle']}" } ] } ], "actions": [ { "type": "Action.OpenUrl", "title": "View in Gitea", "url": "@{triggerBody()?['potentialAction'][0]['targets'][0]['uri']}" } ] } ``` 6) add the action [Publish card in a chat or channel] and set the message of the previous action as [Adaptive Card] ![Screenshot 2024-08-29 alle 15 46 41](https://github.com/user-attachments/assets/358b149f-cb85-431e-8c7c-15a0f6f8a135) 7) after doing this save and test. The end result will look like this: <img width="777" alt="Screenshot 2024-08-29 alle 16 41 13" src="https://github.com/user-attachments/assets/f6f20da6-9633-4ce7-9977-fce5a167f7cd"> I hope it will be useful for you, Riccardo.

GiteaMirror commented