-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Send-Teams-adaptive-card-on-incident-creation - Teams Sender Issue #11190
Comments
Circling back on this. |
Hi @Guruleenyc, thanks for flagging this issue, we will investigate this issue and get back to you with some updates. Thanks! |
Due to the Adaptive Card shortcomings, I noted, as a workaround I shifted hears to a Playbook / Logic App using a HTTP action POST with the Teams Webhook URL.
|
Hi @Guruleenyc, which issue you are facing now ? |
Hi @Guruleenyc , we are waiting for response on above comment |
Hi @Guruleenyc , Gentle Reminder: We are waiting for your response on this issue. If you still need to keep this issue active, please respond to it in the next 2 days. If we don't receive a response by 18-10-2024 date, we will be closing this issue. |
I got the Send-Teams-adaptive-card-on-incident-creation working with the Playbook and Automation rule, BUT the Logic App is using my account to send to Teams channel. This is NO good since it depends on my account instead of a "service account", anyone in our team that interacts with the Teams channel incident post will be making incident changes on behalf of my account instead of their own, lastly, what happens in the future if my account gets disabled for any reason?
How can we have the Logic App use a managed identity or "service account" so Sentinel incidents in Teams are not bound to a single employees account?
The text was updated successfully, but these errors were encountered: