[ZBX-19331] Official MS Teams Zabbix Connector doesn't work Created: 2021 May 04 Updated: 2021 May 12 Resolved: 2021 May 12 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Templates (T) |
Affects Version/s: | 5.4.0beta3 |
Fix Version/s: | None |
Type: | Problem report | Priority: | Trivial |
Reporter: | Marco Hofmann | Assignee: | Vjaceslavs Bogdanovs |
Resolution: | Cannot Reproduce | Votes: | 1 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
Zabbix 5.2.6 against MS Teams Zabbix Connector |
Attachments: |
![]() ![]() ![]() |
Description |
Steps to reproduce:
Result: I tested with the PS example from Microsoft: Also see the following Forums post where other report the same problem: |
Comments |
Comment by Marco Hofmann [ 2021 May 04 ] |
Update: At the very same customer, we now deleted the Zabbix Connector and replaced it with a generic Incoming Webhook connector from Microsoft. It works instantly. So it can't be licensing or errors in the Tenant I guess. Too bad that the messages don't have the nice red Zabbix logo, now ;-( |
Comment by Vjaceslavs Bogdanovs [ 2021 May 12 ] |
Just checked the Zabbix Webhook connector and it works without any problems. The error that you are getting looks like the one you would get if the configuration of the Connector was not saved. Do you have the same "1 Configured" link at the connector list?
If not, please check you have pressed the save button at the bottom of the configuration page: |
Comment by Marco Hofmann [ 2021 May 12 ] |
I just had a TeamViewer Meeting with the customer. We installed the Teams Connector again in his channel, and this time it worked. We did a PowerShell and Zabbix Test. Both messages arrived. He swears that he also saved it the first time we tried it, because he remembers particularly, that he had deleted it, before replacing it with the generic Incoming Webhook. Anyway, we can't tell why it didn't work the first time, it works now. Sorry for the alarm. |