Teams: Message format about to change

[Selaron]

Teams is adding a warning to all notifications submitted via webhook:

Action Required: O365 connectors within Teams will be deprecated and notifications from this service will stop. Learn more about the timing and how the Workflows app provides a more flexible and secure experience. If you want to continue receiving these types of messages, you can use a workflow to post messages from a webhook request.

There's additional documentation on how to submit notifications to Teams: https://learn.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/connectors-using?tabs=cURL%2Ctext1

[Viajaz]

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

Starting August 15th, 2024 we will be retiring the Office 365 connectors feature from Microsoft Teams. We recommend Power Automate workflows as the solution to relay information into and out of Teams in a scalable, flexible, and secure way. We will gradually roll out this change in waves:

• Wave 1 – effective August 15th, 2024: All new Connector creation will be blocked within all clouds
• Wave 2 – effective October 1st, 2024: All connectors within all clouds will stop working

It should be noted they are already adding warnings to the bottom of every message card posted on Microsoft Teams webhooks:

Action Required: O365 connectors within Teams will be deprecated and notifications from this service will stop. Learn more about the timing and how the Workflows app provides a more flexible and secure experience. If you want to continue receiving these types of messages, you can use a workflow to post messages from a webhook request. Set up workflow.

Use of Microsoft Teams webhooks, example: teams://deadbeef-dead-beef-dead-deadbeefdeadbeefdeadb-dead-beef-dead-deadbeefdead/deadbeefdeadbeefdeadbeefdeadbeef/deadbeef-dead-beef-dead-beefdeadbeef?host=example.webhook.office.com will cease working.

The Flow webooks can accept the same MessageCard/AdaptiveCard format as the Microsoft Teams webhook when using the appropriate Post to a channel when a webhook request is received Flow Template.

An example Flow Webhook from the Post to a channel when a webhook request is received Flow Template: https://prod-03.australiasoutheast.logic.azure.com:443/workflows/ffffffffffffffffffffffffffffffff/triggers/manual/paths/invoke?api-version=2016-06-01&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=ABCdefGHIjklMNOpqrST-UvwxYZabcdefghijklmnop

Perhaps a new service (teams2:// or flow://) that just accepts a Flow webhook (Eg: teams2://prod-03.australiasoutheast.logic.azure.com:443/workflows/ffffffffffffffffffffffffffffffff/triggers/manual/paths/invoke?api-version=2016-06-01&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=ABCdefGHIjklMNOpqrST-UvwxYZabcdefghijklmnop). Presumably it could be based on teams.go and teams_config.go and made to work more like generic.go and generic_config.go but still retain the MessageCard JSON payload.

[Viajaz]

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

Update 07/23/2024: We understand and appreciate the feedback that customers have shared with us regarding the timeline provided for the migration from Office 365 connectors. We have extended the retirement timeline through December 2025 to provide ample time to migrate to another solution such as Power Automate, an app within Microsoft Teams, or Microsoft Graph. Please see below for more information about the extension:

All existing connectors within all clouds will continue to work until December 2025, however using connectors beyond December 31, 2024 will require additional action.

Connector owners will be required to update the respective URL to post by December 31st, 2024. At least 90 days prior to the December 31, 2024 deadline, we will send further guidance about making this URL update. If the URL is not updated by December 31, 2024 the connector will stop working. This is due to further service hardening updates being implemented for Office 365 connectors in alignment with Microsoft’s Secure Future Initiative

This buys us more time.

[steled]

Hi,

today I needed to update our webhook URL due to a message in our notification:

Important: You must update your Webhook URL for this connection in order for your notifications to keep posting into Microsoft Teams. Learn more about this update

I just needed to push the Update URL button and that's it, unfortunately the webhooks doesn't work anymore. After checking the new URL I saw that there is another segment in the URL:

old: https://<organization>.webhook.office.com/webhookb2/<group>@<tenant>/IncomingWebhook/<altId>/<groupOwner>

new: https://<organization>.webhook.office.com/webhookb2/<group>@<tenant>/IncomingWebhook/<altId>/<groupOwner>/<newSegment>

You have a fix for that?

[mustard123]

@steled We are having the same issue here