Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Microsoft Teams workflows - Change to existing notification-provider #1215

Open
samotelf opened this issue Jul 15, 2024 · 3 comments
Open

Microsoft Teams workflows - Change to existing notification-provider #1215

samotelf opened this issue Jul 15, 2024 · 3 comments

Comments

@samotelf
Copy link

samotelf commented Jul 15, 2024

Description

I could not find any other issues specifically relating to Microsoft Teams Workflows.

🏷️ Feature Request Type
Change to existing notification-provider

🔖 Feature description
Microsoft are deprecating O365 connectors https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/ and asking everyone to move to workflows instead. Setting up a workflow in my Teams and then switching the webhook URL in diun to the new workflow one does not work.

✔️ Solution
An update to the Microsoft Teams notification functionality to allow users to switch to using workflow webhooks.

📝 Additional Context
New O365 connectors using the existing method will not be able to be created after August 15th 2024. Existing connectors will stop working after October 1st 2024

@romainl63
Copy link

Hi,
I'm also interested in this change planned by Microsoft.
I can get the workflow webhook to work, diun can trigger it, but I have no idea what template to use to retrieve info from Teams.

@romainl63
Copy link

I've found a way to retrieve information and send it via “Power Automate” workflows.
It works, but would need to be updated on Diun's side to have a clean template.
https://www.youtube.com/watch?v=NycgPisHj4E

@crazy-max
Copy link
Owner

Thanks for your feedback and sorry for the delay, feel free to open a PR.

cc @margaale if you have time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants