You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Microsoft is deprecating their webhooks system for Teams and they will be made unavailable in December 2025. In December 2024 they will require an URL update and if we don’t do it in time, the webhook will apparently be deleted : Retirement of Office 365 connectors within Microsoft Teams
Their new “workflows” system seems to have a new format for the JSON body in the webhook request. They appear to expect the cards to be in a “attachment” array.
The step doesn’t seem to be compatible with the new format, the Teams workflow cannot parse the JSON body (since the card is not wrapped in the “attachment” array). Will it be updated before December 2024?
The text was updated successfully, but these errors were encountered:
hi @nathansalaun-sofia , I was previously maintaining this integration while I was working at a previous org, however I no longer use MS Teams or Bitrise in my current role so unfortunately there's no guarantee I'll have time to prioritize this in my spare time.
Would gladly review/accept any PR's are willing to contribute to adding support for the new workflows though!
Microsoft is deprecating their webhooks system for Teams and they will be made unavailable in December 2025. In December 2024 they will require an URL update and if we don’t do it in time, the webhook will apparently be deleted : Retirement of Office 365 connectors within Microsoft Teams
Their new “workflows” system seems to have a new format for the JSON body in the webhook request. They appear to expect the cards to be in a “attachment” array.
The step doesn’t seem to be compatible with the new format, the Teams workflow cannot parse the JSON body (since the card is not wrapped in the “attachment” array). Will it be updated before December 2024?
The text was updated successfully, but these errors were encountered: