Zabbix Server: zabbix_server (Zabbix) 5.2.3
Linux Server: Linux XYZ 4.19.0-13-amd64 #1 SMP Debian 4.19.160-2 (2020-11-28) x86_64 GNU/Linux
OS-Release: Debian GNU/Linux 10 (buster)
Mysqld: mysqld Ver 10.3.27-MariaDB-0+deb10u1 for debian-linux-gnu on x86_64 (Debian 10)

Sorry, i screwed it up (saved and cant find the "edit" button for the reported issue). So i add the "Fix" sections here:

Here the "full" Fix that is working for me:

Files: 

• ./database/mysql/data.sql
• ./database/sqlite3/data.sql
• ./database/postgresql/data.sql
• ./database/oracle/data.sql

Modify the 

!params.teams_endpoint.startsWith(''https://outlook.office.com/webhook/'')

to

!params.teams_endpoint.includes('office.com/webhook'))

If you dont like "incldues" function for JS we could use the "indexOf".

For my setup i used "includes" and the old + new webhook URL syntax is working now!

Old Syntax: https://outlook.office.com/webhook/

"New" Syntax: https://<companyname.webhook.office.com/webhookb2/

Hello Michael,

So Microsoft Teams changed URL from https://outlook.office.com/webhook/ to https://<companyname.webhook.office.com/webhookb2/?

Available in:

• 5.0.8rc1: b0aebad8416
• 5.2.4rc1: 6f55352604d
• 5.4.0alpha1(master): be69bcefb39

Documentation updated:

• What's new in 5.0.8
• What's new in 5.2.4

I'm still running into this issue in 5.2.5. Do I need to do something more than update from the packages? 

Edit: need to make the change in the media type script. Oops. 

Hi @Tikhon,

i am really sorry, i missed to answer your question. 

We habe some URLs with the "old" syntax https://outlook.office.com/webhook/ and some with the new https//<tentant/company>.webhook.office.com/webhookb2/ , correct.
i cant "test" the fix yet, i am using my workaround. But i will update our Zabbix Server next week an come back with feedback regarding the fix: 

In the Microsoft Teams webhook, hardcoded teams_endpoint check has been removed to prevent URL syntax error.

Best regards and thank you for you help!

Just updated from zabbix-server 5.0.4 to zabbix-server 5.2.6 and this issue is still present. 

Do we need to run some manual change for this?

FYI:

The update from Microsoft is schedule to EOL "old" formats as of 2021-04-11, info from MS:

When this will happen

We will begin transitioning to the new webhook URLs on Monday January 11, 2021; however, existing webhooks URLs will continue to work for three (3) months to allow for migration time.

https://admin.microsoft.com/AdminPortal/Home?#/MessageCenter/:/messages/MC234048

Old formats are still working though, but I guess we can expect them to stop working pretty soon.

Hi everyone!

I'm not a Zabbix user but i am facing a similar problem regarding webhooks from the incoming webhook app on MS Teams. Just like Henrik said the old formats stopped working for us last week. What surprised me was that even the new links with the new format <companyname.webhook.office.com> were not working for us. Are the new links working for you guys?

Any amount of googling has not helped me find answers. So i thought id reach out to you guys even if its not strictly the same case.

Kind Regards.

vrajesh.maniraja Can you show me the error you got?

Do we need to run some manual change for this?

henrik.aronsson sure. When you update Zabbix, you don't get updates for templates and media types. Download new YAML from GIT and import it.
 

Maybe a bit of background info: We were using the webhook url on gitlab to get notifications on the teams channel when there was a push event to a project or when an issue was openend.

After we noticed the notifications were not being pushed by the webhook, we set up the url in gitlab again. This is where i got the first error to the effect of - Testing failed. False.

The error on opening the webhook url on browser was:

Invalid webhook request - GET not supported

Works out properly for us after updating the media template (we the changes according to this diff: https://git.zabbix.com/projects/ZBX/repos/zabbix/diff/templates/media/msteams/media_msteams.yaml?until=e3e211a5b903f13c47dd7dc6e275b38f4abf415b&at=refs%2Fheads%2Frelease%2F5.2

Thanks for your help!