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

O365 connectors within Teams will be deprecated and notifications from this service will stop. #1627

Open
mstfkmlbsbdk2023 opened this issue Jul 8, 2024 · 2 comments

Comments

@mstfkmlbsbdk2023
Copy link

mstfkmlbsbdk2023 commented Jul 8, 2024

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

I am using webhook url to get notification to MS Teams channel. But today I noticed that below message on the the MS Teams:

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

in order to get notification from elementary with this command edr monitor --teams-webhook <your_teams_webhook> --group-by [table | alert]. we are not able to use webhook url anymore. How to get notification from Elementary without using webhook url.

Describe the solution you'd like

MS Teams suggests something in the same action's message. It says that you can set up workflow to get notification instead of using webhook url. But There is not any documentation in elementary documentation page about how to configure workflow to get notification.

Describe alternatives you've considered
n.a

Additional context
n.a

Would you be willing to contribute this feature?
na.

@mstfkmlbsbdk2023
Copy link
Author

More than one user has encountered the same warning message. I shared it on the elementary slack channel and there are people who encountered this warning message.

@elongl
Copy link
Member

elongl commented Jul 9, 2024

Hi @mstfkmlbsbdk2023!
Thanks a lot for reporting this issue.
We'll definitely make sure to update our docs in order to include the new experience with Microsoft Teams.
For the time being, have you tried following the suggested guide from the message?
I've also found resources online for how to make the transition such as this one.
Thanks.

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

2 participants