Microsoft Teams Connector Webhooks are being replaced by Microsoft Flow

[Viajaz]

Is your feature request related to a problem? Please describe.

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 with WATCHTOWER_NOTIFICATION_URL, 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.

Describe the solution you'd like

Probably support for the new Flow/PowerAutomate webhooks, they 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

Describe alternatives you've considered

1. Microsoft Flow that can take an email and post it to a Microsoft Teams Channel
2. Microsoft Teams Channel Email
3. Custom middleware that can accept another for of media (Eg: email, generic webhook) which makes the call to the Flow webhook instead.

Additional context

containrrr/shoutrrr#446

[github-actions]

Hi there! 👋🏼 As you're new to this repo, we'd like to suggest that you read our code of conduct as well as our contribution guidelines. Thanks a bunch for opening your first issue! 🙏

[Aebian]

Just as FYI, the new webhook URL yields in:
time="2024-08-24T21:13:56+02:00" level=fatal msg="failed to create notification config: invalid webhook URL format"

I tested the alternative with the mail address on the teams channel and the implementation in Watchtower for anyone who is interested in some real alternatives and how good they work or not:

Step 01) Go to your MS TEAMS channel
Step 02) Right-Click and select "Get email address"
Step 03) Configure the desired settings, I left it at "Only members of this team" (can send emails to the channel). You then get a mail looking similiar to uuid.example.com@dk.teams.ms

Step 04) Specify notification settings, e.g.:
WATCHTOWER_NOTIFICATIONS: email
WATCHTOWER_NOTIFICATION_EMAIL_FROM: no-reply@example.com
WATCHTOWER_NOTIFICATION_EMAIL_TO: uuid.example.com@dk.teams.ms
WATCHTOWER_NOTIFICATION_EMAIL_SERVER: smtp-relay.example.com

see https://containrrr.dev/watchtower/notifications/#email for other options and more details

Step 05) Watch notifications arrive at your MS TEAMS channel:

[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.